Message boards :
Number crunching :
Panic Mode On (100) Server Problems?
Message board moderation
Previous · 1 . . . 14 · 15 · 16 · 17 · 18 · 19 · 20 . . . 32 · Next
Author | Message |
---|---|
JaundicedEye Send message Joined: 14 Mar 12 Posts: 5375 Credit: 30,870,693 RAC: 1 |
Yeah, whatever the problem is the finished WU uploads seem to go ok but the "report" hangs(?). I've got 9 "Ready to Report" lines starting from 13:13 UTC. Well at least it isn't Friday........
"Sour Grapes make a bitter Whine." <(0)> |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
I notice that in the message Richard has quoted contains the dreaded "Should" word - which of course must be read as "Will cause the unexpected to happen"... Not in the message I quoted, just in my personal spin at the end. But yes, that's why I wrote it that way. |
Oz Send message Joined: 6 Jun 99 Posts: 233 Credit: 200,655,462 RAC: 212 |
My boxes connecting through ver###n, both DSL and fibre have no issues, The boxes connecting through Ti##-War### have the uploads go but can't report, connect or download situation. Also I can ping berkeley.edu but not setiathome.berkeley.edu through T-W. It's possible it may not be on the Berkeley end... Member of the 20 Year Club |
Herb Smith Send message Joined: 28 Jan 07 Posts: 76 Credit: 31,615,205 RAC: 0 |
My machine have not have contact since 8 am CDT. My connection is through Comcast. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Well, I'm connected through FIOS and All 3 Platforms Mac, Win, and Ubuntu are having the Same problem; Wed Sep 30 18:17:48 2015 | SETI@home | Scheduler request failed: Couldn't connect to server 9/30/2015 18:06:43 | SETI@home | Scheduler request failed: Couldn't connect to server Wed 30 Sep 2015 05:56:37 PM EDT | SETI@home | Scheduler request failed: Couldn't connect to server About every 3rd or 4th attempt succeeds. |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
For me it's been intermittent, also, for about 12 hours or so now. Sometimes it works, sometimes it doesn't and sometimes it's a mixed bag, like this sequence earlier this afternoon, where it connected okay, reported okay, then started to download new tasks, but 2 of 3 failed on the initial try: 9/30/2015 2:04:26 PM | SETI@home | Reporting 2 completed tasks 9/30/2015 2:04:26 PM | SETI@home | Requesting new tasks for CPU and NVIDIA GPU 9/30/2015 2:04:28 PM | SETI@home | Scheduler request completed: got 3 new tasks 9/30/2015 2:04:31 PM | SETI@home | Started download of 31my11ae.22917.148527.438086664197.12.9 9/30/2015 2:04:31 PM | SETI@home | Started download of 14dc11ac.8390.19801.438086664199.12.19 9/30/2015 2:04:53 PM | SETI@home | Temporarily failed download of 31my11ae.22917.148527.438086664197.12.9: connect() failed 9/30/2015 2:04:53 PM | SETI@home | Backing off 00:03:50 on download of 31my11ae.22917.148527.438086664197.12.9 9/30/2015 2:04:53 PM | SETI@home | Temporarily failed download of 14dc11ac.8390.19801.438086664199.12.19: connect() failed 9/30/2015 2:04:53 PM | SETI@home | Backing off 00:03:30 on download of 14dc11ac.8390.19801.438086664199.12.19 9/30/2015 2:04:53 PM | SETI@home | Started download of 02ja11ac.13473.4975.438086664196.12.107.vlar 9/30/2015 2:04:55 PM | SETI@home | Finished download of 02ja11ac.13473.4975.438086664196.12.107.vlar 9/30/2015 2:04:57 PM | | Project communication failed: attempting access to reference site 9/30/2015 2:04:58 PM | | Internet access OK - project servers may be temporarily down. I'm on AT&T DSL, only about 100 miles from Berkeley. |
JaundicedEye Send message Joined: 14 Mar 12 Posts: 5375 Credit: 30,870,693 RAC: 1 |
My machine have not have contact since 8 am CDT. My connection is through Comcast. Ditto.... "Sour Grapes make a bitter Whine." <(0)> |
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
We connect through TWC. |
OTS Send message Joined: 6 Jan 08 Posts: 369 Credit: 20,533,537 RAC: 0 |
My boxes connecting through ver###n, both DSL and fibre have no issues, The boxes connecting through Ti##-War### have the uploads go but can't report, connect or download situation. If you do an nslookup of setiathome.berkeley.edu on a box connected to ver###n and do the same for a box conntected to Ti##-War###, are the reported IP addresses the same or different? |
Oz Send message Joined: 6 Jun 99 Posts: 233 Credit: 200,655,462 RAC: 212 |
My boxes connecting through ver###n, both DSL and fibre have no issues, The boxes connecting through Ti##-War### have the uploads go but can't report, connect or download situation. I will check tomorrow, I am several miles from either location connecting through V. However, I did note that a ping of berkeley.edu on TW yields an IPV6 address, while pinging setiathome.berkeley.edu shows an IPV4 address and total packet loss. Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. >ping berkeley.edu Pinging berkeley.edu [2607:f140:0:81::f] with 32 bytes of data: Reply from 2607:f140:0:81::f: time=92ms Reply from 2607:f140:0:81::f: time=108ms Reply from 2607:f140:0:81::f: time=94ms Reply from 2607:f140:0:81::f: time=93ms Ping statistics for 2607:f140:0:81::f: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 92ms, Maximum = 108ms, Average = 96ms ping setiathome.berkeley.edu Pinging setiathome.berkeley.edu [208.68.240.110] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 208.68.240.110: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Member of the 20 Year Club |
OTS Send message Joined: 6 Jan 08 Posts: 369 Credit: 20,533,537 RAC: 0 |
My boxes connecting through ver###n, both DSL and fibre have no issues, The boxes connecting through Ti##-War### have the uploads go but can't report, connect or download situation. Thanks. Perhaps by tomorrow the problem will be history. We can always hope. :). I have now 42 APs that have been uploaded without a single acknowledgement so no new work. :( Such is life. |
Oz Send message Joined: 6 Jun 99 Posts: 233 Credit: 200,655,462 RAC: 212 |
Nope the problem is at Berkeley... >ipconfig /flushdns Windows IP Configuration Successfully flushed the DNS Resolver Cache. >tracert setiathome.berkeley.edu Tracing route to setiathome.berkeley.edu [208.68.240.110] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms xxx 2 * * * Request timed out. 3 22 ms 31 ms 31 ms xxx 4 12 ms 12 ms 10 ms xxx 5 14 ms 13 ms 15 ms xxx 6 28 ms 29 ms 29 ms bu-ether15.chcgildt87w-bcr00.tbone.rr.com [66.10 9.6.72] 7 33 ms 26 ms 28 ms 0.ae1.pr1.chi10.tbone.rr.com [107.14.17.194] 8 36 ms 27 ms 28 ms xe-4-2-0.0.chic0.tr-cps.internet2.edu [64.57.20. 53] 9 26 ms 26 ms 27 ms ae-5.80.rtr.chic.net.internet2.edu [64.57.20.150 ] 10 39 ms 37 ms 36 ms ae-0.80.rtr.kans.net.internet2.edu [64.57.20.148 ] 11 76 ms 93 ms 78 ms ae-0.80.rtr.salt.net.internet2.edu [64.57.20.146 ] 12 72 ms 78 ms 73 ms ae-2.80.rtr.losa.net.internet2.edu [64.57.20.144 ] 13 79 ms 78 ms 77 ms xe-0-0-0.80.rtr.paix.net.internet2.edu [64.57.20 .125] 14 78 ms 78 ms 78 ms 64.57.21.7 15 79 ms 81 ms 81 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.4 6.144] 16 80 ms 82 ms 82 ms ucb--oak-agg4-10g.cenic.net [137.164.50.31] 17 81 ms 83 ms 81 ms t2-3.inr-202-reccev.Berkeley.EDU [128.32.0.39] 18 82 ms 82 ms 87 ms e3-47.inr-310-ewdc.Berkeley.EDU [128.32.0.99] 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Member of the 20 Year Club |
Cosmic_Ocean Send message Joined: 23 Dec 00 Posts: 3027 Credit: 13,516,867 RAC: 13 |
Here's my results as of 0232utc: >ping setiathome.berkeley.edu Pinging setiathome.berkeley.edu [208.68.240.110] with 32 bytes of data: Reply from 128.32.0.101: Destination host unreachable. Reply from 128.32.0.101: Destination host unreachable. Reply from 128.32.0.101: Destination host unreachable. Reply from 128.32.0.101: Destination host unreachable. Ping statistics for 208.68.240.110: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) and >tracert setiathome.berkeley.edu Tracing route to setiathome.berkeley.edu [208.68.240.110] over a maximum of 30 hops: 1 22 ms 9 ms 12 ms xxx 2 28 ms 11 ms 11 ms xxx 3 31 ms 9 ms 11 ms xxx 4 12 ms 25 ms 11 ms xxx 5 20 ms 35 ms 14 ms xxx 6 49 ms 47 ms 24 ms xxx 7 60 ms 37 ms 40 ms xxx 8 54 ms 53 ms 55 ms xxx 9 55 ms 56 ms 53 ms xxx 10 110 ms 55 ms 81 ms as11164-pe01.ashburn.va.ibone.comcast.net [75.149.228.82] 11 106 ms 102 ms 102 ms xe-8-1-1.0.rtr.losa.net.internet2.edu [64.57.20.247] 12 118 ms 119 ms 109 ms xe-0-0-0.80.rtr.paix.net.internet2.edu [64.57.20.125] 13 119 ms 112 ms 112 ms 64.57.21.5 14 112 ms 115 ms 115 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.46.144] 15 132 ms 111 ms 115 ms ucb--oak-agg4-10g.cenic.net [137.164.50.31] 16 113 ms 118 ms 112 ms t2-3.inr-201-sut.Berkeley.EDU [128.32.0.37] 17 113 ms 117 ms 114 ms et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101] 18 et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101] reports: Destination host unreachable. Trace complete. Interestingly, scheduler request worked fine (is that one of the issues some of you are having?): 2015-09-30 22:32:46 SETI@home [sched_op_debug] Starting scheduler request 2015-09-30 22:32:46 SETI@home Sending scheduler request: To fetch work. 2015-09-30 22:32:46 SETI@home Requesting new tasks 2015-09-30 22:32:46 SETI@home [sched_op_debug] CPU work request: 181493.50 seconds; 0.00 CPUs 2015-09-30 22:32:48 SETI@home Scheduler request completed: got 0 new tasks 2015-09-30 22:32:48 SETI@home [sched_op_debug] Server version 707 2015-09-30 22:32:48 SETI@home Message from server: No tasks sent 2015-09-30 22:32:48 SETI@home Message from server: No tasks are available for AstroPulse v7 2015-09-30 22:32:48 SETI@home Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v7. 2015-09-30 22:32:48 SETI@home Message from server: Tasks for NVIDIA GPU are available, but your preferences are set to not accept them 2015-09-30 22:32:48 SETI@home Message from server: Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them 2015-09-30 22:32:48 SETI@home Message from server: Tasks for Intel GPU are available, but your preferences are set to not accept them 2015-09-30 22:32:48 SETI@home Project requested delay of 303 seconds 2015-09-30 22:32:48 SETI@home [sched_op_debug] Deferring communication for 5 min 3 sec 2015-09-30 22:32:48 SETI@home [sched_op_debug] Reason: requested by project My message log is littered with "project communication failed" and "couldn't connect to server" attempts, with an occasional successful scheduler request here and there. And I had an upload that went through at 0148utc and was reported 20 seconds later in the next successful scheduler contact.. and then there were 12 failed contacts and one good one, then a few more failed, then two in a row that were good, etc etc. Seems to be intermittent routing troubles, or packets being inexplicably dropped into the bit bucket for random durations of time. Linux laptop: record uptime: 1511d 20h 19m (ended due to the power brick giving-up) |
OTS Send message Joined: 6 Jan 08 Posts: 369 Credit: 20,533,537 RAC: 0 |
After playing with it a bit more, it seems it might not even be a DNS issue. Using both 208.68.240.110 and setiathome.berkeley.edu brings up the same home page so it appears the name is resolved correctly. It might be that an IPv4 router isn't configured to handle ICMP or the port needed to reach the server that acknowledges uploads. Just a WAG of course but it passes the time. Edit: I guess I should have checked to see what the most recent posts came up with first as this might not explain intermittent connectivity, but for me it does not seem to be intermittent. I think we can all agree however that something is "broke". :). |
Donald L. Johnson Send message Joined: 5 Aug 02 Posts: 8240 Credit: 14,654,533 RAC: 20 |
Did anybody else lose access to the Forums Wednesday afternoon? My provider is ATT, and while reading some of the earlier posts about uploading and reporting problems, I lost access to the Forums and the Homepage around 1200 PDT (1900 UTC). Yahoo and Google access were fine, so it wasn't an ATT outage. Don't know when S@H came back up, I went on to other tasks. Donald Infernal Optimist / Submariner, retired |
Gary Charpentier Send message Joined: 25 Dec 00 Posts: 30639 Credit: 53,134,872 RAC: 32 |
Did anybody else lose access to the Forums Wednesday afternoon? http://boinc.berkeley.edu/dev/forum_thread.php?id=8105 |
Jimbocous Send message Joined: 1 Apr 13 Posts: 1853 Credit: 268,616,081 RAC: 1,349 |
Pretty bizarre, actually. One would think this forum would be inaccessible as well, yet there's no problem with that? |
Donald L. Johnson Send message Joined: 5 Aug 02 Posts: 8240 Credit: 14,654,533 RAC: 20 |
Did anybody else lose access to the Forums Wednesday afternoon? Thank you, Gary. As I had other things to take care of, I didn't really worry about it. Just wondered if it might have been related to the upload/download issues being reported. Donald Infernal Optimist / Submariner, retired |
Matt Lebofsky Send message Joined: 1 Mar 99 Posts: 1444 Credit: 957,058 RAC: 0 |
This is a really hard problem to characterize, and thus it's hard to help campus solve, but it looks like there is a router (on campus and out of our control) acting funny. Or it may be an internal problem that is difficult to track down (as this weirdness is affecting random machines at random times in random ways). We shall see.. Sorry for all the confusing lack of connectivity. :( - Matt -- BOINC/SETI@home network/web/science/development person -- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude |
Jimbocous Send message Joined: 1 Apr 13 Posts: 1853 Credit: 268,616,081 RAC: 1,349 |
http://boinc.berkeley.edu/dev/forum_thread.php?id=8105 This now seems to be down. tracert boinc.berkeley.edu ... * et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101] reports: Destination host unreachable. What a hoot ... Watching the SSP is very interesting. It seems to stay up to date, indicates splitting, uploads and downloads are happening and look normal. |
©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.