Portal Home > Knowledgebase > Articles Database > Pingdom sending timeout
Pingdom sending timeout
| Posted by kshazad86, 04-27-2011, 01:49 PM |
| I'm monitoring my server using Pingdoms monitoring tool, and recently I've been getting a downtime message, caused by timeout. The problem is that I cant figure out what caused the downtime message.
The downtime lasts only 5 minutes, and then I can access the server again. Can anyone help?
|
| Posted by kshazad86, 04-27-2011, 02:47 PM |
| What do you mean server problem? can you be more specific...
Note: If I restart named, then it starts working fine...but Pingdom regularly reports timeout errors.
|
| Posted by asciiDigital, 04-27-2011, 03:51 PM |
| You can start by checking the named log file for any error messages:
/var/log/named.log
|
| Posted by kshazad86, 04-27-2011, 03:52 PM |
| I tried that but I cant find the file, named.log doesn't exist in the log folder.
|
| Posted by asciiDigital, 04-27-2011, 04:05 PM |
| Run this
or
|
| Posted by kshazad86, 04-27-2011, 04:06 PM |
| This is the response:
|
| Posted by asciiDigital, 04-27-2011, 04:08 PM |
| What about the locate command? There is no named.log file?
|
| Posted by kshazad86, 04-27-2011, 04:17 PM |
| Yea, it doesn't return anything.
|
| Posted by asciiDigital, 04-27-2011, 04:30 PM |
| You may need to enable DNS logging. Run this command and tell me what it returns:
This is the command to turn on or off logging. If it was already on you will need to run it again. You can then check /var/log/messages for DNS errors.
|
| Posted by kshazad86, 04-28-2011, 04:06 AM |
| I've added the rndc query like you mentioned, and the named process is now appearing in /var/log/messages
How do I know for particular that it was named? What causes timeout error messages on a server when the load is completely fine?
|
| Posted by ibee, 04-28-2011, 06:29 AM |
| sometimes if any obstacle on the route pingdom is reaching to the server having problem also, it will show that the server is down. This kind of monitoring is not accurate i assume.
|
| Posted by kshazad86, 04-28-2011, 06:31 AM |
| But surely, I would have thought that Pingdom use and check on several servers before they send you a warning email?
The pingdom tool monitors my site every minute. Is this too much?
|
| Posted by uptimedoctor, 04-28-2011, 07:09 AM |
| To the OP, you should check Pingdom detailed log to determine the locations that confirmed the outage, and the EXACT error message logged.
"timeout" alone sounds very vague. The detailed log should show you the full error message, and you will know whether it was DNS related. If it was a connection timeout or response timeout, then there is no point in looking at named's log. A connection or response timeout could be caused by the server or the network. In the latter case, your server log will not show anything unusual, but you can check your MRTG to see if there was a reduction in traffic during the reported outage.
It depends on your intention of using an off-site monitoring service like Pingdom. Such a service monitors from outside your DC and can detect network issues. This is useful to many administrators. If you do not want to know about network issues, you should use a local solution (eg. Nagios).
|
| Posted by kshazad86, 04-28-2011, 07:16 AM |
| Yes, I checked the Pingdom detailed log, but they reveal that Resolve IP and traceroute were fine but an error was received on "Get Content" and it shows the analysis was performed from Las Vegas, and Copenhagen, Denmark.
Note: The servers are in the UK
|
| Posted by uptimedoctor, 04-28-2011, 07:42 AM |
| A timeout during the "Get Content" phase means that the monitoring locations were able to send HTTP request to the web server but did not receive a response after waiting for 30 sec (therefore a timeout).
High server load, or a problem with your web server (Apache?) can lead to timeouts. The problem can also be caused by network (although less likely). You should check /var/log/messages and your web server access and error logs.
|
| Posted by speckl, 04-28-2011, 08:56 AM |
| I got the same message recently and then remembered an email from them about a month ago that they were adding about 10 more servers.
You probably need to add the ips to your firewall allow config file. There is a list of all the ips on the pingdom website.
|
| Posted by kshazad86, 04-28-2011, 01:11 PM |
| I can't find their IP list...have you got a direct link?
|
| Posted by speckl, 04-28-2011, 01:21 PM |
| Login to the control panel and click on the link at the bottom of the left menu.
http://awesomescreenshot.com/0eec4k959
|
| Posted by kshazad86, 04-28-2011, 01:34 PM |
| Thanks, I will add this to the firewall...
One thing I did notice jsut now is that the firewall was not isntalled at the time the timeout happened, but I'll add the IP's to the allow list anyway.
Another thing.. I just checked the apache error logs and precisely at the time I had the timeout, the following error message is written hundreds of time in the log file:
I then tried to vist the link mentioned in the above error, and it is hosted on my servers..the server just jung like hell...had to restart apache to get it back online again
Any ideas what this is?
Last edited by kshazad86; 04-28-2011 at 01:40 PM.
|
Add to Favourites 
Print this Article
Also Read
Shared Hosting
Shared Hosting
