看到已经十多个计算好的WU在那里等待上传.如何才能强制让它上传到服务器？或者是如何能设置它计算好就马上上传？

等待上传?

已计算好应该是立即就上传的(应该也没地方修改),然后进入ready to report状态,这个时候update project就可以立即完成report

就是PROJECT里面的UPDATE

点update project无任何反映啊

2005-4-7 13:22:20||Starting BOINC client version 4.25 for windows_intelx86
2005-4-7 13:22:20|SETI@home|Host location: home
2005-4-7 13:22:20|SETI@home|Using your default project prefs
2005-4-7 13:22:20|SETI@home|Host ID is 694103
2005-4-7 13:22:20||General prefs: from SETI@home (last modified 2005-04-06 07:51:59)
2005-4-7 13:22:20||General prefs: using your defaults
2005-4-7 13:22:20|SETI@home|Resuming computation for result 19dc04ab.9173.31121.928404.231_0 using setiathome version 4.10
2005-4-7 13:22:20|SETI@home|Deferring communication with project for 2 hours, 29 minutes, and 11 seconds
2005-4-7 14:22:20|SETI@home|Deferring communication with project for 1 hours, 29 minutes, and 10 seconds
2005-4-7 15:22:20|SETI@home|Deferring communication with project for 29 minutes and 10 seconds
2005-4-7 15:43:46|SETI@home|Computation for result 19dc04ab.9173.31121.928404.231 finished
2005-4-7 15:43:46|SETI@home|Starting result 02ja05aa.18682.27456.415910.201_3 using setiathome version 4.10
2005-4-7 15:43:47|SETI@home|Started upload of 19dc04ab.9173.31121.928404.231_0_0
2005-4-7 15:44:07|SETI@home|Finished upload of 19dc04ab.9173.31121.928404.231_0_0
2005-4-7 15:44:07|SETI@home|Throughput 16658 bytes/sec
2005-4-7 15:51:32|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-4-7 15:52:19|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-4-7 15:52:19|SETI@home|No schedulers responded
2005-4-7 15:52:19|SETI@home|Deferring communication with project for 1 minutes and 0 seconds
2005-4-7 15:53:33|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-4-7 15:53:40|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-4-7 15:53:40|SETI@home|No schedulers responded
2005-4-7 15:53:40|SETI@home|Deferring communication with project for 1 minutes and 0 seconds
2005-4-7 15:54:41|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-4-7 15:55:15|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-4-7 15:55:15|SETI@home|No schedulers responded
2005-4-7 15:55:15|SETI@home|Deferring communication with project for 1 minutes and 0 seconds
2005-4-7 15:56:16|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-4-7 15:56:23|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-4-7 15:56:23|SETI@home|No schedulers responded
2005-4-7 15:56:23|SETI@home|Deferring communication with project for 1 minutes and 0 seconds
2005-4-7 15:57:24|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-4-7 15:58:15|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-4-7 15:58:15|SETI@home|No schedulers responded
2005-4-7 15:58:15|SETI@home|Deferring communication with project for 1 minutes and 0 seconds
2005-4-7 15:59:15|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-4-7 15:59:22|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-4-7 15:59:22|SETI@home|No schedulers responded
2005-4-7 15:59:22|SETI@home|Deferring communication with project for 1 minutes and 52 seconds
2005-4-7 16:01:15|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-4-7 16:02:07|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-4-7 16:02:07|SETI@home|No schedulers responded
2005-4-7 16:02:07|SETI@home|Deferring communication with project for 5 minutes and 36 seconds
2005-4-7 16:07:44|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-4-7 16:07:51|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-4-7 16:07:51|SETI@home|No schedulers responded
2005-4-7 16:07:51|SETI@home|Deferring communication with project for 6 minutes and 23 seconds
2005-4-7 16:14:14|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-4-7 16:14:28|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-4-7 16:14:28|SETI@home|No schedulers responded
2005-4-7 16:14:28|SETI@home|Deferring communication with project for 8 minutes and 28 seconds
2005-4-7 16:22:57|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-4-7 16:23:10|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-4-7 16:23:10|SETI@home|No schedulers responded
2005-4-7 16:23:10|SETI@home|Deferring communication with project for 1 hours, 44 minutes, and 43 seconds
2005-4-7 17:23:11|SETI@home|Deferring communication with project for 44 minutes and 42 seconds
2005-4-7 17:52:01|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-4-7 17:52:15|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-4-7 17:52:15|SETI@home|No schedulers responded
2005-4-7 17:52:15|SETI@home|Deferring communication with project for 1 hours, 6 minutes, and 36 seconds
2005-4-7 17:54:08|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi

这是什么意思啊

2005-4-7 17:52:15|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
应该是连接失败了……

正常的应该是

2005-4-7 17:44:02|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

[ Last edited by 第三类接触 on 2005-4-7 at 17:58 ]

为什么会连接失败呢？

原因很多………………boinc的服务器经常出点问题………………

不是BOINC服务器出问题，是SETI的schedulers offline

总体感觉BOINC越来越不好用了，而且各个项目的服务器都很难连接。

我现在只跑einstein@home，感觉还可以