Server Outages

Thanks Tom. I turned my machine back on and updated the project (clicked "Update" in the Boinc client). I had a long list of finished work, but it just disappeared, and I instantly had a lot of new work. Did all my work count?

I didn't delete any workunits, so everything that you did should count. There is a huge backlog of work that is waiting to be validated, so that will cause completed work to trickle in over the next couple days.

I did re-number the workunit IDs on the database though, so maybe that's causing glitches on the client's end -- your client might be looking for workunit IDs that don't exist anymore?

Ok. I was just checking. I had the computer off and turned it back on, but it may have just sat there by itself for longer than I realized and synced everything. Just wanted to be sure nothing got lost or garbled.

Thank you for all the work put into this... And in my case it was done just in time too, doing just CPU work, still had 5 WUs when I could connect again and get more :)

But I'm guessing that this didn't also involve a cleanup of old "stuck" results? Because I see a total of 125 tasks among mine, if I counted right, stuck there since late Jan to Feb 2.

Pending is falling quickly. Thanks for working on the server.

Merry Christmas

Any update from the admins why the project went missing for a day?

---

Hey there, we're trying to figure it out. Restarted the server, it came back up, then crashed again. This doesn't seem related to previous outages.

Just now got all 3 computers running again. They are grinding away on MW@home.

Hey there, we're trying to figure it out. Restarted the server, it came back up, then crashed again. This doesn't seem related to previous outages.

Facilities maintenance pulled the server plug out of the socket to dust behind the rack, ha ha hah. LOL.

---

not getting CPU tasks, only GPU

---

Facilities maintenance pulled the server plug out of the socket to dust behind the rack, ha ha hah. LOL.

I once restarted a server rack after it had been moved after major building work. I knew there would be quite a lot of dust in it. I also knew that the servers start up with full blast on all fans. So I got one of the builders to peer into the back of it to "check something". An enormous cloud of dust covered his face entirely. I suggested they not create so much dust near delicate equipment in future.

Facilities maintenance pulled the server plug out of the socket to dust behind the rack, ha ha hah. LOL.

I once restarted a server rack after it had been moved after major building work. I knew there would be quite a lot of dust in it. I also knew that the servers start up with full blast on all fans. So I got one of the builders to peer into the back of it to "check something". An enormous cloud of dust covered his face entirely. I suggested they not create so much dust near delicate equipment in future.

Facilities maintenance pulled the server plug out of the socket to dust behind the rack, ha ha hah. LOL.

I once restarted a server rack after it had been moved after major building work. I knew there would be quite a lot of dust in it. I also knew that the servers start up with full blast on all fans. So I got one of the builders to peer into the back of it to "check something". An enormous cloud of dust covered his face entirely. I suggested they not create so much dust near delicate equipment in future.

LOL... gotta remember that one next time I need to restart my clustered hosts!