I know that some work was carried out on the cpdn servers over the weekend, and as far as I am aware, we have received news on one of the BB\'s that the project is back up and working.

However, I am continuing to receive these messages:

14/08/2007 17:55:37|climateprediction.net|Fetching scheduler list
14/08/2007 17:55:59||Project communication failed: attempting access to reference site
14/08/2007 17:56:00||Access to reference site succeeded - project servers may be temporarily down.
14/08/2007 17:56:02|climateprediction.net|Deferring communication for 1 days 0 hr 0 min 0 sec
14/08/2007 17:56:02|climateprediction.net|Reason: 15 consecutive failures fetching scheduler list


Is it me or my setup or a more general problem? Does anyone have any suggestions of a fix if it is just down to me?

---

I know that some work was carried out on the cpdn servers over the weekend, and as far as I am aware, we have received news on one of the BB\'s that the project is back up and working.

However, I am continuing to receive these messages:

14/08/2007 17:55:37|climateprediction.net|Fetching scheduler list
14/08/2007 17:55:59||Project communication failed: attempting access to reference site
14/08/2007 17:56:00||Access to reference site succeeded - project servers may be temporarily down.
14/08/2007 17:56:02|climateprediction.net|Deferring communication for 1 days 0 hr 0 min 0 sec
14/08/2007 17:56:02|climateprediction.net|Reason: 15 consecutive failures fetching scheduler list


Is it me or my setup or a more general problem? Does anyone have any suggestions of a fix if it is just down to me?

I re-established contact on Sunday afternoon and have had normal service since. Looks like it may be at your end. Try stopping and re-starting Boinc.

It\'s definitly at your end. This server was also \'down\', and you wouldn\'t be able to post here if it was still a problem.

As well as stop/start BOINC, try a computer re-boot, as this often fixes problems.

---

Backups: Here

Thank you for your responses. However, I am running 3 PC\'s, I have re-started BOINC on all of then and re-booted all of them and still have a problem.

I Have also tried manually pinging the climateprediction.net site with two different IP addresses: 137.108.64.198 and 137.108.64.33 and got no responses from either ping and have noticed that some of the message boards do not work. So I do wonder if some of the servers are up and some are down leading to some kind of intermittent problems.

Can anyone from the project please give any advice?

---

This is the server status page.

And whatever happened to your computers, appears to have happened soon after the 10th of August, as this is when all 3 last contacted the server.

What changes did you make about then, or the 11th, 12th? (The servers all come back on the 12th.)
Update the firewall program? Change your ISP?

What are the hostnames you\'re trying to ping? Perhaps there is a stale DNS cache entry somewhere which your network is picking up (try rebooting your router if it caches DNS entries).

Note that climateprediction.net isn\'t one of the servers affected by the weekend\'s work, since it\'s hosted at the Open University rather than Oxford University.

---

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

Yes, I know, I can see the server status page and can see that is shows the servers as being up.

But I can\'t ping the servers, if indeed the IP addresses I got from WhoIs search are correct. This seems to indicate there is some sort of problem.

On my main PC I am running Vista and IE 7. On my other PC\'s I am running Win XP and IE6 and IE7.

Also just typing http://climateprediction.net into a web browser can\'t get through to the server. (Well it couldn\'t from home this morning, but it can now from work (over a proxy server).

And no, I didn\'t change the computers at that time - any of them.

I will check McaFEE again when I get home and try to re-boot my wireless router, but all other internet activity is working fine.

---

Mike, I am pinging the IP addresses directly. I will try to re-boot the router when I get home tonight.

Thnkas for your efforts.

---

Can you let me know the IP addresses of the servers that BOINC tries to contact when trying to send trickles throughl, and I can try and ping those directly.

I did try and re-connec to climateprediction.net through BOINC on 1 PC this morning but couldn\'t get through.

---

Can you let me know the IP addresses of the servers that BOINC tries to contact when trying to send trickles throughl, and I can try and ping those directly.

climateapps2.oucs.ox.ac.uk

---

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

For reference the IP for climateapps2 is 163.1.13.17 (subject to change, of course). This is hosted at Oxford University.

Ping / tracert / etc will sometimes be blocked by firewalls, although normal traffic gets through OK.

--- Edit: What I mean here is the firewall at the Open University blocks ping and tracert. Although it\'s a good idea to check your own firewall as well, since it\'s a potential culprit.

---

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

Thanks, I\'ll try when I get home tonight, after re-booting my router and checking the McAfee firewall.

---

Thank you all. Re-booting the router did the trick.

---

Excellent news, glad everythings working now. :-)

What I think happened is that the router stores DNS queries (translating from the hostname to the IP address, for the people who aren\'t familiar with this). Some routers notice that a site is down (unroutable), and store this information in order to avoid doing \'unnecessary\' DNS queries to the ISP DNS server.

The trouble is that when the site goes back up, the router doesn\'t know it\'s now back on the net, and keeps rejecting the DNS queries as unroutable.

A very similar problem is when the IP for a hostname changes, but the routers keep supplying the old IP address rather than the new one.

---

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

I had a similar situation, only not with climateprediction.net. I have a Linksys wireless router, and sometimes, for unknown reasons to me (probably explained now by Mike), certain sites would become unreachable, and remain unreachable even after I knew they were up. Resetting the router would fix the problem. A firmware update to the router stopped this behavior.

Well you seemto have hit the nail on the head. I too have a Linksys wireless router, but haven\'t noticed the behaviour before.

Well, back to normal now. And thanks again.

---