Busy server

[Treecycle]

In the last few weeks, every now and then when changing screens I get a message saying that "The server is too busy at the moment. Please try again later". Is this a problem with the server, or is it just too many people on at the same time?

[Mobyturns]

No idea but I have experienced the same particularly around 6am. Lost a few posts when hitting "submit reply".

[Bedford]

No idea but I have experienced the same particularly around 6am. Lost a few posts when hitting "submit reply".

From Neil,

There is major backup of the forums at around 6:00 am each day and again in the wee small hours, there are also small backups run at intivals throughout the day. Most of the backups run without a problem. The 6:00 am one does shut things down a little for up to 5 minutes of minutes.

[steven]

Besides when the database is backed up, the server has been experiencing high load all week. You should find the site much quicker now and the busy message shouldn't be showing except for a little after 6am for 5 minutes and for a few minutes between 2am and 3am.

regards
steve

[RoyG]

Besides when the database is backed up, the server has been experiencing high load all week. You should find the site much quicker now and the busy message shouldn't be showing except for a little after 6am for 5 minutes and for a few minutes between 2am and 3am.

regards
steve

Steve,

I've also been seeing this "Server Slow" messages since around the 1/7/2014. Unfortunately, until I saw this thread, I had not taken much notice of what time the errors were occurring. So, now I'm taking notice. This morning (4/7/2014) between 8:00 and 8:45am I saw the error about five times - well outside your backup window. I also saw the error a few times yesterday afternoon (3/7/2014 at around 5:00pm. So, the backups may not always be the cause of these errors.

Also, between 8:00am and 9:45am this morning, your web server has been throwing up lots of 104 errors (Connection reset by peer). When this happens, I've tried pinging your server, but no response - but then your server is probably set to ignore ping requests. traceroute still gets through to your server when 104 errors are happening, so I suspect that the problem lies on your web server, and possibly just reinforces the fact that the server has been under a heavy load recently.

Hope that info is useful.

Regards,

Roy
(Retired Unix/Linux System Admin)

[steven]

Hi Roy

I've never seen the 'connection reset by peer' error on here before. When it happened were you just browsing around or were you submitting a post?

Since my last post, there were a few load spikes which I haven't been able to track down the cause of. I had also lowered the threshold for when that message appears, it's been back to normal for about an hour tho.

In regards to pinging the server, you should be able to do this;

C:\Users\stevenr>ping woodworkforums.com -n 15


Pinging woodworkforums.com [75.126.207.178] with 32 bytes of data:
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48
Reply from 75.126.207.178: bytes=32 time=200ms TTL=48


Ping statistics for 75.126.207.178:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 200ms, Maximum = 200ms, Average = 200ms

[RoyG]

Hi Roy

I've never seen the 'connection reset by peer' error on here before. When it happened were you just browsing around or were you submitting a post?

Steven,

When I first got the 104 error, I was logging in, and the error repeated a few times when I was browsing. Pings were definitely going unanswered earlier this morning when I was having the problem - but I'm now getting ping responses:

royg@royg-Galago-UltraPro $ ping -c5 www.woodworkforum.com
PING www.woodworkforum.com (50.63.202.104) 56(84) bytes of data.
64 bytes from ip-50-63-202-104.ip.secureserver.net (50.63.202.104): icmp_seq=1 ttl=45 time=241 ms
64 bytes from ip-50-63-202-104.ip.secureserver.net (50.63.202.104): icmp_seq=2 ttl=45 time=242 ms
64 bytes from ip-50-63-202-104.ip.secureserver.net (50.63.202.104): icmp_seq=3 ttl=45 time=248 ms
64 bytes from ip-50-63-202-104.ip.secureserver.net (50.63.202.104): icmp_seq=4 ttl=45 time=767 ms
64 bytes from ip-50-63-202-104.ip.secureserver.net (50.63.202.104): icmp_seq=5 ttl=45 time=640 ms


--- www.woodworkforum.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 241.443/428.376/767.959/228.969 ms
royg@royg-Galago-UltraPro $

When I wasn't getting a ping response this morning, I was getting a traceroute response - so if the server was responding to Traceroute icmp packets, I'd have thought it should have also been responding to ping requests. Can't explain that

Additional Info: Just had another 104 error when I was posting this reply at 12:00md 4/7/2014 .....

Regards,

Roy