Opened 15 years ago

Last modified 13 years ago

#938 new Defect

BOINC daemon hangs when internet not available

Reported by: Raistmer Owned by: davea
Priority: Major Milestone: Undetermined
Component: Client - Daemon Version: 6.6.36
Keywords: Cc:

Description

This defect affects not only BOINC 6.6.36, I've seen it with prev BOINC versions too. Also I've seen it on different hosts under different OSes. Common part is: internet connection for host in question was provided via native windows ICF (internet connection sharing).

Surely, in such hanging state not only BOINC manager can;t communicate with daemon, science apps can't too. That is, when internet connection (not network connection!) is unavailable, BOINC's work on server completely blocked.

See this thread http://boinc.berkeley.edu/dev/forum_thread.php?id=4101 for network configuration description and more thorough description of situation in whole

Change History (3)

comment:1 Changed 15 years ago by Nicolas

Known issue, reported around four times in Trac.

comment:2 Changed 15 years ago by Raistmer

Well, maybe 5th reporting time will be lucky and get fix ? ;)

comment:3 Changed 15 years ago by Nicolas

There are two ways to fix it. One is to enable async DNS in libcurl. Apparently that causes crashes, which are not out fault, but libcurl's; so we can't fix it. It's not even clear why it crashes.

The other way is to redesign the whole client code to handle everything in different threads so that if one process hangs (like networking), the rest still work (like talking to science apps).

It's not a minor bug that can be fixed in five minutes if someone just tries.

Note: See TracTickets for help on using tickets.