HE connection problems thread


log in

Advanced search

Message boards : Number crunching : HE connection problems thread

Previous · 1 · 2 · 3 · 4 · 5 . . . 25 · Next
Author Message
bertbob
Send message
Joined: 4 Jul 02
Posts: 1
Credit: 734,573
RAC: 733
United States
Message 1122318 - Posted: 28 Jun 2011, 4:18:33 UTC

I'm in Salt Lake City, Utah, ISP xmission.com

I haven't been able to connect to any servers for about a week.

no answers to pings to any of the four addresses.

traceroute for each shows failure at he.net

2 lo1.erx1.slc.xmission.net (166.70.0.1) 43.538 ms 46.204 ms 47.608 ms
3 403.gi-3-13.dcr2.slc.xmission.net (166.70.5.82) 47.232 ms 48.591 ms 50.320 ms
4 te11-3-0d0.mcr1.saltlake-ut.us.xo.net (65.46.61.5) 51.785 ms 53.206 ms 55.373 ms
5 ae1d0.mcr1.saltlake2-ut.us.xo.net (216.156.1.2) 57.948 ms 59.104 ms 61.037 ms
6 vb1611.rar3.sanjose-ca.us.xo.net (216.156.0.5) 78.971 ms 77.606 ms 78.179 ms
7 * * *
8 206.111.6.166.ptr.us.xo.net (206.111.6.166) 57.623 ms 59.203 ms 61.163 ms
9 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 63.709 ms 67.571 ms
10 * * *
...
30 * * *

nslookup all resemble

nslookup 208.68.240.20
Server: 127.0.0.1
Address: 127.0.0.1#53

Non-authoritative answer:
20.240.68.208.in-addr.arpa name = setiboinc.ssl.berkeley.edu.

Authoritative answers can be found from:
240.68.208.in-addr.arpa nameserver = adns2.berkeley.edu.
240.68.208.in-addr.arpa nameserver = adns1.berkeley.edu.
adns1.berkeley.edu internet address = 128.32.136.3
adns1.berkeley.edu has AAAA address 2607:f140:ffff:fffe::3
adns2.berkeley.edu internet address = 128.32.136.14
adns2.berkeley.edu has AAAA address 2607:f140:ffff:fffe::e




____________

1mp0£173
Volunteer tester
Send message
Joined: 3 Apr 99
Posts: 8423
Credit: 356,897
RAC: 0
United States
Message 1122350 - Posted: 28 Jun 2011, 4:54:14 UTC - in response to Message 1122104.

Hey all - I'm trying to characterize this current problem where some users are unable to reach any of our servers through Hurricane Electric. If possible please answer in this thread the following questions (feel free to leave out anything you want to keep private, or don't understand):

1. Are you able to reach ANY of the upload, download, or scheduling servers?
2. When did you start having this problem?
3. What is your ISP?
4. What is your geographic location?
5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?
6. How about traceroutes of the above four addresses?
7. Or nslookups of the above four addresses?

Or if you know what the exact problem is (or if there isn't really a single problem but a set of problems) that would be useful, too.

Thanks!

- Matt

On Level(3), through LSANCA54. They peer with HE in San Jose.

From my edge router, I see quite good ping times (15 msec) up to 64.71.140.42 - and no packet loss.

208.68.243.254 shows 25% packet loss, and when it does answer, times range up to 97 msec.

For 208.68.240.20, I see around 20% packet loss and times over 130msec.

In my professional opinion, the "problem" is congestion between HE and campus, and the wire is performing admirably under the current load.

Profile Jim_S
Avatar
Send message
Joined: 23 Feb 00
Posts: 4472
Credit: 18,281,023
RAC: 6,021
United States
Message 1122355 - Posted: 28 Jun 2011, 5:34:06 UTC
Last modified: 28 Jun 2011, 5:41:32 UTC

This is what I've been getting.

Tracing route to setiboinc.ssl.berkeley.edu [208.68.240.20]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 25 ms 26 ms 25 ms 66-38-56-1.static.bbtel.com [66.38.56.1]
3 26 ms 25 ms 26 ms bbtel-6509-g2-2.serial.blue.net [66.38.60.193]
4 27 ms 26 ms 25 ms rc-mlx8-ve31.serial.blue.net [66.38.58.169]
5 26 ms 26 ms 29 ms h1.126.55.139.static.ip.windstream.net [139.55.1
26.1]
6 29 ms 29 ms 29 ms h25.222.90.75.static.ip.windstream.net [75.90.22
2.25]
7 29 ms 28 ms 29 ms h36.254.213.151.static.ip.windstream.net [151.21
3.254.36]
8 47 ms 46 ms 46 ms h14.254.213.151.static.ip.windstream.net [151.21
3.254.14]
9 46 ms 47 ms 47 ms ip65-47-204-81.z204-47-65.customer.algx.net [65.
47.204.81]
10 46 ms 47 ms 53 ms v306.core1.dal1.he.net [64.71.189.217]
11 112 ms 100 ms 100 ms 10gigabitethernet1-2.core1.phx1.he.net [72.52.92
.253]
12 97 ms 99 ms 99 ms 10gigabitethernet2-2.core1.lax1.he.net [72.52.92
.249]
13 114 ms 110 ms 113 ms 10gigabitethernet1-3.core1.pao1.he.net [72.52.92
.21]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
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.


Pings "Time Out"...Also This.

6/19/2011 12:55:47 PM SETI@home Fetching scheduler list
6/19/2011 12:55:48 PM SETI@home Master file download succeeded
came from the 19th
6/19/2011 12:49:02 PM SETI@home Started upload of 13mr11ah.3053.10292.10.10.80_0_0
6/19/2011 12:49:09 PM Project communication failed: attempting access to reference site
6/19/2011 12:49:10 PM Internet access OK - project servers may be temporarily down.
6/19/2011 12:49:24 PM Project communication failed: attempting access to reference site
6/19/2011 12:49:24 PM SETI@home Temporarily failed upload of 08ap11ab.18487.8247.5.10.123_0_0: connect() failed
6/19/2011 12:49:24 PM SETI@home Backing off 2 hr 36 min 22 sec on upload of 08ap11ab.18487.8247.5.10.123_0_0
6/19/2011 12:49:24 PM SETI@home Temporarily failed upload of 13mr11ah.3053.10292.10.10.80_0_0: connect() failed
6/19/2011 12:49:24 PM SETI@home Backing off 2 hr 33 min 59 sec on upload of 13mr11ah.3053.10292.10.10.80_0_0
6/19/2011 12:49:26 PM Internet access OK - project servers may be temporarily down.
6/19/2011 12:50:25 PM SETI@home Started upload of 05mr11af.8242.137390.11.10.10_2_0
6/19/2011 12:50:25 PM SETI@home Started upload of 18ap11aa.18789.4157.6.10.49_1_0
6/19/2011 12:50:47 PM Project communication failed: attempting access to reference site
6/19/2011 12:50:47 PM SETI@home Temporarily failed upload of 05mr11af.8242.137390.11.10.10_2_0: connect() failed
6/19/2011 12:50:47 PM SETI@home Backing off 7 min 21 sec on upload of 05mr11af.8242.137390.11.10.10_2_0
6/19/2011 12:50:47 PM SETI@home Temporarily failed upload of 18ap11aa.18789.4157.6.10.49_1_0: connect() failed
6/19/2011 12:50:47 PM SETI@home Backing off 3 hr 19 min 3 sec on upload of 18ap11aa.18789.4157.6.10.49_1_0
6/19/2011 12:50:48 PM Internet access OK - project servers may be temporarily down.
6/19/2011 12:54:25 PM SETI@home Sending scheduler request: To report completed tasks.
6/19/2011 12:54:25 PM SETI@home Reporting 32 completed tasks, not requesting new tasks
6/19/2011 12:54:47 PM Project communication failed: attempting access to reference site
6/19/2011 12:54:47 PM SETI@home Scheduler request failed: Couldn't connect to server
6/19/2011 12:54:48 PM Internet access OK - project servers may be temporarily down.
6/19/2011 12:55:01 PM Re-reading cc_config.xml
6/19/2011 12:55:01 PM Re-read config file
6/19/2011 12:55:01 PM log flags: file_xfer, sched_ops, task
6/19/2011 12:55:47 PM SETI@home Fetching scheduler list
6/19/2011 12:55:48 PM SETI@home Master file download succeeded
6/19/2011 12:55:54 PM SETI@home Sending scheduler request: To report completed tasks.
6/19/2011 12:55:54 PM SETI@home Reporting 32 completed tasks, not requesting new tasks
6/19/2011 12:56:15 PM Project communication failed: attempting access to reference site
6/19/2011 12:56:15 PM SETI@home Scheduler request failed: Couldn't connect to server
6/19/2011 12:56:16 PM Internet access OK - project servers may be temporarily down.
____________

I Desire Peace and Justice, Jim Scott

Profile Jim_S
Avatar
Send message
Joined: 23 Feb 00
Posts: 4472
Credit: 18,281,023
RAC: 6,021
United States
Message 1122373 - Posted: 28 Jun 2011, 7:10:38 UTC
Last modified: 28 Jun 2011, 7:16:50 UTC

Oh Yeah,
I'm through bbtel.com Brandenburg, KY.
Problems started on the 15th and 16th.
____________

I Desire Peace and Justice, Jim Scott

-BeNt-
Avatar
Send message
Joined: 17 Oct 99
Posts: 1234
Credit: 10,116,112
RAC: 0
United States
Message 1122388 - Posted: 28 Jun 2011, 7:51:11 UTC

Checking out a DNS transveral report of "setiboincdata.ssl.berkeley.edu" I get the following servers:

adns1.berkeley.edu (128.32.136.3)
adns2.berkeley.edu (128.32.136.14)
aodns1.berkeley.edu (192.35.225.133)
ns.v6.berkeley.edu (128.32.136.6)
phloem.uoregon.edu (128.223.32.35)
sns-pb.isc.org (192.5.4.1)

'a/c/d/f/g/l'.edu-servers.net

Usage of checks:
25% 199.254.63.254 (ns.isc.afilias-nst.info) with 192.5.4.1
25% 199.6.1.30 (ams.sns-pb.isc.org) with 192.5.4.1
25% 149.20.64.3 (sfba.sns-pb.isc.org) with 192.5.4.1
25% 199.6.0.30 (ord.sns-pb.isc.org) with query timed out

Percentage of answers to checks above out of 100%:
39.6% 128.32.136.14 (adns2.berkeley.edu) with 208.68.240.16
39.6% 128.32.136.3 (adns1.berkeley.edu) with 208.68.240.16
16.7% 128.32.136.6 (ns.v6.berkeley.edu) with 208.68.240.16
4.1% 199.6.0.30 (ord.sns-pb.isc.org) with failed to resolve sns-pb.isc.org due to 199.6.0.30 - query timed out

'a/b/c/d/e/f/g/h/i/j/k/l/m'.root-servers.net (This refers clients back to the edu name servers.)

Doing a lookup on Hurricane's end for:
setiboinc.ssl.berkeley.edu(208.68.240.20) - Perfect
boinc2.ssl.berkeley.edu(208.68.240.13 / 208.68.240.18) - Perfect
setiboincdata.ssl.berkeley.edu(208.68.240.16) - Perfect

Doing a lookup on my end:
setiboinc.ssl.berkeley.edu(208.68.240.20) - Perfect
boinc2.ssl.berkeley.edu(208.68.240.13 / 208.68.240.18) - Perfect
setiboincdata.ssl.berkeley.edu(208.68.240.16) - Perfect

From what I've seen everyone just about is having packet loss at 208.68.243.254 which is well inside of Hurricane's network and more than likely at the campus judging by the very next entry for most is the actual server. With that being said I'm showing 40% loss at 208.68.240.13 and ~10-50% loss at the switch(I'm assuming since I don't really know.)

However with that being said, I'm showing just about what everyone that's having problem connecting is showing, except I can connect. I'm really starting to think that this isn't going to be an issue on Hurricane's side and something inside the lab. At first I was thinking it was a DNS issue, but it's not a DNS issue, in fact it's not even a routing issue per-say because everyone can find where they are going, it's just back to back pings are timing out.

Guys on campus - I would find where 208.68.243.254 is and try a reboot / kick. After all it does return the name of "SETIATHOME" belonging to the "Space Sciences Laboratory". Sounds like it's time for a reset ;).

As another side note to those wondering, "I can get to the website fine but not the servers!". The website is hosted off Thinman and it's not in the Hurricane network, it's hosted on Cenic.




















____________
Traveling through space at ~67,000mph!

msattler
Volunteer tester
Avatar
Send message
Joined: 9 Jul 00
Posts: 38154
Credit: 556,300,122
RAC: 593,118
United States
Message 1122397 - Posted: 28 Jun 2011, 7:58:03 UTC

I would just like to interrupt for a moment to say thank you to Matt for digging into this on behalf of my fellow crunchers who are experiencing the problem.

Meow, Matt!
____________
*********************************************
Embrace your inner kitty...ya know ya wanna!

I have met a few friends in my life.
Most were cats.

jo
Send message
Joined: 3 Dec 00
Posts: 2
Credit: 333,865
RAC: 23
Germany
Message 1122434 - Posted: 28 Jun 2011, 12:51:58 UTC

1. Are you able to reach ANY of the upload, download, or scheduling servers?
No

2. When did you start having this problem?
> 1 week

3. What is your ISP?
Telefonica Germany/Alice/Hansenet

4. What is your geographic location?
Germany

5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?
"Zeitüberschreitung der Anforderung" / "Request Times Out."

6. How about traceroutes of the above four addresses?
Trace : 208.68.240.13
------------------------------------------------
local -> IP= 192.168.1.100 RESERVED
TTL= 1 IP= 192.168.1.1 0 ms RESERVED
TTL= 2 IP= 213.191.89.38 23 ms GERMANY
TTL= 3 IP= 62.109.112.29 17 ms GERMANY
TTL= 4 TimedOut
TTL= 5 IP= 62.109.69.30 25 ms GERMANY
TTL= 6 TimedOut
TTL= 7 IP= 80.81.192.172 22 ms GERMANY
TTL= 8 IP= 72.52.92.89 35 ms UNITED STATES
TTL= 9 IP= 184.105.213.90 36 ms
TTL= 10 IP= 184.105.213.93 112 ms
TTL= 11 IP= 184.105.213.177 184 ms
TTL= 12 TimedOut
TTL= 13 TimedOut
TTL= 14 TimedOut
ICMP Errors

Trace : 208.68.240.16
------------------------------------------------
local -> IP= 192.168.1.100 RESERVED
TTL= 1 IP= 192.168.1.1 0 ms RESERVED
TTL= 2 IP= 213.191.89.38 16 ms GERMANY
TTL= 3 IP= 62.109.112.61 19 ms GERMANY
TTL= 4 TimedOut
TTL= 5 IP= 62.109.69.2 22 ms GERMANY
TTL= 6 TimedOut
TTL= 7 IP= 80.81.192.172 23 ms GERMANY
TTL= 8 IP= 72.52.92.89 36 ms UNITED STATES
TTL= 9 IP= 184.105.213.90 38 ms
TTL= 10 IP= 184.105.213.93 113 ms
TTL= 11 IP= 72.52.92.29 197 ms UNITED STATES
TTL= 12 TimedOut
TTL= 13 TimedOut
TTL= 14 TimedOut
ICMP Errors

Trace : 208.68.240.18
------------------------------------------------
local -> IP= 192.168.1.100 RESERVED
TTL= 1 IP= 192.168.1.1 0 ms RESERVED
TTL= 2 IP= 213.191.89.38 16 ms GERMANY
TTL= 3 IP= 62.109.112.62 18 ms GERMANY
TTL= 4 TimedOut
TTL= 5 IP= 62.109.69.6 23 ms GERMANY
TTL= 6 TimedOut
TTL= 7 IP= 80.81.192.172 25 ms GERMANY
TTL= 8 IP= 72.52.92.89 35 ms UNITED STATES
TTL= 9 IP= 184.105.213.90 38 ms
TTL= 10 IP= 184.105.213.93 122 ms
TTL= 11 IP= 184.105.213.177 191 ms
TTL= 12 TimedOut
TTL= 13 TimedOut
TTL= 14 TimedOut
ICMP Errors

Trace : 208.68.240.20
------------------------------------------------
local -> IP= 192.168.1.100 RESERVED
TTL= 1 IP= 192.168.1.1 0 ms RESERVED
TTL= 2 IP= 213.191.89.38 16 ms GERMANY
TTL= 3 IP= 62.109.112.61 18 ms GERMANY
TTL= 4 TimedOut
TTL= 5 IP= 62.109.69.30 22 ms GERMANY
TTL= 6 TimedOut
TTL= 7 IP= 80.81.192.172 25 ms GERMANY
TTL= 8 IP= 72.52.92.89 35 ms UNITED STATES
TTL= 9 IP= 184.105.213.90 37 ms
TTL= 10 IP= 184.105.213.93 113 ms
TTL= 11 IP= 184.105.213.177 185 ms
TTL= 12 TimedOut
TTL= 13 TimedOut
TTL= 14 TimedOut
ICMP Errors

7. Or nslookups of the above four addresses?
---
____________

archae86
Send message
Joined: 31 Aug 99
Posts: 886
Credit: 1,572,037
RAC: 0
United States
Message 1122478 - Posted: 28 Jun 2011, 15:29:46 UTC - in response to Message 1122104.

First, my personal light use of the SETI servers (one host set to Astropulse only, so on average getting/putting a little under two WUs a day) has been adequately served in the current unpleasantness, so I may not be your target information source. But on a lark I tried some of your tests, and for several minutes found pings to 208.68.240.13 to fail, while the other three worked. By the time I got to doing tracert, however, .13 worked--and on recheck it could ping as well. A quick recheck showed .16 had become unresponsive. So at least for me, at this moment, there may be a time-varying modest problem, so in case it might help, I shall try to answer your questions.

1. Are you able to reach ANY of the upload, download, or scheduling servers?

Yes

2. When did you start having this problem?

Not sure things have changed for me--never did these checks before

3. What is your ISP?

Comcast

4. What is your geographic location?

Albuquerque, NM

5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?

When first I tried this a few minutes ago, 16,18 and 20 all responded with times clustered near 85 msec. 13 timed out on at least three trials. More recently, 13,18, and 20 were fine, but 16 timed out. A recheck just as I type this line shows 13 again to fail on first trial, with others working--a retry of 13 after the others passed, worked, but had 227 msec time--out of the recently observed distribution. More retries gave successes in the 80s.

6. How about traceroutes of the above four addresses?

for .13 (just after a ping had worked)
1 * * * Request timed out.
2 9 ms 12 ms 8 ms 73.108.56.1
3 8 ms 6 ms 7 ms ge-1-1-ur01.sandia.nm.albuq.comcast.net [68.86.183.41]
4 8 ms 9 ms 9 ms te-9-1-ur02.sandia.nm.albuq.comcast.net [68.86.182.50]
5 9 ms 14 ms 11 ms te-8-2-ar02.albuquerque.nm.albuq.comcast.net [68.86.182.33]
6 15 ms 15 ms 15 ms te-0-0-0-2-cr01.santateresa.tx.ibone.comcast.net [68.86.94.197]
7 36 ms 33 ms 30 ms pos-0-4-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.86.17]
8 31 ms 33 ms 33 ms 66-208-233-202.ubr01a.sprgfd01.mi.hfc.comcastbusiness.net [66.208.233.202]
9 * 43 ms 45 ms Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net [64.214.174.246]
10 49 ms 48 ms 49 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
11 43 ms 46 ms * 64.71.140.42
12 * 206 ms * 208.68.243.254
13 * * 108 ms boinc2.ssl.berkeley.edu [208.68.240.13]

for .16 similar, except appreciable timing difference in late steps:

11 43 ms 44 ms 49 ms 64.71.140.42
12 83 ms 87 ms * 208.68.243.254
13 * * 81 ms setiboincdata.ssl.berkeley.edu [208.68.240.16]

for .18
on first trial, I got a single-line response !!??, so I'll give both the command and the response--don't know if this is abnormal (caching??)
C:\Users\Peter Stoll>tracert -w 250 208.68.240.18

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.18]
over a maximum of 30 hops:

1 84 ms 93 ms 82 ms boinc2.ssl.berkeley.edu [208.68.240.18]

Trace complete.

for .20
immediately after the .18 result shown above, got the same sort of single-line response for .20. And for a little while (maybe ten trials) I got single-line for all of the four as tried in sequence. Then I finally got a normal looking tracert output for .20, in which it looked immaterially different (few milliseconds of timing) from the others.

7. Or nslookups of the above four addresses?

At a time when pings were working, all four gave responses like:

Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.13

Hoping to catch it doing something bad, I delayed posting until I again got no ping on .13. But an nslookup immediately after was normal, followed by another bad ping.

Or if you know what the exact problem is (or if there isn't really a single problem but a set of problems) that would be useful, too.

Not me.

____________

Twisted
Send message
Joined: 27 May 99
Posts: 81
Credit: 1,819,751
RAC: 2,021
United States
Message 1122494 - Posted: 28 Jun 2011, 16:26:14 UTC - in response to Message 1122190.



6. As shown below, it stops after
10gigabitethernet1-4.core1.pao1.he.net [72.52.92.29]
OR
10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]

Good luck!
And thanks in advance, Matt



This is what I'm seeing at home as well. - core1.pao1.he.net seems to be the killer...


1. Are you able to reach ANY of the upload, download, or scheduling servers?
at work yes - at home no

2. When did you start having this problem?
About the 16th - then it was resolved at work last weeks down time
still not working from home

3. What is your ISP?
work AT&T - home Cox Cable

4. What is your geographic location?
Louisiana, US UTC-6

5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?
work has no issues - home No response

6. How about traceroutes of the above four addresses?
work has no issues - home Only tried *.20 - deadends at ***.core1.pao1.he.net

7. Or nslookups of the above four addresses?
work has no issues - home Haven't tried...can try when I get home and update

Thanks guys
____________
"Two things are infinite: The universe and human stupidity; and I'm not sure about the universe." - Albert Einstein

Profile White Mountain Wes
Avatar
Send message
Joined: 24 Jul 08
Posts: 258
Credit: 3,125,880
RAC: 988
United States
Message 1122519 - Posted: 28 Jun 2011, 22:28:55 UTC - in response to Message 1122104.

Hey all - I'm trying to characterize this current problem where some users are unable to reach any of our servers through Hurricane Electric. If possible please answer in this thread the following questions (feel free to leave out anything you want to keep private, or don't understand):

1. Are you able to reach ANY of the upload, download, or scheduling servers?
2. When did you start having this problem?
3. What is your ISP?
4. What is your geographic location?
5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?
6. How about traceroutes of the above four addresses?
7. Or nslookups of the above four addresses?

Or if you know what the exact problem is (or if there isn't really a single problem but a set of problems) that would be useful, too.

Thanks!

- Matt


I am running 2 machines over the same DSL modem/router. One is running win7-64 with an AMD quad core and it seems to communicate S@H normally. The other is an older single core Celeron D machine running Linux Ubuntu. That one was also communicating fine up until 2 weeks ago. Now it is only able to connect to S@H to download, upload, or report once or twice a day at best. Why one works and the other doesn’t is a mystery. This data is from the Ubuntu machine.

ISP: Granite State Communications (local phone company)
Location: New Hampshire (USA)

Ping to 208.68.240.13: 65% successful, Average time 193ms
Ping to 208.68.240.16: 88% successful, Average time 178ms
Ping to 208.68.240.18: 91% successful, Average time 179ms
Ping to 208.68.240.20: 84% successful, Average time 179ms

Trace Route to 208.68.240.13
1 dslmodem.domain.actdsltmp 1.100ms
2 e0-gw.wear.gsinet.net 107.708ms
3 gi0-3.ca01.bos04.atlas.cogentco.com 264.068ms
4 no reply
5 te0-3-0-7.ccr21.bos01.atlas.cogentco.com 115.299ms
6 te0-5-0-3.mpd21.jfk02.atlas.cogentco.com 115.512ms
7 te0-1-0-4.mpd21.dca01.atlas.cogentco.com 121.374ms
8 te0-2-0-1.mpd21.iad02.atlas.cogentco.com 122.401ms
9 te2-3-10GE.ar5.DCA3.gblx.net 127.728ms
10 te4-3-10G.ar3.SJC2.gblx.net 278.085ms
11 Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net 191.041ms
12 10gigabitethernet3-2.core1.pao1.he.net 197.203ms
13 64.71.140.42 189.568ms
14 64.71.140.42 188.351ms
14 208.68.243.254 230.443ms
15 no reply
Continues “no reply” up to hop 30

Trace Route to 208.68.240.16
1 dslmodem.domain.actdsltmp 3.898ms
2 e0 107.718ms
3 gi0 108.683ms
4 no reply
5 te0 115.478ms
6 te0-3-0-2.mpd21.jfk02.atlas.cogentco.com 115.435ms
7 te0-2-0-2.mpd21.dca01.atlas.cogentco.com 121.851ms
8 te0-1-0-1.mpd21.iad02.atlas.cogentco.com 121.878ms
9 te2 124.913ms
10 te4 188.106ms
11 Hurricane 187.431ms
12 10gigabitethernet3 192.410ms
13 64.71.140.42 189.472ms
14 64.71.140.42 188.797ms
14 208.68.243.254 190.599ms
15 no reply
Continues “no reply” to hop 30

Trace Route to 208.68.240.18
1 dslmodem.domain.actdsltmp 1.589ms
2 e0-gw.wear.gsinet.net 108.216ms
3 gi0-3.ca01.bos04.atlas.cogentco.com 109.407ms
4 no reply
5 te0-3-0-7.ccr21.bos01.atlas.cogentco.com 115.353ms
6 te0-0-0-3.mpd21.jfk02.atlas.cogentco.com 115.508ms
7 te0-3-0-7.mpd21.dca01.atlas.cogentco.com 120.828ms
8 te0-1-0-5.mpd21.iad02.atlas.cogentco.com 123.161ms
9 te2-3-10GE.ar5.DCA3.gblx.net 122.477ms
10 te4-3-10G.ar3.SJC2.gblx.net 349.554ms
11 Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net 187.462ms
12 10gigabitethernet3-2.core1.pao1.he.net 192.323ms
13 64.71.140.42 188.984ms
14 64.71.140.42 189.246ms
14 208.68.243.254 228.607ms
15 no reply
Continues “no reply” to hop 30

I forgot to record the trace Route to 208.68.240.20 but it looks pretty much the same; Nothing after 208.68.243.254.

____________

Peter Kehne
Send message
Joined: 11 Jul 06
Posts: 1
Credit: 261,010
RAC: 0
Germany
Message 1122658 - Posted: 29 Jun 2011, 10:19:05 UTC

1. Are you able to reach ANY of the upload, download, or scheduling servers?
no

2. When did you start having this problem?
about 2 weeks ago

3. What is your ISP?
Alice

4. What is your geographic location?
Germany

5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?

C:\Dokumente und Einstellungen\Peter_K>ping 208.68.240.13

Ping wird ausgeführt für 208.68.240.13 mit 32 Bytes Daten:

Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.

Ping-Statistik für 208.68.240.13:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust),

C:\Dokumente und Einstellungen\Peter_K>ping 208.68.240.16

Ping wird ausgeführt für 208.68.240.16 mit 32 Bytes Daten:

Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.

Ping-Statistik für 208.68.240.16:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust),

C:\Dokumente und Einstellungen\Peter_K>ping 208.68.240.18

Ping wird ausgeführt für 208.68.240.18 mit 32 Bytes Daten:

Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.

Ping-Statistik für 208.68.240.18:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust),

C:\Dokumente und Einstellungen\Peter_K>ping 208.68.240.20

Ping wird ausgeführt für 208.68.240.20 mit 32 Bytes Daten:

Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.

Ping-Statistik für 208.68.240.20:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4 (100% Verlust),

6. How about traceroutes of the above four addresses?
C:\Dokumente und Einstellungen\Peter_K>tracert 208.68.240.13

Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.13] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms alice.box [192.168.1.1]
2 32 ms 32 ms 32 ms lo1.br54.weham.de.hansenet.net [213.191.64.175]
3 32 ms 32 ms 32 ms ae1-102.cr01.weham.de.hansenet.net [62.109.121.125]
4 39 ms 39 ms 39 ms ae4-0.cr01.fra.de.hansenet.net [213.191.66.73]
5 40 ms 48 ms 39 ms ae0-0.xd01.fra.de.hansenet.net [62.109.69.2]
6 39 ms 39 ms 40 ms ae1-0.pr03.decix.de.hansenet.net [213.191.66.142]
7 40 ms 43 ms 49 ms 20gigabitethernet4-3.core1.fra1.he.net [80.81.192.172]
8 55 ms 54 ms 54 ms 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
9 49 ms 50 ms 49 ms 10gigabitethernet1-1.core1.par2.he.net [184.105.213.90]
10 136 ms 128 ms 129 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
11 203 ms 203 ms 215 ms 10gigabitethernet1-4.core1.pao1.he.net [72.52.92.29]
12 * * * Zeitüberschreitung der Anforderung.
...
30 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

C:\Dokumente und Einstellungen\Peter_K>tracert 208.68.240.16

Routenverfolgung zu setiboincdata.ssl.berkeley.edu [208.68.240.16] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms alice.box [192.168.1.1]
2 32 ms 32 ms 32 ms lo1.br54.weham.de.hansenet.net [213.191.64.175]
3 33 ms 67 ms 32 ms ae0-101.cr01.weham.de.hansenet.net [62.109.120.125]
4 40 ms 40 ms 71 ms ae4-0.cr01.fra.de.hansenet.net [213.191.66.73]
5 39 ms 41 ms 40 ms ae0-0.xd02.fra.de.hansenet.net [62.109.69.30]
6 39 ms 39 ms 40 ms ae0-0.pr03.decix.de.hansenet.net [213.191.66.138]
7 40 ms 40 ms 46 ms 20gigabitethernet4-3.core1.fra1.he.net [80.81.192.172]
8 51 ms 50 ms 51 ms 10gigabitethernet1-4.core1.par2.he.net [184.105.213.162]
9 128 ms 137 ms 128 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
10 225 ms 200 ms 201 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
11 * * * Zeitüberschreitung der Anforderung.
...
30 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

C:\Dokumente und Einstellungen\Peter_K>tracert 208.68.240.18

Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.18] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms alice.box [192.168.1.1]
2 32 ms 32 ms 32 ms lo1.br54.weham.de.hansenet.net [213.191.64.175]
3 32 ms 32 ms 32 ms ae0-101.cr01.asham.de.hansenet.net [62.109.120.126]
4 39 ms 39 ms 40 ms ae4-0.cr01.fra.de.hansenet.net [213.191.66.77]
5 39 ms 40 ms 47 ms ae1-0.xd01.fra.de.hansenet.net [62.109.69.6]
6 40 ms 40 ms 40 ms ae0-0.pr03.decix.de.hansenet.net [213.191.66.138]
7 40 ms 41 ms 45 ms 20gigabitethernet4-3.core1.fra1.he.net [80.81.192.172]
8 63 ms 54 ms 55 ms 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
9 54 ms 50 ms 49 ms 10gigabitethernet1-1.core1.par2.he.net [184.105.213.90]
10 135 ms 128 ms 129 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
11 207 ms 203 ms 203 ms 10gigabitethernet1-4.core1.pao1.he.net [72.52.92.29]
12 * * * Zeitüberschreitung der Anforderung.
...
30 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

C:\Dokumente und Einstellungen\Peter_K>tracert 208.68.240.20

Routenverfolgung zu setiboinc.ssl.berkeley.edu [208.68.240.20] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms alice.box [192.168.1.1]
2 33 ms 32 ms 32 ms lo1.br54.weham.de.hansenet.net [213.191.64.175]
3 32 ms 32 ms 32 ms ae0-101.cr01.weham.de.hansenet.net [62.109.120.125]
4 40 ms 39 ms 40 ms ae4-0.cr01.fra.de.hansenet.net [213.191.66.73]
5 40 ms 40 ms 40 ms ae0-0.xd01.fra.de.hansenet.net [62.109.69.2]
6 39 ms 40 ms 40 ms ae1-0.pr03.decix.de.hansenet.net [213.191.66.142]
7 40 ms 40 ms 56 ms 20gigabitethernet4-3.core1.fra1.he.net [80.81.192.172]
8 60 ms 55 ms 55 ms 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
9 50 ms 49 ms 50 ms 10gigabitethernet1-1.core1.par2.he.net [184.105.213.90]
10 128 ms 128 ms 138 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
11 209 ms 202 ms 202 ms 10gigabitethernet1-4.core1.pao1.he.net [72.52.92.29]
12 * * * Zeitüberschreitung der Anforderung.
...
30 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

7. Or nslookups of the above four addresses?
C:\Dokumente und Einstellungen\Peter_K>nslookup 208.68.240.13
Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.13

C:\Dokumente und Einstellungen\Peter_K>nslookup 208.68.240.16
Name: setiboincdata.ssl.berkeley.edu
Address: 208.68.240.16

C:\Dokumente und Einstellungen\Peter_K>nslookup 208.68.240.18
Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.18

C:\Dokumente und Einstellungen\Peter_K>nslookup 208.68.240.20
Name: setiboinc.ssl.berkeley.edu
Address: 208.68.240.20


Best regards
Peter

Dr. Wolfram Sperber
Send message
Joined: 4 Jul 99
Posts: 9
Credit: 723,628
RAC: 295
Germany
Message 1122659 - Posted: 29 Jun 2011, 11:23:41 UTC - in response to Message 1122519.

When all will be functioning again - it will be a pity that lots of older results uploaded then will be gone... at least for credit points.
(Today I'm loosing 8 results of 20 in my local queue.)

Good luck in fixing the problem!

____________
<a href="http://allprojectstats.com/showuser.php?id=622594"><img src="http://allprojectstats.com/su622594n3-2a12-1-0.png" border=0>

caldwel1
Avatar
Send message
Joined: 9 Oct 07
Posts: 1
Credit: 266,801
RAC: 0
Canada
Message 1122661 - Posted: 29 Jun 2011, 11:42:07 UTC
Last modified: 29 Jun 2011, 11:43:59 UTC

1. Are you able to reach ANY of the upload, download, or scheduling servers?
sporadically
2. When did you start having this problem?
over a month ago
3. What is your ISP?
eastlink.ca
4. What is your geographic location?
northern Ontario, Canada
5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?
all are fine
6. How about traceroutes of the above four addresses?
all are fine
7. Or nslookups of the above four addresses?
N/A

Currently unable to get new wu's - for the past several hours.

Profile Wiggo
Avatar
Send message
Joined: 24 Jan 00
Posts: 6452
Credit: 90,126,597
RAC: 72,379
Australia
Message 1122666 - Posted: 29 Jun 2011, 12:10:15 UTC - in response to Message 1122661.

1. Are you able to reach ANY of the upload, download, or scheduling servers?
sporadically
2. When did you start having this problem?
over a month ago
3. What is your ISP?
eastlink.ca
4. What is your geographic location?
northern Ontario, Canada
5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?
all are fine
6. How about traceroutes of the above four addresses?
all are fine
7. Or nslookups of the above four addresses?
N/A

Currently unable to get new wu's - for the past several hours.

You currently can't get any because there is none as shown by the Server Statis page. ;)

Cheers.
____________

Twisted
Send message
Joined: 27 May 99
Posts: 81
Credit: 1,819,751
RAC: 2,021
United States
Message 1122669 - Posted: 29 Jun 2011, 12:39:41 UTC

Something must have happened at HE...my two at the house are working again!

Kevin

____________
"Two things are infinite: The universe and human stupidity; and I'm not sure about the universe." - Albert Einstein

Profile ML1
Volunteer tester
Send message
Joined: 25 Nov 01
Posts: 8263
Credit: 4,070,696
RAC: 426
United Kingdom
Message 1122671 - Posted: 29 Jun 2011, 12:46:00 UTC - in response to Message 1122190.
Last modified: 29 Jun 2011, 12:46:45 UTC


1. ... not reaching any of your servers!
2. As I wrote initially on June 24th, this all began about June 16th...
3. Alice (Hansenet), Germany
4. Berlin, Germany
5. All four servers don't respond at all (s.b.)
6. As shown below, it stops after
10gigabitethernet1-4.core1.pao1.he.net [72.52.92.29]

OR
10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
7. nslookup: addresses seem to be resolved correctly

...


(My emphasis.)

From that example and a few others listed in the thread, as commented by others, the next hop after those two nodes looks to be a problem for HE to fix...


I'd guess the data packet loss the rest of us see is just the s@h pipe being congested and dropping data due to overload.

Hope this thread gives Matt something to work on.

Keep searchin',
Martin
____________
See new freedom: Mageia4
Linux Voice See & try out your OS Freedom!
The Future is what We make IT (GPLv3)

Neonblue
Send message
Joined: 15 May 07
Posts: 2
Credit: 7,190,573
RAC: 9,846
United States
Message 1122677 - Posted: 29 Jun 2011, 13:07:05 UTC

Just a FYI here, my computer hasn't received a task in a long while. I see other posts here as well regarding the same thing but I just wanted to let you know that I'm having the same issue.

For me it appears that I am communicating with the server; just not receiving a task.

6/29/2011 6:01:16 AM Starting BOINC client version 6.10.58 for windows_x86_64
6/29/2011 6:01:16 AM log flags: file_xfer, sched_ops, task
6/29/2011 6:01:16 AM Libraries: libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3
6/29/2011 6:01:16 AM Data directory: C:\ProgramData\BOINC
6/29/2011 6:01:16 AM Running under account XXXXXXXX
6/29/2011 6:01:16 AM Processor: 2 AuthenticAMD AMD Processor model unknown [Family 15 Model 67 Stepping 3]
6/29/2011 6:01:16 AM Processor: 1.00 MB cache
6/29/2011 6:01:16 AM Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni cx16 syscall nx lm svm rdtscp 3dnowext 3dnow
6/29/2011 6:01:16 AM OS: Microsoft Windows 7: Ultimate x64 Edition, Service Pack 1, (06.01.7601.00)
6/29/2011 6:01:16 AM Memory: 4.00 GB physical, 8.00 GB virtual
6/29/2011 6:01:16 AM Disk: 465.76 GB total, 191.38 GB free
6/29/2011 6:01:16 AM Local time is UTC -5 hours
6/29/2011 6:01:19 AM NVIDIA GPU 0: GeForce 9600 GT (driver version 27533, CUDA version 4000, compute capability 1.1, 465MB, 214 GFLOPS peak)
6/29/2011 6:01:19 AM NVIDIA GPU 1: GeForce 9600 GT (driver version 27533, CUDA version 4000, compute capability 1.1, 464MB, 214 GFLOPS peak)
6/29/2011 6:01:20 AM SETI@home URL http://setiathome.berkeley.edu/; Computer ID 5189447; resource share 100
6/29/2011 6:01:20 AM SETI@home General prefs: from SETI@home (last modified 19-May-2007 12:59:00)
6/29/2011 6:01:20 AM SETI@home Host location: none
6/29/2011 6:01:20 AM SETI@home General prefs: using your defaults
6/29/2011 6:01:20 AM Reading preferences override file
6/29/2011 6:01:20 AM Preferences:
6/29/2011 6:01:20 AM max memory usage when active: 2047.77MB
6/29/2011 6:01:20 AM max memory usage when idle: 3685.99MB
6/29/2011 6:01:20 AM max disk usage: 10.00GB
6/29/2011 6:01:20 AM don't compute while active
6/29/2011 6:01:20 AM don't use GPU while active
6/29/2011 6:01:20 AM suspend work if non-BOINC CPU load exceeds 50 %
6/29/2011 6:01:20 AM (to change preferences, visit the web site of an attached project, or select Preferences in the Manager)
6/29/2011 6:01:20 AM Not using a proxy
6/29/2011 6:01:20 AM Suspending computation - user is active
6/29/2011 6:01:20 AM Suspending network activity - user is active
6/29/2011 6:33:30 AM Resuming network activity
6/29/2011 6:33:30 AM SETI@home Restarting task ap_29ap11ah_B0_P0_00035_20110627_19753.wu_1 using astropulse_v505 version 505
6/29/2011 6:33:30 AM SETI@home Sending scheduler request: To fetch work.
6/29/2011 6:33:30 AM SETI@home Requesting new tasks for CPU
6/29/2011 6:33:32 AM SETI@home Scheduler request completed: got 0 new tasks
6/29/2011 6:33:32 AM SETI@home Message from server: Project has no tasks available
6/29/2011 6:38:37 AM SETI@home Sending scheduler request: To fetch work.
6/29/2011 6:38:37 AM SETI@home Requesting new tasks for CPU
6/29/2011 6:38:39 AM SETI@home Scheduler request completed: got 0 new tasks
6/29/2011 6:38:39 AM SETI@home Message from server: Project has no tasks available
6/29/2011 6:43:44 AM SETI@home Sending scheduler request: To fetch work.
6/29/2011 6:43:44 AM SETI@home Requesting new tasks for CPU
6/29/2011 6:43:46 AM SETI@home Scheduler request completed: got 0 new tasks
6/29/2011 6:43:46 AM SETI@home Message from server: Project has no tasks available
6/29/2011 6:48:51 AM SETI@home Sending scheduler request: To fetch work.
6/29/2011 6:48:51 AM SETI@home Requesting new tasks for CPU
6/29/2011 6:48:52 AM SETI@home Scheduler request completed: got 0 new tasks
6/29/2011 6:48:52 AM SETI@home Message from server: Project has no tasks available
6/29/2011 6:53:57 AM SETI@home Sending scheduler request: To fetch work.
6/29/2011 6:53:57 AM SETI@home Requesting new tasks for CPU
6/29/2011 6:53:58 AM SETI@home Scheduler request completed: got 0 new tasks
6/29/2011 6:53:58 AM SETI@home Message from server: Project has no tasks available
6/29/2011 6:59:03 AM SETI@home Sending scheduler request: To fetch work.
6/29/2011 6:59:03 AM SETI@home Requesting new tasks for CPU
6/29/2011 6:59:04 AM SETI@home Scheduler request completed: got 0 new tasks
6/29/2011 6:59:04 AM SETI@home Message from server: Project has no tasks available
6/29/2011 7:18:10 AM SETI@home Sending scheduler request: To fetch work.
6/29/2011 7:18:10 AM SETI@home Requesting new tasks for GPU
6/29/2011 7:18:11 AM SETI@home Scheduler request completed: got 0 new tasks
6/29/2011 7:18:11 AM SETI@home Message from server: Project has no tasks available
6/29/2011 7:29:48 AM Suspending computation - user is active
6/29/2011 7:29:48 AM Suspending network activity - user is active

Profile HAL9000
Volunteer tester
Avatar
Send message
Joined: 11 Sep 99
Posts: 3842
Credit: 106,476,910
RAC: 92,073
United States
Message 1122693 - Posted: 29 Jun 2011, 14:13:03 UTC - in response to Message 1122671.
Last modified: 29 Jun 2011, 14:14:18 UTC


1. ... not reaching any of your servers!
2. As I wrote initially on June 24th, this all began about June 16th...
3. Alice (Hansenet), Germany
4. Berlin, Germany
5. All four servers don't respond at all (s.b.)
6. As shown below, it stops after
10gigabitethernet1-4.core1.pao1.he.net [72.52.92.29]

OR
10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
7. nslookup: addresses seem to be resolved correctly

...


(My emphasis.)

From that example and a few others listed in the thread, as commented by others, the next hop after those two nodes looks to be a problem for HE to fix...


I'd guess the data packet loss the rest of us see is just the s@h pipe being congested and dropping data due to overload.

Hope this thread gives Matt something to work on.

Keep searchin',
Martin

I think that is close to the issue. For most people the next hop after those is 64.71.140.42. For me at work I hit hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54] before 64.71.140.42 & don't have much of an issue. So I would guess whatever equipment 64.71.140.42 happens to be might be the issue. Perhaps some routing issue internally, or it could be the 10gigabitethernet*.core1.pao1.he.net side.
____________
SETI@home classic workunits: 93,865 CPU time: 863,447 hours

Join the BP6/VP6 User Group today!

Russell McGaha
Volunteer tester
Send message
Joined: 3 Apr 99
Posts: 11
Credit: 23,885,409
RAC: 6,258
United States
Message 1122726 - Posted: 29 Jun 2011, 15:23:12 UTC

Well I've 2 machine thats been unable to communicate with SETI for two weeks; the last successfull communication was 6/11. The following messages are repeated in the log.
Wed Jun 29 07:53:57 2011 SETI@home Sending scheduler request: To fetch work.
Wed Jun 29 07:53:57 2011 SETI@home Requesting new tasks
Wed Jun 29 07:55:12 2011 Project communication failed: attempting access to reference site
Wed Jun 29 07:55:12 2011 SETI@home Scheduler request failed: Couldn't connect to server
Wed Jun 29 07:55:13 2011 Internet access OK - project servers may be temporarily down.
Wed Jun 29 07:57:50 2011 Suspending network activity - user is active
Wed Jun 29 08:06:03 2011 Resuming network activity
Wed Jun 29 08:06:11 2011 Suspending network activity - user is active

These machine are communicating with Einstien fine.

My ISP is Bellsouth [AT&T]
Location East Central Alabama
Ping 208.68.240.13
PING 208.68.240.13 (208.68.240.13): 56 data bytes
^C
--- 208.68.240.13 ping statistics ---
318 packets transmitted, 0 packets received, 100% packet loss

Ping 208.68.240.16
PING 208.68.240.16 (208.68.240.16): 56 data bytes
^C
--- 208.68.240.16 ping statistics ---
265 packets transmitted, 0 packets received, 100% packet loss

Ping 208.68.240.18
PING 208.68.240.18 (208.68.240.18): 56 data bytes
^C
--- 208.68.240.18 ping statistics ---
37 packets transmitted, 0 packets received, 100% packet loss

Ping 208.68.240.20
PING 208.68.240.20 (208.68.240.20): 56 data bytes
^C
--- 208.68.240.20 ping statistics ---
80 packets transmitted, 0 packets received, 100% packet loss

..........
...........
phone call to AT&T
............
.............

Strange problem here; the above ping stats hold for 4 machines I have [only two run Boinc/SETI) that are IPMAPed to public IP's, others that are behind a router and a non IPMAPed ip and have no trouble reaching SETI or Einstien.

Traceroute for all of the IP's ends at the same place:
traceroute to 208.68.240.20 (208.68.240.20), 64 hops max, 40 byte packets
5 12.81.36.2 (12.81.36.2) 14.632 ms 14.514 ms 15.290 ms
6 12.83.2.206 (12.83.2.206) 16.430 ms 15.584 ms 15.786 ms
7 12.81.16.69 (12.81.16.69) 14.956 ms 14.560 ms 14.693 ms
8 74.175.192.86 (74.175.192.86) 19.595 ms 19.118 ms 19.156 ms
9 cr1.attga.ip.att.net (12.122.141.186) 25.545 ms 20.524 ms cr2.attga.ip.att.net (12.122.140.186) 21.221 ms
10 attga01jt.ip.att.net (12.122.80.185) 18.583 ms attga01jt.ip.att.net (12.122.80.221) 29.165 ms 19.075 ms
11 192.205.33.150 (192.205.33.150) 19.127 ms 192.205.35.90 (192.205.35.90) 19.641 ms 19.175 ms
12 Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net (64.214.174.246) 91.302 ms 97.454 ms 97.581 ms
13 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 93.529 ms 91.843 ms 92.128 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *

Hope this helps.

If this isn't the same problem; anyone have any ideas??

Russell

archae86
Send message
Joined: 31 Aug 99
Posts: 886
Credit: 1,572,037
RAC: 0
United States
Message 1122731 - Posted: 29 Jun 2011, 15:36:50 UTC - in response to Message 1122671.
Last modified: 29 Jun 2011, 15:37:39 UTC

I'd guess the data packet loss the rest of us see is just the s@h pipe being congested and dropping data due to overload.
Perhaps yes.
With a view to illuminating this point, I intend to try parallel 100 count pings in time of low and high load. By the cricket graph, this morning I'd call low load, as the traffic out (which it labels as in) having declined hours ago and currently bumping along at 12 Mbits/sec, though traffic the other way is pretty ordinary, at 16).

Using commands like:
ping -n 100 -w 500 208.68.240.13

I got:
min max avg loss server 43 178 50 1% .13 43 56 46 0% .16 43 107 46 0% .18 43 180 48 1% .20


By memory, these are across-the-board much better than I saw when running the same tests about twelve hours earlier.

(during worse times early, I tried a value of 10000 millisecs for the -w parameter, thinking the default might be missing some late replies, but there seemed to be no data above 500, which saves time lost on failures.
____________

Previous · 1 · 2 · 3 · 4 · 5 . . . 25 · Next

Message boards : Number crunching : HE connection problems thread

Copyright © 2014 University of California