Seti for BOINC info after latest outage.

[Rattledagger]

February 3, 2005 - 23:30 UTC
Around 12:40 UTC today the BOINC database server didn't crash as much as hang there doing nothing, spinning on hundreds of threads (and prohibiting any new connections). After hours of troubleshooting we had to kill it ungracefully which resulted in several hours of rebooting and recovery. Eventually, we were able to get back on line with (seemingly) everything intact.

There remains two outstanding issues, though. The current database continues to produce heavy I/O for no obvious reason, and we still need to migrate it all the data to the new server (this task is slated for this upcoming Monday).

 

[Wolfsraider]

Thanks Rattledagger

 

[Dalephi]

Thanks Rattledagger.

 

[kamper]

Thanks Rattledagger. I find it difficult to interpret all the news that's been coming in this vein. On one hand, it seems like they're so close to being able to kill classic any time they wish, but, in some ways, it seems like they're so far from being stable that it's no different from anything we've experienced over the past year or so (about the time that I've been doing classic 😛).

 

[Rattledagger]

Well, don't know the problem with the new database-server, but since they're planning to try upgrading to this again next week they're hopefully solved the problem...

After new database-server is running stable, must also make sure the rest of the services is keeping up with demand.
They're not planning to shut down "classic" before can handle the load of 500k more users...



BTW, in the Taskbase, M2 is "Decommission Old SETI@home", and this target is met when separate gui is released, but have also added the hardware-requirement.

They're planning to release the client in 2-3 weeks time...