I have been getting the following messages and I was wondering as to the effect they may have on the current work unit. Can anyone please explain the reason why these messages appear? Do I have a corrupt file?

17/11/2005 19:22:20|climateprediction.net|Resuming computation for result 146e_300072613_1 using hadsm3 version 4.13
17/11/2005 19:37:34||Can\'t open temp state file: client_state_next.xml
17/11/2005 19:37:34||Couldn\'t write state file: -108
17/11/2005 19:37:44|climateprediction.net|Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
17/11/2005 19:37:44|climateprediction.net|scheduler init_op_project to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed, error -1
17/11/2005 19:37:45|climateprediction.net|Deferring communication with project for 59 seconds
17/11/2005 19:38:45|climateprediction.net|Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
17/11/2005 19:38:45|climateprediction.net|scheduler init_op_project to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed, error -1
17/11/2005 19:38:46|climateprediction.net|Deferring communication with project for 58 seconds
17/11/2005 19:39:45|climateprediction.net|Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
17/11/2005 19:39:45|climateprediction.net|scheduler init_op_project to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed, error -1
17/11/2005 19:39:46|climateprediction.net|Deferring communication with project for 58 seconds
17/11/2005 19:40:46|climateprediction.net|Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
17/11/2005 19:40:46|climateprediction.net|scheduler init_op_project to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed, error -1
17/11/2005 19:40:47|climateprediction.net|Deferring communication with project for 58 seconds
17/11/2005 19:41:47|climateprediction.net|Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
17/11/2005 19:41:47|climateprediction.net|scheduler init_op_project to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed, error -1
17/11/2005 19:41:48|climateprediction.net|Deferring communication with project for 1 minutes and 21 seconds
17/11/2005 19:42:52||Can\'t open temp state file: client_state_next.xml
17/11/2005 19:42:52||Couldn\'t write state file: -108
17/11/2005 19:43:10|climateprediction.net|Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
17/11/2005 19:43:10|climateprediction.net|scheduler init_op_project to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed, error -1
17/11/2005 19:43:11|climateprediction.net|Deferring communication with project for 1 minutes and 15 seconds
17/11/2005 19:44:26|climateprediction.net|Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
17/11/2005 19:44:26|climateprediction.net|scheduler init_op_project to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed, error -1
17/11/2005 19:44:28|climateprediction.net|Deferring communication with project for 2 minutes and 21 seconds
17/11/2005 19:46:50|climateprediction.net|Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
17/11/2005 19:46:50|climateprediction.net|scheduler init_op_project to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed, error -1
17/11/2005 19:46:51|climateprediction.net|Deferring communication with project for 33 minutes and 32 seconds
17/11/2005 19:47:43||Can\'t open temp state file: client_state_next.xml
17/11/2005 19:47:43||Couldn\'t write state file: -108
17/11/2005 19:52:37||Can\'t open temp state file: client_state_next.xml
17/11/2005 19:52:37||Couldn\'t write state file: -108
17/11/2005 19:57:29||Can\'t open temp state file: client_state_next.xml
17/11/2005 19:57:29||Couldn\'t write state file: -108
17/11/2005 20:02:23||Can\'t open temp state file: client_state_next.xml
17/11/2005 20:02:23||Couldn\'t write state file: -108
17/11/2005 20:07:18||Can\'t open temp state file: client_state_next.xml
17/11/2005 20:07:18||Couldn\'t write state file: -108
17/11/2005 20:12:08||Can\'t open temp state file: client_state_next.xml
17/11/2005 20:12:08||Couldn\'t write state file: -108
17/11/2005 20:17:01||Can\'t open temp state file: client_state_next.xml
17/11/2005 20:17:01||Couldn\'t write state file: -108

---

It could be a number of things Yannis:

• you\'ve lost write access to the BOINC directory.
  
• there\'s a read-only client_state_next.xml file in your BOINC directory.
  
• you\'ve run out of disk space.
  

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

It could be a number of things Yannis:

• you\'ve lost write access to the BOINC directory.
  
• there\'s a read-only client_state_next.xml file in your BOINC directory.
  
• you\'ve run out of disk space.
  

Thank you for your reply. I have discovered that I could not access the BOINC folder. After a quick reboot the project was up and running again with no glitch. Despite the unusual error message as described in my original posting, the computations were actually running ( I run the \"Show graphics\" option and it was registering timesteps every 2 seconds).

Thank you once again for your reply.

---

It could be a number of things Yannis:

• you\'ve lost write access to the BOINC directory.
  
• there\'s a read-only client_state_next.xml file in your BOINC directory.
  
• you\'ve run out of disk space.
  

Thank you for your reply. I have discovered that I could not access the BOINC folder. After a quick reboot the project was up and running again with no glitch. Despite the unusual error message as described in my original posting, the computations were actually running ( I run the \"Show graphics\" option and it was registering timesteps every 2 seconds).

Thank you once again for your reply.

Yannis, you are not on any team why not join team \"GREECE\".................

---

Yannis, you are not on any team why not join team \"GREECE\".................[/quote]

Hi,
Thanks for the invite, I\'ll take you up on that. We may even climb up one place on the stats!!!

---