GIBA, have you suddenly converted a Windows machine to Linux? If not and you've already opted into CEP2 though there is no CEP2 work **, then the client probably will be bounced by 3600 seconds. Think it's been doing that for longer. Seeing it occasionally also when only opting to receive DDDT2 during rainy periods.

edit: ** This is Windows I presume!

Got trouble to understand the specificity to CEP2 to be honest, as my duo which is on HFCC/C4CW, no opting for CEP2 got bounced to 3600 seconds, so I'd like to know what the message log said that led up to this. Mine just happened to get kicked 60 minutes when not able to report a result, noting that I've got extra log flags on to know what is going on:

803 WCG 03-11-2010 15:26 [sched_op] Starting scheduler request
804 WCG 03-11-2010 15:26 Sending scheduler request: To report completed tasks.
805 WCG 03-11-2010 15:26 Reporting 1 completed tasks, not requesting new tasks
806 WCG 03-11-2010 15:26 [sched_op] CPU work request: 0.00 seconds; 0.00 CPUs
807 WCG 03-11-2010 15:26 Scheduler request completed
808 WCG 03-11-2010 15:26 [sched_op] Server version 601
809 WCG 03-11-2010 15:26 Message from WCG: Server can't open database
810 WCG 03-11-2010 15:26 Project requested delay of 3600 seconds
811 WCG 03-11-2010 15:26 [sched_op] Deferring communication for 1 hr 0 min 0 sec
812 WCG 03-11-2010 15:26 [sched_op] Reason: project is down

It was not really down this long, but a defense mechanism by the servers so when the DB does get online again there's not a huge assault of thousands of clients connecting simultaneously.

As to caching, was discussing this with the techs and they feel presently there is no justification to increase the default without substantially risking to increase more tasks not being reported in time. It could also mean that those bigger farms that run default and get re-imaged cyclically, that a lot more tasks get dumped back into the repair queue. Had last week 1 day where my quad had 15 (normal production tasks) which took 3/4 of a day to work through as they were no shorties.

...

While typing see a response. Can't understand how a multi-project profile including CEP2 on Windows or Mac get bounced and not receive work for other projects. That I'd consider a scheduling bug. My thinking is that a combo of Beta(is not a project)+CEP2+DDDT2 on Windows or Mac presently will lead to this... risky if not wanting to have idle cores.

edit: added last para.

hmmm, you are aware of the new CEP2 override or are you not (stickied at top of CEP2 forum) ;>)

Just to avoid any kind of jugdement error about if is a CEP2 or not specific aspect, I would like to ask to tech team migrate this thread for other more apropriated forum, maybe to the BOINC agent support or website support forums. Up to you ! thank you in advance.

Dear vcobz,

Of course we are serious about renewable energy, and that is why we have spent preparing for this project pretty much since 2006 (when we were solo) and 2007 or so when we started talking to IBM. The collaboration with IBM has been amazing as they have been able to port probably one of the most challenging codes (Q-Chem) to the BOINC environment. Quantum chemistry is extremely demanding in terms of RAM, CPU, harddisk I/O than say molecular dynamics or other types of calculations. The efforts from IBM staff to port the code to Windows and Mac have been heroic. If I am correct, still, perhaps besides something that was called nanohive, this is the first time a quantum chemistry package is used at this scale in the BOINC environment.

Launching Linux first allowed us to get more than 300,000 calculations done while the challenges with Windows and Mac have been overcame.

Even data storage is a challenge, we are now working with the Department of Energy to store hundreds of terabytes of results.

We expect our first science publications associated with the effort being submitted in the next few months, and our goal is to produce new suggestions for experimentalists to synthesise new compounds.

This is a multi person, multi year project that is quite challenging. Hang on, we are moving on with the beta testing.

Cheers,

Alan
The Clean Energy Project team