Questions and Answers :
Unix/Linux :
Scheduler req...failed: system fopen
Message board moderation
Author | Message |
---|---|
W. T. Fudoki Wilkinson Send message Joined: 6 Dec 05 Posts: 7 Credit: 610,345 RAC: 0 |
Yesterday I noticed four work units on one of my P-4 SUSE 10.0, 2.6.15-7 boxen that all claimed "Computational error" as their status in Boinc 5.2.13 I suspended the session because I was doind some installation on that box. This AM when I unsuspended Boinc/SETI, those work units now say "Ready to Report", but two show no CPU time, the other two 100% CPU time. The computer is newly built, with a P-4 2.6GHz on an Asus P4P800-VM w/ 512 Mb interleaved&tiled SDRAM and an i865G chipset. The box has successfully completed almost 100 credits of previous work in the past week of it's new life. Any ideas? I'm 1 mystified geek. fudoki |
Dotsch Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0 |
Yesterday I noticed four work units on one of my P-4 SUSE 10.0, 2.6.15-7 boxen that all claimed "Computational error" as their status in Boinc 5.2.13 This with 100% are computed OK. The other are aborted or has some problems. You have not uploaded it in the moment ? - I did not see it in the stats of your computers. You can try to upload it. If they are uploaded the errors from the seti app will also be accessable via the WU details. You can also see this error files in the slots/$NUM/stderr.txt. Can you please post the output from all your stderr.txt files.
Your stderr.txt will give some more hints about the problem.... But could be that it is a hardware problem. For example bad memory. |
©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.