I was just wondering, almost every day at around 4pm (GMT+1) the server goes down for about 10 mins

msgpluslive.net still works but msghelp.net doesnt.

same here

quote:

---

Originally posted by Dazmatic
I was just wondering, almost every day at around 4pm (GMT) the server goes down for about 10 mins

msgpluslive.net still works but msghelp.net doesnt.

---

Downtime is normal, server maintenance, or problems at the data center are usually the causes

quote:

---

Originally posted by absorbation
Downtime is normal, server maintenance, or problems at the data center are usually the causes

---

It is probably maintenance then, they must be doing something to help improve the server

Now my server has gone down

quote:

---

Originally posted by absorbation
It is probably maintenance then, they must be doing something to help improve the server

---

quote:

---

Originally posted by ShawnZ
there's no maintenance that they need to be doing every morning for 10 minutes ¬¬

---

it happened at 6pm and wouldnt let me go on til half past..

quote:

---

Originally posted by server

wj@srv06:~$ uptime
11:49:01 up 83 days, 13:39,  1 user,  load average: 0.50, 0.41, 0.37

---

This happens for me too.  I only pinged the server once and it was fine with the pinging (about 300ms if I remember right).  It anoys me but I can deal with the couple of minutes of nothing (I usually annoy Dazmatic and complain the sever is down )

When is this supposed to happen? In 45 minutes or so?

* WDZ wants to see it

quote:

---

Originally posted by WDZ
When is this supposed to happen? In 45 minutes or so?

* WDZ wants to see it

---

Doesn't look lik it is going to happen today, it usually is out about now if it does.  I can look up my chat logs if you wish and give you the dates I have seen and rough times of when I couldn't access the site if you wanted (might take me a bit but I'd do it for you WDZ )

quote:

---

Originally posted by markee
(I usually annoy Dazmatic and complain the sever is down )

---

There was no downtime related to the server or the connection it was on.

Any downtime you experience has been from one of the upstream providers between you and the server.

quote:

---

Originally posted by Chris Boulton
There was no downtime related to the server or the connection it was on.

Any downtime you experience has been from one of the upstream providers between you and the server.

---

Well it just happened then... I managed to ping it with no problems. It was pretty much 4pm GMT on the dot.

quote:

---

Pinging msghelp.net [64.62.180.102] with 32 bytes of data:

Reply from 64.62.180.102: bytes=32 time=330ms TTL=52
Reply from 64.62.180.102: bytes=32 time=338ms TTL=53
Reply from 64.62.180.102: bytes=32 time=337ms TTL=52
Reply from 64.62.180.102: bytes=32 time=336ms TTL=52

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

---

Happened here too...

Here's my ping & tracert results while I couldnt connect... :

quote:

---

Originally posted by ping.exe
C:\Documents and Settings\Mike>ping msghelp.net

Pinging msghelp.net [64.62.180.102] with 32 bytes of data:

Reply from 64.62.180.102: bytes=32 time=331ms TTL=51
Reply from 64.62.180.102: bytes=32 time=318ms TTL=51
Reply from 64.62.180.102: bytes=32 time=321ms TTL=51
Reply from 64.62.180.102: bytes=32 time=330ms TTL=51

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

---

quote:

---

Originally posted by tracert.exe
C:\Documents and Settings\Mike>tracert msghelp.net

Tracing route to msghelp.net [64.62.180.102]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    42 ms    39 ms    38 ms  62.103.1.80
  3    31 ms    45 ms    33 ms  vlan55-k2.otenet.net [62.103.14.193]
  4    32 ms    28 ms    35 ms  62.103.6.145
  5    30 ms    31 ms    34 ms  athe-GSRb-po1.otenet.net [62.103.6.4]
  6   117 ms   117 ms   112 ms  62.75.3.245
  7   185 ms   195 ms   195 ms  pos2-0-cr02.lon.oteglobe.net [62.75.4.78]
  8   103 ms    98 ms   108 ms  lon.he.net [195.66.226.21]
  9   248 ms   267 ms   268 ms  pos4-1.gsr12416.nyc.he.net [216.218.200.101]
10   322 ms   331 ms   322 ms  pos0-1.gsr12416.sjc2.he.net [216.218.223.133]
11   249 ms   246 ms   249 ms  pos10-0.gsr12416.fmt.he.net [216.218.229.38]
12   341 ms   345 ms   346 ms  64.62.180.102

Trace complete.

---

just happened for me too, in Canada. I'd provide a tracert and ping, if the ports weren't blocked

Yeah, happened to me.. I ran tracert and ping, everything succesfull, but i didnt save the results

I just got it for a second time too. Ping results were the same as above although this time figures were hovering around the 3000ms mark.

quote:

---

Originally posted by haydn
It was pretty much 4pm GMT on the dot.

---

Well, i've noticed it as well, but there isn't an obvious reason why.. i wonder what on earth could be causing it...

I missed it today... was busy messing with MyBB 1.2...

Confirmed, happened for the third day in a row now

Ping results are essentially useless as they don't say where the problem lies or give a good indication of what your ping reply time should be. You need to post complete trace routes (as was done in one case)

The server can go down on me any day.
if u gno wat i mean and i think u do am i rite???

Blame abovenet, their routes have been shitty the last week.

Sorry for bringing this back but they went down again heres the tracert and ping

code:

---

Microsoft Windows XP [Version 5.1.2600]
Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\felu>ping msghelp.net

Pinging msghelp.net [64.62.180.102] with 32 bytes of data:

Reply from 64.62.180.102: bytes=32 time=332ms TTL=49
Reply from 64.62.180.102: bytes=32 time=333ms TTL=49
Reply from 64.62.180.102: bytes=32 time=328ms TTL=49
Reply from 64.62.180.102: bytes=32 time=334ms TTL=49

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

C:\Documents and Settings\felu>tracert msghelp.net

Tracing route to msghelp.net [64.62.180.102]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    21 ms    26 ms    22 ms  rasBTNLDel-static-135.215.56.202.mantraonline.co
m [202.56.215.135]
  3    24 ms    21 ms    22 ms  rasBTNLDel-static-230.215.56.202.mantraonline.co
m [202.56.215.230]
  4    22 ms    29 ms    21 ms  rasBTNLDel-static-162.215.56.202.mantraonline.co
m [202.56.215.162]
  5    31 ms    20 ms    22 ms  203.101.95.181
  6    73 ms    65 ms    67 ms  203.101.100.181
  7    63 ms    68 ms    71 ms  203.101.95.173
  8    58 ms    70 ms    64 ms  61.95.180.17
  9    72 ms    64 ms    69 ms  59.145.11.69
10   334 ms   337 ms   337 ms  217.6.50.109
11   340 ms   337 ms   332 ms  lon-sa1.LON.GB.net.DTAG.DE [62.154.5.37]
12   334 ms   338 ms   336 ms  ldn-b2-pos1-1.telia.net [213.248.75.105]
13   335 ms   337 ms   338 ms  ldn-bb2-pos6-1-0.telia.net [213.248.64.49]
14   350 ms   345 ms   353 ms  adm-bb2-pos6-0-0.telia.net [213.248.65.158]
15   336 ms   338 ms   345 ms  adm-b3-link.telia.net [80.91.249.230]
16   344 ms   350 ms   349 ms  hurricane-109025-adm-b3.c.telia.net [213.248.72.
146]
17   351 ms   345 ms   360 ms  pos0-0.gsr12416.lon.he.net [216.66.24.157]
18   312 ms   307 ms   307 ms  pos4-1.gsr12416.nyc.he.net [216.218.200.101]
19   330 ms   329 ms   331 ms  pos0-1.gsr12416.sjc2.he.net [216.218.223.133]
20   332 ms   328 ms   328 ms  pos10-0.gsr12416.fmt.he.net [216.218.229.38]
21   332 ms   330 ms   330 ms  64.62.180.102

Trace complete.

C:\Documents and Settings\felu>

---

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.

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.

---

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.