WU waiting to run

B.I.G
B.I.G
Joined: 26 Oct 07
Posts: 57
Credit: 318,133,355
RAC: 289,307
Topic 193772

I have a problem with a work unit, it did run for 17 hours, then the client switched to a SETI WU which is my backup project. After the SETI WU was finished the Einstein WU didn't start again. I tried whatever came into my mind but there it stays "waiting to run"
After increasing the cache it is crunching the next WU, any ideas how to get the started one running again?

Here it is by the way:
http://einsteinathome.org/workunit/41426841

Bikeman (Heinz-Bernd Eggenstein)
Bikeman (Heinz-...
Moderator
Joined: 28 Aug 06
Posts: 3,516
Credit: 455,818,610
RAC: 41,805

WU waiting to run

Hi!

Just to make sure: is there *any* WU running (SETI or BOINC) at the moment, or none at all? Could you provide the contents of the "messages" tab from BOINC manager GUI (advanced view), there might be some hints in this why E@H is not scheduled to run.

CU
Bikeman

B.I.G
B.I.G
Joined: 26 Oct 07
Posts: 57
Credit: 318,133,355
RAC: 289,307

SETI was running all the time

Message 82953 in response to message 82952

SETI was running all the time although I only gave it 1% share, so I did suspend SETI but the WU still wouldn't run again, at that time it was the only Workunit on that machine. Then I increased the work buffer after which I got two new Einstein WUs and the machine is crunching one of them at the moment but it just doesn't want to resume to the already started one.
I checked the messages but it all seems to be normal, nothing special in the past weeks.

Bikeman (Heinz-Bernd Eggenstein)
Bikeman (Heinz-...
Moderator
Joined: 28 Aug 06
Posts: 3,516
Credit: 455,818,610
RAC: 41,805

Hi! Anyway, the messages

Hi!

Anyway, the messages from the messages tab would be useful. Sometimes you even get some info from what is NOT printed.

Please also make sure you haven't inadvertently suspended E@H locally in Boinc manager.

Next thing to check are the preferences in your account. There are some settings that might suspend E@H tasks, like

- don't run BOINC during certain time of day, or

- don't run BOINC if (BOINC thinks) the computer is not idle (keyboard or mouse activity...). Usually you don't need this idle detection as the science apps run in low prio mode. It's worth a try to allow BOINC to run ALWAYS.

CU
Bikeman

M. Schmitt
M. Schmitt
Joined: 27 Jun 05
Posts: 478
Credit: 15,872,262
RAC: 0

As your Mac has only 512 MB

As your Mac has only 512 MB RAM, there is a little chance, that the WU that is not running again, is just waiting for memory. This depends on the setting: 'Leave applications in memory while suspended?' in the preferences for this host.

Did you quit boinc and restart it again?

If this doesn't help, please find the slot/x directory where the waiting WU saves its status and c&p the content of stderr.txt in that directory.

cu,
Michael

B.I.G
B.I.G
Joined: 26 Oct 07
Posts: 57
Credit: 318,133,355
RAC: 289,307

RE: Did you quit boinc and

Message 82956 in response to message 82955

Quote:
Did you quit boinc and restart it again?


Stupid me, the first thing you should try when troubleshooting, the easiest and most successful way to solve problems, and yet for a whole day it didn't come into my mind.
Thanks for the hint, the WU is running again now.

Bikeman, interestingly when I had only that problem WU in the Task noting was running, the machine was idle and didn't ask for new work as it still had one WU to finish. When I forced it to download new WUs, SETI or Einstein it started to crunch them immediately and went idle again when they were finished. Fortunately everything is running ok now.
If that problem aperas again I will copy the messages, it's not that easy with remote control on a slow line.

Thunder
Thunder
Joined: 18 Jan 05
Posts: 138
Credit: 46,754,541
RAC: 0

RE: Stupid me, the first

Message 82957 in response to message 82956

Quote:
Stupid me, the first thing you should try when troubleshooting, the easiest and most successful way to solve problems, and yet for a whole day it didn't come into my mind.
Thanks for the hint, the WU is running again now.

It hasn't happened in months, but I've had the same thing happen on very rare occasions. Either restarting the computer entirely or else simply restarting BOINC has fixed it, but you're not alone in remembering the "first thing" to try. I think I fiddled around trying to be all diagnostic for a time as well. :P

Glad to know it's running well again. :)

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.