STR: Your host is *&^$*

Ne'er a single issue here nor at work.

Since net neutrality's dead, perhaps Cox has begun rating your STR content as low priority.

jk. No idea.

 

Approximately 6AM - 8AM +

 

I recently began starting my day a little earlier and noticed the same thing, probably between 6:00 and 6:30. I suspect there's a script performing some kind of maintenance at that hour. Is STR on a dedicated server?

 

Nothing with me.
I had to pull an all-nighter last Wednesday. Everything else I was having a problem, STR worked fine for me.
Internet: Upstairs neighbor's cracked WiFi.

 

Never a problem other than some regretable posts. Time Warner Cable.

 

NIGHTTIME PINGS:
circa 9PM PST

pimac:~ mmcclure$ ping socaltrailriders.org
PING socaltrailriders.org (67.222.133.102): 56 data bytes
64 bytes from 67.222.133.102: icmp_seq=0 ttl=48 time=51.281 ms
64 bytes from 67.222.133.102: icmp_seq=1 ttl=48 time=56.814 ms
64 bytes from 67.222.133.102: icmp_seq=2 ttl=48 time=50.814 ms
64 bytes from 67.222.133.102: icmp_seq=3 ttl=48 time=51.667 ms
64 bytes from 67.222.133.102: icmp_seq=4 ttl=48 time=49.065 ms
64 bytes from 67.222.133.102: icmp_seq=5 ttl=48 time=52.052 ms
^C
--- socaltrailriders.org ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 49.065/51.949/56.814/2.374 ms

imac:~ mmcclure$ ping google.com
PING google.com (66.102.7.99): 56 data bytes
64 bytes from 66.102.7.99: icmp_seq=0 ttl=54 time=20.285 ms
64 bytes from 66.102.7.99: icmp_seq=1 ttl=54 time=16.883 ms
64 bytes from 66.102.7.99: icmp_seq=2 ttl=54 time=19.860 ms
64 bytes from 66.102.7.99: icmp_seq=3 ttl=54 time=17.747 ms
64 bytes from 66.102.7.99: icmp_seq=4 ttl=54 time=19.899 ms
^C
--- google.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 16.883/18.935/20.285/1.359 ms

imac:~ mmcclure$ ping yahoo.com
PING yahoo.com (72.30.2.43): 56 data bytes
64 bytes from 72.30.2.43: icmp_seq=0 ttl=53 time=30.053 ms
64 bytes from 72.30.2.43: icmp_seq=1 ttl=53 time=47.248 ms
64 bytes from 72.30.2.43: icmp_seq=2 ttl=53 time=30.050 ms
64 bytes from 72.30.2.43: icmp_seq=3 ttl=53 time=32.591 ms
64 bytes from 72.30.2.43: icmp_seq=4 ttl=53 time=28.702 ms
^C
--- yahoo.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 28.702/33.729/47.248/6.876 ms

imac:~ mmcclure$ ping disney.com
PING disney.com (199.181.132.250): 56 data bytes
64 bytes from 199.181.132.250: icmp_seq=0 ttl=240 time=40.168 ms
64 bytes from 199.181.132.250: icmp_seq=1 ttl=240 time=41.861 ms
64 bytes from 199.181.132.250: icmp_seq=2 ttl=240 time=39.721 ms
64 bytes from 199.181.132.250: icmp_seq=3 ttl=240 time=49.168 ms
64 bytes from 199.181.132.250: icmp_seq=4 ttl=240 time=42.783 ms
^C
--- disney.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 39.721/42.740/49.168/3.401 ms

=======

STR is certainly slower than the above major services (see the red average ping times). I'll test again in the early AM tomorrow.

- shud

 

Ping tells us that we're ringing the right phone but not if anyone is going to talk.

I'll start timing (with a watch) the page load time.

 

Ringing the right phone.

Aren't you clever?... Yeah sure, that is most often its basic use when you are checking to see if a remote host is available, but it also detects round-trip time as well as packet loss, so can help determine if you have a good, solid connection between two hosts. It won't tell you why you suffer from poor response, but it is a good tool to start off with in the case of connection slowness.

Let's see what my morning numbers return...

- shud

 

ok, I just got a ping spike. Lasted > 1min
1:20AM PST
C:\Documents and Settings\Teh_Administrator>ping socaltrailriders.org

Pinging socaltrailriders.org [67.222.133.102] with 32 bytes of data:

Reply from 67.222.133.102: bytes=32 time=113ms TTL=49
Reply from 67.222.133.102: bytes=32 time=208ms TTL=49
Reply from 67.222.133.102: bytes=32 time=68ms TTL=49
Reply from 67.222.133.102: bytes=32 time=133ms TTL=49

Ping statistics for 67.222.133.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 208ms, Average = 130ms

C:\Documents and Settings\Teh_Administrator>ping google.com

Pinging google.com [66.102.7.104] with 32 bytes of data:

Reply from 66.102.7.104: bytes=32 time=17ms TTL=56
Reply from 66.102.7.104: bytes=32 time=16ms TTL=56
Reply from 66.102.7.104: bytes=32 time=14ms TTL=56
Reply from 66.102.7.104: bytes=32 time=16ms TTL=56

Ping statistics for 66.102.7.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 17ms, Average = 15ms

C:\Documents and Settings\Teh_Administrator>ping socaltrailriders.org

Pinging socaltrailriders.org [67.222.133.102] with 32 bytes of data:

Reply from 67.222.133.102: bytes=32 time=47ms TTL=49
Reply from 67.222.133.102: bytes=32 time=48ms TTL=49
Reply from 67.222.133.102: bytes=32 time=49ms TTL=49
Reply from 67.222.133.102: bytes=32 time=48ms TTL=49

Ping statistics for 67.222.133.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 49ms, Average = 48ms

C:\Documents and Settings\Teh_Administrator>

If it were a problem with the server, like everyone has said. Probably server maintenance seem likely due to the times.

 

While I am usually on in the late evenings and early mornings, I have never had a page load issue (not counting the virus/attack last summer).

 

MORNING PINGS:
circa 530AM PST

Ping times seem fine as of 530AM PST. Still avging ~50ms on round-trips when pinging 67.222.133.102 with no packet loss.

Clicking the link to bring me to this page however resulted in a 10.1 second wait for page load.

- shud

P.S. Clicking the Quick Reply button to push this reply into the thread resulted in a 7.4 second wait.

P.P.S. A few minutes later (541AM)... As I move around the site, previously visited pages that are cached load up quickly (except theHome page, likely because it continually changes?...), but new pages take between 5 and 8 seconds to load. The Home page seems to take a long time always at this moment.

HTH

 

5:57 AM


--- socaltrailriders.org ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 52.258/53.506/54.742/0.897 ms


PING google.com (66.102.7.99): 56 data bytes
64 bytes from 66.102.7.99: icmp_seq=0 ttl=53 time=21.746 ms
64 bytes from 66.102.7.99: icmp_seq=1 ttl=53 time=16.007 ms
64 bytes from 66.102.7.99: icmp_seq=2 ttl=53 time=21.219 ms



but it took 7 or 8 seconds to post the reply...

 

it took about 15 seconds to load this page. but now its snappy!

 

At 6:15 the response dropped badly.

I was browsing "my son is a man" (which had loaded easily - one sip of coffee). Refreshing the page took 1:30. Loading the Home page took 1 minute. In parallel in another window I pinged the site and got a 200ms time but then times in the teens (11, 13, 12 .. ms) repeatedlly.

At 5:45 Advanced search (single content) took 1 minute. Browsing and then repeating the search - the time dropped to 3 sec. Slow database and fast cache?


Update: 6:44 erratic??

Ping 67.222.133.102
[host.socaltrailriders.org]
Round trip time to 67.222.133.102: 12 ms
Round trip time to 67.222.133.102: 6 ms
Round trip time to 67.222.133.102: 6 ms
Round trip time to 67.222.133.102: 6 ms
Round trip time to 67.222.133.102: 10 ms
Timed out
Round trip time to 67.222.133.102: 28 ms
Timed out
Round trip time to 67.222.133.102: 33 ms
Timed out

Average time over 10 pings: 10.1 ms

Update
7:25AM Home page wait >2 min, walked away for ...


Ping 67.222.133.102
[host.socaltrailriders.org]
Round trip time to 67.222.133.102: 205 ms
Round trip time to 67.222.133.102: 190 ms
Round trip time to 67.222.133.102: 123 ms
Round trip time to 67.222.133.102: 102 ms
Round trip time to 67.222.133.102: 165 ms
Timed out
Round trip time to 67.222.133.102: 150 ms
Timed out
Round trip time to 67.222.133.102: 51 ms
Round trip time to 67.222.133.102: 52 ms

Average time over 10 pings: 103.8 ms

Update
8:03 3:30 to get window for Go Advanced.

 

I too had problems at 6.18am. Loading was very slow on this site but not on others. I just had the message "waiting for http://www.socaltrailriders.org" I waited abot a minute and a half before going and doing something else. It still seems a little slow, but better than earlier.

 

I gave up after about 40 secs on the main page at 5:50 or so...

 

seems fine now

 

I have a glitch at 8:03 this morning, page took forever - went to another site, no problem, back to STR still hadn't loaded. Waited a few minutes and came back - no problem.

 

Yea, see my update above.

 

We were off a shared environment a long time ago. Now on a dedicated (and not cheap!) server.

Thanks Doug and everyone. I suspect there's some maintenance thing scheduled around that time. Perhaps backups or something. I'll try and check it out later tonight. If it's just some maintenance jobs I'll try to get it moved sometime between 2 and 4am.