Run Times forcms_GA[e30-50MB_Lin65f] tasks

[mxplm]

It wasn't the BOINC client which exited with status 11, cmsearch reported that exit code when it terminated. The link you posted describes a BOINC client error due to a segfault.

[mxplm]

UPDATE:

I just noticed that the two long runners are still running! BOINC doesn't know anything about them, so it's the same problem I described earlier (German).

Code: Alles auswählen

$ ps -fu boinc
UID        PID  PPID  C STIME TTY          TIME CMD
boinc     1102     1  0 Feb13 ?        00:41:57 /usr/bin/boinc --check_all_logins --redirectio --dir /var/lib/boinc-client
boinc    13286  1102  0 09:29 ?        00:00:14 ../../projects/www.rnaworld.de_rnaworld/cmcwrapper_0.22_x86_64-pc-linux-gnu
boinc    13305 13286  8 09:29 ?        00:41:50 cmcalibrate --mxsize 4096 -s 1246654610 cmfile
boinc    14653  1102  0 16:00 ?        00:00:02 ../../projects/wuprop.boinc-af.org/data_collect_2.40_x86_64-pc-linux-gnu__nci
boinc    15389  1102  0 17:29 ?        00:00:00 ../../projects/www.rnaworld.de_rnaworld/cmswrapper_0.20_x86_64-pc-linux-gnu
boinc    15399 15389 84 17:29 ?        00:06:13 cmsearch -o out cmfile in
boinc    20350     1 99 Feb20 ?        9-18:01:24 cmsearch -o out cmfile in
boinc    20860     1 99 Feb20 ?        9-17:49:44 cmsearch -o out cmfile in

[Michael H.W. Weber]

..this is the english subforum.

Michael.

[mxplm]

Translated ;)

[coturnix]

Exit status 11 is most likely an indicator for insufficient memory. I had this once when two tasks had their memory peak at the very same time.

Tilman

[mxplm]

In that case, the processes would have terminated with exit code 11 I think. In my case, BOINC (or the wrapper?) just reported the application had exited with code 11 while they were really still running (even a day after BOINC reported them as errored out). Also, the "memory recording script" on my host for those two processes didn't report any kind of memory peak.