Server Failure
Don't waste your time virus scanning. The server is as flaky as they get.
TraceRoute to 67.201.16.188 [forums.rennlist.com]
Hop (ms) (ms) (ms) IP Address Host name
1 29 25 23 72.249.0.65 -
2 15 26 43 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
3 32 30 14 4.68.19.126 vlan79.csw2.dallas1.level3.net
4 27 40 30 4.69.136.157 ae-73-73.ebr3.dallas1.level3.net
5 53 52 44 4.69.132.77 ae-3.ebr2.losangeles1.level3.net
6 54 54 44 4.69.137.26 ae-82-82.csw3.losangeles1.level3.net
7 45 41 38 4.68.20.137 ae-3-89.edge3.losangeles1.level3.net
8 40 55 58 4.71.136.2 xe2-0.cr01.lax01.mzima.net
9 51 54 39 64.235.224.182 xe1-0.cr01.lax02.mzima.net
10 Timed out Timed out Timed out -
11 Timed out Timed out Timed out -
12 Timed out Timed out Timed out -
13 Timed out Timed out Timed out -
Trace aborted.
TraceRoute to 67.201.16.188 [forums.rennlist.com]
Hop (ms) (ms) (ms) IP Address Host name
1 29 25 23 72.249.0.65 -
2 15 26 43 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
3 32 30 14 4.68.19.126 vlan79.csw2.dallas1.level3.net
4 27 40 30 4.69.136.157 ae-73-73.ebr3.dallas1.level3.net
5 53 52 44 4.69.132.77 ae-3.ebr2.losangeles1.level3.net
6 54 54 44 4.69.137.26 ae-82-82.csw3.losangeles1.level3.net
7 45 41 38 4.68.20.137 ae-3-89.edge3.losangeles1.level3.net
8 40 55 58 4.71.136.2 xe2-0.cr01.lax01.mzima.net
9 51 54 39 64.235.224.182 xe1-0.cr01.lax02.mzima.net
10 Timed out Timed out Timed out -
11 Timed out Timed out Timed out -
12 Timed out Timed out Timed out -
13 Timed out Timed out Timed out -
Trace aborted.
Traceroutes are very subjective to your location. If your ISP/telco has a buggy router, downed router or a noisy fibre link, you can get oddities show up in traceroutes. From the looks of it, they're not doing anything sophisticated like load-balancing using DNS round-robins. I imagine they're just experiencing high server loads due to some rogue process of some sort. It might be the the database backend that's slowing things down as well.
...my two cents
...my two cents
Don't waste your time virus scanning. The server is as flaky as they get.
TraceRoute to 67.201.16.188 [forums.rennlist.com]
Hop (ms) (ms) (ms) IP Address Host name
1 29 25 23 72.249.0.65 -
2 15 26 43 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
3 32 30 14 4.68.19.126 vlan79.csw2.dallas1.level3.net
4 27 40 30 4.69.136.157 ae-73-73.ebr3.dallas1.level3.net
5 53 52 44 4.69.132.77 ae-3.ebr2.losangeles1.level3.net
6 54 54 44 4.69.137.26 ae-82-82.csw3.losangeles1.level3.net
7 45 41 38 4.68.20.137 ae-3-89.edge3.losangeles1.level3.net
8 40 55 58 4.71.136.2 xe2-0.cr01.lax01.mzima.net
9 51 54 39 64.235.224.182 xe1-0.cr01.lax02.mzima.net
10 Timed out Timed out Timed out -
11 Timed out Timed out Timed out -
12 Timed out Timed out Timed out -
13 Timed out Timed out Timed out -
Trace aborted.
TraceRoute to 67.201.16.188 [forums.rennlist.com]
Hop (ms) (ms) (ms) IP Address Host name
1 29 25 23 72.249.0.65 -
2 15 26 43 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
3 32 30 14 4.68.19.126 vlan79.csw2.dallas1.level3.net
4 27 40 30 4.69.136.157 ae-73-73.ebr3.dallas1.level3.net
5 53 52 44 4.69.132.77 ae-3.ebr2.losangeles1.level3.net
6 54 54 44 4.69.137.26 ae-82-82.csw3.losangeles1.level3.net
7 45 41 38 4.68.20.137 ae-3-89.edge3.losangeles1.level3.net
8 40 55 58 4.71.136.2 xe2-0.cr01.lax01.mzima.net
9 51 54 39 64.235.224.182 xe1-0.cr01.lax02.mzima.net
10 Timed out Timed out Timed out -
11 Timed out Timed out Timed out -
12 Timed out Timed out Timed out -
13 Timed out Timed out Timed out -
Trace aborted.
I've done a probe in the past and IB seems to be blocking ICMP and UDP at their firewall -- that's why you never see a response from 67.201.16.188. I have a tool at home I can run that probes a bit deeper than is possible with traceroute... I'll post results later, after I get home.
Chronic Tool Dropper
Lifetime Rennlist
Member
Lifetime Rennlist
Member
Joined: Oct 2001
Posts: 20,506
Likes: 564
From: Bend, Oregon
Dave
I'm only 6 hops away from them, and still see erratic server performance on a very regular basis. I think it's a database server issue, because I can see the non-caches page sections pretty quickly but wait for the dynamic stuff to load. No telling what other server loads are sharing the database server at any given time.
I'm only 6 hops away from them, and still see erratic server performance on a very regular basis. I think it's a database server issue, because I can see the non-caches page sections pretty quickly but wait for the dynamic stuff to load. No telling what other server loads are sharing the database server at any given time.
Trending Topics
Bob, John, I know there is a lot more to it than ping times(e.g. traceroute). They seem to be running mysql, which ought to be pretty scalable -- but it seems that they are just no allocating many resources at the moment. They could be doing rolling upgrades or some such that leaves a portion of their capacity down at any given time.
BTW... slightly more info here: http://toolbar.netcraft.com/site_rep...s.rennlist.com
BTW... slightly more info here: http://toolbar.netcraft.com/site_rep...s.rennlist.com
I see there is a notification at the top of the forum:
"Yikes someone has fitted a Corvette engine to our firewall, and we are runnniiiiinnnnnnggggggg ssslllllooooowwwwww. A flat six will be returning soon."
It's not a problem reaching the web server, it's a problem internal to IB (most likely with the webserver talking to the database and figuring out what to send back to you). Note the 78ms HTTP response. Maybe they should skip the flat six and fit a Porsche V8 to the firewall...
"Yikes someone has fitted a Corvette engine to our firewall, and we are runnniiiiinnnnnnggggggg ssslllllooooowwwwww. A flat six will be returning soon."
It's not a problem reaching the web server, it's a problem internal to IB (most likely with the webserver talking to the database and figuring out what to send back to you). Note the 78ms HTTP response. Maybe they should skip the flat six and fit a Porsche V8 to the firewall...
Good news and bad news: They found the problem, but the solution might be worse... 
From the "Notices" banner:
From the "Notices" banner:
Yikes someone has fitted a Corvette engine to our firewall, and we are runnniiiiinnnnnnggggggg ssslllllooooowwwwww. A flat six will be returning soon.



