my350z.com issues for the last 2 weeks
Joined: May 2009
Posts: 4,293
Likes: 2
From: Spartanburg(SparkleCity), SC
I have been seeing the problems consistently for the past week. It doesn't matter where I am (home, work, datacenter), what kind of computer (Windows, Mac, iPad, Android), or what kind of browser (IE, Firefox, Safari, Opera). I have no problems browsing or interacting with other websites while my350z is taking a siesta.
Many times, I find that requests for pages are just being dropped by the server and never responded to. I can click the same link again, and by the 2nd or 3rd attempt, the page will load at a reasonable speed. Also, I am getting the database error messages. It looks to me to be an issue on the hosting side with the database server or webserver itself. Most likely a capacity issue or a database indexing issue. I say this, because I spend a lot of time working in our own datacenters. At times, I find that there is a higher latency to the my350z hosting when checking with Ping or Traceroute, but I realize that these tests are likely only testing latency to the hosting company's firewall/router and not actually testing the latency to the servers hosting the site.
I'm not sure if IB actually owns the site/domain or just has a hosting agreement, but if the powers that be need a rock solid datacenter for hosting, someone let me know and I'll be happy to help just to get the site back to a healthy state again.
Many times, I find that requests for pages are just being dropped by the server and never responded to. I can click the same link again, and by the 2nd or 3rd attempt, the page will load at a reasonable speed. Also, I am getting the database error messages. It looks to me to be an issue on the hosting side with the database server or webserver itself. Most likely a capacity issue or a database indexing issue. I say this, because I spend a lot of time working in our own datacenters. At times, I find that there is a higher latency to the my350z hosting when checking with Ping or Traceroute, but I realize that these tests are likely only testing latency to the hosting company's firewall/router and not actually testing the latency to the servers hosting the site.
I'm not sure if IB actually owns the site/domain or just has a hosting agreement, but if the powers that be need a rock solid datacenter for hosting, someone let me know and I'll be happy to help just to get the site back to a healthy state again.
^what he said.
I'm still having lots of issues. I always try to post and it just stalls on me. Saying that it is "waiting for my350z.com..." and it never loads.
I just give up on it most of the time and I leave or close it. it pisses me off, every other site works.
I'm still having lots of issues. I always try to post and it just stalls on me. Saying that it is "waiting for my350z.com..." and it never loads.
I just give up on it most of the time and I leave or close it. it pisses me off, every other site works.
Code:
Traceroute has started ... traceroute to www.my350z.com (98.158.195.249), 64 hops max, 40 byte packets 1 192.168.1.1 (192.168.1.1) 1.733 ms 1.220 ms 1.176 ms 2 * * * 3 ge-1-3-0-152.aggr01.odestx.grandecom.net (216.82.203.182) 11.356 ms 8.964 ms 9.239 ms 4 ae3-24.core01.gf01.dllstx.grandecom.net (24.155.121.95) 16.177 ms 16.347 ms 15.708 ms 5 xe-0-0-1-0.aggr08.austtx.grandecom.net (24.155.121.120) 21.004 ms 21.873 ms 21.782 ms 6 207.238.76.5 (207.238.76.5) 123.658 ms 43.462 ms 59.672 ms 7 vb1310.rar3.dallas-tx.us.xo.net (216.156.0.105) 42.898 ms 43.535 ms 44.794 ms 8 * 207.88.14.245.ptr.us.xo.net (207.88.14.245) 43.803 ms 38.595 ms 9 * * * 10 vlan70.csw2.Dallas1.Level3.net (4.69.145.126) 37.846 ms vlan90.csw4.Dallas1.Level3.net (4.69.145.254) 39.651 ms vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 36.840 ms 11 ae-93-93.ebr3.Dallas1.Level3.net (4.69.151.170) 37.226 ms ae-63-63.ebr3.Dallas1.Level3.net (4.69.151.134) 47.653 ms ae-73-73.ebr3.Dallas1.Level3.net (4.69.151.146) 39.159 ms 12 ae-3-3.ebr2.LosAngeles1.Level3.net (4.69.132.77) 71.715 ms 71.322 ms 70.214 ms 13 ae-82-82.csw3.LosAngeles1.Level3.net (4.69.137.26) 70.445 ms ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 70.746 ms ae-82-82.csw3.LosAngeles1.Level3.net (4.69.137.26) 70.767 ms 14 ae-11-60.car1.LosAngeles1.Level3.net (4.69.144.3) 70.114 ms ae-21-70.car1.LosAngeles1.Level3.net (4.69.144.67) 73.950 ms ae-11-60.car1.LosAngeles1.Level3.net (4.69.144.3) 73.102 ms 15 INTERNET-BR.car1.LosAngeles1.Level3.net (4.59.56.162) 76.231 ms 72.528 ms 75.128 ms 16 rev-98-158-192-10.dvpne.com (98.158.192.10) 70.070 ms 70.888 ms 76.974 ms 17 nissangroup-98-158-195-249.dvpne.com (98.158.195.249) 73.324 ms 73.607 ms 73.048 ms 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 nissangroup-98-158-195-249.dvpne.com (98.158.195.249) 73.277 ms !H 73.942 ms !H 73.220 ms !H
Joined: May 2009
Posts: 4,293
Likes: 2
From: Spartanburg(SparkleCity), SC
When I see the issues, it doesn't appear to be connectivity based delays between our computers and the hosting network. It appears to be server issues, because we are getting an IB screen with database error messages or we are getting no response on one particular HTTP query, but a response on another. That means that connectivity is up, because we are getting an IB screen or we are getting a response immediately with a second, third, or fourth attempt. The traceroutes aren't going to tell you anything, because that isn't where the issue is.
The issue appears to be either in the webserver's inability to handle the load of requests (processor/memory/pagefile), or the database server's inability to efficiently process the queries (indexing,database structure/consistency,disk i/o, processor, memory, pagefile).
If it were connectivity issues, we would quickly get a 404 error.
We wouldn't be left hanging while our client expects a response from the webserver, we wouldn't get a response from a subsequent request in a separate browser even as we are still waiting for the first few attempts, and we wouldn't get the IB screens telling us that there was a database failure/error.
Please don't take this as an attack, I'm just trying to share information that I feel will be helpful since I did a little digging when it first started happening (mainly to make sure that there was nothing happening on any of my networks that was impacting my access). I would put 50 to 1 odds that it is a server capacity issue - most likely on the database side - which could be as simple as improving the indexing or could be as complicated as reconfiguring the database structure and upgrading server infrastructure. I'd suggest having a high level DBA look into your database server performance, queries, and indexes.
Joined: May 2009
Posts: 4,293
Likes: 2
From: Spartanburg(SparkleCity), SC
