Jump to content

Recommended Posts

Posted

Question to all the people who have MW outages sometimes:

Do any of you have a yahoo mail account, and do you also experience yahoo mail outages?

I just realized that for the last three months, only Macross World and my Yahoo mail account have been on-and-off experiencing outages.

-Sherlock Holmes

Posted

I've got yahoo mail as well, but no outages there, only MW.

Posted (edited)
I've got yahoo mail as well, but no outages there, only MW.

Mmm....the plot thickens! How about bad weather? It's summer here, but it's been raining for two months pretty much non stop.

I'm trying to deduce causality...

-Sherlock Holmes

Edited by VFTF1
Posted

I wanted to write that I had an outage, but then I had another outage when I clicked "add reply" :(

I think it's all yahoo mail's fault. Because obviously my yahoo mail didn't work either.

Now both MW and Yahoo mail work fine.

Maybe someone is doing an EMS attack... or EMP? EMP.

It's an EMP attack by aliens.

These are the first signals.

Oh man! Think about it!

These are the warning signals. And we will scratch our heads and ignore them. But then, in five years - the aliens will come and eat us all! We have to spread the word now! These can't be any ordinary outages! There is no rational explanation for why Yahoo mail and Macross world are the only ones having outages?

It must be aliens trying to access our emails to learn about us, and mistakenly thinking that Macross world contains pictures of real life mecha that Earth has to defend itself!

It's like Galaxy Quest!

Pete

Posted
Almost not really worth mentioning everything is running so good guys thanks Shaun!!!

Oh - yeah. I'm not complaining. I could care less about the outages. If Shawn can't find out what the problem is, then he shouldn't have to bend over backwards trying. Maybe it'll sort itself out. The site works fine 99% of the time. The outages are short lived.

So - just to be clear that I wasn't complaining or nagging "fix it!" - It's not that big a deal. Just a kind of FYI thread.

Pete

Posted (edited)

My money is on a few people having routing issues to the MW server.

Announcing "I've had an outage" and noting the time, while providing some information, eventually stops being helpful when the problem persists after basic actions (like a server restart) have been taken. ;)

In the hopes of figuring out if its a routing/connectivity issue (rather than a server side issue). . .

While things are working, please take a moment to do the following from a Windows command prompt:

tracert macrossworld.com > c:\mw-good.txt

The file on the root of your c: drive named "mw-good.txt" should now have a record of the route you were taking when things were working. Save this for later.

The next time you have an outage, run the following from a Windows command prompt:

tracert macrossworld.com > c:\mw-bad.txt

Then, post the contents of both the "good" and "bad" file here (take out the first few lines of each unless you want everyone to know where you live and/or your home IP address!).

By comparing the two files, we can hopefully determine if overall connectivity to the MW server has been lost, and if so, at what point. And from there, we can determine if there's a realistic hope of Shawn actually being able to do anything about it or if possibly the hosting provider needs to get on the horn to their upstream network providers to report intermittent outages.

Best,

H

P.S. If you are not an admin on your computer, you may get an error when trying to write to the root of your c: drive. If that's the case, remove the "c:\" and just give a filename. . . it should then be written to your user directory.

P.P.S. Here's an example of a successful traceroute (tracert)

Tracing route to macrossworld.com [74.86.23.244]
over a maximum of 30 hops:

1     1 ms    <1 ms    <1 ms  -------bleh------------
2    <1 ms    <1 ms    <1 ms  -------bleh------------
3   187 ms     1 ms     1 ms  -------bleh------------
4    <1 ms    <1 ms    <1 ms  -------bleh------------
5     3 ms     3 ms     2 ms  -------bleh------------
6     3 ms     3 ms     4 ms  -------bleh------------
7     3 ms     3 ms     3 ms  -------bleh------------ 
8     3 ms     3 ms     3 ms  -------bleh------------
9     3 ms     3 ms     3 ms  te-4-1-0.rar3.la-ca.us.xo.net [207.88.12.153] 
10    36 ms    36 ms    36 ms  207.88.12.45.ptr.us.xo.net [207.88.12.45] 
11    36 ms    36 ms    36 ms  207.88.14.34.ptr.us.xo.net [207.88.14.34] 
12    36 ms    36 ms    36 ms  207.88.185.74.ptr.us.xo.net [207.88.185.74] 
13    36 ms    36 ms    36 ms  border3.tge4-1-bbnet2.ext1.dal.pnap.net [216.52.191.83] 
14    36 ms    36 ms    36 ms  te2-1.cer03.dal01.dallas-datacenter.com [216.52.189.30] 
15    38 ms    39 ms    39 ms  po3.dar01.dal01.dallas-datacenter.com [66.228.118.209] 
16    39 ms    39 ms    39 ms  po1.fcr02.dal01.dallas-datacenter.com [66.228.118.178] 
17    39 ms    39 ms    40 ms  macrossworld.com [74.86.23.244] 

Trace complete.

Edited by Hurin
Posted

What's a Windows Command Prompt? :o

I think I'm gonna stick my head back in the sand and leave this to people who are clearly smarter than me :(

Pete

Posted
What's a Windows Command Prompt? :o

I think I'm gonna stick my head back in the sand and leave this to people who are clearly smarter than me :(

Pete

It's also called a command prompt or "dos prompt". . . or the "command line."

The easiest way to get to it is by:

1. On your keyboard, press "windows key" and "R" key at the same time.

2. Type "cmd" in the run dialog box that pops up.

3. Click OK.

You're now looking at the windows command prompt. But that's only one of many ways to get to it. It's also buried in the start menu somewhere (usually under accessories).

(type "exit" to close the command prompt and its window)

Posted

Do you want multiple copies of good ones? I could run one every day or so. I've only had the one outage this week, so I can't provide a bad one yet.

Posted
Do you want multiple copies of good ones? I could run one every day or so. I've only had the one outage this week, so I can't provide a bad one yet.

No need for several good ones. What might be best, though, is a saved good one taken whenever, then a bad one, then once it starts working, grab another good one.

Ideally, the route should remain the same in each one. However, when experiencing trouble, the route should be broken at some point along the line if it's a issue with one of the "hops" along a user's route to the MW server.

Posted

Got a partial-----didn't connect for 60 secs, then it did on the second try. But it may be useful:

Good/working:

1 4 ms 6 ms 5 ms

2 8 ms 5 ms 5 ms

3 12 ms 14 ms 13 ms

4 13 ms 13 ms 17 ms

5 12 ms 13 ms 14 ms

6 14 ms 13 ms 13 ms 12.122.86.41

7 14 ms 13 ms 14 ms att-gw.chicago.savvis.net [192.205.35.42]

8 14 ms 13 ms 13 ms cr2-tengig-0-0-5-0.chicago.savvis.net [204.70.195.117]

9 38 ms 41 ms 43 ms cr2-tengig0-0-2-0.dallas.savvis.net [204.70.196.210]

10 39 ms 70 ms 40 ms dpr1-ge-4-0-0.dallasequinix.savvis.net [204.70.196.30]

11 40 ms 39 ms 40 ms er1-te-2-1.dallasequinix.savvis.net [204.70.204.145]

12 39 ms 39 ms 40 ms te1-1.cer02.dal01.dallas-datacenter.com [208.175.175.10]

13 38 ms 39 ms 40 ms po2.dar01.dal01.dallas-datacenter.com [66.228.118.205]

14 39 ms 39 ms 39 ms po1.fcr02.dal01.dallas-datacenter.com [66.228.118.178]

15 40 ms 41 ms 40 ms macrossworld.com [74.86.23.244]

Failed:

1 6 ms 5 ms 5 ms

2 7 ms 6 ms 7 ms

3 12 ms 12 ms 13 ms

4 13 ms 13 ms 14 ms

5 12 ms 13 ms 14 ms

6 13 ms 13 ms 13 ms 12.122.86.41

7 14 ms 13 ms 13 ms att-gw.chicago.savvis.net [192.205.35.42]

8 13 ms 16 ms 13 ms cr2-tengig-0-0-5-0.chicago.savvis.net [204.70.195.117]

9 41 ms 40 ms 39 ms cr2-tengig0-0-2-0.dallas.savvis.net [204.70.196.210]

10

Posted

ugh, don't know about router issues but I couldn't get on before I left for MWCon and still had trouble when I got to Con and tried to log on with iphone. Wanted to blog to the thread from there...

Posted

Failures from a few hours ago:

1 7 ms 7 ms 8 ms

2 6 ms 7 ms 7 ms

3 35 ms 23 ms 14 ms

4 15 ms 14 ms 14 ms

5 14 ms 13 ms 17 ms

6 12 ms 13 ms 14 ms 12.122.86.41

7 16 ms 12 ms 23 ms att-gw.chicago.savvis.net [192.205.35.42]

8 13 ms 13 ms 13 ms cr2-tengig-0-0-5-0.chicago.savvis.net [204.70.195.117]

9 39 ms 40 ms 40 ms cr2-tengig0-0-2-0.dallas.savvis.net [204.70.196.210]

10 40 ms 41 ms 52 ms dpr1-ge-4-0-0.dallasequinix.savvis.net [204.70.196.30]

11 41 ms 40 ms 41 ms er1-te-2-1.dallasequinix.savvis.net [204.70.204.145]

12 46 ms 40 ms 50 ms te1-1.cer02.dal01.dallas-datacenter.com [208.175.175.10]

13 41 ms 41 ms 42 ms po2.dar01.dal01.dallas-datacenter.com [66.228.118.205]

14 38 ms 50 ms 50 ms po1.fcr02.dal01.dallas-datacenter.com [66.228.118.178]

15 40 ms 42 ms 41 ms macrossworld.com [74.86.23.244]

1 5 ms 5 ms 6 ms

2 5 ms 6 ms 7 ms

3 13 ms 16 ms 13 ms

4 13 ms 13 ms 13 ms

5 14 ms 23 ms 13 ms

6 16 ms 12 ms 15 ms

7 14 ms 13 ms 15 ms att-gw.chicago.savvis.net [192.205.35.42]

8 13 ms 15 ms 14 ms cr2-tengig-0-0-5-0.chicago.savvis.net [204.70.195.117]

9 41 ms 41 ms 40 ms cr2-tengig0-0-2-0.dallas.savvis.net [204.70.196.210]

10 39 ms 42 ms 40 ms dpr1-ge-4-0-0.dallasequinix.savvis.net [204.70.196.30]

11 56 ms 210 ms 207 ms er1-te-2-1.dallasequinix.savvis.net [204.70.204.145]

12 39 ms 41 ms 38 ms te1-1.cer02.dal01.dallas-datacenter.com [208.175.175.10]

13 39 ms 51 ms 39 ms po2.dar01.dal01.dallas-datacenter.com [66.228.118.205]

14 39 ms 41 ms 40 ms po1.fcr02.dal01.dallas-datacenter.com [66.228.118.178]

15 42 ms 40 ms 39 ms macrossworld.com [74.86.23.244]

Current working one:

1 19 ms 5 ms 17 ms

2 6 ms 5 ms 10 ms

3 13 ms 11 ms 11 ms

4 14 ms 13 ms 25 ms

5 12 ms 14 ms 21 ms

6 14 ms 13 ms 13 ms

7 14 ms 13 ms 15 ms att-gw.chicago.savvis.net [192.205.35.42]

8 12 ms 19 ms 26 ms cr2-tengig-0-0-5-0.chicago.savvis.net [204.70.195.117]

9 48 ms 39 ms 40 ms cr2-tengig0-0-2-0.dallas.savvis.net [204.70.196.210]

10 39 ms 39 ms 39 ms dpr1-ge-4-0-0.dallasequinix.savvis.net [204.70.196.30]

11 38 ms 39 ms 42 ms er1-te-2-1.dallasequinix.savvis.net [204.70.204.145]

12 40 ms 39 ms 40 ms te1-1.cer02.dal01.dallas-datacenter.com [208.175.175.10]

13 39 ms 200 ms 203 ms po2.dar01.dal01.dallas-datacenter.com [66.228.118.205]

14 40 ms 39 ms 43 ms po1.fcr02.dal01.dallas-datacenter.com [66.228.118.178]

15 40 ms 39 ms 41 ms macrossworld.com [74.86.23.244]

Posted

It's interesting that DH's original failed traceroute (a few posts back) showed a failed traceroute as well. Which would indicate that it's a network provider. And it appeared that the failed hop was within the savvis network a few hops upstream from MW.

But this latest report doesn't show any connectivity issues while apparently the site was down from DH's perspective. Which would tend to indicate a problem on the server itself.

So, at this point, we're getting contradictory indications.

Which, sorta just means we need more data (traceroutes).

DH, can you confirm that those first two traceroutes in your latest post were taken while MW was fully down from your perspective. And, what was the experience on your end when you tried to access it? Timing out? Error message? Just browser icon turning but no result?

Posted

Lost some access around the usual time today. Only browser timeout.

Here's the bad:

Tracing route to macrossworld.com [74.86.23.244]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms

2 <1 ms <1 ms <1 ms

3 <1 ms <1 ms <1 ms

4 <1 ms <1 ms <1 ms

5 1 ms 1 ms 1 ms dc-oak-core1--oak-agg2-10ge.cenic.net [137.164.47.117]

6 1 ms 1 ms 1 ms dc-paix-px1--oak-core1-ge.cenic.net [137.164.47.18]

7 2 ms 1 ms 2 ms xo--paix-px1-ge.cenic.net [198.32.251.42]

8 3 ms 2 ms 2 ms 207.88.12.181.ptr.us.xo.net [207.88.12.181]

9 43 ms 43 ms 43 ms te-3-0-0.rar3.la-ca.us.xo.net [207.88.12.62]

10 43 ms 44 ms 43 ms 207.88.12.45.ptr.us.xo.net [207.88.12.45]

11 43 ms 43 ms 43 ms 207.88.14.34.ptr.us.xo.net [207.88.14.34]

12 53 ms 53 ms 54 ms 207.88.185.74.ptr.us.xo.net [207.88.185.74]

13 53 ms 53 ms 53 ms border3.tge3-1-bbnet1.ext1.dal.pnap.net [216.52.191.22]

14 43 ms 43 ms 43 ms te2-1.cer03.dal01.dallas-datacenter.com [216.52.189.30]

15 44 ms 43 ms 43 ms po3.dar02.dal01.dallas-datacenter.com [66.228.118.211]

16 44 ms 43 ms 44 ms po2.fcr02.dal01.dallas-datacenter.com [66.228.118.182]

17 43 ms 44 ms 45 ms macrossworld.com [74.86.23.244]

Trace complete.

Tracing route to macrossworld.com [74.86.23.244]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms

2 <1 ms <1 ms <1 ms

3 <1 ms <1 ms <1 ms

4 <1 ms <1 ms <1 ms

5 1 ms 1 ms 1 ms dc-oak-core1--oak-agg2-10ge.cenic.net [137.164.47.117]

6 1 ms 1 ms 1 ms dc-paix-px1--oak-core1-ge.cenic.net [137.164.47.18]

7 2 ms 1 ms 2 ms xo--paix-px1-ge.cenic.net [198.32.251.42]

8 2 ms 2 ms 2 ms 207.88.12.181.ptr.us.xo.net [207.88.12.181]

9 44 ms 43 ms 43 ms te-3-0-0.rar3.la-ca.us.xo.net [207.88.12.62]

10 43 ms 43 ms 44 ms 207.88.12.45.ptr.us.xo.net [207.88.12.45]

11 44 ms 44 ms 43 ms 207.88.14.34.ptr.us.xo.net [207.88.14.34]

12 53 ms 53 ms 251 ms 207.88.185.74.ptr.us.xo.net [207.88.185.74]

13 53 ms 53 ms 53 ms border3.tge3-1-bbnet1.ext1.dal.pnap.net [216.52.191.22]

14 43 ms 43 ms 43 ms te2-1.cer03.dal01.dallas-datacenter.com [216.52.189.30]

15 43 ms 43 ms 43 ms po3.dar02.dal01.dallas-datacenter.com [66.228.118.211]

16 43 ms 69 ms 44 ms po2.fcr02.dal01.dallas-datacenter.com [66.228.118.182]

17 44 ms 43 ms 44 ms macrossworld.com [74.86.23.244]

Trace complete.

Here's the good:

Tracing route to macrossworld.com [74.86.23.244]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms

2 <1 ms <1 ms <1 ms

3 <1 ms <1 ms <1 ms

4 <1 ms <1 ms <1 ms

5 1 ms 1 ms 1 ms dc-oak-core1--oak-agg2-10ge.cenic.net [137.164.47.117]

6 2 ms 1 ms 2 ms dc-paix-px1--oak-core1-ge.cenic.net [137.164.47.18]

7 2 ms 1 ms 2 ms xo--paix-px1-ge.cenic.net [198.32.251.42]

8 2 ms 2 ms 3 ms 207.88.12.181.ptr.us.xo.net [207.88.12.181]

9 46 ms 44 ms 44 ms te-3-0-0.rar3.la-ca.us.xo.net [207.88.12.62]

10 43 ms 43 ms 43 ms 207.88.12.45.ptr.us.xo.net [207.88.12.45]

11 43 ms 43 ms 43 ms 207.88.14.34.ptr.us.xo.net [207.88.14.34]

12 53 ms 53 ms 53 ms 207.88.185.74.ptr.us.xo.net [207.88.185.74]

13 53 ms 53 ms 53 ms border3.tge3-1-bbnet1.ext1.dal.pnap.net [216.52.191.22]

14 44 ms 43 ms 43 ms te2-1.cer03.dal01.dallas-datacenter.com [216.52.189.30]

15 44 ms 44 ms 44 ms po3.dar02.dal01.dallas-datacenter.com [66.228.118.211]

16 44 ms 43 ms 44 ms po2.fcr02.dal01.dallas-datacenter.com [66.228.118.182]

17 44 ms 44 ms 44 ms macrossworld.com [74.86.23.244]

Trace complete.

I'm tempted to say it was a fluke today since the outage didn't feel as long. If I can't reach the site for more than an hour, then I'll post those logs.

Posted

For me, I almost always get a "browser icon turning for minutes on end". It is very rare for me to actually get some sort of message/error. (I'm talking about MW over the past decade or so)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...