The data server is up and running, but dropping connections
Right now the data server machine is up, but not all clients are able to connect.
This is due to our server being swamped with requests,
and usually happens right after a server outage, or if there are
greater network/database problems we are currently trying to fix.
Please try connecting later.
ボイン子YOUR ACCOUNT
General preferences の Connect to network about every
を、デフォルトのままだと0.1dayで遅いマシンだと１ユニット位しか
ダウンロード可能にならないけど、3day位にすれば、複数ユニット
ダウンロード可能になり、さらにそれの75%以上は、ダウンロード完了して実行待機になるので、
継続して処理できるよ。
4.11に最適化入れてます。入れた後には順調に落ちてきたんですが・・・
連休前からまったく落ちてきません。
|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
|SETI@home|No schedulers responded
|SETI@home|Deferring communication with project for 59 seconds
こんな感じのメッセージ出てます。
May run out of work in 5.00 days; requesting more
request_reschedule_cpus: process exited
アップロードが終わっても次のWUはすぐに落ちて来ないですね。
Deferring communication with project for 10 minutes and 4 seconds
のMSGが必ず表示されてます。
その1秒後にWUが落ちて来たり、とあまり意味の無いような表示ですが。
WUのｽﾃｰﾀｽを見ると4台のｸﾗｲｱﾝﾄに同時に送っているようなので
そのﾀｲﾐﾝｸﾞを合わせているのだと思われます。
722氏やTAILOR氏のように何日も落ちて来ない理由は不明ですが･･･。
BOINC5.2.2落としてリセットしたけど
>Attempting to communicate with [setiboinc.ssl.berkeley.edu] timed out
>Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -182
>No schedulers responded
FWでブロックはしていないし、もしかしてルータ?…けど設定変更をした覚えはない。
BOINC周りの設定を見直してみますわ。
どうやら一緒にやっていた、Predictor が悪かったようです。 http://predictor.scripps.edu/
News に
Abeta work units:
There is a problem with the Abeta series of work units.
Please abort any you have downloaded
なんて書かれていました。
Abeta Work Unit は全部実行して終了しちゃていました。
Predictor から離脱したら SETI がちゃんと復活しました。
２台ともそうでした。
ひどい！
2006-09-02 01:34:00 [SETI@home] Sending scheduler request to ttp://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2006-09-02 01:34:00 [SETI@home] Reason: To fetch work
2006-09-02 01:34:00 [SETI@home] Requesting 518400 seconds of work, returning 0 results
2006-09-02 01:34:02 [SETI@home] Scheduler request to ttp://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2006-09-02 01:34:02 [SETI@home] Message from server: No work sent
2006-09-02 01:34:02 [SETI@home] No work from project
2006-09-02 01:34:03 [SETI@home] Deferring communication with project for 59 minutes and 58 seconds
>>820
昨日の夜あたりからつながりにくくなった。
Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
とか
No work from project
がいっぱいでてるよ。
昨日から時々サーバ状態見てるけど、
赤／オレンジ／緑になんども変わっているので、
メンテナンス中かもしれない。
＞On the science database front, the outage continues. Not much to say
＞about that except we're still working on getting replacement hardware.
＞Frankly, no real time estimate on that. Some people have noticed,
＞despite apparent claims on our website otherwise, their clients were
＞able to get new workunits. This is because, due to some BOINC clients
＞taking too long to process/return results or failures during validation,
＞the BOINC backend puts these timed-out/unvalidated workunits back in
＞the "to do" pile. I just checked and noticed we're still sending out
＞workunit at the rate of 1 every 10+ seconds. Not exactly a lot... but
＞not zero, either.
ttp://setiathome.berkeley.edu/forum_thread.php?id=39230#558802
>Great news! Sun Microsystems is coming to the rescue and will be replacing our inoperative
>science data base server. They are preparing the machine now and will be rushing it to us on
>Monday. Once we have the machine up and the database recovered, we can start sending work
>out again. Details on the server crash and our recovery from it can be found in Technical News.
現地時間で月曜には新しいマシンが届く様子。
不安定ながらもバークレー復活！！
5/12/2007 3:27:56 PM|SETI@home Sending scheduler request: Requested by user
5/12/2007 3:27:56 PM|SETI@home Requesting 385074 seconds of new work
5/12/2007 3:28:47 PM|SETI@home Scheduler RPC succeeded [server version 509]
5/12/2007 3:28:47 PM|SETI@home Deferring communication for 11 sec
5/12/2007 3:28:47 PM|SETI@home Reason: requested by project
5/12/2007 3:28:47 PM|SETI@home Deferring communication for 1 min 0 sec
5/12/2007 3:28:47 PM|SETI@home Reason: no work from project
5/12/2007 3:29:47 PM|SETI@home Fetching scheduler list
5/12/2007 3:29:52 PM|SETI@home Master file download succeeded
>>849
きちんとソース当たってるあるよ。こんなんでガセ流してどーする。
＞It's around 6:35 pm here at the Space Sciences Lab, and Eric and Jeff
＞are still up in the lab working on thumper. Everything's going well - the
＞machine arrived with 48 drives in it, so they took 24 out and put in
＞the 24 we had previously, turned it on, and everything is going well
＞so far. Eric said he hoped to have thumper up and running today, so
＞keep your fingers crossed.
ttp://setiathome.berkeley.edu/forum_thread.php?id=39394
宇宙科学ラボは今6時35分。エリック、ジェフ両名はいまだにラボでサンパーと
格闘中。現時点で万事順調。マシンはドライブ48台組んだ状態で到着したので、
うち24台を取り出し、それまで使ってたものと入れ替え。起動してみても問題は
出ていないので、エリックは今日中にサンパーを稼動させたい、とのこと。
幸運を祈られたし。
2009/01/26 22:44:49|SETI@home|Backing off 1 min 0 sec on upload of 15dc08ae.20353.45247.14.8.96_1_0
2009/01/26 22:44:50||Internet access OK - project servers may be temporarily down.
2009/01/26 22:45:49|SETI@home|Started upload of 15dc08ae.20353.45247.14.8.96_1_0
2009/01/26 22:46:10||Project communication failed: attempting access to reference site
2009/01/26 22:46:10|SETI@home|Temporarily failed upload of 15dc08ae.20353.45247.14.8.96_1_0: connect() failed
2009/01/26 22:46:10|SETI@home|Backing off 1 min 0 sec on upload of 15dc08ae.20353.45247.14.8.96_1_0
....
2009/01/26 22:44:49|SETI@home|Backing off 1 min 0 sec on upload of 15dc08ae.20353.45247.14.8.96_1_0
2009/01/26 22:44:50||Internet access OK - project servers may be temporarily down.
2009/01/26 22:45:49|SETI@home|Started upload of 15dc08ae.20353.45247.14.8.96_1_0
2009/01/26 22:46:10||Project communication failed: attempting access to reference site
2009/01/26 22:46:10|SETI@home|Temporarily failed upload of 15dc08ae.20353.45247.14.8.96_1_0: connect() failed
2009/01/26 22:46:10|SETI@home|Backing off 1 min 0 sec on upload of 15dc08ae.20353.45247.14.8.96_1_0
