Not had any units for the past few days, and as much as I like seeing -15C idle temps, I’d rather my CPU was loaded.
Getting really bored of it being up and down so much.
Rys
SETI@home - 2004-07-21 09:38:52 - Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-07-21 09:38:55 - Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-07-21 09:38:55 - Message from server: Server can’t open log file
SETI@home - 2004-07-21 09:38:55 - Project is down
:rolleyes:
I think it adds a little piqancy to the project, living on the edge, wondering if your crunchers will get through the day. :spin: Hoping that you’ve managed to download more WUs than your nearest rival. :rotate:
Just up your cache to something obscene :nod: 
My cache was set to 10 days, but I’m down to my last unit and am now getting the project down message 
running low here too now
The Lifemapper servers are still up though 
DT.
I’ve had to turn one of my rigs OFF today as no new WUs have been downloaded for a few days now and look unlikely to before tonight
:eek: @ Donna. Try a bit of classic. It all adds to the stats. 
Chin up Guys,
I have set 9-10 days and have also run out on my main Cruncher, it will be the same for everyone it was those units that were coming out with large completion times that lowered my cache right down.
Hopefully they will be gone now, so we can fill our boots when the work is available.
I’ve just done a massive check round all my crunchers, seems I should be fine for today. 
They must haved picked up a few units overnight 
, but not got time to check the logs to see.
As you rightly point out M@tt, I think they are clearing out those silly timing wu’s. As always though, communication not there again
DT.
Teething troubles, bear with it guys and it’ll be oooookay
I ended up back on Classique today, with Boinc bonging away periodically looking for work. No drama - at least it was doing something!
Look on the bright side - the software is working, its the servers which are letting us down. And I can’t see that changing massively until they finally pull the plug on SETI 1 - because that is what the main web & server “big iron” is doing at the moment.
Three days on one and only half a days worth on the second. If only we could move WUs between machines.
Luckily I have quite a lot of predictor units to keep me going until the server comes up again.
yeah, teething problems imo as well, and totally agree with you Mojo. The sooner they pull the plug on seti classic the better Boinc should get. Either that or they are still waiting on the MAOJC donation of hardware.
Proving a pain to test out my delve into linux and diskless when there is no work though
DT.
July 21, 2004
The log files are currently being compressed, after thats done the project should return to normal.
Soon maybe, it will be up again
The other problem is I’ve uninstalled SETI1 totally and I don’t want to start it up again if I can help it. I’m still running Folding as a project to keep the CPU cycles ticking over, but I’d rather crunch SETI. It’s very frustrating.
SETI@home - 2004-07-21 20:16:13 - Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
Ah but is there any work
Getting a little desperate here now despite Mrs B’s help this afternoon in switching my main home rig off because it was making a funny noise :Bless:
Yes the third case fan kicked in and the CPU fan went to full chat because it was getting too warm. :rolleyes:
Anyone else got some little helpers
2004-07-21 21:19:20 [Predictor@home] Sending request to scheduler: http://predictor.scripps.edu/predictor_cgi/cgi
2004-07-21 21:19:20 [Predictor@home] Scheduler RPC to http://predictor.scripps.edu/predictor_cgi/cgi succeeded
2004-07-21 21:19:20 [Predictor@home] Message from server: Project is temporarily shut down for maintenance
2004-07-21 21:19:20 [Predictor@home] Project is down
2004-07-21 21:19:20 [Predictor@home] Project is down
2004-07-21 21:19:20 [Predictor@home] Deferring communication with project for 1 hours, 0 minutes, and 0 seconds