Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
C:>ping son240sx.org
Pinging son240sx.org [208.113.204.238] with 32 bytes of data:
Reply from 208.113.204.238: bytes=32 time=87ms TTL=46
Reply from 208.113.204.238: bytes=32 time=89ms TTL=46
Reply from 208.113.204.238: bytes=32 time=90ms TTL=46
Reply from 208.113.204.238: bytes=32 time=90ms TTL=46
Ping statistics for 208.113.204.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 90ms, Average = 89ms
C:>tracert 208.114.204.238
Tracing route to 208.114.204.238 over a maximum of 30 hops
1 4 ms 1 ms 1 ms mymodem [192.168.2.1]
2 16 ms 10 ms 11 ms bas1-cooksville01_lo0_symp.net.bell.ca [64.230.1
97.2]
3 10 ms 12 ms 10 ms core1-toronto63_13-1-0_143.net.bell.ca [64.230.1
39.9]
4 12 ms 11 ms 11 ms core3-toronto63_pos6-0.net.bell.ca [64.230.242.1
01]
5 21 ms 21 ms 23 ms core1-chicago23_pos12-0-0.net.bell.ca [64.230.14
7.14]
6 23 ms 188 ms 21 ms bx2-chicagodt_so-2-0-0-0.net.bell.ca [64.230.203
.146]
7 21 ms 21 ms 21 ms 206.111.3.45.ptr.us.xo.net [206.111.3.45]
8 21 ms 21 ms 21 ms 207.88.14.9.ptr.us.xo.net [207.88.14.9]
9 49 ms 49 ms 47 ms 207.88.14.10.ptr.us.xo.net [207.88.14.10]
10 48 ms 47 ms 47 ms 207.88.185.74.ptr.us.xo.net [207.88.185.74]
11 47 ms 47 ms 47 ms border2.ge1-1-bbnet1.ext1a.dal.pnap.net [216.52.
191.25]
12 49 ms 47 ms 47 ms huntbros-1.border2.ext1a.dal.pnap.net [63.251.33
.149]
13 60 ms 58 ms 59 ms hb207-29-219-121.huntbrothers.com [207.29.219.12
1]
14 57 ms 56 ms 57 ms hb207-29-219-114.huntbrothers.com [207.29.219.11
4]
15 57 ms 57 ms 57 ms 206-41-32-45.idsno.net [206.41.32.45]
16 61 ms 58 ms 60 ms 206-41-32-114.idsno.net [206.41.32.114]
17 60 ms 58 ms 58 ms 206-41-32-34.idsno.net [206.41.32.34]
18 60 ms 59 ms 59 ms 208.114.192.4
19 * * * Request timed out.
20 * * * Request timed out.
21 * *
i get it a couple times now and again
yep, i agree. we have DB’s at work that can reach over 2GB before we have to perform maintenance to clean up old records from old transactions to reduce the size, improve performance, and decrease the risk of corruption.
if there is a problem with the DB, we should still be able to load a vBulletin page displaying teh SQL error message. i think it’s an issue with the web server configuration.
once in a while, i get the 500 message, other times a timeout (which is why i suggested a traceroute - maybe there are issues with their WAN provider or LAN configuration as well - an issue with the DB shouldn’t cause a complete loss of connection to the web server and break the route.)
just a thought.
I get this several times a day… I have to hit the refresh button several times to get it to work… It surely is annoying though.
Its just because their hosts are refreshing at an inconsistent rate, either too fast or too slow to sync with whatever SQL database their using for their site.
Try either slowing down your hosts or decreasing the lag time to find connection on the SQL DB
keep in mind this is a web server error, either from apache or IIS or whatever they use to host the site.
also, 500 errors are (vague) general exception messages (giving away too much info regarding errors is a terrible idea), requires admins to search through logs to determine the root cause, and could be one or more of many things.
i doubt this has much to do with the DB - even if a connection cannot be properly established to the SQL server, in this case, vBulletin uses MySQL(i), the page should still load and return a PHP-generated error message, since the PHP module is making the calls to the DB, not the web server app per se.
Gonad’s on top of it, so no worries.
over the last month its happened to me on and off, but the last few days its been happenening more often. sometimes i have to wait a bit then return to the site.
lol the new job I got now (WOOHOO KICK ASS JOB) we do literally terrabytes upon terrabytes of nightly tape backups, our SQL server is pretty hot 
I laugh at the 250MB+ database
Anywho in all seriousness, so whats up, any updates? I haven’t had the issues in a few days but yesterday/today I had a slow down and had to wait for it to refresh…