Kłopoty z Boincem

[krzysiob]

Po pierwsze WITAM WSZYSTKICH!
To jest mój pierwszy post, chociaż udostepniam swój komp dla SETI już od dawna
16 Oct 2006 19:34:50 UTC i nawet wcześniej, ponieważ nie udało mi się
aktywować starego konta po wymianie kompa.
Ale to  to już historia...
Problem mam inny - teraz nie wiem czy to jest powodem padnięcia serwera SETI
czy wymiany FireWalla z Nortona na Sygate
Oto moje ostatnie logi:

Kod [Zaznacz] Rozwiń

07-05-11 16:30:58||Starting BOINC client version 5.4.11 for windows_intelx86
07-05-11 16:31:00||libcurl/7.15.3 OpenSSL/0.9.8a zlib/1.2.3
07-05-11 16:31:00||Data directory: C:\PROGRAM FILES\BOINC
07-05-11 16:31:00||Processor: 1 AuthenticAMD AMD Athlon(tm) XP 2400+
07-05-11 16:31:00||Memory: 510.36 MB physical, 1.13 GB virtual
07-05-11 16:31:00||Disk: 9.27 GB total, 1.06 GB free
07-05-11 16:31:00|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 2765162; location: ; project prefs: default
07-05-11 16:31:00||No general preferences found - using BOINC defaults
07-05-11 16:31:00||Local control only allowed
07-05-11 16:31:00||Listening on port 31416
07-05-11 17:09:24|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 17:09:24|SETI@home|Reason: To fetch work
07-05-11 17:09:24|SETI@home|Requesting 8640 seconds of new work
07-05-11 17:10:09||Project communication failed: attempting access to reference site
07-05-11 17:10:11||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 17:10:11|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 17:10:11|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
07-05-11 17:11:12|SETI@home|Fetching scheduler list
07-05-11 17:11:17|SETI@home|Scheduler list download succeeded
07-05-11 17:11:23|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 17:11:23|SETI@home|Reason: To fetch work
07-05-11 17:11:23|SETI@home|Requesting 8640 seconds of new work
07-05-11 17:12:25|SETI@home|Scheduler request succeeded
07-05-11 17:12:25|SETI@home|No work from project
07-05-11 17:12:25|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
07-05-11 17:13:27|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 17:13:27|SETI@home|Reason: To fetch work
07-05-11 17:13:27|SETI@home|Requesting 8640 seconds of new work
07-05-11 17:14:13||Project communication failed: attempting access to reference site
07-05-11 17:14:15||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 17:14:16|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 17:14:16|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
07-05-11 17:15:20|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 17:15:20|SETI@home|Reason: To fetch work
07-05-11 17:15:20|SETI@home|Requesting 8640 seconds of new work
07-05-11 17:16:06||Project communication failed: attempting access to reference site
07-05-11 17:16:07|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 17:16:07|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
07-05-11 17:16:08||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 17:17:09|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 17:17:09|SETI@home|Reason: To fetch work
07-05-11 17:17:09|SETI@home|Requesting 8640 seconds of new work
07-05-11 17:17:55||Project communication failed: attempting access to reference site
07-05-11 17:17:56||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 17:17:59|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 17:17:59|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
07-05-11 17:19:02|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 17:19:02|SETI@home|Reason: To fetch work
07-05-11 17:19:02|SETI@home|Requesting 8640 seconds of new work
07-05-11 17:19:48||Project communication failed: attempting access to reference site
07-05-11 17:19:50||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 17:19:51|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 17:19:51|SETI@home|Deferring scheduler requests for 1 minutes and 3 seconds
07-05-11 17:21:00|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 17:21:00|SETI@home|Reason: To fetch work
07-05-11 17:21:00|SETI@home|Requesting 8640 seconds of new work
07-05-11 17:21:45||Project communication failed: attempting access to reference site
07-05-11 17:21:48||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 17:21:48|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 17:21:48|SETI@home|Deferring scheduler requests for 5 minutes and 28 seconds
07-05-11 17:27:16|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 17:27:16|SETI@home|Reason: To fetch work
07-05-11 17:27:16|SETI@home|Requesting 8640 seconds of new work
07-05-11 17:28:02||Project communication failed: attempting access to reference site
07-05-11 17:28:03||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 17:28:06|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 17:28:06|SETI@home|Deferring scheduler requests for 6 minutes and 43 seconds
07-05-11 17:34:55|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 17:34:55|SETI@home|Reason: To fetch work
07-05-11 17:34:55|SETI@home|Requesting 8640 seconds of new work
07-05-11 17:35:41||Project communication failed: attempting access to reference site
07-05-11 17:35:42||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 17:35:44|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 17:35:44|SETI@home|Deferring scheduler requests for 30 minutes and 47 seconds
07-05-11 18:06:36|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 18:06:36|SETI@home|Reason: To fetch work
07-05-11 18:06:36|SETI@home|Requesting 8640 seconds of new work
07-05-11 18:07:35|SETI@home|Scheduler request succeeded
07-05-11 18:07:35|SETI@home|No work from project
07-05-11 18:07:35|SETI@home|Deferring scheduler requests for 1 hours, 40 minutes and 42 seconds
07-05-11 19:48:19|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 19:48:19|SETI@home|Reason: To fetch work
07-05-11 19:48:19|SETI@home|Requesting 8640 seconds of new work
07-05-11 19:49:05||Project communication failed: attempting access to reference site
07-05-11 19:49:07||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 19:49:08|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 19:49:08|SETI@home|Deferring scheduler requests for 2 hours, 30 minutes and 17 seconds
07-05-11 22:19:28|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 22:19:28|SETI@home|Reason: To fetch work
07-05-11 22:19:28|SETI@home|Requesting 8640 seconds of new work
07-05-11 22:20:44|SETI@home|Scheduler request succeeded
07-05-11 22:20:44|SETI@home|No work from project
07-05-11 22:20:44|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
07-05-11 22:21:47|SETI@home|Fetching scheduler list
07-05-11 22:21:53|SETI@home|Scheduler list download succeeded
07-05-11 22:21:58|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 22:21:58|SETI@home|Reason: To fetch work
07-05-11 22:21:58|SETI@home|Requesting 8640 seconds of new work
07-05-11 22:22:43||Project communication failed: attempting access to reference site
07-05-11 22:22:44||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 22:22:46|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 22:22:46|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
07-05-11 22:23:51|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 22:23:51|SETI@home|Reason: To fetch work
07-05-11 22:23:51|SETI@home|Requesting 8640 seconds of new work
07-05-11 22:24:36||Project communication failed: attempting access to reference site
07-05-11 22:24:36|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 22:24:36|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
07-05-11 22:24:38||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 22:25:41|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 22:25:41|SETI@home|Reason: To fetch work
07-05-11 22:25:41|SETI@home|Requesting 8640 seconds of new work
07-05-11 22:26:27||Project communication failed: attempting access to reference site
07-05-11 22:26:30||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 22:26:31|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 22:26:31|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
07-05-11 22:27:35|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 22:27:35|SETI@home|Reason: To fetch work
07-05-11 22:27:35|SETI@home|Requesting 8640 seconds of new work
07-05-11 22:28:24|SETI@home|Scheduler request succeeded
07-05-11 22:28:24|SETI@home|No work from project
07-05-11 22:28:24|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
07-05-11 22:29:25|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 22:29:25|SETI@home|Reason: To fetch work
07-05-11 22:29:25|SETI@home|Requesting 8640 seconds of new work
07-05-11 22:30:11||Project communication failed: attempting access to reference site
07-05-11 22:30:13||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 22:30:13|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 22:30:13|SETI@home|Deferring scheduler requests for 1 minutes and 6 seconds
07-05-11 22:31:24|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 22:31:24|SETI@home|Reason: To fetch work
07-05-11 22:31:24|SETI@home|Requesting 8640 seconds of new work
07-05-11 22:32:12||Project communication failed: attempting access to reference site
07-05-11 22:32:14||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 22:32:14|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 22:32:14|SETI@home|Deferring scheduler requests for 2 minutes and 3 seconds
07-05-11 22:34:21|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 22:34:21|SETI@home|Reason: To fetch work
07-05-11 22:34:21|SETI@home|Requesting 8640 seconds of new work
07-05-11 22:35:08||Project communication failed: attempting access to reference site
07-05-11 22:35:09|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 22:35:09|SETI@home|Deferring scheduler requests for 14 minutes and 8 seconds
07-05-11 22:35:10||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 22:49:22|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
07-05-11 22:49:22|SETI@home|Reason: To fetch work
07-05-11 22:49:22|SETI@home|Requesting 8640 seconds of new work
07-05-11 22:50:08||Project communication failed: attempting access to reference site
07-05-11 22:50:09||Access to reference site succeeded - project servers may be temporarily down.
07-05-11 22:50:12|SETI@home|Scheduler request failed: couldn't connect to server
07-05-11 22:50:12|SETI@home|Deferring scheduler requests for 46 minutes and 1 seconds

Proszę znawców o diagnozę
Pozdrawiam,
Krzysiob

[Thomas]

Odpowiedź jest prosta – aktualnie SETI padł serwer – więcej danych w tym temacie: [moderacja: link nie aktualny] tutaj.

[Wydmek]

Najwcześniej Seti ma działać dopiero w najbliższy poniedziałek - do tego czasu polecamy jakiś inny projekt :)

[krzysiob]

Dzięki za odpowiedż
:)