Joined: 26 Aug 04
Got the message "no work from project -- daily quota exceeded".
The last three or so days my system has spent mostly idle. [It's sitting there doing nothing right now.]
A number of workunits have been downloaded to my client, but they all have quickly failed with error code 251. [WHAT CAUSES THIS ERROR ?]
I am trying to be a "good faith" participant. From my perspective, it is the *software* I downloaded that has had problems (error code 251). But now the project appears to be penalizing *me* because it is on my system that the software problems show up.
I guess the project was set up to run in a "perfect" world. And users whose experience is not "perfect" are to be shunned. [What a way to run a railroad!]
mikus (4.19, AMD CPU, Suse 9.2]
Joined: 26 Aug 04
Did not think this could be involved here, but I just had trouble doing a "shutdown" -- so it might be a hardware problem, after all.
It sure would be nice if somewhere I could look up what error code 251 meant.
Joined: 5 Sep 04
> It sure would be nice if somewhere I could look up what error code 251 meant.
Been there, Done that, Can't find the thread. It may be on the BOINC forum, or on the board that is still down.
The following MAY have been about error 251, but it still applies:
A few Linux people have been trying to put the data files on a network drive.
DON'T do this! The network can't handle the data bursts!
(This from one of the CPDN programmers.)
Have you run These tests?
I usually list the following as causes for CPDN crashing:
A power supply that can't provide stable voltages under full processor load.
Fans and heatsinks covered with dust.
There was a user in the last few days with continual crashing.
I suggested the three tests; he ran prime95 for 3 minutes: CRASH
The board temp was 75C.
He looked inside; thick layers of dust.
Cleaned out dust; re-ran prime95. OK
>I guess the project was set up to run in a "perfect" world. And users whose experience is not "perfect" are to be shunned.
RUBBISH! It works fine for thousands of people, even those with slow computers.
> [What a way to run a railroad!]
The railroad is fine. It's your locomotive which is faulty.
So: let's try and repair it.