2 Client errors in a row
Anonymous
22 Aug 2006 15:42:21 UTC
Topic 13423
(moderation:
Thanks for the report. I think indeed that adjusting the credit in the current way may have caused this as an unwanted side effect on slow machines. We're looking into this, this is probably a problem of workunit generation.
BM
2 Client errors in a row
)
The "validate error" result file looks pretty bad. It isn't correctly compressed, and of what can be uncompressed the first lines look ok, but the last lines look like complete trash of digits, dots, blanks and linebreaks. This might be the result of a bad compression.
There are many possible reasons for that. My first guess would be transmission problems, it may also be a problem with the harddisk, RAM or CPU, and may or may not be temperature dependent.
BM
BM
RE: Bernd: I'll go ahead
)
Bruce fixed this today, the WUs that are now inserted in the DB shouldn't cause this problem anymore. However currently you will probably get a Task with old settings, so better wait a bit longer before resuming the project on this machine.
BM
BM
RE: RE: Bernd: I'll go
)
I also fixed this retroactively. Any WU that your machine downloads from the server should have a higher CPU time limit.
Bruce
RE: Started a new machine
)
See the stderr output of the results you reported. This is a "general access violation" (code 0xc0000005), which can have many reasons. By far the most common is a graphics driver that crashes when Einstein@Home is trying to show its graphics (screensaver).
When you get new work and have an Einstein@Home task running, mark it (in the "Tasks" tab of the manager) and click "show graphics". If it gives a client error immediately, this is most likely the problem. A short term solution would be to disable the screensaver (or set it to some other than the BOINC saver) (and of course don't touch the "show graphics" anymore), in the longer term I would suggest to update your graphics card driver.
There is a small chance that something else is broken, e.g. a file of the project (in this case resetting the project would help), a bad memory or CPU that gets too hot sometimes. If it's not the graphics driver as mentioned above, check your hardware.
BM
BM