VCCA Home Forums GENERAL DISCUSSION Forum Questions Chat Slowdown?

yep.... it's pretty dang fast for me this morning...

Ruscar -- please perform the TRACE during the time that you can't log in. (Although you can do it anytime that you want, just to see how the network is behaving.) What it is doing is measuring how long it takes the network to make each of the "hops" to the Chat server. Ultimately it should time-out at the offending location. Then we know that it's a "network" issue and not a "server" issue.

On the contrary, if you get all hops completed, then we know it's a "server" issue since you can "ping" all the way to it.

Thanks for asking.

Sunday afternoon: Chevy Chatter would not load between 1:30 PM and 3:25 PM PDT.

@ ca 9:40 all is good.

But,

9:10 pm cdt
Service Unavailable.
Technical description:
504 Gateway Time-out - The web server is not responding

Service Unavailable.
Technical description:
504 Gateway Time-out - The web server is not responding

Service Unavailable.
Technical description:
504 Gateway Time-out - The web server is not responding

Response Error.
Technical description:
502 Bad Gateway - Response Error, a bad response was received from another proxy server or the destination origin server.

Response Error.
Technical description:
502 Bad Gateway - Response Error, a bad response was received from another proxy server or the destination origin server.

Service Unavailable.
Technical description:
504 Gateway Time-out - The web server is not responding

Service Unavailable.
Technical description:
504 Gateway Time-out - The web server is not responding

Sorry but don't have exact times or since I didn't copy the instructions given on page 6 didn't get the other requested information.

9:22 pm cdt okay

9:25 pm cdt
Response Error.
Technical description:
502 Bad Gateway - Response Error, a bad response was received from another proxy server or the destination origin server.

Response Error.
Technical description:
502 Bad Gateway - Response Error, a bad response was received from another proxy server or the destination origin server.

Service Unavailable.
Technical description:
504 Gateway Time-out - The web server is not responding

Service Unavailable.
Technical description:
504 Gateway Time-out - The web server is not responding

Again didn't get exact times for each message. Takes between 1-2 minutes for to get the time out message.

Finally gave up and looked at other websites.

At 9:40 pm cdt everything good

Chipper,
Did you use Trace Route?

3. Run Traceroute -->
Start -> Run.
Type "cmd" and then click "ok".
Enter --> tracert vcca.org
(After it finishes the trace--> Right Click -- <Select All> -- Press <ENTER> --> then CTRL+V to insert on your Notepad page)

I'm with you Kevin. I have never had the problems these guys have had. I nomally log on in the late evening here in Nor Cal.

Bill, last night 9:30 PM EDT I typed a reply in '46-48. Hit view post button. 5 min. went by, nothing. Hit view post button again, nothing. Hit refresh, still nothing. At 9:45 PM EDT ran trace.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Russell>tracert vcca.org

Tracing route to vcca.org [64.6.242.76]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 17 ms 18 ms 17 ms adsl-68-217-245-1.ags.bellsouth.net [68.217.245.
1]
3 23 ms 24 ms 22 ms 70.159.181.15
4 24 ms 22 ms 22 ms 12.81.64.67
5 25 ms 27 ms 26 ms 12.83.0.102
6 21 ms 22 ms 20 ms 12.81.0.15
7 32 ms 24 ms 29 ms 74.175.192.102
8 * 26 ms 23 ms cr2.attga.ip.att.net [12.122.140.170]
9 21 ms 23 ms 23 ms attga02jt.ip.att.net [12.123.22.153]
10 22 ms 87 ms 22 ms 144.232.1.65
11 23 ms 23 ms 23 ms sl-crs4-atl-.sprintlink.net [144.232.1.217]
12 28 ms 29 ms 28 ms 144.232.5.211
13 42 ms 42 ms 42 ms 144.232.10.46
14 42 ms 42 ms 42 ms sl-crs2-rly-0-0-3-0.sprintlink.net [144.232.8.16
5]
15 48 ms 48 ms 48 ms sl-st21-pit-1-0-0.sprintlink.net [144.232.9.99]

16 50 ms 49 ms 50 ms 63.160.2.10
17 64 ms 65 ms * te1-7-4.4037.upa-core.expedient.com [209.166.144
.210]
18 58 ms 54 ms 55 ms myhostcenter-gw-primary.cust.e-xpedient.com [66.
11.1.179]
19 * * 70 ms s34.n230.n6.n64.static.myhostcenter.com [64.6.23
0.34]
20 * * * Request timed out.
21 71 ms 71 ms 72 ms s76.n242.n6.n64.static.myhostcenter.com [64.6.24
2.76]

Trace complete.

C:\Users\Russell>
C:\Users\Russell>

At 10:00 PM EDT


C:\Users\Russell>Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Russell>tracert vcca.org

Tracing route to vcca.org [64.6.242.76]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 18 ms 17 ms 19 ms adsl-68-217-245-1.ags.bellsouth.net [68.217.245.
1]
3 22 ms 23 ms 23 ms 70.159.181.15
4 23 ms 21 ms 22 ms 12.81.64.67
5 25 ms 27 ms 24 ms 12.83.0.102
6 22 ms 21 ms 21 ms 12.81.0.15
7 22 ms 22 ms 22 ms 74.175.192.102
8 28 ms 27 ms 27 ms cr2.attga.ip.att.net [12.122.140.170]
9 21 ms 21 ms 21 ms attga02jt.ip.att.net [12.123.22.153]
10 22 ms 22 ms 21 ms 144.232.1.65
11 23 ms 22 ms * sl-crs4-atl-.sprintlink.net [144.232.1.217]
12 26 ms 28 ms 28 ms 144.232.5.211
13 90 ms 75 ms 74 ms 144.232.10.46
14 88 ms 88 ms 87 ms sl-crs2-rly-0-0-3-0.sprintlink.net [144.232.8.16
5]
15 88 ms 87 ms 87 ms sl-st21-pit-1-0-0.sprintlink.net [144.232.9.99]

16 49 ms 49 ms 49 ms 63.160.2.10
17 80 ms 65 ms 69 ms te1-7-4.4037.upa-core.expedient.com [209.166.144
.210]
18 55 ms 53 ms 56 ms myhostcenter-gw-primary.cust.e-xpedient.com [66.
11.1.179]
19 * * 63 ms s34.n230.n6.n64.static.myhostcenter.com [64.6.23
0.34]
20 * * * Request timed out.
21 * 73 ms * s76.n242.n6.n64.static.myhostcenter.com [64.6.24
2.76]
22 72 ms 75 ms * s76.n242.n6.n64.static.myhostcenter.com [64.6.24
2.76]
23 * * 74 ms s76.n242.n6.n64.static.myhostcenter.com [64.6.24
2.76]

Trace complete.

C:\Users\Russell>

At 10:15 PM EDT
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Russell>tracert vcca.org

Tracing route to vcca.org [64.6.242.76]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 18 ms 17 ms 19 ms adsl-68-217-245-1.ags.bellsouth.net [68.217.245.
1]
3 22 ms 23 ms 23 ms 70.159.181.15
4 23 ms 21 ms 22 ms 12.81.64.67
5 25 ms 27 ms 24 ms 12.83.0.102
6 22 ms 21 ms 21 ms 12.81.0.15
7 22 ms 22 ms 22 ms 74.175.192.102
8 28 ms 27 ms 27 ms cr2.attga.ip.att.net [12.122.140.170]
9 21 ms 21 ms 21 ms attga02jt.ip.att.net [12.123.22.153]
10 22 ms 22 ms 21 ms 144.232.1.65
11 23 ms 22 ms * sl-crs4-atl-.sprintlink.net [144.232.1.217]
12 26 ms 28 ms 28 ms 144.232.5.211
13 90 ms 75 ms 74 ms 144.232.10.46
14 88 ms 88 ms 87 ms sl-crs2-rly-0-0-3-0.sprintlink.net [144.232.8.16
5]
15 88 ms 87 ms 87 ms sl-st21-pit-1-0-0.sprintlink.net [144.232.9.99]

16 49 ms 49 ms 49 ms 63.160.2.10
17 80 ms 65 ms 69 ms te1-7-4.4037.upa-core.expedient.com [209.166.144
.210]
18 55 ms 53 ms 56 ms myhostcenter-gw-primary.cust.e-xpedient.com [66.
11.1.179]
19 * * 63 ms s34.n230.n6.n64.static.myhostcenter.com [64.6.23
0.34]
20 * * * Request timed out.
21 * 73 ms * s76.n242.n6.n64.static.myhostcenter.com [64.6.24
2.76]
22 72 ms 75 ms * s76.n242.n6.n64.static.myhostcenter.com [64.6.24
2.76]
23 * * 74 ms s76.n242.n6.n64.static.myhostcenter.com [64.6.24
2.76]

Trace complete.

C:\Users\Russell>

Is myhostcenter where our server is????????

10:30 gave up!
Bill, What do YOU make of this??????
Russell

Hi Bill, I had trouble accessing yesterday as well, in morning (about 5am PDT) and last night about 6pm PDT. Both times I could get to the chatter forum page in a few seconds but no further. Last nite I tried a second time, and message was web page not available for display, or some common system message like that. Sorry did not write it down, but you probably know it. Keep on truckin'.

Is there a message in this post? Perhaps 2: First, since logging on in Cali late at night is always positive, likely when all other site traffic from the east has ended, it might suggest there is a capacity issue on the site. Second, we should all be so lucky to live there!!

Keith, maybe it is because you and Kevin live close to the server?? Or, Maybe, it likes people who's names start with a "K"??

It has happened to me at least once a week for the past 5 weeks. All different times of the day and days of the week. And from two different location. Each are different networks.

You guys are lucky!!!!

Bill,
I hadn't saved the trace route instruction in a separate file and didn't remember exactly what the procedure involved. Without access to the Chat Slowdown thread I couldn't get the process. So I did the best I could. Oh yes, I have put the four steps in a MS Word file so when I can't get on Chat again, I will have the steps that I can use.

Response Error.
Technical description:
502 Bad Gateway - Response Error, a bad response was received from another proxy server or the destination origin server.

166.147.72.26

Tracing route to vcca.org [64.6.242.76]
over a maximum of 30 hops:

1 7 ms <1 ms <1 ms 192.168.42.129
2 1613 ms * 92 ms 172.26.241.53
3 107 ms 79 ms 77 ms 172.26.236.2
4 92 ms 78 ms 77 ms 172.26.96.3
5 152 ms 79 ms 90 ms 172.26.96.193
6 129 ms 119 ms 80 ms 172.16.78.113
7 106 ms 109 ms 81 ms 12.249.2.1
8 109 ms 112 ms 73 ms 12.83.179.194
9 145 ms 81 ms 105 ms gar25.dlstx.ip.att.net [12.122.85.233]
10 74 ms 99 ms 77 ms 192.205.32.178
11 132 ms 101 ms 117 ms te2-1-10G.ar5.CHI2.gblx.net [67.16.130.2]
12 102 ms 109 ms 111 ms CONTINENTAL-BROADBAND.Te6-2.ar5.CHI1.gblx.net [2
07.138.128.70]
13 106 ms 125 ms 105 ms te1-4.4038.cr2.701hn.iplsin.e-xpedient.com [209.
166.144.213]
14 101 ms 115 ms 113 ms te1-2.4042.cr1.701hn.iplsin.e-xpedient.com [216.
130.11.141]
15 108 ms 147 ms 122 ms te2-7-4.4043.upa-core.expedient.com [66.11.0.29]

16 134 ms 109 ms 107 ms myhostcenter-gw-primary.cust.e-xpedient.com [66.
11.1.179]
17 * * 302 ms s34.n230.n6.n64.static.myhostcenter.com [64.6.23
0.34]
18 * * * Request timed out.
19 * * 181 ms s76.n242.n6.n64.static.myhostcenter.com [64.6.24
2.76]

Trace complete.

Approx 8:45 pm CDT

Good one... I just did the same thing from Seattle and Dave Miner did it from Ohio.

All of them show that the network allowed us full access across the USA to the HOST...

So -- the HOST (our server) is where the problem is.

I open a trouble ticket.

Finally got the instructions printed out so I could follow it to a T. Had to add run to my start menu which took me a few minutes to get done.

Hope those clowns get this fixed. Of course pointing people in the wrong direction is the strategy used by many techs so they have the pressure off and have time to actually find the problem. Won't tell you how I know that.

I'll be happy when we can get back to devoting our time to old cars than to IT problems!

Seems like we have had similar problems with other "hosts" of this site in the past as well.

9:25 PM to 11:09 PM PDT......Chevy Chatter completely dead.

I've been working this for the past 6 hours.

We have discovered the cause. I will post a comment to a new thread in the members area.

Bill, oh Bill. It happened AGAIN last night at 9:15 PM EDT. Looks like the same as Sunday night.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Russell>tracert vcca.org

Tracing route to vcca.org [64.6.242.76]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 18 ms 17 ms 17 ms adsl-98-94-15-1.ags.bellsouth.net [98.94.15.1]
3 23 ms 22 ms 23 ms 70.159.181.47
4 22 ms 23 ms 23 ms 12.81.64.67
5 24 ms 23 ms 31 ms 12.83.0.102
6 21 ms 22 ms * 12.81.0.17
7 65 ms 32 ms 34 ms 74.175.192.98
8 27 ms 23 ms 28 ms cr2.attga.ip.att.net [12.122.140.170]
9 22 ms 23 ms 22 ms attga02jt.ip.att.net [12.123.22.153]
10 23 ms 23 ms 22 ms 144.232.1.65
11 22 ms 23 ms 22 ms sl-crs4-atl-.sprintlink.net [144.232.1.219]
12 28 ms 28 ms 28 ms 144.232.5.211
13 41 ms 40 ms 42 ms 144.232.10.46
14 42 ms 43 ms 43 ms sl-crs2-rly-0-0-3-0.sprintlink.net [144.232.8.16
5]
15 46 ms 47 ms 47 ms sl-st21-pit-1-0-0.sprintlink.net [144.232.9.99]

16 49 ms 50 ms 49 ms 63.160.2.10
17 61 ms * 63 ms te1-7-4.4037.upa-core.expedient.com [209.166.144
.210]
18 54 ms 55 ms * myhostcenter-gw-primary.cust.e-xpedient.com [66.
11.1.179]
19 * * 63 ms s34.n230.n6.n64.static.myhostcenter.com [64.6.23
0.34]
20 73 ms * * s76.n242.n6.n64.static.myhostcenter.com [64.6.24
2.76]
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * 69 ms s76.n242.n6.n64.static.myhostcenter.com [64.6.24
2.76]

Trace complete.

C:\Users\Russell>

And at 9:40 PM EDT

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Russell>tracert vcca.org

Tracing route to vcca.org [64.6.242.76]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 18 ms 18 ms 18 ms adsl-98-94-15-1.ags.bellsouth.net [98.94.15.1]
3 23 ms 23 ms 24 ms 70.159.181.47
4 23 ms 22 ms 23 ms 12.81.64.67
5 28 ms 27 ms 23 ms 12.83.0.102
6 22 ms 22 ms 21 ms 12.81.0.17
7 22 ms 22 ms 20 ms 74.175.192.98
8 25 ms 27 ms 27 ms cr2.attga.ip.att.net [12.122.140.170]
9 22 ms 22 ms 22 ms attga02jt.ip.att.net [12.123.22.153]
10 23 ms 22 ms 23 ms 144.232.1.65
11 24 ms 42 ms 22 ms sl-crs4-atl-.sprintlink.net [144.232.1.219]
12 29 ms 28 ms 29 ms 144.232.5.211
13 40 ms 40 ms 41 ms 144.232.10.46
14 47 ms 42 ms 42 ms sl-crs2-rly-0-0-3-0.sprintlink.net [144.232.8.16
5]
15 46 ms 45 ms 47 ms sl-st21-pit-1-0-0.sprintlink.net [144.232.9.99]

16 49 ms 50 ms 48 ms 63.160.2.10
17 67 ms 67 ms 66 ms te1-7-4.4037.upa-core.expedient.com [209.166.144
.210]
18 60 ms 54 ms 59 ms myhostcenter-gw-primary.cust.e-xpedient.com [66.
11.1.179]
19 63 ms * * s34.n230.n6.n64.static.myhostcenter.com [64.6.23
0.34]
20 * * * Request timed out.
21 * * * Request timed out.
22 73 ms 73 ms 73 ms s76.n242.n6.n64.static.myhostcenter.com [64.6.24
2.76]

Trace complete.

C:\Users\Russell> 10:40 PM



Looks like me and Chipper are in the same boat!

SO,IS this OUR host that is the culprit or not????

Thanks

SORRY, I missed where you said you have discovered the problem (above) post.

Will leave this post anyway.

Glad you super sleuths ferreted out the cause. It sure was frustrating to not be able to post all our nuggets of wisdom before we forgot what they were.

Thanks to YOU guys... for sending the trace routes. That was convincing evidence that it was NOT a network problem. Once we confirmed that from 3 different areas of the country, then it helped convince them to FOCUS on the server.

But -- a small warning... If "they" did it once, then they can do it again... So we need to watch for ongoing suspicions.

Maybe this will turn the corner for us. Tonight I made a MAJOR change. We now are using a different NETWORK PROVIDER. Let me know if you notice a difference.

6:45AM CDT and it's screaming. Faster loads than I've ever seen on Chat. Now that I've said that it'll probably fall on it's face.

Looking good so far.

Bill, let me express thanks on behalf of the thousands of VCCA members for your tireless work (and that of your elves) on our behalf in trying to keep our site safe, secure and functional. I'm sure you are setting aside your own priorities and fun in order to do this, and I did not want your efforts to go by without acknowledgement. Cheers

I also want to second, third or fourth, what has been said about your efforts. Thanks!

Am a little confused though, not uncommon. Your last two post seem to contradict one another. One states it was not a network problem. The other, we changed networks. Just saying.

Anyway, I for one hope this solves our issues with connecting to this site.