... until we ran out of work to send out. Turns out the last 10 files I brought up from Arecibo are all broken. <sad trombone>Fwa wa wa waaaaa</sad trombone>. This is particularly frustrating as I was busting my hump trying to get enough work on line before the long holiday weekend, and now we have zero. So it'll be to me and Jeff to check in over the next few days and kick the pipeline along. We'll be out of real work to send out until this evening at the earliest, and quite probably hit long periods of no work throughout the weekend. Fine.

Oh well, we tried. We thought we would just have to put some extra minutes monitoring the data pipeline over the weekend (after wasting a lot of time bringing up many broken files), which wouldn't have been too bad, but...

Then bambi crashed last night - it's our secondary science database server but also manage a lot of the data pipeline stuff. I happened to be free so I drove up to the lab around 10:30pm and rebooted it. After that, the pipeline zipped right along.

That is... until 11pm when the router up and died. Or something along the entire Hurricane Electric network path died. We have no idea. Jeff and I fought with it (both remotely) this morning, but we're throwing up our hands at this point and going on holiday.

Might as well have everything fail at once, and at the start of a long holiday weekend. Why not?

- Matt

November 27, 2009
The connectivity problem noted yesterday turned out to be one of our switches and not the router. We swapped in a replacement switch today and connectivity was restored.

After 10 solid days, Collatz seems to have gone walkabout -- I hadn't tracked their homepage over the past couple of days, so I don't know if this outage is a planned one.

Make that 40 hours for Collatz -- I'm hoping that whatever took Slicker away from the project (I'm assuming that the extended outage is a combination of one or more problems with his server AND him being called away to other matters) is both a short term event and one not strewn with bad news (personal or project wise).

Seti@Home is down for maintenance. The forums and scheduler are off line. And it's not even Tuesday.

Temporary Outage
Our database work has progressed to the point where we are bringing up SETI@Home. Astropulse remains offline.

Temporary Outage
Both SETI@Home and Astropulse work production have been halted in order to give database resources to the repairing of a large Astropulse table.

December 10, 2009
Parts of the project were taken offline for some cleanup necessary to fix the recent scheduler http problems. We hoped that this could be done within minutes and thus remain unnoticed for most users, but it looks like it will take another hour or two until the scheduler is running again.

Einstein News wrote:

December 10, 2009
Parts of the project were taken offline for some cleanup necessary to fix the recent scheduler http problems. We hoped that this could be done within minutes and thus remain unnoticed for most users, but it looks like it will take another hour or two until the scheduler is running again.

GPUGRID is offline from every aspect i've looked at.... switching to back up project collatz and seti for nvidia gtx 260 FOC.