Ticket #707 (new Defect)

Opened 1 year ago

Last modified 3 months ago

detect network availability

Reported by: Dagorath Assigned to: davea
Priority: Major Milestone: Undetermined
Component: Client - Daemon Version: 6.6.37
Keywords: Cc: mjakubicek

Description (Last modified by Nicolas)

This issue was brought up in this thread. Summarising, the user starts BOINC client as a daemon during boot on a Fedora 9 system that apparently brings up the network rather slowly. When BOINC client starts it finds no network available. Putting a 15 second delay in the system startup scripts to delay starting the BOINC daemon fixed the problem for the user.

I imagine BOINC client, when it starts, checks if the network is available before proceeding. Perhaps the OS (Fedora 9) is reporting incorrectly? Perhaps the OS reports correctly but BOINC times out too quickly?

Change History

08/01/08 15:44:47 changed by Nicolas

  • status changed from new to closed.
  • resolution set to worksforme.

Already possible. Set <start_delay> in cc_config.xml

08/02/08 15:49:05 changed by Dagorath

  • priority changed from Undetermined to Major.
  • resolution deleted.
  • status changed from closed to reopened.
  • component changed from Undetermined to Client - Daemon.
  • version set to 6.2.14.

Setting <start_delay> in cc_config.xml delays starting science apps which is not the preferred solution.

08/02/08 16:10:25 changed by Nicolas

Sorry, my misunderstanding. I thought start_delay made the client do absolutely nothing until the delay finished.

<start_delay> only delays the client starting science apps. You want to limit the client accessing the network. So, good to reopen ticket :)

08/02/08 16:21:47 changed by mjakubicek

  • milestone changed from Undetermined to 6.4.

In my point of view the problem cannot be solved by waiting on startup: the real trouble is that BOINC cannot use any networks newly available after its startup. This regards not only slow DHCP responses but mainly wireless connections or any connections which indeed come up when BOINC is already running.

From what I know this should be solved in BOINC 6.4 by the asynchronous GUI RPC. I truly do not understand how GUI (!) RPC connections are related to this (isn't it a problem in the client itself?), but I hope I'm just wrong in this and it will be solved soon.

08/02/08 21:52:48 changed by Nicolas

The new asynchronous GUI RPCs won't stop the client from attempting network access during startup. They will stop the GUI from hanging while the client is busy, for example, trying to access the network.

08/03/08 14:55:35 changed by Nicolas

  • description changed.

fixed link to forum thread in ticket description.

01/15/09 06:42:06 changed by mjakubicek

  • cc set to mjakubicek.

02/25/09 13:46:32 changed by romw

  • owner set to davea.
  • status changed from reopened to new.
  • milestone changed from 6.6 to Undetermined.

07/19/09 09:08:59 changed by mjakubicek

  • version changed from 6.2.14 to 6.6.37.
  • summary changed from Wait for slow network startup to detect network availability.

This is actually a general problem, boinc should be able to detect network availability if the user e.g. switches network, moves with the laptop etc.

07/25/09 15:24:34 changed by mjakubicek

Hm...I've done some testing on this again on behalf of a Fedora user request and this seems to be fixed. What has changed? I was searching the changeset for "network" and there are only two of them that seem to be related according to the svn commit message, either [13295] or even [12665], but those are so so old that I can't believe it took more than two year to make it into current branch for them.

So either I screwed up the testing (probably) or it has been indeed fixed meanwhile (somewhere)...could anyone please retest this? Thanks a lot.

(follow-up: ↓ 12 ) 07/28/09 01:49:25 changed by kamil.paral

This is not fixed, in Boinc Manager 6.4.7 on Fedora 11 it is still not able to connect to network without restarting the daemon. It is quite annoying, could somebody fix it please?

(in reply to: ↑ 11 ) 07/28/09 08:51:18 changed by mjakubicek

Replying to kamil.paral:

This is not fixed, in Boinc Manager 6.4.7 on Fedora 11 it is still not able to connect to network without restarting the daemon. It is quite annoying, could somebody fix it please?

I should have emphasized it more than by setting the "version" of this ticket, sorry: the version I was speaking about is 6.6.37 of course, please retest with this version. For Fedora it's currently available in the updates-testing repositories. You can download and provide feedback here:

Fedora 10: https://admin.fedoraproject.org/updates/F10/FEDORA-2009-7973
Fedora 11: https://admin.fedoraproject.org/updates/F11/FEDORA-2009-7940

07/28/09 09:16:25 changed by kamil.paral

Unfortunately I will not be able to test it for a week, I'm leaving for holiday. If it is then still in testing repo, I will surely test it.

08/05/09 07:43:10 changed by kamil.paral

It seems to be fixed from the first glance.

08/10/09 04:07:05 changed by kamil.paral

I believe it is fixed, thanks.

If this page is incomplete or incorrect, please edit it or add it to the wiki to-do list. To do this, you must be logged in; click Login or Register above.