I ran into one of those 'stuck' abrelax wu's overnite:
resid 144202
running ralph 5.19 on my P-M laptop. It showed 100% done at 3:14:58 CPU time, but no activity, screensaver wouldn't come up (blank area only), task manager showed all cycles going to System Idle Process. Suspended acty and re-started Boinc, no-joy. Closed BM and re-started machine, brought it back up, no-joy. Aborted the WU and BM went right back to work. Didn't want to wait ?16hrs? (4x4) to see if it would somehow wake-up and finish on its own!

This version works without problems on x64.

Work tasks : OK
Graphics : OK

This time I had a work unit that ran for 59 min 35 seconds... then went dormant for 60 min 25 seconds. Total was 2 hrs instead of 1.

Are your workunits CASP7? If so, it's natural to delay to finish.

Moderator9 has mentioned in the post, http://ralph.bakerlab.org/forum_thread.php?id=209#1654

d287__CASP7_ABRELAX_521_7

has been running for 6 hours and shows only 1.044% progress. This is running on a Mac.

Let it run. It is a test Work Unit for CASP7. It is probably just a large Work Unit. Do not be surprised if it suddenly jumps to 100% at the end of the first model. Do not stop Boinc Or Rosetta or it will start over at 0%.

If it gets to the place where is has run longer that about 5 times the setting for "Time" in your preferences, it will either be stopped by the "Watchdog" or you might want to consider aborting it manually at that time.

Keep us posted.

If your units aren't CASP7 ones, it might be an error, I think.

Had an occasion where a work unit was showing at the end 100% complete but was not using any CPU time. I investigated and indeed the Idle Task was running at 99%+ while the 5.19 work unit was apparently idle. This lasted for at least 2 minutes, but might have been up to 2 hours before I saw it as that's how much time the Idle task has accumulated. Without intervention, the work unit completed and was reported normally. Not sure what this means, I'll keep an eye out for a similar occurrence.


As I was typing this, another work unit has gotten into this mode. Showing 100% complete and not using any CPU time.

It completed after being dormant for 18 minutes. I'll watch for another.

The very next work unit also showed 100% with no CPU time after about 40 minutes of run time. It stayed dormant for 20 minutes, then completed and reported.

For the next two work units. Run 35 minutes, dormant for 24. Run 51 minutes, dormant for 9.

The pattern seems to be that the work unit will go dormant after completion until one full hour has elapsed.

Note: this is in the account file for Ralph: <cpu_run_time>0</cpu_run_time>

Had an occasion where a work unit was showing at the end 100% complete but was not using any CPU time. I investigated and indeed the Idle Task was running at 99%+ while the 5.19 work unit was apparently idle. This lasted for at least 2 minutes, but might have been up to 2 hours before I saw it as that's how much time the Idle task has accumulated. Without intervention, the work unit completed and was reported normally. Not sure what this means, I'll keep an eye out for a similar occurrence.


As I was typing this, another work unit has gotten into this mode. Showing 100% complete and not using any CPU time.

It completed after being dormant for 18 minutes. I'll watch for another.

The very next work unit also showed 100% with no CPU time after about 40 minutes of run time. It stayed dormant for 20 minutes, then completed and reported.

Had an occasion where a work unit was showing at the end 100% complete but was not using any CPU time. I investigated and indeed the Idle Task was running at 99%+ while the 5.19 work unit was apparently idle. This lasted for at least 2 minutes, but might have been up to 2 hours before I saw it as that's how much time the Idle task has accumulated. Without intervention, the work unit completed and was reported normally. Not sure what this means, I'll keep an eye out for a similar occurrence.


As I was typing this, another work unit has gotten into this mode. Showing 100% complete and not using any CPU time.

It completed after being dormant for 18 minutes. I'll watch for another.

Had an occasion where a work unit was showing at the end 100% complete but was not using any CPU time. I investigated and indeed the Idle Task was running at 99%+ while the 5.19 work unit was apparently idle. This lasted for at least 2 minutes, but might have been up to 2 hours before I saw it as that's how much time the Idle task has accumulated. Without intervention, the work unit completed and was reported normally. Not sure what this means, I'll keep an eye out for a similar occurrence.


As I was typing this, another work unit has gotten into this mode. Showing 100% complete and not using any CPU time.

Debugging is optional... okay... how? Is it on, is it off? How do we test it?

See this post Item 2.

So the short of this is, if the workunit is simply running uninterrupted, it could run forever, or until it hits the Max time setting. This is the risk of running a single project setup. If you don't see movement in the graphic, try suspending the Work unit and letting the system run a different one for 5 min. Then restart the first Work unit again for 5 min. Repeat this process 4 -5 times and it should abort the workunit if it was stuck. If it is not stuck it should let it keep running. Either that or we have a watchdog bug.

[This computer is headless. Remote access only. Hence no screensaver.

Mike, I use VNC to see the graphics on my remote monitorless, keyboardless, and mouseless puter. I click on the WU from the task tab and then view graphics. No screensaver here either. If it's a service install your hosed.

tony

It is a service install. I forgot about the "View Graphics button" I do VN into this computer. OK... 1.041% complete after 40 hours. Stage Full atom relax, Mode 1, Step 100, Accepted RMSD 50.36, Accepted Energy -19.40622 whatever this all means.