Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 11
Posts: 11   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1599 times and has 10 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Many TCP connections remaining in CLOSE_WAIT state eventually stopping communications

I see a lot (and I mean A LOT) of TCP connections from the boinc.exe process to the HTTP proxy server that remain in CLOSE_WAIT state. Eventually, this depletes the stock of IP sockets and no further communication is possible.
Is this a bug in boinc?
Thanks for suggesting a solution,
Jantje.
[Nov 16, 2009 1:28:35 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Many TCP connections remaining in CLOSE_WAIT state eventually stopping communications

Hello jantje,
This is a new observation - at least to me. Perhaps it has already been reported for other BOINC projects. But since you are making the first report on WCG, you had better give us complete information.

What OS, BOINC version, security software, type of proxy and connection to Internet, etc? Perhaps you should include a listing from the Messages tab of BOINC after a reboot since that contains a lot of information and saves you from typing.

Lawrence
[Nov 16, 2009 2:02:10 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Many TCP connections remaining in CLOSE_WAIT state eventually stopping communications

Well... here goes...


netstat -b

Active Connections

Proto Local Address Foreign Address State PID
netstat -b

Active Connections

Proto Local Address Foreign Address State PID
...
TCP mycomputer:1816 proxyserver:8080 CLOSE_WAIT 5048
[boinc.exe]

TCP mycomputer:1818 proxyserver:8080 CLOSE_WAIT 5048
[boinc.exe]

TCP mycomputer:2348 proxyserver:8080 CLOSE_WAIT 5048
[boinc.exe]

TCP mycomputer:2356 proxyserver:8080 CLOSE_WAIT 5048
[boinc.exe]

TCP mycomputer:2357 proxyserver:8080 CLOSE_WAIT 5048
[boinc.exe]
... snip ...


Windows XP SP 2 and current with security fixes.
Corporate proxy server (I forgot the make... Blue something?...), Proxy settings have been entered correctly.
Symantec Client Firewall 8.7.4.79 protecting and monitoring connections. But not showing any problem in its log.


Messages:

18/11/2009 09:10:49||Starting BOINC client version 6.2.28 for windows_intelx86
18/11/2009 09:10:49||log flags: task, file_xfer, sched_ops
18/11/2009 09:10:50||Libraries: libcurl/7.19.0 OpenSSL/0.9.8i zlib/1.2.3
18/11/2009 09:10:50||Data directory: C:\Documents and Settings\All Users\Application Data\BOINC
18/11/2009 09:10:50||Running under account myaccount
18/11/2009 09:10:51||Processor: 1 GenuineIntel Intel(R) Pentium(R) M processor 1.86GHz [x86 Family 6 Model 13 Stepping 8]
18/11/2009 09:10:51||Processor features: fpu tsc pae nx sse sse2 mmx
18/11/2009 09:10:51||OS: Microsoft Windows XP: Professional x86 Editon, Service Pack 2, (05.01.2600.00)
18/11/2009 09:10:51||Memory: 2.00 GB physical, 4.84 GB virtual
18/11/2009 09:10:51||Disk: 37.25 GB total, 4.60 GB free
18/11/2009 09:10:51||Local time is UTC +1 hours
18/11/2009 09:10:52|World Community Grid|URL: http://www.worldcommunitygrid.org/; Computer ID: 632505; location: (none); project prefs: default
18/11/2009 09:10:52||General prefs: from World Community Grid (last modified 18-Jun-2008 13:10:54)
18/11/2009 09:10:52||Host location: none
18/11/2009 09:10:52||General prefs: using your defaults
18/11/2009 09:10:52||Reading preferences override file
18/11/2009 09:10:52||Preferences limit memory usage when active to 1023.21MB
18/11/2009 09:10:52||Preferences limit memory usage when idle to 1534.81MB
18/11/2009 09:10:52||Preferences limit disk usage to 1.81GB
18/11/2009 09:13:02|World Community Grid|Restarting task mx762_00012_18 using hpf2 version 603
... snip ...


Cheers,
Jantje.
----------------------------------------
[Edit 1 times, last edit by Former Member at Nov 20, 2009 12:02:18 PM]
[Nov 19, 2009 9:32:13 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Many TCP connections remaining in CLOSE_WAIT state eventually stopping communications

Hi Jantje via Nagano (that's what your IP tells me, thus better edit that out of your post)

Not a first time for me reading this and suspicions. AV & Firewall need a few traffic ekseptions for the BOINC processes over localhost IP. But first start setting some quick local preferences

1. Bevestiging bij het openen van de internet verbinding
2. Verbinding verbreken indien gereed.

(Presuming you read dutch of course)

The killer test is pulling the ethernet cable, which might even lead to science crashing in some reported cases. Normally though BOINC only communicates constantly over 127.0.0.1 and or periodically over the LAN IP assigned to the device. I see mine with netstat -b listed twice in association with BOINC.exe but with high local ports, not the internet 80 [8080] port.

Let us know. Can't help you with Symantec (Norton I think) to find the right fields to set the exclusions.

PS: What is the network option "Verbind elke xx dagen" set at? If very small or 0.00 for your testing set it to 0.1 days.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
----------------------------------------
[Edit 1 times, last edit by Sekerob at Nov 19, 2009 10:19:19 AM]
[Nov 19, 2009 10:15:00 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Many TCP connections remaining in CLOSE_WAIT state eventually stopping communications

Well, I do read (and speak) Dutch...

Not sure I like the option to confirm before connecting. What if my machine is running through the weekend and then needs to connect? It will have to wait for me to arrive on Monday morning...

According to the help, the disconnect when done option only applies to dial-up connections. My internet connection is permanent...

The "Connect about every" is set to 0.2

You say that BOINC normally only communicates over loopback address. But that will not give it access to the grid servers... To get work in and out, surely it needs to communicate with the internet over a LAN address.

Maybe you want to elaborate on that?

Thanks,

Jantje.
[Nov 20, 2009 12:13:50 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Many TCP connections remaining in CLOSE_WAIT state eventually stopping communications

Hello jantje,
https://secure.worldcommunitygrid.org/help/viewTopic.do?shortName=netconn says:
What ports do I have to open on my firewall to let the software connect to the server?
Open ports 80, 443 and 31416 outbound.

The loopback is used to communicate between BOINC Manager, boinc.exe and the science application on your computer.

Lawrence
[Nov 20, 2009 1:10:06 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Many TCP connections remaining in CLOSE_WAIT state eventually stopping communications

BOINC=Voodoo to most and many, including me, so often I'll take the trial/error approach diagnosing cause and effect and this is one of them bugs. If it is what I suspect, it's been a long standing bug, some being hit by it, some not. In instances loosing Intranet/Internet connection causing the sciences to crash.

Yes of course your client needs scheduled contact with the servers, but not constants, so changing options and yanking the Lan cable I'm hoping that something pops up on your screen or something else BOINC related acts up.

- Does the Activity (Prestaties) menu setting say to crunch and network according preferences (voorkeuren)? If not set that and observe.

Supposedly fixed in the new client, maybe try 6.6.38 or 6.10.18 if no resolution is found.

Oh, can't remember how to see from your log if BOINC is installed as service/daemon or as user application. The newer clients make that quite clear by printing:

20-11-2009 0:13:10 Running as a daemon
20-11-2009 0:13:10 Data directory: C:\ProgramData\BOINC
20-11-2009 0:13:10 Running under account boinc_master

Service is better. Does not require for the BOINC manager to run first before the core client is loaded.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Nov 20, 2009 1:11:10 PM]   Link   Report threatening or abusive post: please login first  Go to top 
sk..
Master Cruncher
http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif
Joined: Mar 22, 2007
Post Count: 2324
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Many TCP connections remaining in CLOSE_WAIT state eventually stopping communications

jantje, assuming this is not a case of the network card shutting down to save energy, ie a power option issue, the problem could well be a router issue.

On many routers you can limit the number of active connections, and perhaps Boinc/XP is not closing them. Once that limit is reached, the router will not let you connect to another system. On a large network, Internet usage is a major concern and Engineers have to take action to prevent unnecessary use, such as leaving web pages open that continuously download adverts, and use up the bandwidth.

Another possibility is that you are denied Network or Internet access during the weekend, either on a router or a server - user account access is limited to normal work hours only (say 8am to 6pm M-F). This is a common security setup used to stop hackers gaining access to corporate systems, at least out of hours!

Another possibility is that the router/firewall on your company network now thinks your laptop is sending odd requests too frequently and has started to actively block them. Perhaps a security software update caused this to kick in recently.

I am of course assuming you leave your laptop on at work, and dont take it home? If you do take it home then you will need to change the proxy settings - as you would no longer be connecting to the Internet through your works proxy server!
If you do leave it at work I would suggest you have your task cache set to 3 days:

From the menu bar,
Advanced, network usage, Additional work buffer – set to 3.0 days, and click OK.
[Nov 21, 2009 2:07:15 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Many TCP connections remaining in CLOSE_WAIT state eventually stopping communications

Well, it is not a laptop, so it remains indeed at the office. I don't know about router and firewall settings, except for that they are indeed very restrictive.
I'll try to increase the amount of work fetched and the interval between connections. See what gives.
Thank you all for the suggestions.

BTW. Is it indeed a good idea to go for a newer BOINC than what WorldCommunityGrid recommends?
Thanks
[Nov 24, 2009 10:30:22 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Many TCP connections remaining in CLOSE_WAIT state eventually stopping communications

Not really. Wait a bit as WCG is scheduled to have a client upgrade by maybe Jan-10. Testing is still ongoing and a WCG Beta will be announced.

Still if you have the opportunity to pull the network cable you'd be able to find out if BOINC continues to run and or a message showing such as "need an internet connection". Set in Options, Verbindingen, Netwerk Herinnerings Interval to 120 minutes. There's no reason whatsoever for the client to go outside the computer on a perpetual basis.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Nov 24, 2009 10:39:31 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 11   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread