RMN IS UP! NO, IT'S DOWN. NOW IT'S UP! OH WAIT... DOWN AGAIN.

Posts

Pages: first prev 123 last
Marrend
Guardian of the Description Thread
21806
The last time I had trouble, I ran tracert and got three lines with information before it starting giving me a bunch of lines of asterisks with a "Timed out" message on the end. It basically looked like:


1 1 ms 1 ms 1 ms dslrouter.westell.com [10.0.0.1]
2 251 ms 41 ms 41 ms oh-71-50-192-1.dhcp.embarqhsd.net [71.50.192.1]
3 43 ms 44 ms 42 ms oh-69-34-31-165.sta.embarqhsd.net [69.34.31.165]
4 * * * Timed out
5 * * * Timed out
6 * * * Timed out
7 * * * Timed out
8 * * * Timed out
9 * * * Timed out
10 * * * Timed out
11 * * * Timed out
author=chana
Oh, also, the IsItJustMe site said it wasn't, just me?!


Yes, the site was down for a few hours yesterday afternoon/evening because of a problem at the data center where it lives.
chana
(Socrates would certainly not contadict me!)
1584
traceroute to rpgmaker.net (67.23.177.196), 30 hops max, 60 byte packets
1 freebox-server.local (192.168.1.254) 3.640 ms 3.633 ms 3.635 ms
2 82.227.211.254 (82.227.211.254) 32.313 ms 35.406 ms 35.408 ms
3 nantes-6k-1-a5.routers.proxad.net (213.228.11.254) 40.129 ms * *
4 marseille-6k-1-po1.intf.routers.proxad.net (212.27.57.113) 45.844 ms 45.847 ms 45.851 ms
5 bzn-crs16-1-be1104.intf.routers.proxad.net (212.27.50.185) 51.326 ms 52.903 ms 52.907 ms
6 te0-2-0-6.373.mag21.par01.atlas.cogentco.com (149.6.115.17) 55.429 ms 40.627 ms 42.799 ms
7 te0-4-0-2.ccr22.par01.atlas.cogentco.com (130.117.49.253) 37.763 ms te0-6-0-6.ccr22.par01.atlas.cogentco.com (154.54.38.177) 40.646 ms te0-6-0-6.mpd22.par01.atlas.cogentco.com (154.54.38.185) 43.580 ms
8 te0-5-0-6.mpd21.jfk02.atlas.cogentco.com (154.54.43.149) 115.767 ms te0-7-0-7.mpd22.jfk02.atlas.cogentco.com (154.54.46.105) 121.815 ms te0-5-0-6.mpd21.jfk02.atlas.cogentco.com (154.54.43.149) 119.421 ms
9 te0-3-0-7.mpd21.dca01.atlas.cogentco.com (154.54.40.45) 127.538 ms te0-2-0-7.mpd22.dca01.atlas.cogentco.com (154.54.41.25) 129.112 ms te0-4-0-6.ccr22.dca01.atlas.cogentco.com (154.54.42.29) 131.915 ms
10 te0-0-0-3.mpd22.atl01.atlas.cogentco.com (154.54.28.210) 143.643 ms te0-2-0-6.ccr22.atl01.atlas.cogentco.com (154.54.1.121) 147.660 ms te0-1-0-2.ccr21.atl01.atlas.cogentco.com (154.54.28.237) 146.047 ms
11 te7-7.ccr01.atl04.atlas.cogentco.com (154.54.6.114) 129.660 ms te0-0-0-0.mpd21.atl01.atlas.cogentco.com (154.54.45.25) 129.751 ms te0-2-0-0.ccr21.atl01.atlas.cogentco.com (154.54.28.61) 131.783 ms
12 38.122.46.94 (38.122.46.94) 147.890 ms 131.509 ms 38.122.46.90 (38.122.46.90) 139.571 ms
13 * 38.122.46.90 (38.122.46.90) 139.557 ms *
14 * * *
15 * * *
16 75-131-187-34.static.gwnt.ga.charter.com (75.131.187.34) 133.249 ms 135.892 ms 135.894 ms
17 * * *
18 * * *
19 67.23.177.196 (67.23.177.196) 141.764 ms 143.380 ms 143.382 ms

If I could have any explanatins, that would be great. Happens to me every other time, not quite but really often, thx.
If your traceroute has this line at the end:

19 67.23.177.196 (67.23.177.196) 141.764 ms 143.380 ms 143.382 ms

Then there should be no problems for you connecting to RMN.

I checked the server logs and noticed some timeout error messages so I made some changes to see if they would help.
by the time they did the traceroute the issue was resolved?
chana
(Socrates would certainly not contadict me!)
1584
thanks, ankylo.
chana
(Socrates would certainly not contadict me!)
1584
Sorry to bother you with this but is this normal :
traceroute to rpgmaker.net (67.23.177.196), 30 hops max, 60 byte packets
1 freebox-server.local (192.168.1.254) 3.361 ms 3.353 ms 3.353 ms
2 82.227.211.254 (82.227.211.254) 31.631 ms 41.272 ms 41.270 ms
3 213.228.11.254 (213.228.11.254) 41.271 ms * *
4 marseille-6k-1-po1.intf.routers.proxad.net (212.27.57.113) 47.594 ms 47.597 ms 47.602 ms
5 bzn-crs16-1-be1104.intf.routers.proxad.net (212.27.50.185) 50.380 ms 52.066 ms 52.069 ms
6 te0-2-0-6.373.mag21.par01.atlas.cogentco.com (149.6.115.17) 60.284 ms 37.203 ms 39.078 ms
7 te0-7-0-7.mpd22.par01.atlas.cogentco.com (130.117.49.125) 52.799 ms te0-6-0-6.ccr21.par01.atlas.cogentco.com (154.54.38.173) 52.791 ms te0-0-0-7.mpd22.par01.atlas.cogentco.com (154.54.38.185) 52.781 ms
8 te0-2-0-5.ccr21.jfk02.atlas.cogentco.com (154.54.5.177) 113.403 ms 115.025 ms te0-6-0-2.mpd21.jfk02.atlas.cogentco.com (154.54.46.109) 115.028 ms
9 te0-3-0-6.mpd21.dca01.atlas.cogentco.com (154.54.41.21) 123.292 ms te0-1-0-3.ccr21.dca01.atlas.cogentco.com (66.28.4.126) 126.346 ms te0-3-0-3.ccr21.dca01.atlas.cogentco.com (154.54.26.185) 127.967 ms
10 te0-0-0-3.mpd22.atl01.atlas.cogentco.com (154.54.28.210) 139.812 ms te0-1-0-2.ccr21.atl01.atlas.cogentco.com (154.54.28.237) 141.431 ms te0-0-0-6.ccr22.atl01.atlas.cogentco.com (154.54.28.222) 146.112 ms
11 te9-2.ccr01.atl04.atlas.cogentco.com (154.54.82.122) 235.153 ms te7-8.ccr01.atl04.atlas.cogentco.com (154.54.6.122) 236.758 ms 236.760 ms
12 38.122.46.94 (38.122.46.94) 144.966 ms te8-7.ccr01.atl04.atlas.cogentco.com (154.54.3.174) 125.679 ms 38.122.46.90 (38.122.46.90) 141.726 ms
13 38.122.46.94 (38.122.46.94) 135.192 ms * *
14 crr11gnvlsc-tge-0-1-0-18.gnvl.sc.charter.com (96.34.72.35) 139.996 ms crr11gnvlsc-tge-0-1-0-13.gnvl.sc.charter.com (96.34.78.33) 141.628 ms crr11gnvlsc-tge-0-1-0-15.gnvl.sc.charter.com (96.34.72.177) 144.252 ms
15 crr11gnvlsc-tge-0-1-0-14.gnvl.sc.charter.com (96.34.72.207) 145.944 ms crr12gnvlsc-tge-0-1-0-2.gnvl.sc.charter.com (96.34.92.64) 145.953 ms crr12gnvlsc-tge-0-0-0-0.gnvl.sc.charter.com (96.34.92.52) 151.125 ms
16 * * *
17 * * crr02hckrnc-tge-0-1-0-0.hckr.nc.charter.com (96.34.67.181) 129.975 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 ahvl.immedion.charter.com (68.115.192.218) 136.552 ms * 140.205 ms
23 ahvl.immedion.charter.com (68.115.192.218) 142.825 ms * *
24 67.23.177.196 (67.23.177.196) 135.092 ms 135.565 ms 132.704 ms
Yes, that is normal. Anytime it ends with 67.23.177.196, that means there is nothing wrong with your connection to the server, but that doesn't mean the webserver is serving requests.

I don't think we have a DNS issue. I think that some of our issues were related to problems at the data center where the server is hosted (which I believe are fixed now) and some of the problems were too much traffic for the webserver (which I think I improved, but perhaps did not totally fix).

Today's problem was that the webserver froze. I haven't figured out why it froze, but I'm working on that.
Thiamor
I assure you I'm no where NEAR as STUPID as one might think.
63
Not sure if this was ever resolved, but it very well could be a mixture of the server and individual networks. Thus it starts to lag up, and then their network does the rest by messing up and not connecting the rest of the way.
Pages: first prev 123 last