About SRB2.org's downtime.

[Sniperific]

Support could find my sever (they find some other guy's, -_-) so now I'm starting to recreate the blogs, and the posts. then make a html dump of log of changes that where made of the wiki before the old server went

So we have moved to a new host for srb2.org then =S

 

[Cue]

Support could find my sever (they find some other guy's, -_-) so now I'm starting to recreate the blogs, and the posts. then make a html dump of log of changes that where made of the wiki before the old server went

So we have moved to a new host for srb2.org then =S

We moved ages ago, where the heck have you been?

 

[Kopper]

Probably in a cave somewhere, sleeping. *shot* Well anyway, it's all OK again, let's hope the n00bs stay out this time!

 

[Sniperific]

We moved ages ago, where the heck have you been?

in a cave somewhere, sleeping

 

[LoganA]

... then make a html dump of log of changes that where made of the wiki before the old server went

http://ms.srb2.org/phoenix/wiki 1of2.html
http://ms.srb2.org/phoenix/wiki 2of2.html

 

[Cue]

... then make a html dump of log of changes that where made of the wiki before the old server went

http://ms.srb2.org/phoenix/wiki 1of2.html
http://ms.srb2.org/phoenix/wiki 2of2.html

So, uhh, who wants to go through and restore all that? =P

FYI: Starts from the change with the comment:

Missing stuff: AHEM

Just do a search on it, should be a June 24th change.

 

[LoganA]

Just to let you all know, support got in contact with me again, after a 6 day gap.

 

[Rob]

I think I'll go and restore those old pages, the ones that aren't rather minor edits, anyways.

Also, Logan, any good news from support?

 

[LoganA]

I think I'll go and restore those old pages, the ones that aren't rather minor edits, anyways.

Also, Logan, any good news from support?

The best way would to start fro the 2nd part, from the bottom, and work upward, then go to the bottom of the 1st page, and work upward again.

Well, support said that the server been up for a week now. I told that that the server isn't up because I can't see anything running from the IP, no DNS server, HTTP, SSH, FTP, anything, so we are trying to find out why this is happening.

 

[Cue]

Bet they've blocked all the ports... =P

 

[Scarbo the Black Sheep]

Unfortunately, I was only able to restore about 200 edits. I didn't bother restoring talk pages. A ton of stuff didn't make it to the atom feeds, and I did use both pages.

 

[Rob]

See, that's bad, because I have a huge backup of everything thanks to Oogaland, and I can restore it all easily, when I have the time.

 

[Scarbo the Black Sheep]

That totally makes me feel appreciated.

 

[Rob]

Well, I was kinda hoping you'd pick up on the edit summaries I left on certain pages as "I'll do other stuff while he restores older edits". =P

 

[Scarbo the Black Sheep]

I picked up on the Logan-tells-me-specifically-in-my-talk-page-to-restore-the-edits thing, though.

 

[LoganA]

The server's Internet connection seem to have gone down around 10/08/08 22:49:33 EST [TZ -5:00]

>ping 69.197.136.58

Pinging 69.197.136.58 with 32 bytes of data:

Reply from 69.30.235.209: TTL expired in transit.
Reply from 69.30.235.209: TTL expired in transit.
Reply from 69.30.235.209: TTL expired in transit.
Reply from 69.30.235.209: TTL expired in transit.

Ping statistics for 69.197.136.58:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

#traceroute 69.197.136.58
traceroute to 69.197.136.58 (69.197.136.58), 30 hops max, 38 byte packets
 1 * * *
 2 68.85.140.125 (68.85.140.125) 10.963 ms 7.048 ms 7.446 ms
 3 po-20-ur02.lawrence.ma.boston.comcast.net (68.87.144.141) 9.131 ms 7.599 ms 9.025 ms
 4 be-15-crs01.woburn.ma.boston.comcast.net (68.87.145.153) 10.606 ms 10.883 ms 14.581 ms
 5 po-15-ar02.woburn.ma.boston.comcast.net (68.87.145.154) 9.732 ms 11.085 ms 9.158 ms
 6 te-3-1-ar01.chartford.ct.hartford.comcast.net (68.86.90.58) 16.769 ms 13.858 ms 13.412 ms
 7 pos-0-3-0-0-cr01.chicago.il.ibone.comcast.net (68.86.90.57) 15.391 ms 16.069 ms 16.699 ms
 8 66-109-10-137.tbone.rr.com (66.109.10.137) 17.008 ms 15.848 ms 15.191 ms
 9 ae-1-0.cr0.nyc20.tbone.rr.com (66.109.6.156) 16.748 ms 15.501 ms 17.136 ms
10 ae-3-0.cr0.chi30.tbone.rr.com (66.109.6.25) 42.922 ms 41.364 ms 41.328 ms
11 66.109.6.113 (66.109.6.113) 43.155 ms 42.197 ms 41.262 ms
12 RDC-24-94-161-33.kc.rr.com (24.94.161.33) 65.142 ms 61.090 ms 61.274 ms
13 gig1-0.kscymordc-rtr5.kc.rr.com (24.94.160.42) 61.271 ms 61.235 ms 61.358 ms
14 rrcs-67-53-162-198.west.biz.rr.com (67.53.162.198) 65.340 ms 84.905 ms 65.354 ms
15 69.30.235.209 (69.30.235.209) 108.992 ms 135.846 ms *
16 69.30.235.210 (69.30.235.210) 64.602 ms 64.720 ms 65.758 ms
17 69.30.235.209 (69.30.235.209) 74.226 ms 106.658 ms 121.954 ms
18 69.30.235.210 (69.30.235.210) 64.634 ms 64.332 ms 65.902 ms
19 * 69.30.235.209 (69.30.235.209) 124.334 ms 130.366 ms
20 69.30.235.210 (69.30.235.210) 65.194 ms 65.074 ms 65.206 ms
21 69.30.235.209 (69.30.235.209) 150.125 ms 124.302 ms 123.576 ms
22 69.30.235.210 (69.30.235.210) 65.014 ms 65.116 ms 64.194 ms
23 69.30.235.209 (69.30.235.209) 120.099 ms 117.325 ms 174.281 ms
24 69.30.235.210 (69.30.235.210) 65.419 ms 77.933 ms 65.447 ms
25 69.30.235.209 (69.30.235.209) 159.644 ms 133.761 ms 125.918 ms
26 69.30.235.210 (69.30.235.210) 65.562 ms 65.572 ms 65.775 ms
27 69.30.235.209 (69.30.235.209) 142.998 ms 103.046 ms 97.919 ms
28 69.30.235.210 (69.30.235.210) 66.155 ms 65.731 ms 65.748 ms
29 69.30.235.209 (69.30.235.209) 69.749 ms 77.301 ms 75.291 ms
30 69.30.235.210 (69.30.235.210) 66.857 ms 65.220 ms 65.713 ms

I opened up a support ticket at the datacenter.

 

[Cue]

And as per usual, Joe is swift and promptly fixes the problem. :)

 

[Scarbo the Black Sheep]

So what's the problem this time?

 

[Cue]

Data Centre is down.

 

[light the elementa]

Anyone have a clue about when the MasterServer will be back up?