Questions and Answers :
Unix/Linux :
Constantly restarting Work units
Message board moderation
Author | Message |
---|---|
Phil Savoie Send message Joined: 21 Feb 00 Posts: 6 Credit: 3,842,073 RAC: 0 ![]() |
Hi All, First thanks for the good advice on my previous post as my intel Solaris 10 box is happily chugging away. Next question is why on a sparc 5 running Solaris 9 is this happening? 2006-05-04 19:04:34 [SETI@home] Restarting result 21fe99ab.20616.26513.686074.1.125_3 using setiathome version 4.02 2006-05-04 19:04:35 [SETI@home] Result 21fe99ab.20616.26513.686074.1.125_3 exited with zero status but no 'finished' file 2006-05-04 19:04:35 [SETI@home] If this happens repeatedly you may need to reset the project. 2006-05-04 19:04:35 [---] request_reschedule_cpus: process exited 2006-05-04 19:04:35 [---] schedule_cpus: must schedule 2006-05-04 19:04:35 [---] earliest deadline: 1147992197.000000 21fe99ab.20616.26513.686074.1.125_3 I keep getting this repeatedly over and over. Any info would be great as to why, please. Thanks in advance, Phil |
Dotsch ![]() Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0 ![]() |
It is a known problem in the older version 4 boinc clients. The boinc client sometimes did not get any status informations from the seti app. If it happens not to often, it is not problematic. If it happens permanently, it is problematic. How often did it occour ? Which boinc client do you use ? Can you please post the $BOINCDIR/projects/setiathome.berkeley.edu/stderr.txt. |
©2025 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.