climateprediction.net - 2004-12-28 21:26:24 - Deferring communication with project for 6 days, 16 hours, 18 minutes, and 44 seconds...
I'm getting this error all the time, what is wrong?
Im working with BOINC client version 4.13 on my computer (Pentium-M, 1,5 GHz, Windows XP)

Hmm last trickle 6 Dec. Don't suppose you made any changes to firewall about then did you. You can force an immediate attempt to communicate by going to the project tab and a right click on climateprediction.net should show an update option. What do the messages then say?

---

Visit BOINC WIKI for help

And join BOINC Synergy for all the news in one place.

1. climateprediction.net - 2004-12-29 10:12:09 - Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi

2. climateprediction.net - 2004-12-29 10:12:12 - Scheduler RPC to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded

3. climateprediction.net - 2004-12-29 10:12:12 - Project prefs: no separate prefs for home; using your defaults

I've had the same problem for the past week and a half, and didn't know I could force an update. Forcing the update worked, but I also removed a ZoneAlarm firewall entry related to BOINC before trying the force. Interestingly, the ZoneAlarm entry specifically _allowed_ BOINC to access the Internet. But, I didn't isolate variables, so I'm not quite sure what caused the problem. ;-)

> Hmm last trickle 6 Dec. Don't suppose you made any changes to firewall about
> then did you. You can force an immediate attempt to communicate by going to
> the project tab and a right click on climateprediction.net should show an
> update option. What do the messages then say?
>

Interesting ... now I see on my profile that trickles have been going through despite the message. Or could it be that a set of trickles just now went through when I ran the force?

> I've had the same problem for the past week and a half, and didn't know I
> could force an update. Forcing the update worked, but I also removed a
> ZoneAlarm firewall entry related to BOINC before trying the force.
> Interestingly, the ZoneAlarm entry specifically _allowed_ BOINC to access the
> Internet. But, I didn't isolate variables, so I'm not quite sure what caused
> the problem. ;-)
>
> > Hmm last trickle 6 Dec. Don't suppose you made any changes to firewall
> about
> > then did you. You can force an immediate attempt to communicate by going
> to
> > the project tab and a right click on climateprediction.net should show
> an
> > update option. What do the messages then say?
> >
>

---

Regarding ZoneAlarm problems.
This may have happened because of a changed BOINC version. I've had this problem with another program (FileZilla). The entry was set in ZA for the previous version.
When I removed the entry and ran the program, ZA duly asked if I wanted to grant permission. I did and got everything working again. (though if I remember right, I had to restart FileZilla).

---

Forum search Site search

The server was down from approximately 10.00 UTC 27 March until 12.00 on 29 March.

---