Multibeam WU appears to end processing but doesn't stop running - general problem?

Message boards : Number crunching : Multibeam WU appears to end processing but doesn't stop running - general problem?
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Graham Thomas

Send message
Joined: 19 May 99
Posts: 32
Credit: 3,880,875
RAC: 4
United Kingdom
Message 821899 - Posted: 22 Oct 2008, 15:18:44 UTC

Every so often (but twice in the past two days, which is why I'm writing) I get a Seti work unit that seems to reach its conclusion (either 100% or 99.997% complete, and no more graphics action) but never stops running. Normally my WUs take either just over an hour or just over four hours, but one of these rogues can go on for over 24 hours.

So I abort, but then of course don't get any credit. Is this a general problem or is it something to do with my setup? (I'm running an Athlon 64 3200 - I know AMD chips take longer to process Astropulse units but I haven't seen any issues relating to multibeam ones.) Should I abort or will the unit eventually complete?

Graham
Graham Thomas
ID: 821899 · Report as offensive
kittyman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Jul 00
Posts: 51468
Credit: 1,018,363,574
RAC: 1,004
United States
Message 821905 - Posted: 22 Oct 2008, 15:22:54 UTC - in response to Message 821899.  

Every so often (but twice in the past two days, which is why I'm writing) I get a Seti work unit that seems to reach its conclusion (either 100% or 99.997% complete, and no more graphics action) but never stops running. Normally my WUs take either just over an hour or just over four hours, but one of these rogues can go on for over 24 hours.

So I abort, but then of course don't get any credit. Is this a general problem or is it something to do with my setup? (I'm running an Athlon 64 3200 - I know AMD chips take longer to process Astropulse units but I haven't seen any issues relating to multibeam ones.) Should I abort or will the unit eventually complete?

Graham

Sometimes in the past when I have had a 'stuck' WU, shutting down Boinc and restarting it would boot the WU into proper completion. If that didn't work, sometimes a reboot of the rig would do the trick.

You might try that before you abort the WU if it happens again.....


"Freedom is just Chaos, with better lighting." Alan Dean Foster

ID: 821905 · Report as offensive
Profile Graham Thomas

Send message
Joined: 19 May 99
Posts: 32
Credit: 3,880,875
RAC: 4
United Kingdom
Message 822048 - Posted: 22 Oct 2008, 22:54:40 UTC - in response to Message 821905.  

Thanks. That's worth a try.

Graham
Graham Thomas
ID: 822048 · Report as offensive
kittyman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Jul 00
Posts: 51468
Credit: 1,018,363,574
RAC: 1,004
United States
Message 822121 - Posted: 23 Oct 2008, 4:15:38 UTC - in response to Message 822048.  

Thanks. That's worth a try.

Graham

Your welcome.....
Please let us know if it happens again and if the restart and/or reboot clears the problem.....
"Freedom is just Chaos, with better lighting." Alan Dean Foster

ID: 822121 · Report as offensive

Message boards : Number crunching : Multibeam WU appears to end processing but doesn't stop running - general problem?


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.