WU's error out when resumed from suspend or system restarted

Mersenneplustwo home page
log in

Advanced search

Message boards : Number crunching : WU's error out when resumed from suspend or system restarted

Author Message
Tex1954
Send message
Joined: 18 Mar 13
Posts: 9
Credit: 1,824,441
RAC: 0
Message 198 - Posted: 29 Apr 2014, 22:35:11 UTC
Last modified: 29 Apr 2014, 22:36:43 UTC

Like the title says, if you suspend the tasks and then restart them, they all fail. One may need to do this from time to time for updates or adjustments to BIOS etc...

Even if you don't stop the system and keep the programs in memory, a resume causes them to fail.

8-)

<core_client_version>7.2.42</core_client_version>
<![CDATA[
<message>
process got signal 11
</message>
<stderr_txt>
APP: wep: argv[0] is ../../projects/bearnol.is-a-geek.com_wanless2/wep_1.13_x86_64-pc-linux-gnu
APP: wep: starting, argc 1
No heartbeat from core client for 30 sec - exiting
SIGABRT: abort called

</stderr_txt>
]]>


Post to thread

Message boards : Number crunching : WU's error out when resumed from suspend or system restarted


Return to WEP-M+2 Project main page


Copyright © 2019 M+2 Group