BarryAZ, I am an old-timer, too - I began crunching for Seti in 2000, long before Berkeley developed the BOINC framework. I still crunch a small amount for Seti, but have shifted focus to other projects; it became too burdensome to troubleshoot the Seti optimized clients, particularly since the Mac OS is not a focal point for Seti. So, once, GPU apps were released by Einstein and Collatz, I shifted a lot of my effort there.

I'd note that Collatz is still offline. It as almost he stopped by two weeks ago, said, 'oh heck, I'll give more shot with a server restart' -- and left.

He might simply be getting on with life. 6 years is a long run for a single operator project.

At one point I was running ATI 4550 and 4650's. I still have one workstation reporting work (on moo) that way.

Over time I've cycled out the older cards -- first to ATI 4850's and then to ATI 6750's and 7850's.

These days, when I replace an ATI 4850 it typically has been with a GTX 750ti.

Those systems are running mostly GPUGrid.

Again, it would be a shame if Slicker pulled the plug on the project. Once we get passed the Martin Luther King Jr holiday, I will look to see if Slicker gives us some sign that the project is coming back online.

WUProp@home is currently down.

The web site pages say that "The project's database server is down" and (unsurprisingly) scheduler requests are failing:

21/01/2015 12:39:25 | WUProp@Home | Reporting 1 completed tasks, requesting new tasks for CPU
21/01/2015 12:39:27 | WUProp@Home | Scheduler request completed: got 0 new tasks
21/01/2015 12:39:27 | WUProp@Home | Server error: feeder not running

Collatz was up for a short time last night but is down again. There was a very short note about the problem on the home page which I will try to paraphrase here. Unfortunately, I did not read it as carefully as I now wish.

Basically, it has been a recurring problem with DB indexing that is somehow related to the nightly back-up process. They rebuild the indexes and attempt to replicate the problem, but haven't been able to. Then the problem comes back later and crashes the server again. In other words, they are still scratching their heads.

Stick -- note, it is not a 'they' Slicker is a one man shop there.

Collatz was up for a short time last night but is down again. There was a very short note about the problem on the home page which I will try to paraphrase here. Unfortunately, I did not read it as carefully as I now wish.

Basically, it has been a recurring problem with DB indexing that is somehow related to the nightly back-up process. They rebuild the indexes and attempt to replicate the problem, but haven't been able to. Then the problem comes back later and crashes the server again. In other words, they are still scratching their heads.

And this basically boils down to:
"Open the source code and build a community or die"

Switched to Einstein.

---

WuProp is up

Stick -- note, it is not a 'they' Slicker is a one man shop there.

Thanks! I imagine he is a very busy man right now.

I've been a Collatz member for several years now and until recently it has run like clockwork. Hope he can figure things out!

WuProp is down again

WuProp is down again

Back up

Collatz is back up again!

And back down -- I suspect he's got a hardware intermittent -- since his logs don't provide any enlightenment.

Collatz is back up again!

LHC@home doesn't supply new scores to statistics servers for last 5 days.

LHC@home doesn't supply new scores to statistics servers for last 5 days.

It could be worse http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=2206

CPDN Scheduled downtime 29-30 January 2015

Jonathan Miller says:

I have to schedule some project downtime this week, 29 & 30 Jan 2015.

This is so that we can configure the underlying hardware to accept a tape backup system as part of the 'near-line' storage.

I will taking the opportunity to move the database backup to a different server, to make us more resilient in case of failure of the above hardware.

The downtime ought to be no more than a few hours on Thursday, but I have said that many times before!

As in the CPDN thread:

The scheduled [CPDN] downtime has been pushed back a week and will now be on Thursday 5th and Friday 6th February.

Einstein@Home

"[Later] today we're going to shutdown the project for at most 1-2 hours to deploy important security fixes on our infrastructure. 28 Jan 2015"

Looks like the shutdown has already taken place, but they're having difficulty bringing it back up - all services are disabled or showing errors.

Einstein@Home is back up - Oliver says:

I updated 19 servers and gateways in two data centers in the past seven hours, fixing the Ghost CVE, upgraded kernels, updated our master/slave databases and deployed pending package updates.

CSG@Home is down