|
|
|
|
|
|
|
|
|||||||
![]() |
|
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
|
#1 |
|
Are you sure you're an accredited and honored pornographer?
Join Date: Sep 2008
Posts: 67
|
Seems almost too obvious to mention but it hasn't come up yet ...
The web server logs may be useful in tracking this down. Access logs should tell you whether the user is getting through. That may help distinguish a firewall block from a flaky connection. It might also help you tell how many connections are being opened - a bit less sure there. There might also be some kind of error in the error logs - worth a look I guess. fg |
|
|
|
|
|
#2 |
|
Get me!
|
This may sound silly, but find out from your hosting company when the last time your server had a reboot.
I was having a similar issue not too long ago, where I couldn't even connect to my own sites. Seems it had been way too long since the last reboot. After they forced a manual reboot, I'm fly fine now. |
|
|
|
|
|
#3 | |
|
Rock stars ... is there anything they don't know?
Join Date: Apr 2008
Posts: 10
|
Quote:
Just had a harddrive upgrade. Cathy xxx |
|
|
|
|
|
|
#4 | |
|
The only guys who wear Hawaiian shirts are gay guys and big fat party animals
|
Quote:
it will eventually come back, and now that the problem is temporarily gone, it's virtually impossible to diagnose. Personally, I'd much rather diagnose and fix a problem than wait until a user bothers to email me about it and then reboot and hope it takes a while before it happens again. Servers, running network operating systems, should never need a reboot, except when certain hardware has to be removed. We've had web servers running years without a reboot. Hard drives and even PCI cards can be changed out while the system runs. |
|
|
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|