Thyme Lawn wrote in another thread...

But the -161 errors aren\'t the real problem. They\'re to do with the fact that the model uses BOINC\'s intermediate upload feature to return a result file at the end of each phase. The files are only generated at the end of the appropriate phase. When the model errors out it doesn\'t generate any of the missing result files and the error message indicates that BOINC is trying to return them. For some reason this causes BOINC to suppress the message indicating what the real error was :(

Hmmm...I\'ve now been bitten by this. Using BOINC 5.2.13 in WinXP. End of phase 1 file uploaded, there were a bunch of trickles within minutes after upload, \"12/18/2005 8:30:08 PM||request_reschedule_cpus: process exited\", then the -161 errors. Nothing for me to see why it was an unrecoverable error. Is this -161 error a BOINC thing or CPDN thing? And is there anything we can do about it?

Edit...The following were at the end of yabsd.out. I haven\'t seen anything about this before. Can anyone make anything of it?

Mismatch in no of prognostic fields.
No of prog fields in Atmos dump 388
No of prog fields expected 389

Run RECONFIGURATION to get correct no of prognostic fields in atmos dump
or
Check/Reset experiment in User Interface

*********************************************************************************
Model aborted with error code - 102 Routine and message:-
INITDUMP: Wrong no of atmos prognostic fields
*********************************************************************************

12/18/2005 8:23:23 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
12/18/2005 8:23:23 PM|climateprediction.net|Reason: To send trickle-up message
12/18/2005 8:23:23 PM|climateprediction.net|Note: not requesting new work or reporting results
12/18/2005 8:23:28 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
12/18/2005 8:23:55 PM|climateprediction.net|Started upload of sulphur_ftnb_000738263_0_1.zip
12/18/2005 8:23:58 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
12/18/2005 8:23:58 PM|climateprediction.net|Reason: To send trickle-up message
12/18/2005 8:23:58 PM|climateprediction.net|Note: not requesting new work or reporting results
12/18/2005 8:24:03 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
12/18/2005 8:26:19 PM|climateprediction.net|Finished upload of sulphur_ftnb_000738263_0_1.zip
12/18/2005 8:26:19 PM|climateprediction.net|Throughput 61318 bytes/sec
12/18/2005 8:26:23 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
12/18/2005 8:26:23 PM|climateprediction.net|Reason: To send trickle-up message
12/18/2005 8:26:23 PM|climateprediction.net|Note: not requesting new work or reporting results
12/18/2005 8:26:28 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
12/18/2005 8:28:48 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
12/18/2005 8:28:48 PM|climateprediction.net|Reason: To send trickle-up message
12/18/2005 8:28:48 PM|climateprediction.net|Note: not requesting new work or reporting results
12/18/2005 8:28:53 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
12/18/2005 8:28:58 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
12/18/2005 8:28:58 PM|climateprediction.net|Reason: To send trickle-up message
12/18/2005 8:28:58 PM|climateprediction.net|Note: not requesting new work or reporting results
12/18/2005 8:29:03 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
12/18/2005 8:30:08 PM||request_reschedule_cpus: process exited
12/18/2005 8:30:08 PM|climateprediction.net|Computation for result sulphur_ftnb_000738263_0 finished
12/18/2005 8:30:08 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
12/18/2005 8:30:08 PM|climateprediction.net|Reason: To fetch work
12/18/2005 8:30:08 PM|climateprediction.net|Requesting 8640 seconds of new work
12/18/2005 8:30:09 PM|climateprediction.net|Unrecoverable error for result sulphur_ftnb_000738263_0 ({file_xfer_error}  {file_name}sulphur_ftnb_000738263_0_2.zip{/file_name}  {error_code}-161{/error_code}  {error_message}{/error_message}{/file_xfer_error}{file_xfer_error}  
{file_name}sulphur_ftnb_000738263_0_3.zip{/file_name}  {error_code}-161{/error_code}  {error_message}{/error_message}{/file_xfer_error}{file_xfer_error}  
{file_name}sulphur_ftnb_000738263_0_4.zip{/file_name}  {error_code}-161{/error_code}  {error_message}{/error_message}{/file_xfer_error}{file_xfer_error}  
{file_name}sulphur_ftnb_000738263_0_5.zip{/file_name}  {error_code}-161{/error_code}  {error_message}{/error_message}{/file_xfer_error})

If anyone else has experienced this. Could you please send me the
model restart file.

---

If anyone else has experienced this. Could you please send me the
model restart file.

Where shall I send the restart.day.gz ?

If anyone else has experienced this. Could you please send me the
model restart file.

Where shall I send the restart.day.gz ?

It has been fixed in the new work units now, so shouldn\'t be a problem in any recently downloaded units.