I came home from work today to find my Vista Business desktop stacked with several dialog boxes announcing \"Visual Fortran failures....\" and climateprediction was the referenced culprit. I wish I could have gotten the screenshot to post here.

Here is the message log for today (so far) on the C2D box running (2) instances simultaneously on BOINC ver. 5.10.28 (24/7/365 on a static Cable IP):

12/12/2007 8:12:37 AM|climateprediction.net|Task hadsm3fub_0553_005914074_7 exited with zero status but no \'finished\' file
12/12/2007 8:12:37 AM|climateprediction.net|If this happens repeatedly you may need to reset the project.
12/12/2007 8:13:47 AM|climateprediction.net|Restarting task hadsm3fub_0553_005914074_7 using hadsm3 version 506
12/12/2007 8:14:58 AM|climateprediction.net|Task hadsm3fub_0337_005912504_9 exited with zero status but no \'finished\' file
12/12/2007 8:14:58 AM|climateprediction.net|If this happens repeatedly you may need to reset the project.
12/12/2007 8:16:08 AM|climateprediction.net|Restarting task hadsm3fub_0337_005912504_9 using hadsm3 version 506
12/12/2007 8:40:45 AM|climateprediction.net|Task hadsm3fub_0553_005914074_7 exited with zero status but no \'finished\' file
12/12/2007 8:40:45 AM|climateprediction.net|If this happens repeatedly you may need to reset the project.
12/12/2007 8:40:45 AM|climateprediction.net|Restarting task hadsm3fub_0553_005914074_7 using hadsm3 version 506
12/12/2007 8:48:13 AM|climateprediction.net|Sending scheduler request: To send trickle-up message. Requesting 0 seconds of work, reporting 0 completed tasks
12/12/2007 8:49:29 AM|climateprediction.net|Scheduler request failed: HTTP internal server error
12/12/2007 8:50:29 AM|climateprediction.net|Sending scheduler request: To send trickle-up message. Requesting 0 seconds of work, reporting 0 completed tasks
12/12/2007 8:51:54 AM|climateprediction.net|Scheduler request failed: HTTP internal server error
12/12/2007 8:52:54 AM|climateprediction.net|Sending scheduler request: To send trickle-up message. Requesting 0 seconds of work, reporting 0 completed tasks
12/12/2007 8:54:19 AM|climateprediction.net|Scheduler request failed: HTTP internal server error
12/12/2007 8:55:20 AM|climateprediction.net|Sending scheduler request: To send trickle-up message. Requesting 0 seconds of work, reporting 0 completed tasks
12/12/2007 8:55:42 AM||Project communication failed: attempting access to reference site
12/12/2007 8:55:43 AM||Access to reference site succeeded - project servers may be temporarily down.
12/12/2007 8:55:45 AM|climateprediction.net|Scheduler request failed: Couldn\'t connect to server
12/12/2007 8:56:45 AM|climateprediction.net|Sending scheduler request: To send trickle-up message. Requesting 0 seconds of work, reporting 0 completed tasks
12/12/2007 8:57:05 AM|climateprediction.net|Scheduler request succeeded: got 0 new tasks
12/12/2007 11:58:56 AM|climateprediction.net|Sending scheduler request: To send trickle-up message. Requesting 0 seconds of work, reporting 0 completed tasks
12/12/2007 11:59:01 AM|climateprediction.net|Scheduler request succeeded: got 0 new tasks
12/12/2007 3:46:44 PM|climateprediction.net|Sending scheduler request: To send trickle-up message. Requesting 0 seconds of work, reporting 0 completed tasks
12/12/2007 3:46:49 PM|climateprediction.net|Scheduler request succeeded: got 0 new tasks
12/12/2007 7:34:38 PM|climateprediction.net|Sending scheduler request: To send trickle-up message. Requesting 0 seconds of work, reporting 0 completed tasks
12/12/2007 7:34:43 PM|climateprediction.net|Scheduler request succeeded: got 0 new tasks
12/12/2007 7:50:31 PM|climateprediction.net|Sending scheduler request: To send trickle-up message. Requesting 0 seconds of work, reporting 0 completed tasks
12/12/2007 7:50:36 PM|climateprediction.net|Scheduler request succeeded: got 0 new tasks
12/12/2007 7:50:47 PM|climateprediction.net|Sending scheduler request: To send trickle-up message. Requesting 0 seconds of work, reporting 0 completed tasks
12/12/2007 7:50:52 PM|climateprediction.net|Scheduler request succeeded: got 0 new tasks
12/12/2007 7:53:48 PM|climateprediction.net|Computation for task hadsm3fub_0337_005912504_9 finished
12/12/2007 7:53:48 PM|climateprediction.net|Output file hadsm3fub_0337_005912504_9_2.zip for task hadsm3fub_0337_005912504_9 absent
12/12/2007 7:53:48 PM|climateprediction.net|Output file hadsm3fub_0337_005912504_9_3.zip for task hadsm3fub_0337_005912504_9 absent
12/12/2007 7:54:49 PM|climateprediction.net|Sending scheduler request: To fetch work. Requesting 86401 seconds of work, reporting 1 completed tasks
12/12/2007 7:54:54 PM|climateprediction.net|Scheduler request succeeded: got 1 new tasks
12/12/2007 7:54:56 PM|climateprediction.net|Started download of hadsm3fub_0515_005914731.zip
12/12/2007 7:54:59 PM|climateprediction.net|Finished download of hadsm3fub_0515_005914731.zip
12/12/2007 7:55:00 PM|climateprediction.net|Starting hadsm3fub_0515_005914731_4
12/12/2007 7:55:00 PM|climateprediction.net|Starting task hadsm3fub_0515_005914731_4 using hadsm3 version 506

When I had a look at the status last night, \"hadsm3fub_0337_005912504_9 using hadsm3 version 506\" was only just over 40%.

Could it have completed at an greatly accelerated rate or did it get wiped?

That result has errored out.

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/result.php?resultid=6998030

There were an extraordinary number of \"No heartbeat from core client\" messages in your stderr_txt file. Is this PC running any CPU intensive or memory intensive programs in background, or scheduled, besides BOINC?

...
No heartbeat from core client for 54 sec - exiting
No heartbeat from core client for 55 sec - exiting
No heartbeat from core client for 56 sec - exiting
No heartbeat from core client for 57 sec - exiting
No heartbeat from core client for 58 sec - exiting
No heartbeat from core client for 59 sec - exiting
No heartbeat from core client for 60 sec - exiting
No heartbeat from core client for 61 sec - exiting
No heartbeat from core client for 62 sec - exiting
No heartbeat from core client for 63 sec - exiting
No heartbeat from core client for 64 sec - exiting
No heartbeat from core client for 65 sec - exiting
cpdnmonitor: cannot open input file dataout/restart.day

Model crashed: ��
</stderr_txt>
]]>

Hi Zapp,

Another thing which comes to mind is that network issues can cause something similar as well - if the Boinc client is unable to contact a DNS server when it thinks it is connected to the internet, it will hang and eventually crash any outstanding workunits (see trak ticket 113). The manager will also appear to lock up. While losing a few short workunits from other projects is bad enough, losing a climate model due to a network glitch is really frustrating.

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ

That result has errored out.

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/result.php?resultid=6998030

There were an extraordinary number of \"No heartbeat from core client\" messages in your stderr_txt file. Is this PC running any CPU intensive or memory intensive programs in background, or scheduled, besides BOINC?

Zonealarm Pro Antivirus and AntiSpam checks are auto-scheduled every morning at 6AM but both have the BOINC directory and subdirectories excluded from scans. There isn\'t anything set to auto-update. Whenever, I see an alert that an update is available, I check to see if any proj is in the process of uploading or downloading, then I put the BOINC Manager is snooze mode. After all projects are suspended then I exit BOINC Manager and procede to complete the updates which usually require an reboot to complete installation. Upon restart, BOINC initializes and starts up wherever it was prior to snooze was set (after startup benchmarking, of course).

---