climateprediction.net home page
WU config error : Maximum CPU time exceeded

WU config error : Maximum CPU time exceeded

Message boards : Number crunching : WU config error : Maximum CPU time exceeded
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Ananas
Volunteer moderator

Send message
Joined: 31 Oct 04
Posts: 336
Credit: 3,316,482
RAC: 0
Message 47922 - Posted: 2 Jan 2014, 23:59:42 UTC
Last modified: 3 Jan 2014, 0:11:04 UTC

at about half the model hadcm3n_4jfo_2020_40_008402337

Maximum CPU time exceeded

Mine got further than the previous deliveries so I would have had a chance to finish it :-/

This might be a series of errors as usually all models of a series have the same FPOPS_BOUND value.

p.s.: I'm not using any tweaks that influence the benchmark result so the calculated FPOPS are standard BOINC, no power saving mode either - that's why it can only be a WU configuration problem.
ID: 47922 · Report as offensive     Reply Quote
Les Bayliss
Volunteer moderator

Send message
Joined: 5 Sep 04
Posts: 7629
Credit: 24,240,330
RAC: 0
Message 47923 - Posted: 3 Jan 2014, 0:23:58 UTC - in response to Message 47922.  

I've previously only heard about that error when the model is started on one computer, and then transferred to another, much faster, computer.

Still, that unit is now on it's last chance, so it won't bother anyone else.

ID: 47923 · Report as offensive     Reply Quote
Profile Ananas
Volunteer moderator

Send message
Joined: 31 Oct 04
Posts: 336
Credit: 3,316,482
RAC: 0
Message 47925 - Posted: 3 Jan 2014, 8:20:49 UTC - in response to Message 47923.  

I did such a move once when I switched that box to Ubuntu for some testing but this time everything has been just standard.

The trickle times where within the normal time/speed range for that box, even somewhat faster than the previous model on the same box.
ID: 47925 · Report as offensive     Reply Quote
Profile mo.v
Volunteer moderator
Avatar

Send message
Joined: 29 Sep 04
Posts: 2363
Credit: 14,611,758
RAC: 0
Message 47926 - Posted: 4 Jan 2014, 2:11:17 UTC
Last modified: 4 Jan 2014, 2:12:35 UTC

I can't understand why this model crashed. It's a perfectly normal computer and the trickle times ie processing times are good. If the model got into a loop and stayed stuck there for a long time, that would eventually result in BOINC aborting the model with this error if the model didn't abort itself first. But the trickle times show no evidence of any persistent loop. Other computers have completed models that appear to be from the same batch and took three or four times longer to process.

Could the error possibly be caused by the fact that this computer still has BOINC v.5?
Cpdn news
ID: 47926 · Report as offensive     Reply Quote

Message boards : Number crunching : WU config error : Maximum CPU time exceeded

©2024 climateprediction.net