Unrecoverable error (exit code 127 0x7f)
Questions and Answers :
Unix/Linux :
Unrecoverable error (exit code 127 0x7f)
Message board moderation
| Author | Message |
|---|---|
|
BonnyFused Send message Joined: 14 Jun 00 Posts: 6 Credit: 325,626 RAC: 0 
|
Hello all! My linux client is telling me following: 2005-08-22 15:01:16 [SETI@home] Starting result 27oc03aa.14269.29777.204810.233_2 using setiathome version 4.02 2005-08-22 15:01:17 [SETI@home] Unrecoverable error for result 27oc03aa.14269.29777.204810.233_2 (process exited with code 127 (0x7f)) 2005-08-22 15:01:17 [SETI@home] Unrecoverable error for result 27oc03aa.14269.29777.204810.233_2 (process exited with code 127 (0x7f)) 2005-08-22 15:01:17 [---] request_reschedule_cpus: process exited 2005-08-22 15:01:17 [SETI@home] Deferring communication with project for 59 seconds 2005-08-22 15:01:17 [SETI@home] Deferring communication with project for 59 seconds 2005-08-22 15:01:17 [SETI@home] Computation for result 27oc03aa.14269.29777.204810.233_2 finished 2005-08-22 15:01:17 [---] schedule_cpus: must schedule What's happening? Thanks. ID: 155038 ·  |
Dotsch  Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0 
|
Your stderr.txt reports followin error : setiathome_4.02_i686-pc-linux-gnu: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory It it missing the libgcc_s.so.1. Please check if it is installed, and have the read and execute rights for everyone. Can you please post the output from "ldd setiathome_4.02_i686-pc-linux-gnu". If the setiathome binary don't find your libgcc, try to "export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:PATH_TO_YOUR_LIBGCC" ID: 155201 · |
|
BonnyFused Send message Joined: 14 Jun 00 Posts: 6 Credit: 325,626 RAC: 0
|
Your stderr.txt reports followin error : This is OK, thanks. Now I get: 23/08/2005 13.30.51||Starting BOINC client version 4.43 for i686-pc-linux-gnu 23/08/2005 13.30.51||Data directory: /root/BOINC 23/08/2005 13.30.51|SETI@home|Computer ID: 1329467; location: work; project prefs: default 23/08/2005 13.30.51||General prefs: from SETI@home (last modified 2004-06-25 14:26:56) 23/08/2005 13.30.51||General prefs: no separate prefs for work; using your defaults 23/08/2005 13.30.51||Remote control allowed 23/08/2005 13.30.51||Insufficient work; requesting more 23/08/2005 13.30.51|SETI@home|Requesting 8640.00 seconds of work 23/08/2005 13.30.51|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 23/08/2005 13.30.53|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded 23/08/2005 13.30.53||schedule_cpus: must schedule 23/08/2005 13.30.54|SETI@home|Started download of 28oc03ab.6636.3650.361092.187 23/08/2005 13.30.59|SETI@home|Finished download of 28oc03ab.6636.3650.361092.187 23/08/2005 13.30.59|SETI@home|Throughput 85766 bytes/sec 23/08/2005 13.30.59||request_reschedule_cpus: files downloaded 23/08/2005 13.30.59||schedule_cpus: must schedule 23/08/2005 13.30.59|SETI@home|Starting result 28oc03ab.6636.3650.361092.187_3 using setiathome version 4.02 23/08/2005 13.31.00|SETI@home|Requesting 8640.00 seconds of work 23/08/2005 13.31.00|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 23/08/2005 13.31.03|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded 23/08/2005 13.31.03|SETI@home|Message from server: Not sending work - last RPC too recent: 11 sec 23/08/2005 13.31.03|SETI@home|No work from project 23/08/2005 13.31.03|SETI@home|Deferring communication with project for 10 minutes and 5 seconds 23/08/2005 13.31.04||Computer is overcommitted 23/08/2005 13.31.04||Nearly overcommitted. 23/08/2005 13.31.04||New work fetch policy: no work fetch allowed. 23/08/2005 13.31.04||New CPU scheduler policy: earliest deadline first. ----------- What's the meaning of the "overcommitted" stuff? Thanks again! ID: 155586 · |
|
Dotsch Send message Joined: 9 Jun 99 Posts: 2422 Credit: 919,393 RAC: 0
|
Your stderr.txt reports followin error : Your machine have to much work which cannout computed in the deadlines. Look here: http://boinc-doc.net/boinc-wiki/index.php?title=Computer_is_overcommitted Your system is now crunching setiathome ? ID: 155714 · |
©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.