Message boards :
Number crunching :
Panic Mode On (100) Server Problems?
Message board moderation
Previous · 1 . . . 17 · 18 · 19 · 20 · 21 · 22 · 23 . . . 32 · Next
Author | Message |
---|---|
Oz Send message Joined: 6 Jun 99 Posts: 233 Credit: 200,655,462 RAC: 212 |
I find it interesting that the received WUs dropped about 23k when all this started. No spikes or dips, just lower. I noticed the same thing. It begs a more interesting question, why are ~70% of seti clients apparently still able to connect? Member of the 20 Year Club |
criton Send message Joined: 28 Feb 00 Posts: 131 Credit: 13,351,000 RAC: 2 |
closed boinc down and then restarted boinc straight after retried to send completed work units in and they went straight through and down loaded my cash to full again. the other pc wouldn't close down boinc so rebooted it and the same result all work sent in and cash filled up to max. les |
Iztok s52d (and friends) Send message Joined: 12 Jan 01 Posts: 136 Credit: 393,469,375 RAC: 116 |
I find it interesting that the received WUs dropped about 23k when all this started. No spikes or dips, just lower. No. When I looked at hosts stats, I found it very consistent: machines on one ISP are connecting, downloading, reporting, crunching. Machines on another has not reported a single WU since 30 Sep 2015, 14:09:45 UTC. Upload works, but I can not report completed tasks. On theory side: maybe difference is in the time to live? One ISP uses more hops? sorry, behind firewalls, no ICMP possible on non-working ISP. 73 s52d |
Iztok s52d (and friends) Send message Joined: 12 Jan 01 Posts: 136 Credit: 393,469,375 RAC: 116 |
No. linux: echo "128" >/proc/sys/net/ipv4/ip_default_ttl and no help. Unless firewalls are modifying TTL field? 73 s52d |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
Still intermittent for me here. This is from just a few moments ago on my laptop: 10/1/2015 11:13:17 AM | SETI@home | Sending scheduler request: To report completed tasks. 10/1/2015 11:13:17 AM | SETI@home | Reporting 1 completed tasks 10/1/2015 11:13:17 AM | SETI@home | Requesting new tasks for CPU 10/1/2015 11:13:38 AM | SETI@home | Scheduler request failed: Couldn't connect to server 10/1/2015 11:13:42 AM | | Project communication failed: attempting access to reference site 10/1/2015 11:13:44 AM | | Internet access OK - project servers may be temporarily down. 10/1/2015 11:15:15 AM | SETI@home | Sending scheduler request: To report completed tasks. 10/1/2015 11:15:15 AM | SETI@home | Reporting 1 completed tasks 10/1/2015 11:15:15 AM | SETI@home | Requesting new tasks for CPU 10/1/2015 11:15:17 AM | SETI@home | Scheduler request completed: got 1 new tasks 10/1/2015 11:15:19 AM | SETI@home | Started download of 02ja11ac.6328.8247.438086664203.12.35.vlar 10/1/2015 11:15:21 AM | SETI@home | Finished download of 02ja11ac.6328.8247.438086664203.12.35.vlar It fails on the first try, then sails through without a problem on the second. (The previous scheduler contact on this machine completed the scheduler request okay, then the download failed, only to succeed a couple minutes later.) |
John Neale Send message Joined: 16 Mar 00 Posts: 634 Credit: 7,246,513 RAC: 9 |
I'm in Outokumpu, Finland at the moment, using the hotel's wi-fi. I cannot report results, and I also cannot access the BOINC website. I am not experiencing any problems with the SETI@home website. I experienced the same behaviour earlier in the day using the wi-fi where I'm working. Here are a few traceroute results: Tracing route to setiathome.berkeley.edu [208.68.240.110] over a maximum of 30 hops: Tracing route to setiboinc.ssl.berkeley.edu [208.68.240.126] over a maximum of 30 hops: Tracing route to boinc.berkeley.edu [208.68.240.115] over a maximum of 30 hops: |
grn Send message Joined: 23 Oct 00 Posts: 13 Credit: 2,608,907 RAC: 0 |
I have 3 systems that have been unable to upload results for a almost a day now and was wondering if there is any idea when the issue may be resolved. I am on holiday on Saturday and have about 50 completed WUs to upload most of which have deadlines sometime during the next week. My machines will be shutdown early Saturday morning at the latest, so hoping it is resolved before then. Keeping my fingers crossed. George |
Phil Burden Send message Joined: 26 Oct 00 Posts: 264 Credit: 22,303,899 RAC: 0 |
closed boinc down and then restarted boinc straight after retried to send completed work units in and they went straight through and down loaded my cash to full again. the other pc wouldn't close down boinc so rebooted it and the same result all work sent in and cash filled up to max. les same result here too, stop & restart Boinc and all tasks reported ok, though subsequent schedule requests failed with "can't connect to server" |
qbit Send message Joined: 19 Sep 04 Posts: 630 Credit: 6,868,528 RAC: 0 |
Once again out of work.....:-( |
Bruce Send message Joined: 15 Mar 02 Posts: 123 Credit: 124,955,234 RAC: 11 |
Wish I know what was wrong. My last successful communication with the Scheduler was 7:00AM PDT on 9/30/2015. Since that time I have not reached it even once. All I have ever gotten is: 10/1/2015 2:36:47 PM | SETI@home | Reporting 100 completed tasks 10/1/2015 2:36:47 PM | SETI@home | Requesting new tasks for NVIDIA 10/1/2015 2:37:08 PM | SETI@home | Scheduler request failed: Couldn't connect to server 10/1/2015 2:37:23 PM | | Project communication failed: attempting access to reference site 10/1/2015 2:37:24 PM | | Internet access OK - project servers may be temporarily down. I have tried all the obvious things multiple times. Restart Boinc Reboot computer Reboot router Flush DNS Nothing seems to work for me. I don't understand how some people can get through to the Scheduler without any trouble, and I can not reach it even a single time. Here are the pertinent lines from the Tracert I just did: Tracing route to setiathome.berkeley.edu [208.68.240.110] over a maximum of 30 hops: 16 74 ms 74 ms 74 ms t2-3.inr-202-reccev.Berkeley.EDU [128.32.0.39] 17 75 ms 75 ms 75 ms e3-47.inr-310-ewdc.Berkeley.EDU [128.32.0.99] 18 * * * Request timed out. Tracing route to setiathome.ssl.berkeley.edu [208.68.240.110] over a maximum of 30 hops: 16 74 ms 73 ms 74 ms t2-3.inr-202-reccev.Berkeley.EDU [128.32.0.39] 17 75 ms 75 ms 74 ms e3-47.inr-310-ewdc.Berkeley.EDU [128.32.0.99] 18 * * * Request timed out. Tracing route to setiathome.berkeley.edu [208.68.240.110] over a maximum of 30 hops: 16 74 ms 74 ms 74 ms t2-3.inr-202-reccev.Berkeley.EDU [128.32.0.39] 17 75 ms 75 ms 75 ms e3-47.inr-310-ewdc.Berkeley.EDU [128.32.0.99] 18 * * * Request timed out. Hope that this info might help someone to figure out what the problem is. In the mean time, I am out of work and have a cache full of results that I can not report. Bruce Bruce |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Tracing route to setiathome.berkeley.edu [208.68.240.110] Well, that looks like a DNS problem to me. Different servers, same IP address. You haven't been fiddling with a hosts file, have you? Edit - or maybe not. I don't think "setiathome.ssl.berkeley.edu" (the second one) is a real server. Where did you get that name from? |
Brent Norman Send message Joined: 1 Dec 99 Posts: 2786 Credit: 685,657,289 RAC: 835 |
Richard, my routes come up the same. One server can host multiple sites, so I don't think that is it. |
Baiteh Send message Joined: 10 Sep 15 Posts: 34 Credit: 7,705,483 RAC: 0 |
I get this; Thu 01 Oct 2015 20:55:11 IST | SETI@home | Requesting new tasks for CPU Thu 01 Oct 2015 20:55:13 IST | SETI@home | Scheduler request failed: Couldn't connect to server Thu 01 Oct 2015 20:55:14 IST | | Project communication failed: attempting access to reference site Thu 01 Oct 2015 20:55:16 IST | | Internet access OK - project servers may be temporarily down. I can get to the BOINC site but it's slow. Also PING setiathome.ssl.berkeley.edu (208.68.240.110) 56(84) bytes of data. ^C --- setiathome.ssl.berkeley.edu ping statistics --- 67 packets transmitted, 0 received, 100% packet loss, time 66528ms |
Zombu2 Send message Joined: 24 Feb 01 Posts: 1615 Credit: 49,315,423 RAC: 0 |
every once in a while i get master file download succeeded but thats it I came down with a bad case of i don't give a crap |
OGM Send message Joined: 14 Apr 15 Posts: 12 Credit: 1,001,458 RAC: 0 |
Also no server contact for over a day now on my end. Uploads seem to work, but the report and download part fail. |
Zombu2 Send message Joined: 24 Feb 01 Posts: 1615 Credit: 49,315,423 RAC: 0 |
i abused teh hell out of it now i have a hole in the back of the screen I came down with a bad case of i don't give a crap |
Oz Send message Joined: 6 Jun 99 Posts: 233 Credit: 200,655,462 RAC: 212 |
Here is a tracert from one of my boxes that has been connecting... Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. >tracert -h 20 -w 15001 setiathome.berkeley.edu Tracing route to setiathome.berkeley.edu [208.68.240.110] over a maximum of 20 hops: 1 <1 ms <1 ms <1 ms xxx 2 3 ms 4 ms 4 ms xxx 3 7 ms 7 ms 7 ms xxx 4 * * * Request timed out. 5 * * * Request timed out. 6 16 ms 16 ms 15 ms 0.ae2.BR3.NYC4.ALTER.NET [140.222.229.99] 7 * * * Request timed out. 8 75 ms 74 ms 74 ms ae-3-80.ear1.SanJose1.Level3.net [4.69.152.150] 9 * * * Request timed out. 10 73 ms 73 ms 73 ms CENIC.ear1.SanJose1.Level3.net [4.15.122.46] 11 74 ms 75 ms 74 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.46.144] 12 75 ms 81 ms 76 ms ucb--oak-agg4-10g.cenic.net [137.164.50.31] 13 75 ms 74 ms 74 ms t2-3.inr-201-sut.Berkeley.EDU [128.32.0.37] 14 75 ms 75 ms 74 ms et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101] 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. Trace complete. So... WTF!?! Member of the 20 Year Club |
Zombu2 Send message Joined: 24 Feb 01 Posts: 1615 Credit: 49,315,423 RAC: 0 |
yeah same traceroute as everyone else I came down with a bad case of i don't give a crap |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
I wonder if TCP Optimizer might help some of those who haven't been able to connect at all. As I recall, I set my machines up with that before the move to the co-lo and currently I'm at least getting intermittently successfully connections. The thread Windows TCP Settings - Follow up - Help with server communication is where I originally got the info and settings for TCP Optimizer. EDIT: Changed the link to force it to the beginning of that thread. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Also Pinging the servers won't help, because the ping is caught by the campus firewall. So even when Seti (and BOINC) are available, pinging them will result in zero packets returning. |
©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.