Inhoudsopgave Seti@Home hitparades week 40
- DPC SETI@Home hitparade van 03 oktober 2010*
- DPC SETI@Home hitparade van 04 oktober 2010*
- DPC SETI@Home hitparade van 05 oktober 2010*
- DPC SETI@Home hitparade van 06 oktober 2010*
- DPC SETI@Home hitparade van 07 oktober 2010*
- DPC SETI@Home hitparade van 08 oktober 2010*
- DPC SETI@Home hitparade van 09 oktober 2010
Wat is Seti@Home ?
Wat is SETI@home?
SETI@home is de naam van een wetenschappelijk experiment dat computers die via het internet met elkaar verbonden zijn, inzet om buitenaardse intelligentie op te sporen. U kunt hieraan deelnemen middels een gratis computerprogramma dat radiotelescoop-data download en analyseert.
BELANGRIJK: wekelijks driedaagse server outage
Weekly Outage and Initial Catch Up
Every Tuesday morning (Pacific time) we begin a 3 day data distribution outage to focus on science processing and development plus any needed systems maintenance. The upload/download servers will be offline during this time. The web site (including the forums) will only be offline during the database maintenance and backup portion of the outage. On Friday, you may experience connectivity issues as the servers catch up with demand.21 Sep 2010 17:01:37 UTC
6 Oct 2010 17:57:16 UTC
It's been a painful week, but with some progress.
The server run before last was cut short by our upload space filling up. That was fixed by the bruno migration and we started the last server run a bit early.
But a crash of our primary boinc db machine, mork, got the secondary db server, jocelyn, out of sync. That meant that all of the read only queries had to go to mork instead of jocelyn. This overwhelmed mork and I turned off web access just so the server run could continue. Then mork crashed again Monday evening. Ouch.
Yesterday, we did our normal backup of mork and are recovering jocelyn from that today. The forums are up, but result viewing is disabled at the moment. We need to clear the back end queues ahead of the next server run and mork resources are needed for that.
Mork's tendency to crash seems to have accelerated. Perhaps this is secondary to the cooling crisis we had a couple of weeks ago. Actually, "crash" is not the correct term. It simply hangs and requires a power cycle to boot. Fortunately, we have mork on a networked power strip and can power cycle it remotely. Upon boot, there are no footprints whatsoever as to the cause of the hang. This sounds like hardware. So today we are going to bring mork down to swap out all of the memory and remove a couple of unused components in a desperate attempt to fix the problem. The forums of course will be down during this operation.
[Voor 26% gewijzigd door APClll op 09-10-2010 15:51]