Just noticed that these two servers aren't running at the moment . - Checked after seeing a feeder not running error on event log. My understanding is that an email will automagically have been sent about this to those managing the servers.

It is now several days that I couldn't connect to climateprediction.net.
The error message is:

06.04.2017 13:26:11 | climateprediction.net | Server error: feeder not running


Who knows when the server will work again ?
Thanks for some news !
Greetings from Germany
Dr.Mabuse

---

*** Since I'm a fool I prooved that the system is not foolproof ;-) ***

The 2 servers have been done for about a week now, presumably for some work to be done on "something" while there's no work to download.

Who knows when the server will work again ?

The Shadow knows

(And also the IT people who work on our servers.)

It's not the problem that there's no work to download - the problem is that wus on the pcs can't report.

It's not the problem that there's no work to download - the problem is that wus on the pcs can't report.

Yes reporting and trickle up messages don't work but zips are still being uploaded. The project people are aware of this and it is being looked at.

2 tasks are ready for reporting.
But they couldn't get uploaded.

1 task still running for 16 à 17 hours to go

And now working again, just did an update and one task reported, now gone from list of tasks on computer.

I've been getting communication deferred for a few days since i've installed the programme, is this normal quite new to this? :)

... and a reissue of some WUS25/21 models from batch 534 (396 work units vs 363 originally). Gone in a flash.

Hi Kristian,

the communication deferred is a delay put in by the BOINC server programme after an attempt to get work. I think it is set at 1 hour and 1 minute or something close to that. If you don't get any work, don't try again before that time is up as it just resets the clock so if you click on project update again even just before that time is up, it will start again.

Of course in times of work a plenty, there is no need to re-try as it will have downloaded all the work you need.

Hi Dave,

Thanks very much for the info! I was wondering why haha, hopefully can make some contributions soon!

The way cpdn works now-a-days is:
weeks of "no new work" - maybe a few mini-batches and re-issues,

Then, when the various research projects get all their ducks in a row (and think they're ready for prime-time) --
Several huge production batches of work, tens of thousands of workunits running days or weeks each (or even months, for some wu's and slow, part-time machines).

Call it "feast or famine" call it "hurry up and wait" - whatever --

It's how the research projects interact with the volunteer computers on this project.

Me, this is the BOINC project I most support. When CPDN is out of work, I let my mini-farm work on other projects, or do hardware and software upgrades (like the Oxford support group have been doing :)

When there's oodles of work available, I redirect all my local compute capacity to CPDN.

E

---