New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


What can I check if SNMP and SSH sensors throw timeout and auth errors?

Votes:

0

Your Vote:

Up

Down

In the past, our SNMP and SSH sensors have shown a down status sporadically, throwing timeout and authentication errors without any obvious reasons. Suddenly many sensor types using SNMP and SSH are down and show these errors. Now they do not turn up again. We did not change anything on the target systems like passwords or private keys. The credentials we defined in PRTG are still correct.

What can be the reason for these SNMP and SSH timeouts and auth errors? How can I avoid these SNMP and SSH sensor instabilities?

authentication error prtg sensor-instability snmp ssh timeout

Created on Mar 26, 2015 4:36:45 PM by  Gerald Schoch [Paessler Support]



1 Reply

Accepted Answer

Votes:

0

Your Vote:

Up

Down

This article applies to PRTG Network Monitor 14 or later

Sporadic Timeouts and Authentication Errors with SNMP and SSH Sensors

Connection instabilities with your SNMP sensors and SSH sensors so that they switch between the sensor states Up and Down from time to time, showing errors with timeouts and authentication, can be a result of the configuration of your monitored devices. If you are sure that credentials, passwords, private keys, etc. on the target devices remained unchanged all the time, check other connections that the affected servers might establish.

Look for configurations that devices have in common on which SNMP and SSH sensor are failing. For example, a customer reported that the devices on which the sensors showed the errors all sent syslogs to an external server. First, timeouts happened only sporadically. But after switching off this external server without disabling sending syslogs, the sensors were permanently in error status.

Turning off the syslog receiver server resulted also in strange behavior of other services on the sender servers. For example, some services needed a lot of time to spawn child services, which also affected SSH. Because this always happened when a new connection was created, it showed up as timeout or authentication error in PRTG.

Disabling syslogs sending to external servers resolved the timeout and auth issues of SNMP and SSH sensors in PRTG in this case. If you encounter such issues as well, keep in mind when investigating the errors that these can be potential side effects of applications like sending syslog messages from the monitored server.

Created on Mar 26, 2015 4:47:45 PM by  Gerald Schoch [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.