On Sun, 27 Aug 2006 00:13:50 -0400
Richard A Steenbergen <ras e-gerbil.net> wrote:
> On Sun, Aug 27, 2006 at 08:04:01AM +0930, Mark Smith
wrote:
> >
> > On Sat, 26 Aug 2006 12:48:39 -0700 (PDT)
> > Henry Linneweh <hrlinneweh sbcglobal.net> wrote:
> >
> > >
> > > Every where I go that uses MySql is hozed and
I can not access the pages
> > >
> > > -Henry
> >
> > There seems to have been a big fault over there
that is effecting us
> > here in .AU. According to our local upstream it's
a GLX fault, and by
> > it's duration, it seems to have been a big one -
I was told about it
> > more than 12 hours ago. Examples of sites
customers are having trouble
> > accessing are :
>
> I think you're referring to an issue of blackholed
packets between GX
> (3549) and Singtel (7473) in LA, for packets going to
Optus (4804) (which
> for some reason appear to not be announced to normal
Singtel peers). I
> don't think this was GX's fault actually, but I'm
not sure if the issue
> extended beyond 3549->7473.
>
Optus's AS is 7474, or at least that is the AS we peer
with, and then
that peers with 7473.
Our routes to those destinations had been up for days /
weeks, so it
seemed to be a return path problem. A packet blackhole would
explain it.
> At any rate this has nothing to do with MySQL faults or
off-topic posts,
> and it is venturing dangerously close to actually
talking about routing
> issues. We'd best change the subject to spam or
botnets or something,
> before somebody gets the wrong idea about this list.
>
Maybe the routes were stored in a MySQL database, and they
suffered
from a disk crash ?
Regards,
Mark.
--
"Sheep are slow and tasty, and therefore must
remain constantly
alert."
- Bruce Schneier,
"Beyond Fear"
|