Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Completed Research Forum: Discovering Dengue Drugs - Together - Phase 2 Forum Thread: wus erroring out tonight |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 5
|
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Except for the signature verification issue, I've had smooth sailing with DDDT-2 for quite some time now. Now I have 2 wu's that quit after about 13 minutes (ts01_b386_pqa0001 and _pqb0005), so far. Can't find any indication of the problem, just the "no state to restore" message. And since the server is still hosed I can't see if it will tell me more than I'm finding locally. Anyone else having problems like this? Normally these wu's would take over 3 hours on this host.
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Careful (with that Axe, Eugene), but long as results have not uploaded you can look into the slots and READ the stderr.txt file. Maybe something more meaningful is there.
------------------------------------------//-- Edit: Had several very short 'pr' over the last few waves... 25-35 minutes, when normally 5.25-5.75 hours. They all validated. [Edit 1 times, last edit by Former Member at Mar 3, 2011 10:33:43 AM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I tried, and no state to restore was all it said. Uploaded now.
----------------------------------------Weird, another ts01_b386 completed in 13 1/2 minutes, successfully. Not seen a lot (any?) this short. Hope the server's shared-memory issue gets resolved before my greatly-reduced-after-sig-error-problem cache is crunched; at that rate it wouldn't last long. Definitely a minor rollercoaster ride here so far this month :/ [Edit 2 times, last edit by Former Member at Mar 3, 2011 10:34:37 AM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Here's what they both said:
<core_client_version>6.10.58</core_client_version> <![CDATA[ <message> The system cannot write to the specified device. (0x1d) - exit code 29 (0x1d) </message> <stderr_txt> INFO: No state to restore. Start from the beginning. CHARGE OUTSIDE INNER GSBP REGION Encountered error. Exiting. Had no problems since. 2 other hosts are working on the 2 problematic units, will see how they do. |
||
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2977 Status: Offline Project Badges: |
I've had one of those - and I noticed that it bombed when it was attempting to write it's first checkpoint... Could be something similar...
----------------------------------------Edit : At the time, I recorded it as the second error shown in my first post within the DDDT2: WU download error: couldn't get input files: thread. I noticed it, as I'd spotted that a wingman had errored out previously, and thus, I started it there and then and watched it closely... [Edit 1 times, last edit by gb009761 at Mar 3, 2011 11:26:47 PM] |
||
|
|