Posts by Wang Solutions
|
1)
Message boards :
Team Recruitment Center :
The Great Aussie Assault Number four
(Message 470433)
Posted 2 Dec 2006 by  Wang Solutions
Post: Haha. Witness the power of our FULLY OPERATIONAL crunching station!!! |
|
2)
Message boards :
Team Recruitment Center :
The Aussie Alliance with BOINC@AUSTRALIA
(Message 318241)
Posted 27 May 2006 by Wang Solutions
Post: I'd like to second that. This really is a great team with a great bunch of people, fantastic support from other knowledgeble team members, and best of all a lot of fun to be in. Come and check us out at http://boinc-australia.net. |
|
3)
Message boards :
Number crunching :
Proxy servers to access SETI
(Message 153273)
Posted 18 Aug 2005 by Wang Solutions
Post: Ned.....My gut feel on this is timing. There is another similar issue in thread "getting 500 response from server" . This is mostly Australia that is affected ...with some others. I have tried most of the previous suggestions. The only thing that is working for me at the moment is one of the proxy servers listed on Tigher's website (thanks for that!). I have done route traces to several of the setiboinc servers - here is an example, with the first two hops (my local network) deleted: 3 745 ms 755 ms 727 ms atm1-0-1.lon54.melbourne.telstra.net [139.130.4.149] 4 821 ms 715 ms 735 ms 10gigabitethernet9-0.win-core1.melbourne.telstra.net [203.50.79.129] 5 744 ms 699 ms 719 ms pos9-0.ken-core4.sydney.telstra.net [203.50.6.17] 6 734 ms 719 ms 735 ms 10gigabitethernet3-0.pad-core4.sydney.telstra.net [203.50.6.86] 7 705 ms 779 ms 767 ms 10gigabitethernet2-2.syd-core01.sydney.net.reach.com [203.50.13.38] 8 872 ms 860 ms 859 ms i-12-3.wil-core02.net.reach.com [202.84.249.205] 9 904 ms 984 ms 919 ms i-6-2.wil04.net.reach.com [202.84.251.186] 10 * * * Request timed out. 11 922 ms 983 ms 963 ms dc-slo-dc2--lax-dc1-pos.cenic.net [137.164.22.25] 12 956 ms 987 ms 900 ms dc-slo-dc1--dc2-df-iconn-1.cenic.net [137.164.22.122] 13 913 ms 863 ms 855 ms dc-sol-dc2--slo-dc1-pos.cenic.net [137.164.22.27] 14 886 ms 887 ms 887 ms dc-sol-dc1--sol-dc2-df-iconn-2.cenic.net [137.164.22.212] 15 898 ms 923 ms 859 ms dc-svl-dc1--sol-dc1-pos.cenic.net [137.164.22.29] 16 842 ms 860 ms 859 ms dc-svl-dc1--svl-dc2-df-iconn-2.cenic.net [137.164.22.208] 17 890 ms 827 ms 923 ms ucb--svl-dc1-egm.cenic.net [137.164.23.66] 18 935 ms 972 ms 887 ms g3-17.inr-202-reccev.berkeley.edu [128.32.0.35] 19 901 ms 888 ms 859 ms g6-2.inr-230-spr.berkeley.edu [128.32.255.114] 20 933 ms * 860 ms solen.ssl.berkeley.edu [128.32.18.209] 21 * * 1193 ms galileo.ssl.berkeley.edu [128.32.18.173] Obviously there are some problems, but I am not convinced that this is the issue. I suspect that most of those having trouble in Australia are using the same ISP, and it probably does not matter what type of connection it is - mine is a satellite. I am not experiencing any of the 500 errors that others have been reporting. My problem is simply that without the proxy servers, the messages in the Boinc Manager are all of this type: 18/08/2005 8:57:58 PM|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed 18/08/2005 8:57:58 PM|SETI@home|No schedulers responded 18/08/2005 8:57:58 PM|SETI@home|Deferring communication with project for 1 minutes and 0 seconds When I turn on the proxy server and send the same request a few seconds later, it is successful (eg 18/08/2005 8:58:59 PM|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded) I am no expert in these matters, and am happy to be guided by those that are. |
|
4)
Questions and Answers :
Web site :
No schedulers responding for 9 days now
(Message 152545)
Posted 17 Aug 2005 by Wang Solutions
Post: Yes this has not worked again for the last few days and I am yet to find another proxy server that works. Any suggestions welcome! Works for me too, at least for the moment! Thanks Geoff |
|
5)
Message boards :
Number crunching :
Proxy servers to access SETI
(Message 152525)
Posted 17 Aug 2005 by Wang Solutions
Post: Since recent changes at SETI BOINC, I and many others have been unable to connect to the servers without using proxy servers. The trouble is, each time someone posts details of a proxy server that works, it is either overloaded or disabled so it no longer works. Can anyone post details of any proxy servers that are open and operating that will allow us all to access SETI?? |
|
6)
Questions and Answers :
Web site :
No schedulers responding for 9 days now
(Message 152524)
Posted 17 Aug 2005 by Wang Solutions
Post: Yes this has not worked again for the last few days and I am yet to find another proxy server that works. Any suggestions welcome! |
|
7)
Questions and Answers :
Web site :
No schedulers responding for 9 days now
(Message 149024)
Posted 9 Aug 2005 by Wang Solutions
Post: If you go to the forums number crunching here there are some threads on this problem. These include proxy details which is a work around perhaps for you at the moment. Thanks for this post - I found that the proxy server settings of 203.53.113.5 80 fixed the problem for me. Thanks again. |
|
8)
Questions and Answers :
Web site :
No schedulers responding for 9 days now
(Message 146814)
Posted 4 Aug 2005 by Wang Solutions
Post: Since the DNS switch reported on July 26, my computers have not been able to connect to a scheduler to either upload or download work. I have tried every method I can think of to re-establish a connection without success. Two other computers running on a differnet internet connection can get access. This has to be some sort of DNS issue but my attempts to rectify it have been fruitless. Any suggestions? |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.