Stato server SetiBoinc

[SoulStealer]

SETI@home - 2005-06-13 19:25:51 - Started download of 05no03aa.15866.13746.361092.201
SETI@home - 2005-06-13 19:26:04 - Finished download of 05no03aa.15866.13746.361092.201
SETI@home - 2005-06-13 19:26:04 - Throughput 29214 bytes/sec
SETI@home - 2005-06-13 19:27:08 - Started download of 05no03aa.15866.13746.361092.205
SETI@home - 2005-06-13 19:27:13 - Started download of 05no03aa.15866.13794.23560.12
SETI@home - 2005-06-13 19:27:25 - Finished download of 05no03aa.15866.13746.361092.205
SETI@home - 2005-06-13 19:27:25 - Throughput 22021 bytes/sec
SETI@home - 2005-06-13 19:27:30 - Finished download of 05no03aa.15866.13794.23560.12
SETI@home - 2005-06-13 19:27:30 - Throughput 24006 bytes/sec
SETI@home - 2005-06-13 19:30:29 - Started download of 13ja05aa.16827.15392.490894.11
SETI@home - 2005-06-13 19:30:30 - Started download of 13ja05aa.16827.15392.490894.7
SETI@home - 2005-06-13 19:30:44 - Finished download of 13ja05aa.16827.15392.490894.7
SETI@home - 2005-06-13 19:30:44 - Throughput 25999 bytes/sec
SETI@home - 2005-06-13 19:30:48 - Temporarily failed download of 13ja05aa.16827.15392.490894.11
SETI@home - 2005-06-13 19:30:48 - Backing off 5 minutes and 23 seconds on transfer of file 13ja05aa.16827.15392.490894.11
SETI@home - 2005-06-13 19:31:02 - Started download of 13ja05aa.16827.15392.490894.11
SETI@home - 2005-06-13 19:31:14 - Finished download of 13ja05aa.16827.15392.490894.11

[lanfste]

Originariamente inviato da SoulStealer

SETI@home - 2005-06-13 19:25:51 - Started download of 05no03aa.15866.13746.361092.201
SETI@home - 2005-06-13 19:26:04 - Finished download of 05no03aa.15866.13746.361092.201
SETI@home - 2005-06-13 19:26:04 - Throughput 29214 bytes/sec
SETI@home - 2005-06-13 19:27:08 - Started download of 05no03aa.15866.13746.361092.205
SETI@home - 2005-06-13 19:27:13 - Started download of 05no03aa.15866.13794.23560.12
SETI@home - 2005-06-13 19:27:25 - Finished download of 05no03aa.15866.13746.361092.205
SETI@home - 2005-06-13 19:27:25 - Throughput 22021 bytes/sec
SETI@home - 2005-06-13 19:27:30 - Finished download of 05no03aa.15866.13794.23560.12
SETI@home - 2005-06-13 19:27:30 - Throughput 24006 bytes/sec
SETI@home - 2005-06-13 19:30:29 - Started download of 13ja05aa.16827.15392.490894.11
SETI@home - 2005-06-13 19:30:30 - Started download of 13ja05aa.16827.15392.490894.7
SETI@home - 2005-06-13 19:30:44 - Finished download of 13ja05aa.16827.15392.490894.7
SETI@home - 2005-06-13 19:30:44 - Throughput 25999 bytes/sec
SETI@home - 2005-06-13 19:30:48 - Temporarily failed download of 13ja05aa.16827.15392.490894.11
SETI@home - 2005-06-13 19:30:48 - Backing off 5 minutes and 23 seconds on transfer of file 13ja05aa.16827.15392.490894.11
SETI@home - 2005-06-13 19:31:02 - Started download of 13ja05aa.16827.15392.490894.11
SETI@home - 2005-06-13 19:31:14 - Finished download of 13ja05aa.16827.15392.490894.11

Azz.

[Alvarone]

Niente da fare , per ora acccccccccccccccc....

Xeon fermo da ieri sera.
1 dei 3200 si ferma tra un po'
portatile appena aggiunto , mai partito aveva solo 1 WU
se non mi scarica questa sera , domani fermo quasi tutta la mandria .

Son stato poco previdente ai ai ai
Ma siamo fiduciosi

[trekfan1]

Ogni tanto se si ha fortuna qualcosa si scarica, ma bisogna sperare di trovare il momento buono

[Michele]

Io per fortuna un paio di macchine le ho salvate oggi, e sono riuscito ad uppare parecchie wu fatte, cmq ho l'impressione che non ci stanno capendo ben poco di cosa succeda alle macchine a Berkeley, appena il carico inizia a salire crolla tutto.....

[GHz]

Dalla tech news sembra che il problema sia nel carico e nelle poche macchine a disposizione...

June 13, 2005 - 19:00 UTC
There have been many failures over the past week. Another bug was found (and quickly patched) in our upload/download file server causing it to hang until reboot. Once that was remedied, both the scheduling server and the main web server had separate issues due to extremely high load.

In case you haven't noticed, we recently changed the URL setiathome.ssl.berkeley.edu - instead of pointing to the old SETI@home "classic" project, it now leads users to the new BOINC-based version. As expected, this vastly increased the number of new users joining the BOINC project, and therefore increased the strain on our back-end servers. Soon we will stop new classic account sign-ups altogether, and eventually stop accepting classic results outright (with advance warning) - each step potentially increasing the demands on our hardware.

At this exact point there is no new hardware that BOINC could use as its various servers fail for one reason or another. This is because the classic project is still active and using up half of our server farm. This was soon change.

The classic "master science database server" (a 6 CPU Sun E3500) will be the first machine to be repurposed. We're busy migrating most of its data onto a new database server (an 8 CPU E3500). This migration had been slowed by recent (recoverable) disk failures, but should finish in a month or so. Before then, however, we are going to move the BOINC scheduler onto it. The actual file upload/download handler will remain on its current server, thereby spreading the whole scheduler system over two machines.

As soon as possible, we will add a second webserver (and maybe a third). The BOINC web site contains far more dynamically-generated content than the classic site, and therefore needs more power behind it. We don't really have any spares, so some machines will have to double as web servers and whatever else they are currently doing.

And as if that wasn't enough to worry about, the BOINC replica database has continually fallen further and further behind the master database (because the load on the master increases and the replica hardware is relatively inferior). Then yesterday it was rendered useless as a binary log on the master got corrupted. This didn't damage the master database - only the replica. So we're going to have to build the replica from scratch (or hold off until we somehow obtain between hardware for that).

More to come as things progress...

Chiudendo il classic sale il carico su BOINC quindi devono procedere in maniera graduale con casini vari......ma io dico, cavolo, chiudetelo il classic, si sta fermi una settimana ma poi almeno si va.......boh

[Luca DellOca]

Originariamente inviato da GHz

Chiudendo il classic sale il carico su BOINC quindi devono procedere in maniera graduale con casini vari......ma io dico, cavolo, chiudetelo il classic, si sta fermi una settimana ma poi almeno si va.......boh

Pienamente d'accordo, perche' non lo proponi sul forum?

E poi questa tanto sbandierata stabilità delle macchine Sun, se un server ha un carico estremo ma e' stabile, rallentera' enormemente le sue prestazioni, ma non va in crash!!!

Ciao, Luca.

[Michele]

Originariamente inviato da GHz

Dalla tech news sembra che il problema sia nel carico e nelle poche macchine a disposizione...

Chiudendo il classic sale il carico su BOINC quindi devono procedere in maniera graduale con casini vari......ma io dico, cavolo, chiudetelo il classic, si sta fermi una settimana ma poi almeno si va.......boh

In questo modo non va bene nessuno dei due sistemi.... mah!

[Alvarone]

Allora altro che fiduciosi.... ho letto ora.
Dati non ne danno?
Es: Quanti utenti sono entrati , host ecc. ecc.
quale sono i limiti.

Il loro sistema non rallenta , si pianta proprio .

Appoggio la proposta sul forum, se serve posto anche io.

[Michele]

Che impennata.... reggera? si accettano scommesse...

[GHz]

Originariamente inviato da Michele

http://www.net.berkeley.edu:8885/~cr...=151200;rand=3

Che impennata.... reggera? si accettano scommesse...

Omamma.....90Mbit....

[Michele]

E' un pezzo che non arriva cosi' in alto, speriamo sia un buon segno...

[attackment]

[GHz]

Originariamente inviato da Michele

E' un pezzo che non arriva cosi' in alto, speriamo sia un buon segno...

Già, pare di si...ora ho uppato e sta scaricando parecchie WU

[GHz]

Porc è crollato

Edit: pare ripartito.....

[Michele]

Comunque anche qualche credito non ci starebbe male...

[GHz]

Incredibile ma vero da qualche ora va alla grande.....il backlog del transitioner e le wu da validare stanno calando....tutti a rifare le cache

[Corazzata Be-Spi]

Ho appena scaricato e ricaricato, oggi pomeriggio si parte con il bombardamento a tappeto!!!!

[trekfan1]

Da un mio calcolo direi che entro stasera alle 19 ora italiana (ora più, ora meno) dovrebbe essere tutto a posto (salvo imprevisti ma facciamo gli scongiuri)

[mg13]

Originariamente inviato da GHz

Dalla tech news sembra che il problema sia nel carico e nelle poche macchine a disposizione...

June 13, 2005 - 19:00 UTC
There have been many failures over the past week. Another bug was found (and quickly patched) in our upload/download file server causing it to hang until reboot. Once that was remedied, both the scheduling server and the main web server had separate issues due to extremely high load.

In case you haven't noticed, we recently changed the URL setiathome.ssl.berkeley.edu - instead of pointing to the old SETI@home "classic" project, it now leads users to the new BOINC-based version. As expected, this vastly increased the number of new users joining the BOINC project, and therefore increased the strain on our back-end servers. Soon we will stop new classic account sign-ups altogether, and eventually stop accepting classic results outright (with advance warning) - each step potentially increasing the demands on our hardware.

At this exact point there is no new hardware that BOINC could use as its various servers fail for one reason or another. This is because the classic project is still active and using up half of our server farm. This was soon change.

The classic "master science database server" (a 6 CPU Sun E3500) will be the first machine to be repurposed. We're busy migrating most of its data onto a new database server (an 8 CPU E3500). This migration had been slowed by recent (recoverable) disk failures, but should finish in a month or so. Before then, however, we are going to move the BOINC scheduler onto it. The actual file upload/download handler will remain on its current server, thereby spreading the whole scheduler system over two machines.

As soon as possible, we will add a second webserver (and maybe a third). The BOINC web site contains far more dynamically-generated content than the classic site, and therefore needs more power behind it. We don't really have any spares, so some machines will have to double as web servers and whatever else they are currently doing.

And as if that wasn't enough to worry about, the BOINC replica database has continually fallen further and further behind the master database (because the load on the master increases and the replica hardware is relatively inferior). Then yesterday it was rendered useless as a binary log on the master got corrupted. This didn't damage the master database - only the replica. So we're going to have to build the replica from scratch (or hold off until we somehow obtain between hardware for that).

More to come as things progress...

C'è un'anima pia che mi può tradurre per piacere, grazie.