Boinc Error Codes
15 May 07Posts: 54 Message 13055 - Posted: 13 Oct 2007, 19:18:15 UTC Unrecoverable error for result two2_412_peptidsm.7879_0 (process exited with code 24 (0x18, -232)) I've tried to look for it but havent found it, has anyone encountered this error?ID: 13055 · NicolasSendmessage Joined: 19 Jan 07Posts: 1174 Message 13056 - Posted: 13 Oct 2007, 19:26:08 UTC - in response to Message 13055. Unrecoverable error for result two2_412_peptidsm.7879_0 (process exited with code 24 (0x18, -232)) I've tried to look for it but havent found it, has anyone encountered this error? Seems to be an application-specific problem. Report it on the project forum (btw: you didn't say what project it was).ID: 13056 · AgelessVolunteer moderatorProject administratorHelp desk expertSendmessage Joined: 29 Aug 05Posts: 11090 Message 13057 - Posted: 13 Oct 2007, 20:30:48 UTC And just so you know for a next time, BOINC errors are always negative and in the range of -100 to -224. Application errors are usually positive, although there are negative ones as well, but then the number is very big. Exit code -1073741502 (0xC0000142) -> Application error Exit code 10 -> Application error Exit code -119 -> BOINC error ____________ Jord Ha ha ha ha ha! You can't fool me! There ain't no Sanity Clause!ID: 13057 · daggSendmessage Joined: 15 May 07Posts: 54 Message 13058 - Posted: 13 Oct 2007, 20:38:29 UTC it's QMC I've allready reported it, they dont know what is the cause, I'm trying to see if I can findout what is the cause, it's a problem with 32bit uw sent to 64 bit cpusID: 13058 · NicolasSendmessage Joined: 19 Jan 07Posts: 1174 Message 13059 - Posted: 13 Oct 2007, 20:44:55 UTC - in response to Message 13058. I can findout what is the cause, it's a problem with 32bit uw sent to 64 bit cpus Are you on Linux?ID: 13059 · AgelessVolunteer moderatorProject administratorHelp desk expertSendmessage Joined: 29 Aug 05Posts: 11090 Message 13060 - Posted: 13 Oct 2007, 20:44:56 UTC Is that a BOINC version higher than 5.8 that you are using? Should be 5.9+ And do know in case this is on Linux: "Note that 32-bit binaries don't just work on every 64
Available in: Created: 18/06/2008 16:40:23 Last Modified: 11/07/2012 10:41:18 Contents: Yes, positive error codes, to make things interesting. :-) The following are process exit codes (not function return values). They are used by the client and applications. NOTE: Unix passes only 8 bits of exit code, and Unix uses roughly 1-137, so BOINC errors start at 192. EXIT_STATEFILE_WRITE 192 The client will exit if it cannot write to the client_state.xml file. Make sure you have permission to write to the BOINC Data https://boinc.berkeley.edu/dev/forum_thread.php?id=2198 directory. EXIT_SIGNAL 193 The client, Manager and/or application will exit when getting the exit signal. EXIT_ABORTED_BY_CLIENT 194 Task was aborted by the BOINC client. EXIT_CHILD_FAILED 195 The science application running the task failed for unknown reasons. EXIT_DISK_LIMIT_EXCEEDED 196 The amount of disk space that the task could use was more than the limit set to the task. EXIT_TIME_LIMIT_EXCEEDED 197 The amount of time that http://boincfaq.mundayweb.com/index.php?viewCat=3 the task can run was estimated to be far greater than then time limit set to the task. EXIT_MEM_LIMIT_EXCEEDED 198 The amount of memory that the task could use was greater than the limit set to the task. EXIT_CLIENT_EXITING 199 The task was ended when the client was exited. EXIT_UNSTARTED_LATE 200 Task was aborted due to it having not started and already past the deadline. EXIT_MISSING_COPROC 201 A coprocessor that was detected earlier went missing. Work for it is being aborted. EXIT_ABORTED_BY_PROJECT 202 Tasks on the computer were aborted by the project. EXIT_ABORTED_VIA_GUI 203 Applications exit with this code after you told them to abort. EXIT_UNKNOWN 204 Unknown exit. 01. Error code -100 to -110 explained. FAQ: 01. Error code -100 to -110 explained. Title: 01. Error code -100 to -110 explained. Author: Jorden Views: 213532 Category: 06. BOINC Client Common Errors Available in: Created: 14/02/2008 23:20:15 Last Modified: 27/12/2010 17:21:53 Contents: BOINC_SUCCESS 0 Not an error, but a good thing. Success. Everything is working as it should. Rejoice. ERR_SELECT -100 This error code is no longer used in any of the present versions of BOINC. ERR_MALLOC -101 T
recent post firstMost recent post firstHighest rated posts first https://boinc.bakerlab.org/rosetta/forum_thread.php?id=1233&sort=5 AuthorMessage Thiery Send message Joined: Mar 9 06Posts: 2ID: 64514Credit: 4,928RAC: 0 Message 12005 - Posted 14 Mar 2006 7:24:32 UTC I\'m using Rosetta for a few days, and, at least once a day, I\'m having the : \"Unrecoverable error for result (...) exit code -164 (0xffffff5c)\" According to the FAQ, I\'m not alone, but can\'t see any solution boinc error given here, except if bad WE was sent (wait for a new one), but as new WUs come, fatal error still happend. I had once a general failure (seems that video card was not in sync any more) and needed to reset computer, with loss of data of course. A few error messages below : 12/03/2006 16:35:38|rosetta@home|Unrecoverable error boinc error codes for result HOMSti_homDB015_1tif__352_1687_0 ( - exit code -1073741811 (0xc000000d)) 12/03/2006 16:35:45|rosetta@home|Unrecoverable error for result HOMSog_homDB011_1ogw__352_1867_0 ( - exit code -1073741811 (0xc000000d)) 12/03/2006 22:50:14|rosetta@home|Unrecoverable error for result HOMSmk_homDB019_1mkyA_352_1794_1 ( - exit code -164 (0xffffff5c)) 13/03/2006 16:39:40|rosetta@home|Unrecoverable error for result FA_RLXac_hom026_1acf__359_97_0 ( - exit code -164 (0xffffff5c)) 14/03/2006 07:36:32|rosetta@home|Unrecoverable error for result FA_RLXbg_hom008_1bgf__359_211_0 ( - exit code -1073741811 (0xc000000d)) I\'m suspending the use of rosetta for the moment, as SETI is running fine, I don\'t imagine a hardware failure, nor a computer malfunction. Computer : MoBo Asus P4P800, Pentium 4 3GHz, RAM 512, Windows XP pro SP2 fully updated. Thanks in advance for any solutions you coul\'d give to me. Thierry ____________ ID: 12005 | Rating: 0 | rate: / Reply Feet1st Send message Joined: Dec 30 05Posts: 1740ID: 44890Credit: 2,098,679RAC: 551 Message 12071 - Posted 15 Mar 2006 21:19:46 UTC The suggestion is the allow the application to remain in memory. This is one of the \"general\" preferences, and is called \"Leave applications in memory while preempted?\". So the suggestion is to set it to