Wöchentliche Outage diesmal nicht Mittwoch, sondern Donnerstag?

AndyK

Vice Admiral Special
Mitglied seit
07.01.2006
Beiträge
758
Renomée
18
Matt Lebofsky schrieb:
Doing it (adR: die Outage) twice a week is only to get around pathological problems as of late. It'll be better in general to do it once a week as long as everything is okay. Of course, this week we'll probably do another on Thursday for the reasons already suggested elsewhere in this thread.

Each outage helped shrink the size of the database, making it faster. It was up the 31GB. Then each outage brought it to 25GB, then 19GB, then finally 13GB today. The servers are much, much happier now. It was all excess results that had to get pushed through the back end of the queue, and we still have an extra million kickin' around, so we'll hopefully be even smaller come Thursday.

- Matt

Nachzulesen hier.

AndyK
 
oder vieleicht doch heute ???

January 13, 2006
There have been numerous but very brief network drop outs over the past few days affecting all of the Space Sciences Lab. This turned out to be a problem with the SSL firewall and is hopefully fixed at this point.

http://setiathome.berkeley.edu/index.php

das BOINC Forum brauch auch ewig und 2 Tage...

15.01.2006 23:07:44||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
15.01.2006 23:07:44|SETI@home|Temporarily failed download of 24my03ab.1783.7569.367328.1.94: system I/O
15.01.2006 23:07:44|SETI@home|Backing off 1 hours, 29 minutes, and 28 seconds on download of file 24my03ab.1783.7569.367328.1.94

fiel das erste mal

15.01.2006 04:03:28|SETI@home|No work from project
15.01.2006 04:13:38|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
15.01.2006 04:13:38|SETI@home|Reason: To fetch work

auf, scheint nen grösseren Prob zu sein denn

http://setiathome.berkeley.edu/sah_status.html

alles auf grün und 1,500,007 WUs are ready to send...

hier sieht man zwar Probs

http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html

aber nicht zu dieser Zeit

ping geht auch

C:\Dokumente und Einstellungen\ulli>ping setiboincdata.ssl.berkeley.edu

Ping setiboincdata.ssl.berkeley.edu [66.28.250.125] mit 32 Bytes Daten:

Antwort von 66.28.250.125: Bytes=32 Zeit=213ms TTL=239
Antwort von 66.28.250.125: Bytes=32 Zeit=217ms TTL=239
Antwort von 66.28.250.125: Bytes=32 Zeit=213ms TTL=239
Antwort von 66.28.250.125: Bytes=32 Zeit=214ms TTL=239

Ping-Statistik für 66.28.250.125:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 213ms, Maximum = 217ms, Mittelwert = 214ms

C:\Dokumente und Einstellungen\ulli>

und tracert

C:\Dokumente und Einstellungen\ulli>tracert setiboincdata.ssl.berkeley.edu

Routenverfolgung zu setiboincdata.ssl.berkeley.edu [66.28.250.125] über maximal
30 Abschnitte:

1 1 ms 1 ms 1 ms 192.168.0.22
2 47 ms 48 ms 70 ms 212-62-80-254.teleos-web.de [212.62.80.254]
3 * 46 ms 47 ms m5-re.dts-online.net [212.62.64.3]
4 57 ms 57 ms 56 ms rmws-blfd-de01-gigaet-0-1-0-0.nw.mediaways.net [
195.71.225.169]
5 59 ms 80 ms 100 ms rmws-blfd-de03-gigaet-0-3-0-0.nw.mediaways.net [
195.71.97.117]
6 59 ms 58 ms 57 ms rmwc-gtso-de01-pos-5-0.nw.mediaways.net [195.71.
224.57]
7 58 ms 57 ms 58 ms rmwc-frnk-de01-pos-1-0.nw.mediaways.net [195.71.
254.122]
8 56 ms 57 ms 58 ms rmws-frnk-de07-pos-6-0.nw.mediaways.net [213.20.
249.202]
9 54 ms 54 ms 54 ms po1-0.core01.fra03.atlas.cogentco.com [80.81.192
.63]
10 58 ms 79 ms 57 ms p3-0.core01.ams03.atlas.cogentco.com [130.117.0.
145]
11 75 ms 64 ms 65 ms p5-0.core01.lon02.atlas.cogentco.com [130.117.1.
225]
12 165 ms 146 ms 144 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0
.46]
13 166 ms 164 ms 199 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.11
0]
14 211 ms 211 ms 250 ms p5-0.core01.sfo01.atlas.cogentco.com [66.28.4.18
5]
15 212 ms 236 ms 233 ms UC-Berkeley.demarc.cogentco.com [66.250.4.74]
16 211 ms 212 ms 238 ms 66.28.250.125

Ablaufverfolgung beendet.

geht auch *noahnung*

mfg
Sir Ulli
 
Zurück
Oben Unten