Restart Application

log in

Advanced search

Message boards : SETI@home Enhanced : Restart Application

Author Message
MacDitch
Volunteer tester
Send message
Joined: 1 Aug 06
Posts: 27
Credit: 237,229
RAC: 9
Message 13777 - Posted: 26 Jan 2007, 9:06:29 UTC

Sorry, I was a bit asleep when I got this error but thought I'd post what I could!

When I looked at my machine this morning it was sporting a windows message box telling me that I should restart the seti application process as it had errored and been shutdown. I ok'd the message before copying down any details (sorry!) and opened BoincMgr to find that wu 286075 had errored at 1 second. I don't know if it is important so I thought I'd post here so that someone can check if they think it warrants it.

It may have been my machine, but this is the first work unit it has ever errored on (that I can recall at least!)
____________

Josef W. Segur
Volunteer tester
Send message
Joined: 14 Oct 05
Posts: 1018
Credit: 1,494,957
RAC: 249
Message 13801 - Posted: 27 Jan 2007, 3:31:09 UTC - in response to Message 13777.

Sorry, I was a bit asleep when I got this error but thought I'd post what I could!

When I looked at my machine this morning it was sporting a windows message box telling me that I should restart the seti application process as it had errored and been shutdown. I ok'd the message before copying down any details (sorry!) and opened BoincMgr to find that wu 286075 had errored at 1 second. I don't know if it is important so I thought I'd post here so that someone can check if they think it warrants it.

It may have been my machine, but this is the first work unit it has ever errored on (that I can recall at least!)

It's possible the error on wu 286025 which was handled quietly by BOINC had the same cause. Both are very similar to the symptoms shown by many multi-CPU systems, see the Builds for unexplained error test thread. Having that happen on a single CPU system is quite unusual, though I came across a PIII system doing it some time ago.

Two errors out of 44 results isn't horrible, particularly when they each cost only a few seconds of CPU time. If your long average turnaround time is due to a low resource share for this project, you could boost it for awhile to see if that sort of ratio continues. That would be a good contribution to the ongoing Beta test. OTOH, the errors may have been unrelated to anything we've seen before.
Joe

MacDitch
Volunteer tester
Send message
Joined: 1 Aug 06
Posts: 27
Credit: 237,229
RAC: 9
Message 13814 - Posted: 27 Jan 2007, 10:26:25 UTC - in response to Message 13801.

Having that happen on a single CPU system is quite unusual, though I came across a PIII system doing it some time ago.


Should have mentioned that the computer connected to the net is not the one doing the work (in this case anyway) it was actually a pentium extreme - or whatever tehy call the these days!

not really fussed about the time/redit - just thought I'd highlight it in case it was important.
____________

Message boards : SETI@home Enhanced : Restart Application


Return to SETI@home/AstroPulse Beta main page


Copyright © 2013 University of California

AstroPulse is funded in part by the NSF through grant AST-0307956