When host runs with broken network (for example, network cable unplugged), boinc.exe (runned as service) begins to consume CPU (~2h of CPU time for ~10 hours w/o network).
At this situation BOINC client manager can't connect to boinc service and hangs (not just shows message like "Cant connect to core client" but exactly hangs).

____________

What BOINC version and OS?
____________
Coelum Non Animum Mutant, Qui Trans Mare Currunt

What BOINC version and OS?

What BOINC version and OS?

What BOINC version and OS?

In my case it's BOINC 5.10.45.
OSes Vista Business edition, Windows Server 2003 x64 & Win98 (I seen such behavior few times already, and when it hitted even my new quad with Vista realised that this bug should be reported).

ADDON: Science app (ovserved this on Einstein@home project app) experienced permanent restarts because of not reciving heartbeats from core client.

In your first post you mention 10 hours. Are you saying the network must be broken for about 10 hours to cause the hang?

In your first post you mention 10 hours. Are you saying the network must be broken for about 10 hours to cause the hang? I am wondering because I unplugged the cable between the host and router on 4 of my hosts and saw no problems. But I left them unplugged for only 1 to 2 hours, not 10. One of the hosts is WinXP and BOINC 5.10.45. Two are Linux and BOINC 6.2.15. The other is Linux and BOINC 5.10.45. None are service install.

In your first post you mention 10 hours. Are you saying the network must be broken for about 10 hours to cause the hang? I am wondering because I unplugged the cable between the host and router on 4 of my hosts and saw no problems. But I left them unplugged for only 1 to 2 hours, not 10.

In your first post you mention 10 hours. Are you saying the network must be broken for about 10 hours to cause the hang? I am wondering because I unplugged the cable between the host and router on 4 of my hosts and saw no problems. But I left them unplugged for only 1 to 2 hours, not 10.

Might it be possible, that these 'about 10 hours' correlate with the time, when the machine's IP lease expires? (I've occasionally had this problem too since some 2 years ago (and reported it few times), but not since last months.)

Peter

Well, maybe, although Win98 host has manually assigned IP as I recall.
Other hosts have default IP expire time, don't know how long is it for these OSes.

____________

Other hosts have default IP expire time, don't know how long is it for these OSes.

@Gundolf,

Two of the Linux machines attempted a result upload while the cable was unplugged but the manager didn't hang. Maybe it doesn't occur on Linux? The Win machine in my test did not try to use the network while cable was unplugged.

Other hosts have default IP expire time, don't know how long is it for these OSes.

The expiration delay is defined by the DHCP server, not OS-side.

Peter

Raistmer, are you sure the manager is truly hanging? I unplugged the cable on a Win XP host running BOINC 6.2.18 and waited until it attempted to upload a result. It tries the upload 3 or 4 times then gives an application modal popup saying "BOINC couldn't do Internet communication, and no default connection is selected." The manager appears to hang because clicking on it does nothing. However, if I close the popup then the manager regains control.

Raistmer, are you sure the manager is truly hanging? I unplugged the cable on a Win XP host running BOINC 6.2.18 and waited until it attempted to upload a result. It tries the upload 3 or 4 times then gives an application modal popup saying "BOINC couldn't do Internet communication, and no default connection is selected." The manager appears to hang because clicking on it does nothing. However, if I close the popup then the manager regains control.

Other hosts have default IP expire time, don't know how long is it for these OSes.

The expiration delay is defined by the DHCP server, not OS-side.

Do you really think DHCP service built in Windows is not part of OS?

Maybe I should belive after that Win is true microkernel and modular OS ?Even RTOS maybe? LoL (offtopic, of course, but... sorry :) )

I will try to reproduce this situation in more controlled environment.

Try to reproduce it with 6.2.18
I say this because 5.10 is no longer in development, no new(er) versions of 5.10 will be released.

IP lease from DHCP server[/url] (the server machine defines, for which period of time is the client machine (Windows in our case) allowed to use this IP), not about the client machine's OS' DHCP service (acting as the DHCP client).

Maybe I should belive after that Win is true microkernel and modular OS ?Even RTOS maybe? LoL (offtopic, of course, but... sorry :) )

I've no exact idea, what to compare Windows to, but sure no RTOS :-) (joke taken).

I mean that host in local network so it has local IP and this local IP was assigned by server...in "server" role plays Win2003 x64 in one case and WinXP x86 in another case. Both client (with DHCP client service) and server (with embedded into system DHCP server service) are windows :) That's what I mean :)
So all affected hosts are connected to Internet via Windows embedded NAT services and have no external IP.

Raistmer, are you sure the manager is truly hanging? I unplugged the cable on a Win XP host running BOINC 6.2.18 and waited until it attempted to upload a result. It tries the upload 3 or 4 times then gives an application modal popup saying "BOINC couldn't do Internet communication, and no default connection is selected." The manager appears to hang because clicking on it does nothing. However, if I close the popup then the manager regains control.

I didnt recive that popup.

When I kill BOINC manager process and restart it it hangs again.
The solution for that case was to stop boinc service, thaen start BOINC manager, then disable network access, then restart boinc service and manager.
So, some "hang" occurs into boinc service IMHO, not BOINC manager itself. This is supported by einstein@home app behavior - it perpetually restarts with message like no heartbeat for 30 sec. Apparently, science app can't communicate with boinc service too in that situation. And don't forget increased CPU consumption by boinc.exe process. It looks like service retry his communication attempts too often to be able to do anything else.
I will try to reproduce this situation in more controlled environment.

I agree. It's the client (what you call the service) that hangs on your machine.

Are your hosts connected with WiFi or cables?

I had to stop my attempt to reproduce the problem before 10 hours but I will try again.

P.S. After more thought... the popup is generated by the manager. Since you don't get the popup, the client is obviously hanging before it can tell the manager there is no Internet connection.

BOINC has been running on my Win XP BOINC 5.10.45 system with the network cable unplugged from the hardware router for 25 hours. No hangs, no problems.

Raistmer, have you tried turning on any of the debug options described here? Maybe try these just to see what info turns up:

<file_xfer>
<file_xfer_debug>
<http_debug>
<http_xfer_debug>
<network_status_debug>

BOINC has been running on my Win XP BOINC 5.10.45 system with the network cable unplugged from the hardware router for 25 hours. No hangs, no problems.

Raistmer, have you tried turning on any of the debug options described here? Maybe try these just to see what info turns up:

<file_xfer>
<file_xfer_debug>
<http_debug>
<http_xfer_debug>
<network_status_debug>

Well, after 28h with unplugged cable BOINC manager can connect to service.
On first try (after ~3 h) it showed popup box, on second and third attempt it just opened main window.
Hard reproducible (or nonreproducible) bug it seems.

But for 28h of running w/o network boinc.exe took 1h14min of CPU.
That is, ~4% of CPU goes to boinc service itself.
Almost every second BOINC tries to reconnect for some of results.
There is ~100 results ready to upload already (SETI produces very short tasks now). These retries take too much CPU time it seems.
Maybe it worth to check if project available once per minute (or less often), not each second?
____________

Well, after 28h with unplugged cable BOINC manager can connect to service.
On first try (after ~3 h) it showed popup box, on second and third attempt it just opened main window.
Hard reproducible (or nonreproducible) bug it seems.

But for 28h of running w/o network boinc.exe took 1h14min of CPU.
That is, ~4% of CPU goes to boinc service itself.
Almost every second BOINC tries to reconnect for some of results.
There is ~100 results ready to upload already (SETI produces very short tasks now). These retries take too much CPU time it seems.
Maybe it worth to check if project available once per minute (or less often), not each second?

In the test I did it retried once per minute, not once per second. We are both running 5.10.45 but maybe you have a different build? It might be worth trying the latest version because even if we pinpoint a bug in the source they are not going to release another 5.10.x. Your options will be to compile a fixed 5.10.45 yourself or update to 6.2.18.

When host runs with broken network (for example, network cable unplugged), boinc.exe (runned as service) begins to consume CPU (~2h of CPU time for ~10 hours w/o network).
At this situation BOINC client manager can't connect to boinc service and hangs (not just shows message like "Cant connect to core client" but exactly hangs).

When host runs with broken network (for example, network cable unplugged), boinc.exe (runned as service) begins to consume CPU (~2h of CPU time for ~10 hours w/o network).
At this situation BOINC client manager can't connect to boinc service and hangs (not just shows message like "Cant connect to core client" but exactly hangs).

There is a bug that causes a hang if network is unavailable; unrelated to the high CPU usage.

it happens to me too... I have 4 cores, and they run at night... and in the morning, screensaver says Boinc is loading and then one pop up says no network availabe and manager hangs and closes... I will try it crunching with 3 cores to see if it works..