Shoutbox

quote:

---

Originally posted by wj
Ok, At this point, Tracert's aren't going to help.

If we see it go down, we'll look into it, otherwise there just is not much we can do.

---

always happens at the same time, around 3-4PM GMT but it doesnt happen every day.

Problem being, I think I'm usually the only one on even near the time and it's right during my morning commute to work.

It didn't feel like a network/routing issue, felt more like apache was having issues (or some such thing).

I'm guessing something is running in the cron at that time (though I've checked and didnt find anything) that is just bogging down the server.

Server was off for a bit again....here's the ping and tracert results:

Pingen naar msghelp.net [64.62.180.102] met 32 byte gegevens:

Antwoord van 64.62.180.102: bytes=32 tijd=178 ms TTL=53
Antwoord van 64.62.180.102: bytes=32 tijd=178 ms TTL=53
Antwoord van 64.62.180.102: bytes=32 tijd=177 ms TTL=53
Antwoord van 64.62.180.102: bytes=32 tijd=177 ms TTL=53

Ping-statistieken voor 64.62.180.102:
    Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
    (0% verlies).De gemiddelde tijd voor het uitvoeren van één bewerking in mill
iseconden:
    Minimum = 177ms, Maximum = 178ms, Gemiddelde = 177ms

----------------------------------------------------------------------------------

Bezig met het traceren van de route naar msghelp.net [64.62.180.102]
via maximaal 30 hops:

  1     *        *        *     Time-out bij opdracht.
  2     *        *        *     Time-out bij opdracht.
  3    24 ms    23 ms    23 ms  s55924001.adsl.wanadoo.nl [85.146.64.1]
  4    31 ms    31 ms    31 ms  V812.dr4-asd6.nl.euro.net [194.134.156.89]
  5    30 ms    31 ms    31 ms  10GE2-4.cr2-asd6.nl.euro.net [194.134.162.61]
  6    30 ms    31 ms    31 ms  10GE1-1.cr2-asd4.nl.euro.net [194.134.162.162]
  7    31 ms    31 ms    31 ms  PC12.er1-asd4.nl.euro.net [194.134.162.9]
  8    31 ms    32 ms    32 ms  gsr12416.ams.he.net [195.69.145.150]
  9    39 ms    38 ms    39 ms  pos0-0.gsr12416.lon.he.net [216.66.24.157]
10   108 ms   108 ms   109 ms  pos4-1.gsr12416.nyc.he.net [216.218.200.101]
11   176 ms   176 ms   175 ms  pos0-1.gsr12416.sjc2.he.net [216.218.223.133]
12   182 ms   182 ms   182 ms  pos10-0.gsr12416.fmt.he.net [216.218.229.38]
13   177 ms   178 ms   178 ms  64.62.180.102

De trace is voltooid.

I'm going to close this thread, because we already know what's triggering the downtime, and Chris says he's going to work on it when he has time.

Any downtime around 15:30 to 16:00 GMT should be ignored.