Don Terrill’s Speed-Talk

I think that could probably be traced back to the server starting its backup routine.
The server starts backing up every domain/website, which means copy a website-directory to a tmp-folder, then compress it into a zip-file and move on to the next domain/website.
All this copying/compressing increases the load on the server and 'could' cause some slow response or probably perceived down-time.
But the server logs don't show the CPU's are maxed out yet at those times.

Did it again this AM. About 6:45 Did not have the time to do a tracert.

A few settings had been changed but don't know if they were effective yet.
Thanks for the mention. I'll keep looking into it.

For me, its random. Sometimes I can get on, sometimes I can't. Got on today after trying for 3 days. Actually pulled up the site on 1st day, but could not log on nor go to another page following that. Server timed out and was not able to even pull up the website again until this morning.

HB

Just did it again to me. 3:50 pm approx Looked at two or three threads and then Bam, no more I attached another tracert

Locked out again Just a few minutes ago. Here is the tracert:


Tracing route to www.speed-talk.com [37.34.62.24]
over a maximum of 30 hops:

1 4 ms 1 ms 7 ms 192.168.0.1
2 238 ms 279 ms 269 ms 10.198.32.113
3 225 ms 279 ms 289 ms 10.0.155.1
4 242 ms 279 ms 279 ms 10.198.32.65
5 264 ms 270 ms 269 ms 10.164.106.162
6 246 ms 279 ms 289 ms 10.164.106.165
7 247 ms 309 ms 309 ms 10.164.176.65
8 645 ms 1921 ms 409 ms lag-200.bear1.Boston1.Level3.net [4.14.180.233]
9 301 ms 309 ms 299 ms ae-4.r00.bstnma07.us.bb.gin.ntt.net [129.250.66.93]
10 * * * Request timed out.
11 * * * Request timed out.
12 295 ms 329 ms 329 ms ae-3.r22.asbnva02.us.bb.gin.ntt.net [129.250.6.116]
13 279 ms 319 ms 319 ms ae-0.r23.asbnva02.us.bb.gin.ntt.net [129.250.3.85]
14 375 ms 409 ms 409 ms ae-2.r25.amstnl02.nl.bb.gin.ntt.net [129.250.6.163]
15 333 ms 379 ms 399 ms ae-1.a01.amstnl02.nl.bb.gin.ntt.net [129.250.4.173]
16 350 ms 369 ms 369 ms 213.198.92.22
17 330 ms 379 ms 379 ms e1-a7.r1.ams0.transip.net [157.97.168.0]
18 170 ms 179 ms 179 ms r1.f1.ams4.transip.net [77.72.151.121]
19 285 ms 209 ms 209 ms f1.l1.ams4.transip.net [77.72.151.1]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

For whatever it's worth...I haven't had problems in a couple weeks.

and FWIW i have had 3 days of off and on experience. No rhyme or reason to it . Did the same on my cell phone.

Thanks for the feedback.
There are a few services running on the server which can check for serverload and can limit access if the serverload get too high. But when that's the case, a message should be shown, and not a connection error of some sort.

I've changed a few more settings on the server and on the forum itself.

I just get the 'server timed out" message.

Same here, Dave. Tried to get on yesterday. Managed that and logged in. But then got the 'Server Timed Out' message and could never get past that so gave up and tried again just now.

Best regards,

Harry

Update.
Lately I will be able to read a thread or 2 before it times out.
I guess the good news is that it no longer lasts all day.
Come back later, try again and I may or may not be able to spend as much time as I would like.
It's random on when it does it. I can't catch any particular reason for it.

Thanks for the update Dave. That's helpful.
A few settings that have changed recently can be related to the time the 'outage' seems to last.

Do you always manually log in before every visit?
Aren't your log-in credentials saved so you don't have to log-in everytime?

An actual 'log in' is monitored more closely by the server and it will block an IP if it thinks there's a hacker at work. Unfortunatly the monitoring is very much needed as just about every server on the internet is constantly being probed by botnets to be hacked.
But I know the current system isn't working properly yet as I noticed the same issue on a different website on the same server.

I'm always logged in.