This Work Unit 13594 ran for approx. 120 thousand seconds with no progress made. I aborted it. I watch each project fairly closely for just these types of errors but that just killed about 5,000 (thousand) credits. My question is, is this just a random error (it has happened to me twice in two months) or can we expect this to happen more often? If so, perhaps it is time to invest in a watchdog such as the one ROSETTA uses. That way if the program does not advance (I think it is 900 seconds for Rosetta) the WU is halted and another is started without the intervention of the user.

Just something to think about while we are still in BETA.

Timothy

Ok, so I attempted to run a yoyo WU about 16 hours ago and this too has resulted in zero progress. I aborted that WU and I have now started a PS3Grid WU and I will let it run overnight.

So I have had to abort 2 yoyo and 2 PS3Grid so far and the results for the current WU are already not too promising. This is clearly not an application problem but a BOINC USB build problem. What should I do? Reinstall the entire USB again (the third time actually)? Is anyone else having this problem?

Thanks,

Tim

Is anyone else having this problem?

Is anyone else having this problem?

I have seen it rarely in the past, but not just PS3GRID. I have had same problem on other hosts with other clients with other projects.

Whenever I have seen this it has been necessary to exit all boinc and restart boinc. Sometimes I would just restart the entire system.

Have you tried and restarts since problem started ?

I agree. Restarting BOINC, or rebooting has always fixed it for me. No need to abort.
____________
Reno, NV
Team: SETI.USA

Is anyone else having this problem?

I have seen it rarely in the past, but not just PS3GRID. I have had same problem on other hosts with other clients with other projects.

Whenever I have seen this it has been necessary to exit all boinc and restart boinc. Sometimes I would just restart the entire system.

Have you tried and restarts since problem started ?

I just aborted a PS3 job after 37h worktime.
I had two pending PS3 jobs and did some yoyo work in between.
Will check tomorrow, if yoyo works fine (restarting Boinc as well now)

I agree. Restarting BOINC, or rebooting has always fixed it for me. No need to abort.

Ok, so I attempted to run a yoyo WU about 16 hours ago and this too has resulted in zero progress. I aborted that WU and I have now started a PS3Grid WU and I will let it run overnight.

So I have had to abort 2 yoyo and 2 PS3Grid so far and the results for the current WU are already not too promising. This is clearly not an application problem but a BOINC USB build problem. What should I do? Reinstall the entire USB again (the third time actually)? Is anyone else having this problem?

Thanks,

Tim

I\'m having troubles again.
A PS3 job was running for 30+ hours with no progress.
It shows 89% work done now but it remained the same since maybe 10h.
I can hear the fan so it must be crunching.
Is it always starting from the beginning after doing a yoyo-job?
Is there a bug-fix being worked on to make it stable to switch between 2 projects w/o issues?

I\'m having troubles again.
A PS3 job was running for 30+ hours with no progress.
It shows 89% work done now but it remained the same since maybe 10h.
I can hear the fan so it must be crunching.
Is it always starting from the beginning after doing a yoyo-job?
Is there a bug-fix being worked on to make it stable to switch between 2 projects w/o issues?

The pendrive just boots up and shots down quite fast.
YDL was installed and I think I just have to change the bootloader again :-/