4 replies to this topic

[cnm]

We will be down for about 2 hours, at some time during the 10 hours starting at 5 AM PDT (GMT - 8).
Our host is moving the servers to a new cage.
Thank you for your patience.

Dixiesys said:

This notice is a reminder regarding the upcoming network migration that will take place on October 1, 2011, from 10:00 AM EST to 10:00 PM EST. During the aforementioned window, DixieSystems network engineers and technical staff will be relocating all networking hardware, hosting servers, and other hosting-related inventory to a new enterprise-level hosting cage.

IMPORTANT UPDATES:

* The 12 hour window is the timeframe within which your server will be offline for a portion of the window. We anticipate each actual server move to take no longer than two hours.

* Fresh IP assignments will take place after the move as time allows.

We look forward to making the move proceed as seamlessly as possible, and thank you for your patience while we work to provide you with the world-class hosting you expect.

[cnm]

Well, we went down at 11:30 AM PDT yesterday and were back this morning around 4:00 AM. The server actually booted back up around 10:00 PM last night but a massive DNS foul up made it inaccessible.

We may never know what happened. Someone tripped over the wrong cable at SimpleHelix? Anyway the entire company disappeared from the net. Simplehelix.com, dixiesys.com, alpha-hosting.com, www.451press.com - none of them reachable.

SWI is in good shape now, but our backup site remains down. Support ticket entered but they must have hundreds ahead of us in line. Some very unhappy people at http://www.facebook....Hosting?sk=wall

[cnm]

For a while there I was getting this:
Pinging www.spywareinfoforum.com [75.127.110.25] with 32 bytes of data:
Reply from 64.22.115.61: TTL expired in transit.
Reply from 64.22.115.61: TTL expired in transit.
Reply from 64.22.115.61: TTL expired in transit.
Reply from 64.22.115.61: TTL expired in transit.

I never saw that before. Looked it up and learned "This error indicates network configuration problem. There is loop in routing."
"TTL expired in transit" is related to the TTL value of the packet; every router it passes through lowers it by one, if it hits 0, the packet is returned to the sender. It prevents infinite loops, where packets travel in circles forever.
http://serverfault.c...mpt/39715#39715
http://www.corenetwo...reason-and.html

[mikey]

This is what I saw;

10/01/11 16:44:56 Fast traceroute spywareinfoforum.com
Trace spywareinfoforum.com (75.127.110.25) ...
 1 192.168.1.1       0ms    0ms    0ms  TTL: 64  (No rDNS)
 2 10.239.50.1       9ms    7ms    8ms  TTL:254  (No rDNS)
 3 66.68.1.97        7ms   17ms    9ms  TTL:253  (te1-4.austtxs-er04.texas.rr.com ok)
 4 24.27.13.98      12ms   13ms   13ms  TTL:252  (te0-10-0-0.austtxa-cr01.texas.rr.com ok)
 5 72.179.205.56    16ms   17ms   31ms  TTL:251  (te0-12-0-2.dllatxl3-cr01.texas.rr.com ok)
 6 107.14.17.136    17ms   17ms   15ms  TTL:250  (No rDNS)
 7 66.109.6.209     16ms   17ms   66ms  TTL:249  (ae-3-0.pr0.dfw10.tbone.rr.com bogus rDNS: host not found [authoritative])
 8 154.54.11.49     15ms   15ms   15ms  TTL:248  (te9-4.mpd01.dfw03.atlas.cogentco.com fraudulent rDNS)
 9 154.54.25.218    22ms   22ms   24ms  TTL:246  (te0-0-0-2.ccr21.iah01.atlas.cogentco.com fraudulent rDNS)
10 154.54.2.81      38ms   32ms   34ms  TTL:243  (te0-1-0-3.ccr21.atl01.atlas.cogentco.com fraudulent rDNS)
11 154.54.26.49     50ms   33ms   32ms  TTL:245  (te2-1.ccr01.atl07.atlas.cogentco.com fraudulent rDNS)
12 38.122.130.10    36ms   31ms   32ms  TTL:244  (No rDNS)
13 207.210.114.182  32ms   32ms   34ms  TTL:243  (No rDNS)
14 64.22.76.130     33ms   36ms   33ms  TTL:244  (fe0-24.3550-01.alphahosting.com fraudulent rDNS)
15   No Response      *      *      *                 
16   No Response      *      *      *                 
17   No Response      *      *      *                 
18   No Response      *      *      *                 
19   No Response      *      *      *                 
20   No Response      *      *      *                 
21   No Response      *      *      *                 
22   No Response      *      *      *                 
23   No Response      *      *      *                 
24   No Response      *      *      *                 
25   No Response      *      *      *                 
26   No Response      *      *      *                 
27   No Response      *      *      *                 
28   No Response      *      *      *                 
29   No Response      *      *      *                 


10/01/11 16:47:10 Fast traceroute maddoktor2.com
Trace maddoktor2.com failed, no such host


10/01/11 16:57:44 Fast traceroute alphahosting.com
Trace alphahosting.com (75.127.110.69) ...
 1 192.168.1.1       0ms    0ms    0ms  TTL: 64  (No rDNS)
 2 10.239.50.1       8ms    9ms    8ms  TTL:254  (No rDNS)
 3 66.68.1.97        7ms    7ms    7ms  TTL:253  (te1-4.austtxs-er04.texas.rr.com ok)
 4 24.27.13.98      21ms   35ms   11ms  TTL:252  (te0-10-0-0.austtxa-cr01.texas.rr.com ok)
 5 72.179.205.56    19ms   22ms   35ms  TTL:251  (te0-12-0-2.dllatxl3-cr01.texas.rr.com ok)
 6 66.109.6.88      15ms   22ms   16ms  TTL:250  (ae-4-0.cr0.dfw10.tbone.rr.com bogus rDNS: host not found [authoritative])
 7 66.109.6.209     15ms   16ms   15ms  TTL:249  (ae-3-0.pr0.dfw10.tbone.rr.com bogus rDNS: host not found [authoritative])
 8 154.54.11.49     15ms   19ms   15ms  TTL:248  (te9-4.mpd01.dfw03.atlas.cogentco.com fraudulent rDNS)
 9 154.54.25.218    23ms   23ms   23ms  TTL:246  (te0-0-0-2.ccr21.iah01.atlas.cogentco.com fraudulent rDNS)
10 154.54.25.117    34ms   32ms   34ms  TTL:243  (te0-2-0-7.ccr21.atl01.atlas.cogentco.com fraudulent rDNS)
11 154.54.26.49     37ms   33ms   32ms  TTL:245  (te2-1.ccr01.atl07.atlas.cogentco.com fraudulent rDNS)
12 38.122.130.10    33ms   32ms   32ms  TTL:244  (No rDNS)
13 207.210.114.182  34ms   32ms   32ms  TTL:245  (No rDNS)
14 64.22.76.130     33ms   33ms   33ms  TTL:244  (fe0-24.3550-01.alphahosting.com fraudulent rDNS)
15   No Response      *      *      *                 
16   No Response      *      *      *                 
17   No Response      *      *      *                 
18   No Response      *      *      *                 
19   No Response      *      *      *                 
20   No Response      *      *      *                 
21   No Response      *      *      *                 
22   No Response      *      *      *                 
23   No Response      *      *      *                 
24   No Response      *      *      *                 
25   No Response      *      *      *                 
26   No Response      *      *      *                 
27   No Response      *      *      *                 
28   No Response      *      *      *                 
29   No Response      *      *      *

Edited by mikey, 02 October 2011 - 05:10 PM.

[cnm]

Yes, mostly tracert looked like that, but during the 'TTL expired in transit' interval after the server had booted back up, I got this, with the trace ending in a loop and never getting there:

Tracing route to www.spywareinfoforum.com [75.127.110.25]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    70 ms    21 ms    19 ms  67.169.84.1
  3    24 ms    13 ms    14 ms  te-4-2-ur03.santaclara.ca.sfba.comcast.net [68.85.191.9]
  4    10 ms    12 ms    12 ms  te-1-10-0-7-ar01.sfsutro.ca.sfba.comcast.net [68.85.155.62]
  5    14 ms    31 ms    14 ms  pos-3-3-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.91.229]
  6    13 ms    15 ms    15 ms  pos-0-3-0-0-pe01.529bryant.ca.ibone.comcast.net[68.86.87.142]
  7    14 ms    15 ms    15 ms  te4-7.mpd01.sjc04.atlas.cogentco.com [154.54.11.185]
  8    17 ms    15 ms    15 ms  te4-1.ccr02.sjc04.atlas.cogentco.com [154.54.24.218]
  9    13 ms    15 ms    17 ms  te0-0-0-6.ccr21.sfo01.atlas.cogentco.com [154.54.7.173]
 10    58 ms    56 ms    56 ms  te0-3-0-1.ccr21.mci01.atlas.cogentco.com [154.54.24.110]
 11    72 ms    72 ms    73 ms  te0-0-0-3.ccr21.ord01.atlas.cogentco.com [154.54.2.218]
 12    76 ms    79 ms    79 ms  te0-3-0-5.ccr21.atl01.atlas.cogentco.com [154.54.29.105]
 13    79 ms    79 ms    79 ms  te2-1.ccr01.atl07.atlas.cogentco.com [154.54.26.49]
 14    78 ms    79 ms    76 ms  38.122.130.10
 15    79 ms    77 ms    78 ms  cs01.atl.gnax.pc-e05-r0.tengi1-1.simplehelix.com [64.22.115.62]
 16    76 ms    79 ms    79 ms  64.22.115.61
 17    79 ms    75 ms    77 ms  cs01.atl.gnax.pc-e05-r0.tengi1-1.simplehelix.com [64.22.115.62]
 18    76 ms    76 ms    79 ms  64.22.115.61
 19    78 ms   101 ms    79 ms  cs01.atl.gnax.pc-e05-r0.tengi1-1.simplehelix.com [64.22.115.62]
 20    78 ms    79 ms    76 ms  64.22.115.61
 21    94 ms    76 ms    76 ms  cs01.atl.gnax.pc-e05-r0.tengi1-1.simplehelix.com [64.22.115.62]
 22    76 ms    76 ms    76 ms  64.22.115.61
 23    80 ms   109 ms    76 ms  cs01.atl.gnax.pc-e05-r0.tengi1-1.simplehelix.com [64.22.115.62]
 24    79 ms    79 ms    79 ms  64.22.115.61
 25    94 ms    79 ms   111 ms  cs01.atl.gnax.pc-e05-r0.tengi1-1.simplehelix.com [64.22.115.62]
 26    79 ms    76 ms    79 ms  64.22.115.61
 27    77 ms    76 ms    79 ms  cs01.atl.gnax.pc-e05-r0.tengi1-1.simplehelix.com [64.22.115.62]
 28    79 ms    79 ms    79 ms  64.22.115.61
 29    78 ms    79 ms    76 ms  cs01.atl.gnax.pc-e05-r0.tengi1-1.simplehelix.com [64.22.115.62]
 30    79 ms    79 ms    79 ms  64.22.115.61

Trace complete.