BOINC_Client dosn't start work after last downtime

Questions and Answers : Unix/Linux : BOINC_Client dosn't start work after last downtime
Message board moderation

To post messages, you must log in.

AuthorMessage
Der Schultze

Send message
Joined: 27 Jun 99
Posts: 7
Credit: 2,423,396
RAC: 0
Germany
Message 607670 - Posted: 23 Jul 2007, 14:04:19 UTC

Hello group,

after the servers were down last weekend, my BOINC_Client on Debian (etch) don't start work again.
Is there anyone who can tell me why and what i can do to start it again?

Thanks,
Michael
ID: 607670 · Report as offensive
Dotsch
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 2422
Credit: 919,393
RAC: 0
Germany
Message 607743 - Posted: 23 Jul 2007, 17:07:16 UTC

Am I right, that your system not have work ? - Could you please try to start the BOINC client with "./boinc -update_prefs http://setiathome.berkeley.edu" or do a update project via the BOINC manager.
ID: 607743 · Report as offensive
Der Schultze

Send message
Joined: 27 Jun 99
Posts: 7
Credit: 2,423,396
RAC: 0
Germany
Message 608009 - Posted: 24 Jul 2007, 6:17:33 UTC

Yes, right.

Now i have tried this:
boinc_cmd --passwd *** --project http://setiathome.berkeley.edu/ update

The finished workunits seemed to be sent to the server, but no new work arrived at my workstation.

Michael
ID: 608009 · Report as offensive
Dotsch
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 2422
Credit: 919,393
RAC: 0
Germany
Message 608013 - Posted: 24 Jul 2007, 6:26:58 UTC

I have looked at your computers stats at the website. Both Linux systems have WUs to crunch. If you have your cache set to the default setting (0.1 days), this would be OK.
ID: 608013 · Report as offensive
Der Schultze

Send message
Joined: 27 Jun 99
Posts: 7
Credit: 2,423,396
RAC: 0
Germany
Message 608018 - Posted: 24 Jul 2007, 6:47:14 UTC

Ok, now it works.

Thanks,
Michael
ID: 608018 · Report as offensive
Profile Georg Kaefer
Volunteer tester
Avatar

Send message
Joined: 19 May 99
Posts: 27
Credit: 12,035,327
RAC: 0
Austria
Message 608093 - Posted: 24 Jul 2007, 12:55:20 UTC
Last modified: 24 Jul 2007, 12:56:43 UTC

Hi all,

I struggle with same/similar problem. starting boinc brings no error, but get no new work anymore:
(tips above did not solve the problem for me)

I start my boinc with this command:
/root/downloads/seti/BOINC/run_client -no_gui_rpc -dir /root/downloads/seti/BOINC -return_results_immediately -update_prefs http://setiathome.berkeley.edu > boinc.log &

and in logfile stderrdae.txt I see:

2007-07-22 00:29:13 [SETI@home] No work from project
2007-07-22 00:30:18 [SETI@home] No work from project
2007-07-22 00:31:23 [SETI@home] No work from project
2007-07-22 00:32:58 [SETI@home] Project is down
2007-07-22 01:35:04 [SETI@home] Scheduler request failed: a timeout was reached
(...)
2007-07-22 04:19:49 [SETI@home] Scheduler list fetch failed: http error
2007-07-22 04:22:54 [SETI@home] Scheduler request failed: a timeout was reached
(...)
2007-07-22 07:45:31 [SETI@home] Scheduler list fetch failed: http error
2007-07-22 07:45:31 [SETI@home] 4 consecutive failures fetching scheduler list - deferring 604800 seconds

this would mean I'm down for 7 days. How can I solve this?
many thanks in advance
Liebe Gruesse,
Georg
ID: 608093 · Report as offensive
DJStarfox

Send message
Joined: 23 May 01
Posts: 1066
Credit: 1,226,053
RAC: 2
United States
Message 608444 - Posted: 25 Jul 2007, 13:52:49 UTC - in response to Message 608093.  

Georg:

I too have noticed the servers have been busy and trying to ration work out as best they can. Just leave BOINC running and eventually it will get more work units from the server. I received two last night, so I think you just need to be patient.

If you want to see, check the server status from the SETI main page.
http://setiathome.berkeley.edu/sah_status.html

Under Database Status, if you see "Results ready to send" with a very low number, then the chances are the servers are catching up trying to generate more work.

If you only have internet on the weekends, make sure under your preferences that you set "Computer is connected to the Internet about every" to 7 days, so it will download as much work as it can.
ID: 608444 · Report as offensive
Dotsch
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 2422
Credit: 919,393
RAC: 0
Germany
Message 608476 - Posted: 25 Jul 2007, 16:37:22 UTC

Your problems where related to the power outage at the campus in Berkeley. There was some work in the power supplies of the buildings at 22th July. Also there was some problems in the routing in Berkeley, which recovered at 23th July at 1:00 PDT. So your system could not get any work.

I recommend to set the work cache buffer to 2 or 3 days to cover such outages via the BOINC client.
Alternative join a other BOINC project, evlentualy only as backup project, is also a good idea. There are a lot of interesting projects available. Please look at this lists in the BOINC Wiki :
http://www.boinc-wiki.info/Catalog_of_BOINC_Powered_Projects
http://www.boinc-wiki.info/The_Current_List_of_Alpha_Test/Beta_Test_Projects
If you setup a backup project, you can set SETI a very high resource share (for example 1000) and your backup project a very low resource share (1). If your primary project is down or has no work, the BOINC client downloads work from the other project.
ID: 608476 · Report as offensive

Questions and Answers : Unix/Linux : BOINC_Client dosn't start work after last downtime


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.