Hide Forgot
Description of problem: gnome-panel/clock-applet/libgweather is not closing libsoup HTTP connections after request/response. Connections then time out to CLOSE_WAIT. Connection tracking clears down the connection so any later FIN/FIN+ACK packets show up as "invalid" tracking state. My firewall drops the invalid packets so they get sent 10 times... Just adds more dross to syslog. Version-Release number of selected component (if applicable): kernel-2.6.35.13-92.fc14.x86_64 gnome-panel-2.32.0.2-2.fc14.x86_64 libgweather-2.30.3-1.fc14.x86_64 libsoup-2.32.2-1.fc14.x86_64 How reproducible: Normal Gnome session with weather enabled in clock-applet. Steps to Reproduce: 1. Gnome desktop, clock-applet->preferences. Show weather, Show temperature, set location. 2. Wait a few minutes. 3. Check network connections (e.g. `lsof -i -n -P`) and syslog (e.g. `tail /var/log/messages`). Actual results: clock-app 7689 daveg 24u IPv4 3572762 0t0 TCP 192.168.x.y:36387->88.221.84.43:80 (CLOSE_WAIT) clock-app 7689 daveg 25u IPv4 3573242 0t0 TCP 192.168.x.y:36388->88.221.84.43:80 (CLOSE_WAIT) clock-app 7689 daveg 26u IPv4 3573384 0t0 TCP 192.168.x.y:36390->88.221.84.43:80 (CLOSE_WAIT) Plus _many_ messages like: Jul 4 12:31:14 host kernel: FW:Drop Invalid IN= OUT=br0 SRC=192.168.x.y DST=88.221.84.43 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=28250 DF PROTO=TCP SPT=57551 DPT=80 WINDOW=168 RES=0x00 ACK PSH FIN URGP=0 Expected results: No lingering connections - request, response, close is all that's needed. Additional info: May be more directly related to libgweather and it's use of libsoup, but I see the problem coming from clock-applet.
Looks like this issue was related to libproxy and firewall rules to accommodate direct connections - once that was fixed, this problem goes away (or moves to the proxy, still testing). Ref: bug#653110 <https://bugzilla.redhat.com/show_bug.cgi?id=653110> --DaveG.
No further issues on the client or proxy server since setting up libproxy configuration correctly. Still see the occasional CLOSE_WAIT but they are likely to be random network noise. I can live with that. Please consider the issue CLOSED. --DaveG.