Seems like every day at 4AM, simplemachines.org disapears for about 10 minutes. You can't even connect to the server.
I know that's when Cron.Daily is normally run, so I'm wondering if there's something running that bogs the server down to the point it doesn't respond.
Anyone else that's online in the middle of the night seeing that?
yep every day!
4am what time?
There are people all over the world here with different timezones.
4am what time, EST, CET, PST ?
I'm on Eastern time, and the server is too since it shows the correct time for me (the offset in my profile is at 0)
That's why I suspected cron jobs, since most linux distros run the daily cron at 4:00AM by default.
It does work for me and 10.00 (CET), so probarbly only some of you having connection problems in the 'States. I'm not having problems accessing SMF at all times during the day.
im EST too and I can't access SMF around 4am.
Interesting, will look into it but I know I'm not waking up at 4am to check :)
Have noticed it myself before but never clocked the time.
(https://www.simplemachines.org/community/proxy.php?request=http%3A%2F%2Fwww.woopig.net%2Fimages%2Fsmf.jpg&hash=99c5a2401e0c580126f252cb001fc394f0d900df)
ROTFL.
I've actually noticed that it liked to go down... about 1:00 am my time.. (that is 4 am...)
Strange...
-[Unknown]
Yep. I've noticed that too. (Because I'm always up. 3 am CST, so that coincides with your reports. The whole server goes. Yabbse.org and Simplemachines.org both crash.
Makes sense since both are on the same server - the only things on the server actually.
Quote from: Jeff Lewis on September 11, 2003, 07:24:49 AM
Interesting, will look into it but I know I'm not waking up at 4am to check :)
Well then tell the Sys Admin for Lewis Media to do it. :)
Will take a look at cron but I bet it is some form of backup going on.
That makes sense, every webhost does a backup once a day at the same time everyday.
So that means that backup might be the reason. But, weird since it only occurs in USA, here in Norway I don't experience any problems browsing SMF or YSE at that time of day.
Hmm not sure if it would be a possible router issue.
As for the sys admin, I'm it :P
Quote from: Jeff Lewis on September 11, 2003, 11:54:48 PM
Hmm not sure if it would be a possible router issue.
What would the router be doing at 4:00AM everyday though?
It only lasts about 10 minutes, so anyone not seeing it is probably just not clicking anything during that time. I noticed it was down 3 different nights at around the same time, so I made it a point to check at 4 a couple of other nights since I'm always up. Sure enough, dead as a doornail at 4AM on the dot every night.
Interestingly, look at this traceroute I just ran:
Tracing route to simplemachines.org [216.67.249.136]
over a maximum of 30 hops:
1 4 ms 3 ms 3 ms sbrouter.killearn.com [208.254.245.161]
2 7 ms 7 ms 7 ms Loopback0.GW6.ATL1.ALTER.NET [137.39.5.201]
3 7 ms 7 ms 8 ms 125.at-2-2-0.xl4.atl1.alter.net [152.63.82.146]
4 7 ms 7 ms 7 ms 0.so-3-1-0.xl2.atl5.alter.net [152.63.0.238]
5 9 ms 7 ms 7 ms pos7-0.br2.atl5.alter.net [152.63.82.193]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
Tried several times with the same result, and I know the server is up since I'm posting this.
Yeah, my tracert's always stop one ip before too. It's also ONLY monkey - llama works fine.
-[Unknown]
Well, if the server didn't allow ping, traceroutes would stop 1 IP before the server. But, my traceroute is never leaving Atlanta. Whois on the IP indicates that the server is at Pwebtech, which is in NJ ???
Since I didn't have anything better to do, I sat here and clicked refresh a bunch of times at 4:00. It stopped responding at 4:00:12 and was down for 12 minutes. It's not a routing problem, because I could ping it the entire time.
Then it's about backup. I have the same problem on my site www.dataportalen.com, every now and then I can't access the site, but ping and FTP are working fine.
Thanks for the traceroute, will look into this. Doesn't appear to happen to our other servers at all.
Trace is fine here
Tracing route to simplemachines.org [216.67.249.136]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.2
2 31 ms 29 ms 28 ms lo1-bba1.th.eclipse.net.uk [212.104.130.141]
3 28 ms 29 ms 29 ms ge5-1-core4.th.eclipse.net.uk [81.5.191.41]
4 29 ms 29 ms 29 ms linx.ge-0-2-0.gbr1.ltn.nac.net [195.66.226.94]
5 99 ms 98 ms 98 ms 1209.at-3-1-0.gbr2.nyc.nac.net [209.123.11.245]
6 99 ms 101 ms 101 ms 0.so-0-3-0.gbr2.nwr.nac.net [209.123.11.26]
7 101 ms 101 ms 101 ms 0.so-0-3-0.gbr1.oct.nac.net [209.123.11.233]
8 102 ms 101 ms 101 ms 209.123.182.243
9 102 ms 101 ms 101 ms 216.67.249.136
Trace complete.
If you could access the server when you couldnt ping it then really its nothing to worry about, probably just some router configured to discard ICMP packets.
Quote from: Ben_S on September 12, 2003, 08:35:07 AM
If you could access the server when you couldnt ping it then really its nothing to worry about, probably just some router configured to discard ICMP packets.
Other way around - can ping it, but can't access.
Quote from: Jeff Lewis on September 11, 2003, 11:54:48 PM
As for the sys admin, I'm it :P
I know... it was a joke :P
I had a similar problem with my dedicated server when it was first brought online...every day at 5am it went down for 10 mins...We believe it to be a router issue and the datacenter resolved it after we brought it to their attention about 5 days in a row. They never stated the resolution to us, but it hasn't happened again. There was talk of it being a router issue, but again, I was never told directly -- they just fixed it. It apparently wasn't a big deal for them to solve after we provided them a tracert taken during that time period.
Jason