BOINC client terminates running process on connection errors

Questions and Answers : Unix/Linux : BOINC client terminates running process on connection errors
Message board moderation

To post messages, you must log in.

AuthorMessage
coturnix

Send message
Joined: 1 May 02
Posts: 2
Credit: 1,555,122
RAC: 0
Germany
Message 38282 - Posted: 19 Oct 2004, 18:51:03 UTC

I am just experiencing the following problem: I have a computer which is not connected to the internet all the time, so sometimes the BOINC client tries to contact the scheduler but cannot reach it. In this case the client terminates the running process and all preempted processes. This is especially obstructive when running climateprediction.net which has a large checkpointing interval, so it is interrupted all the time. Here is an example (first connection successful, second connection causes the termination):

2004-10-19 19:38:06 [---] May run out of work in 1.00 days; requesting more
2004-10-19 19:38:06 [LHC@home] Requesting 19799 seconds of work
2004-10-19 19:38:06 [LHC@home] Sending request to scheduler: http://lhcathome-sched1.cern.ch/scheduler/cgi
2004-10-19 19:38:08 [LHC@home] Scheduler RPC to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
2004-10-19 19:38:08 [LHC@home] Message from server: No work available
2004-10-19 19:38:08 [LHC@home] No work from project
2004-10-19 19:38:08 [LHC@home] No work from project
2004-10-19 19:38:08 [LHC@home] Deferring communication with project for 1 hours, 0 minutes, and 0 seconds
2004-10-19 19:38:08 [LHC@home] Deferring communication with project for 1 hours, 0 minutes, and 0 seconds
2004-10-19 20:37:01 [SETI@home] Restarting result 04my04aa.16935.30497.1022174.66_0 using setiathome version 4.02
2004-10-19 20:37:01 [LHC@home] Pausing result v64lhc1000proseven-31s10_12582.71_1_sixvf_1928_1 (left in memory)
2004-10-19 20:38:09 [---] Insufficient work; requesting more
2004-10-19 20:38:09 [LHC@home] Requesting 21984 seconds of work
2004-10-19 20:38:09 [LHC@home] Sending request to scheduler: http://lhcathome-sched1.cern.ch/scheduler/cgi
2004-10-19 20:38:47 [---] Can't resolve hostname lhcathome-sched1.cern.ch (host not found or server failure)
2004-10-19 20:38:47 [---] Can't resolve hostname lhcathome-sched1.cern.ch (host not found or server failure)
2004-10-19 20:38:47 [LHC@home] scheduler init_op_project to http://lhcathome-sched1.cern.ch/scheduler/cgi failed, error -113
2004-10-19 20:38:47 [LHC@home] scheduler init_op_project to http://lhcathome-sched1.cern.ch/scheduler/cgi failed, error -113
2004-10-19 20:38:47 [LHC@home] init_op_project failed, error -113
2004-10-19 20:38:47 [LHC@home] init_op_project failed, error -113
2004-10-19 20:38:47 [SETI@home] Result 04my04aa.16935.30497.1022174.66_0 exited with zero status but no 'finished' file
2004-10-19 20:38:47 [SETI@home] If this happens repeatedly you may need to reset the project.
2004-10-19 20:38:47 [LHC@home] Deferring communication with project for 1 minutes and 0 seconds
2004-10-19 20:38:47 [LHC@home] Deferring communication with project for 1 minutes and 0 seconds
2004-10-19 20:38:47 [SETI@home] Restarting result 04my04aa.16935.30497.1022174.66_0 using setiathome version 4.02
ID: 38282 · Report as offensive

Questions and Answers : Unix/Linux : BOINC client terminates running process on connection errors


 
©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.