Message boards :
Number crunching :
HE connection problems thread
Message board moderation
Previous · 1 . . . 3 · 4 · 5 · 6 · 7 · 8 · 9 . . . 25 · Next
Author | Message |
---|---|
Jim_S Send message Joined: 23 Feb 00 Posts: 4705 Credit: 64,560,357 RAC: 31 |
They can look at my log files...I have Nothing to hide. I Desire Peace and Justice, Jim Scott (Mod-Ret.) |
Hampsteadpete Send message Joined: 11 Jul 99 Posts: 11 Credit: 220,917 RAC: 0 |
I know this is probably already known, but I have been unable to connect to the SETI servers for over a week. My IP is: 187.140.26.252, in Mexico. Today I tried using Hotspot Shield, which I use to change my IP for certain things, and I was able to down a task just now for the first time in quite a while. The IP I was assigned was in Chicago. I guess I'll have to change my IP whenever the task finishes, just like the old days of dial-up. Hope the problem gets fixed soon! I know it's being worked. Pete |
Dr. Wolfram Sperber Send message Joined: 4 Jul 99 Posts: 12 Credit: 1,734,882 RAC: 6 |
Since a week or so, the proxy solution I'd reported on, has gone again: No uploads nor downloads to/from berkeley again. Some experiments with proxy configurations failed, and without any proxy I'm getting the "Internet access OK - project servers may be temporarily down." (So, same situation as others are in.) It seems curious to me that on some days my client is updating statistics: I assume, some evaluated result in the pipe has caused it. --- And since three weeks we have no signal at all from Matt Lebofsky, who opened this thread! Is he still alive? Was he called back to his home planet? For holidays? Does he have no time to write here? A personal ping would be useful! So we do not know if anybody is working on the connection problem, at all. What about other responsible persons? While normal operations seem to continue we even don't know how many clients are affected... <a href="http://allprojectstats.com/showuser.php?id=622594"><img src="http://allprojectstats.com/su622594n3-2a12-1-0.png" border=0> |
Hampsteadpete Send message Joined: 11 Jul 99 Posts: 11 Credit: 220,917 RAC: 0 |
I was able, once again this morning, although it took several retries, to download a task using Hotspot Shield to change my IP from Mexico to Chicago. How can I get the server to send me several tasks at once? That would be so much more convenient. Pete |
perryjay Send message Joined: 20 Aug 02 Posts: 3377 Credit: 20,676,751 RAC: 0 |
And since three weeks we have no signal at all from Matt Lebofsky, who opened this thread! Matt posted this in the tech news forum about a month ago. I'm sure the other guys are keeping a close watch on the problem but since it is on HEs' side there is little they can do except continue to give HE any help they can. Sorry my posts continue to be intermittent. I apologize but expect things to get worse as the music career will temporary consume me. You may see rather significant periods of silence from me for the next... I dunno... 6 to 12 months? I'm sure the others will chime in as needed if I'm not around. PROUD MEMBER OF Team Starfire World BOINC |
[STS]LoB Send message Joined: 23 May 99 Posts: 53 Credit: 3,375,888 RAC: 144 |
Will this ever get fixed eventually? |
Jim_S Send message Joined: 23 Feb 00 Posts: 4705 Credit: 64,560,357 RAC: 31 |
Eventually...They have a work ticket filed with Hurricane Electric where the Routing problem seems to be. As a fellow "Old Timer" I hope they find the problem soon. I also remember in the S@H classic days we would sometimes have some long waits. Things are more complicated now but I have faith in the staff. They will find it soon...Until then I will still use a PROXY to get what Work I can. Have patients [STS]LoB. ;-] I Desire Peace and Justice, Jim Scott (Mod-Ret.) |
[STS]LoB Send message Joined: 23 May 99 Posts: 53 Credit: 3,375,888 RAC: 144 |
If the proxy solution worked for me as well... It uploaded some three results and then stopped working again... |
Stealth Eagle* Send message Joined: 7 Sep 00 Posts: 5971 Credit: 367,640 RAC: 0 |
I was able to get some 58 tasks on the 20th and completed them all. I was able to upload 28 as they were completed, but the last 30 have been waiting since about 14:45 yesterday when the servers went down since then I have not been able to contact the upload servers. This is the response I get when I try; 7/22/2011 12:41:21 PM | SETI@home | update requested by user 7/22/2011 12:41:29 PM | SETI@home | Sending scheduler request: Requested by user. 7/22/2011 12:41:29 PM | SETI@home | Reporting 30 completed tasks, not requesting new tasks 7/22/2011 12:41:32 PM | SETI@home | Scheduler request failed: Couldn't connect to server 7/22/2011 12:41:36 PM | | Project communication failed: attempting access to reference site 7/22/2011 12:41:37 PM | | Internet access OK - project servers may be temporarily down. What you do today you will have to live with tonight |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
I was able to get some 58 tasks on the 20th and completed them all. I was able to upload 28 as they were completed, but the last 30 have been waiting since about 14:45 yesterday when the servers went down since then I have not been able to contact the upload servers. I believe your situation has nothing to do with the HE problem, but simply various Seti server and bandwidth problems. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Matt Lebofsky Send message Joined: 1 Mar 99 Posts: 1444 Credit: 957,058 RAC: 0 |
Sorry about the lack of response from me (or anybody else here). Minor medical issue (all's well), followed by short planned family-related vacation, followed by a weekend of mild food poisoning. It's been a crazy summer. I know it's been a while, but I'm tackling this issue now. - 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 |
Gary Charpentier Send message Joined: 25 Dec 00 Posts: 30653 Credit: 53,134,872 RAC: 32 |
Thanks for the update Matt. |
Jim_S Send message Joined: 23 Feb 00 Posts: 4705 Credit: 64,560,357 RAC: 31 |
Thanks Matt...Hope you are feeling much better. I Desire Peace and Justice, Jim Scott (Mod-Ret.) |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
Thank you for the response, Matt. It is much appreciated by many, I am sure. Glad you are feeling better. Now go kick some HE butt....LOL. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Jim_S Send message Joined: 23 Feb 00 Posts: 4705 Credit: 64,560,357 RAC: 31 |
The RED ones are Different. 7/27/2011 8:39:56 PM | | Not using a proxy 7/27/2011 8:48:23 PM | SETI@home | Computation for task 17dc10ab.14147.590.13.10.178_1 finished 7/27/2011 8:48:23 PM | SETI@home | Starting 17dc10ab.14147.590.13.10.167_0 7/27/2011 8:48:23 PM | SETI@home | Starting task 17dc10ab.14147.590.13.10.167_0 using setiathome_enhanced version 603 7/27/2011 8:48:25 PM | SETI@home | Started upload of 17dc10ab.14147.590.13.10.178_1_0 7/27/2011 8:48:47 PM | | Project communication failed: attempting access to reference site 7/27/2011 8:48:47 PM | SETI@home | Temporarily failed upload of 17dc10ab.14147.590.13.10.178_1_0: connect() failed 7/27/2011 8:48:47 PM | SETI@home | Backing off 15 min 18 sec on upload of 17dc10ab.14147.590.13.10.178_1_0 7/27/2011 8:48:48 PM | | Internet access OK - project servers may be temporarily down. 7/27/2011 9:04:06 PM | SETI@home | Started upload of 17dc10ab.14147.590.13.10.178_1_0 7/27/2011 9:04:29 PM | | Project communication failed: attempting access to reference site 7/27/2011 9:04:29 PM | SETI@home | Temporarily failed upload of 17dc10ab.14147.590.13.10.178_1_0: connect() failed 7/27/2011 9:04:29 PM | SETI@home | Backing off 27 min 15 sec on upload of 17dc10ab.14147.590.13.10.178_1_0 7/27/2011 9:04:30 PM | | Internet access OK - project servers may be temporarily down. 7/27/2011 9:31:45 PM | SETI@home | Started upload of 17dc10ab.14147.590.13.10.178_1_0 7/27/2011 9:32:08 PM | | Project communication failed: attempting access to reference site 7/27/2011 9:32:08 PM | SETI@home | Temporarily failed upload of 17dc10ab.14147.590.13.10.178_1_0: connect() failed 7/27/2011 9:32:08 PM | SETI@home | Backing off 1 hr 0 min 2 sec on upload of 17dc10ab.14147.590.13.10.178_1_0 7/27/2011 9:32:09 PM | | Internet access OK - project servers may be temporarily down. 7/27/2011 10:29:50 PM | SETI@home | Computation for task 17dc10ab.14147.590.13.10.174_1 finished 7/27/2011 10:29:50 PM | SETI@home | Starting 17dc10ab.14147.590.13.10.166_1 7/27/2011 10:29:50 PM | SETI@home | Starting task 17dc10ab.14147.590.13.10.166_1 using setiathome_enhanced version 603 7/27/2011 10:29:52 PM | SETI@home | Started upload of 17dc10ab.14147.590.13.10.174_1_0 7/27/2011 10:30:14 PM | | Project communication failed: attempting access to reference site [color=red]7/27/2011 10:30:14 PM | SETI@home | Temporarily failed upload of 17dc10ab.14147.590.13.10.174_1_0: connect() failed 7/27/2011 10:30:14 PM | SETI@home | Backing off 18 min 44 sec on upload of 17dc10ab.14147.590.13.10.174_1_0 7/27/2011 10:30:16 PM | | Internet access OK - project servers may be temporarily down. 7/27/2011 10:37:26 PM | SETI@home | Computation for task 17dc10ab.14147.590.13.10.172_1 finished 7/27/2011 10:37:26 PM | SETI@home | Starting 17dc10ab.14147.590.13.10.160_0 7/27/2011 10:37:26 PM | SETI@home | Starting task 17dc10ab.14147.590.13.10.160_0 using setiathome_enhanced version 603 7/27/2011 10:47:00 PM | SETI@home | Computation for task 17dc10ab.14147.590.13.10.169_1 finished 7/27/2011 10:47:00 PM | SETI@home | Starting 17dc10ab.14147.590.13.10.154_1 7/27/2011 10:47:00 PM | SETI@home | Starting task 17dc10ab.14147.590.13.10.154_1 using setiathome_enhanced version 603 7/27/2011 10:47:03 PM | SETI@home | Sending scheduler request: To fetch work. 7/27/2011 10:47:03 PM | SETI@home | Requesting new tasks for CPU 7/27/2011 10:47:25 PM | | Project communication failed: attempting access to reference site 7/27/2011 10:47:25 PM | SETI@home | Scheduler request failed: Couldn't connect to server 7/27/2011 10:47:26 PM | | Internet access OK - project servers may be temporarily down. 7/27/2011 10:49:05 PM | SETI@home | Sending scheduler request: To fetch work. 7/27/2011 10:49:05 PM | SETI@home | Requesting new tasks for CPU 7/27/2011 10:49:27 PM | | Project communication failed: attempting access to reference site 7/27/2011 10:49:27 PM | SETI@home | Scheduler request failed: Couldn't connect to server 7/27/2011 10:49:28 PM | | Internet access OK - project servers may be temporarily down. 7/27/2011 10:53:17 PM | SETI@home | Sending scheduler request: To fetch work. 7/27/2011 10:53:17 PM | SETI@home | Requesting new tasks for CPU 7/27/2011 10:53:39 PM | | Project communication failed: attempting access to reference site 7/27/2011 10:53:39 PM | SETI@home | Scheduler request failed: Couldn't connect to server 7/27/2011 10:53:41 PM | | Internet access OK - project servers may be temporarily down. 7/27/2011 10:56:35 PM | SETI@home | Computation for task 17dc10ab.14147.590.13.10.167_0 finished 7/27/2011 10:56:35 PM | SETI@home | Starting 14mr11aa.28837.19290.14.10.99_0 7/27/2011 10:56:35 PM | SETI@home | Starting task 14mr11aa.28837.19290.14.10.99_0 using setiathome_enhanced version 603 7/27/2011 11:01:40 PM | SETI@home | Sending scheduler request: To fetch work. 7/27/2011 11:01:40 PM | SETI@home | Requesting new tasks for CPU 7/27/2011 11:02:03 PM | | Project communication failed: attempting access to reference site 7/27/2011 11:02:03 PM | SETI@home | Scheduler request failed: Couldn't connect to server 7/27/2011 11:02:04 PM | | Internet access OK - project servers may be temporarily down. The Red ones are different than I have seen before I Desire Peace and Justice, Jim Scott (Mod-Ret.) |
Hampsteadpete Send message Joined: 11 Jul 99 Posts: 11 Credit: 220,917 RAC: 0 |
I have been able to get a limited number of tasks by using a proxy, but last night and this morning, I got this message using the proxy: 7/28/2011 9:58:44 AM | SETI@home | update requested by user 7/28/2011 9:58:48 AM | SETI@home | Sending scheduler request: Requested by user. 7/28/2011 9:58:48 AM | SETI@home | Requesting new tasks for CPU 7/28/2011 9:58:50 AM | SETI@home | Scheduler request completed: got 0 new tasks 7/28/2011 9:58:50 AM | SETI@home | Project has no tasks available No tasks? I guess I'll just wait 'till the problems are fixed and not try the proxy solution any longer. My normal IP is 187.140.2.194, if that's any help. Pete |
JohnDK Send message Joined: 28 May 00 Posts: 1222 Credit: 451,243,443 RAC: 1,127 |
I have been able to get a limited number of tasks by using a proxy, but last night and this morning, I got this message using the proxy: Sounds like connection works normal, but that there's simply no tasks available at the moment. |
OfficeDude Send message Joined: 7 Jul 99 Posts: 8 Credit: 2,322,928 RAC: 0 |
Still having problems on one machine. upload: OK download: NOK Located in Belgium ISP: edpnet xxx@server3:~> ping 208.68.240.13 PING 208.68.240.13 (208.68.240.13) 56(84) bytes of data. 64 bytes from 208.68.240.13: icmp_seq=1 ttl=54 time=184 ms 64 bytes from 208.68.240.13: icmp_seq=2 ttl=54 time=185 ms 64 bytes from 208.68.240.13: icmp_seq=3 ttl=54 time=184 ms 64 bytes from 208.68.240.13: icmp_seq=4 ttl=54 time=184 ms --- 208.68.240.13 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3007ms rtt min/avg/max/mdev = 184.039/184.457/185.585/0.837 ms xxx@server3:~> ping 208.68.240.16 PING 208.68.240.16 (208.68.240.16) 56(84) bytes of data. 64 bytes from 208.68.240.16: icmp_seq=1 ttl=54 time=187 ms 64 bytes from 208.68.240.16: icmp_seq=2 ttl=54 time=185 ms 64 bytes from 208.68.240.16: icmp_seq=3 ttl=54 time=186 ms --- 208.68.240.16 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2006ms rtt min/avg/max/mdev = 185.563/186.428/187.216/0.763 ms xxx@server3:~> ping 208.68.240.18 PING 208.68.240.18 (208.68.240.18) 56(84) bytes of data. 64 bytes from 208.68.240.18: icmp_seq=1 ttl=54 time=184 ms 64 bytes from 208.68.240.18: icmp_seq=2 ttl=54 time=183 ms 64 bytes from 208.68.240.18: icmp_seq=3 ttl=54 time=183 ms 64 bytes from 208.68.240.18: icmp_seq=4 ttl=54 time=183 ms --- 208.68.240.18 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3008ms rtt min/avg/max/mdev = 183.027/183.707/184.500/0.649 ms xxx@server3:~> ping 208.68.240.20 PING 208.68.240.20 (208.68.240.20) 56(84) bytes of data. 64 bytes from 208.68.240.20: icmp_seq=1 ttl=54 time=185 ms 64 bytes from 208.68.240.20: icmp_seq=2 ttl=54 time=184 ms 64 bytes from 208.68.240.20: icmp_seq=3 ttl=54 time=184 ms 64 bytes from 208.68.240.20: icmp_seq=4 ttl=54 time=183 ms traceroute to 208.68.240.13 (208.68.240.13), 30 hops max, 40 byte packets 1 dsldevice.lan (192.168.0.254) 37.498 ms 35.725 ms 31.696 ms 2 77.109.102.1.adsl.dyn.edpnet.net (77.109.102.1) 20.202 ms 20.773 ms 20.574 ms 3 85.234.208.29.static.edpnet.net (85.234.208.29) 23.979 ms 24.106 ms 23.395 ms 4 212.71.11.106.adsl.dyn.edpnet.net (212.71.11.106) 34.500 ms 35.373 ms 34.563 ms 5 20gigabitethernet4-3.core1.fra1.he.net (80.81.192.172) 35.781 ms 34.891 ms 34.491 ms 6 10gigabitethernet1-4.core1.par2.he.net (184.105.213.162) 42.199 ms 10gigabitethernet1-2.core1.par1.he.net (72.52.92.89) 41.956 ms 10gigabitethernet1-4.core1.par2.he.net (184.105.213.162) 41.368 ms 7 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 118.777 ms 10gigabitethernet1-1.core1.par2.he.net (184.105.213.90) 40.955 ms 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 113.107 ms 8 10gigabitethernet1-4.core1.pao1.he.net (72.52.92.29) 182.002 ms 182.573 ms 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 122.448 ms Unable to look up 64.71.140.42: Temporary failure in name resolution 9 64.71.140.42 183.518 ms 10gigabitethernet7-4.core1.pao1.he.net (184.105.213.177) 180.661 ms * Unable to look up 208.68.243.254: Temporary failure in name resolution 10 * 208.68.243.254 224.664 ms 199.569 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * server3:~ # traceroute 208.68.240.16 traceroute to 208.68.240.16 (208.68.240.16), 30 hops max, 40 byte packets 1 dsldevice.lan (192.168.0.254) 50.081 ms 45.023 ms 40.952 ms 2 77.109.102.1.adsl.dyn.edpnet.net (77.109.102.1) 20.051 ms 20.901 ms 20.311 ms 3 85.234.208.29.static.edpnet.net (85.234.208.29) 23.015 ms 22.814 ms 23.734 ms 4 212.71.11.106.adsl.dyn.edpnet.net (212.71.11.106) 34.915 ms 34.283 ms 33.655 ms 5 20gigabitethernet4-3.core1.fra1.he.net (80.81.192.172) 34.564 ms 46.726 ms 43.126 ms 6 10gigabitethernet1-2.core1.par1.he.net (72.52.92.89) 41.175 ms 41.700 ms 10gigabitethernet1-4.core1.par2.he.net (184.105.213.162) 42.905 ms 7 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 119.529 ms 10gigabitethernet1-1.core1.par2.he.net (184.105.213.90) 41.016 ms 42.531 ms 8 10gigabitethernet1-4.core1.pao1.he.net (72.52.92.29) 182.633 ms 182.256 ms 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 113.299 ms Unable to look up 64.71.140.42: Temporary failure in name resolution 9 64.71.140.42 184.049 ms 183.182 ms 183.127 ms Unable to look up 64.71.140.42: Temporary failure in name resolution Unable to look up 208.68.243.254: Temporary failure in name resolution Unable to look up 64.71.140.42: Temporary failure in name resolution 10 64.71.140.42 180.961 ms 208.68.243.254 188.291 ms 64.71.140.42 181.781 ms Unable to look up 208.68.243.254: Temporary failure in name resolution 11 * 208.68.243.254 185.010 ms 184.795 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * traceroute to 208.68.240.13 (208.68.240.13), 30 hops max, 40 byte packets 1 dsldevice.lan (192.168.0.254) 37.498 ms 35.725 ms 31.696 ms 2 77.109.102.1.adsl.dyn.edpnet.net (77.109.102.1) 20.202 ms 20.773 ms 20.574 ms 3 85.234.208.29.static.edpnet.net (85.234.208.29) 23.979 ms 24.106 ms 23.395 ms 4 212.71.11.106.adsl.dyn.edpnet.net (212.71.11.106) 34.500 ms 35.373 ms 34.563 ms 5 20gigabitethernet4-3.core1.fra1.he.net (80.81.192.172) 35.781 ms 34.891 ms 34.491 ms 6 10gigabitethernet1-4.core1.par2.he.net (184.105.213.162) 42.199 ms 10gigabitethernet1-2.core1.par1.he.net (72.52.92.89) 41.956 ms 10gigabitethernet1-4.core1.par2.he.net (184.105.213.162) 41.368 ms 7 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 118.777 ms 10gigabitethernet1-1.core1.par2.he.net (184.105.213.90) 40.955 ms 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 113.107 ms 8 10gigabitethernet1-4.core1.pao1.he.net (72.52.92.29) 182.002 ms 182.573 ms 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 122.448 ms Unable to look up 64.71.140.42: Temporary failure in name resolution 9 64.71.140.42 183.518 ms 10gigabitethernet7-4.core1.pao1.he.net (184.105.213.177) 180.661 ms * Unable to look up 208.68.243.254: Temporary failure in name resolution 10 * 208.68.243.254 224.664 ms 199.569 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * server3:~ # traceroute 208.68.240.16 traceroute to 208.68.240.16 (208.68.240.16), 30 hops max, 40 byte packets 1 dsldevice.lan (192.168.0.254) 50.081 ms 45.023 ms 40.952 ms 2 77.109.102.1.adsl.dyn.edpnet.net (77.109.102.1) 20.051 ms 20.901 ms 20.311 ms 3 85.234.208.29.static.edpnet.net (85.234.208.29) 23.015 ms 22.814 ms 23.734 ms 4 212.71.11.106.adsl.dyn.edpnet.net (212.71.11.106) 34.915 ms 34.283 ms 33.655 ms 5 20gigabitethernet4-3.core1.fra1.he.net (80.81.192.172) 34.564 ms 46.726 ms 43.126 ms 6 10gigabitethernet1-2.core1.par1.he.net (72.52.92.89) 41.175 ms 41.700 ms 10gigabitethernet1-4.core1.par2.he.net (184.105.213.162) 42.905 ms 7 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 119.529 ms 10gigabitethernet1-1.core1.par2.he.net (184.105.213.90) 41.016 ms 42.531 ms 8 10gigabitethernet1-4.core1.pao1.he.net (72.52.92.29) 182.633 ms 182.256 ms 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 113.299 ms Unable to look up 64.71.140.42: Temporary failure in name resolution 9 64.71.140.42 184.049 ms 183.182 ms 183.127 ms Unable to look up 64.71.140.42: Temporary failure in name resolution Unable to look up 208.68.243.254: Temporary failure in name resolution Unable to look up 64.71.140.42: Temporary failure in name resolution 10 64.71.140.42 180.961 ms 208.68.243.254 188.291 ms 64.71.140.42 181.781 ms Unable to look up 208.68.243.254: Temporary failure in name resolution 11 * 208.68.243.254 185.010 ms 184.795 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * server3:~ # traceroute 208.68.240.20 traceroute to 208.68.240.20 (208.68.240.20), 30 hops max, 40 byte packets 1 dsldevice.lan (192.168.0.254) 32.524 ms 29.069 ms 25.012 ms 2 77.109.102.1.adsl.dyn.edpnet.net (77.109.102.1) 20.275 ms 19.902 ms 21.158 ms 3 85.234.208.29.static.edpnet.net (85.234.208.29) 23.141 ms 23.155 ms 23.815 ms 4 212.71.11.106.adsl.dyn.edpnet.net (212.71.11.106) 34.991 ms 34.281 ms 35.199 ms 5 20gigabitethernet4-3.core1.fra1.he.net (80.81.192.172) 35.881 ms 35.709 ms 34.400 ms 6 10gigabitethernet1-4.core1.par2.he.net (184.105.213.162) 41.102 ms 10gigabitethernet1-2.core1.par1.he.net (72.52.92.89) 41.060 ms 41.421 ms 7 10gigabitethernet1-1.core1.par2.he.net (184.105.213.90) 40.682 ms 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 113.689 ms 10gigabitethernet1-1.core1.par2.he.net (184.105.213.90) 40.301 ms 8 10gigabitethernet1-4.core1.pao1.he.net (72.52.92.29) 181.574 ms 181.103 ms 10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93) 121.059 ms Unable to look up 64.71.140.42: Temporary failure in name resolution 9 64.71.140.42 183.187 ms 183.131 ms 183.798 ms Unable to look up 64.71.140.42: Temporary failure in name resolution Unable to look up 208.68.243.254: Temporary failure in name resolution 10 64.71.140.42 181.034 ms 208.68.243.254 188.278 ms 187.256 ms Unable to look up 208.68.243.254: Temporary failure in name resolution 11 208.68.243.254 185.868 ms 185.809 ms * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Trace route from another ISP telenet.be as reference case linux-8lh1:~ # traceroute 208.68.240.13 traceroute to 208.68.240.13 (208.68.240.13), 30 hops max, 40 byte packets using UDP 1 sitecomwl328.sitecomwl328 (192.168.0.1) 0.803 ms 0.613 ms 0.623 ms 2 94-224-80-1.access.telenet.be (94.224.80.1) 6.999 ms 9.798 ms 8.707 ms 3 dD5E0C2A1.access.telenet.be (213.224.194.161) 14.161 ms 13.053 ms 11.946 ms 4 dD5E0FD71.access.telenet.be (213.224.253.113) 10.741 ms 16.086 ms 8.523 ms 5 te3-2.ar1.NLD1.ANT1.gblx.net (64.215.184.29) 9.824 ms TenGigabitEthernet3-3.ar1.NDL1.gblx.net (64.210.31.249) 12.565 ms te3-2.ar1.NLD1.ANT1.gblx.net (64.215.184.29) 15.162 ms 6 Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net (64.214.174.246) 165.291 ms 164.139 ms 163.293 ms 7 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 164.274 ms 165.254 ms 162.691 ms 8 64.71.140.42 (64.71.140.42) 161.253 ms 168.622 ms 251.141 ms 9 208.68.243.254 (208.68.243.254) 250.368 ms 249.242 ms 248.025 ms 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * |
Gene F. Send message Joined: 6 Apr 08 Posts: 26 Credit: 2,607,746 RAC: 0 |
Didn't see the size issue in this thread. Apologies if it's something obvious, but I'm not getting any work. Fri Jul 29 12:12:47 2011 SETI@home [error] File 21mr11af.5127.221967.4.10.98 has wrong size: expected 375330, got 0 Fri Jul 29 12:12:47 2011 SETI@home Started download of 21mr11af.5127.221967.4.10.98 Fri Jul 29 12:12:47 2011 SETI@home [error] File 08ap11al.6659.15200.13.10.177 has wrong size: expected 375340, got 0 Fri Jul 29 12:12:47 2011 SETI@home Started download of 08ap11al.6659.15200.13.10.177 Fri Jul 29 12:14:03 2011 Project communication failed: attempting access to reference site Fri Jul 29 12:14:03 2011 SETI@home Temporarily failed download of 21mr11af.5127.221967.4.10.98: connect() failed Fri Jul 29 12:14:03 2011 SETI@home Backing off 2 hr 40 min 25 sec on download of 21mr11af.5127.221967.4.10.98 Fri Jul 29 12:14:03 2011 SETI@home Temporarily failed download of 08ap11al.6659.15200.13.10.177: connect() failed Fri Jul 29 12:14:03 2011 SETI@home Backing off 48 min 40 sec on download of 08ap11al.6659.15200.13.10.177 |
Luigi Naruszewicz Send message Joined: 19 Nov 99 Posts: 620 Credit: 23,910,372 RAC: 14 |
The last 72 hours I not been able to download any work units allocated to me. Pinged the above addresses and everything works fine, I live in Wokingham, England. Also trace route and ns lookups worked fine. Tried using proxy 212.118.224.151 : 80 and with this managed to download 15 of my work units, then nothing happened for about 5 hours, then I managed to download another 15 units. Whilst using the proxy I was not able to upload. Switching the proxy, to upload, I also shut down Boinc manager in order to clear long term debt. On restarting Boinc manager all my outstanding downloads immediateley down loaded. Subsequent downloads failed to work and on stopping and restarting Boinc manager, downloads worked. . A person who makes no mistakes, creates nothing. |
©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.