Hello,

I have a rather starnge issue with one of my physical servers and PRTG. In PRTG, I'm getting SNMP error #2, but the sensors were working fine a couple of days ago.

There has been no change to either PRTG og the server it self. Does anyone have any idea how I can get rid of this error, so the sensors can show normal again?

I've tried:

  • stop/start sensors
  • Pause/unpause sensors
  • stop/start IBM Director services + SNMP service
  • Reconfigured the SNMP service
  • Rebooted the server
  • Tried re-adding the sensors (I can't, because PRTG reports error #2)

Check this screenshot. Please notice that 4 of my hardware sensors are working, but only sensors associated with DISK are not working.

http://i.imgur.com/DzbDunk.png

Article Comments

If you add the sensors anew, without deleting the existing ones, do the newly added sensors return values?


Feb, 2014 - Permalink

Hello,

thanks for getting back to me.

I tried adding the sensors without deleting the existing ones:

http://i.imgur.com/tTKcBCN.png

I still haven't deleted the existing ones.


Feb, 2014 - Permalink

Please forward us an email to support@paessler.com, refering to this thread, and I will send you individual troubleshooting guidelines.


Feb, 2014 - Permalink

i have the same problem, sometimes it works to restart the snmp serivce on the server. than it works some minutes or hours, but it will crashs again and again and again, what was the reason?


Mar, 2014 - Permalink

Same problem here with the IBM System X Sensors. Is it possible to tell us a general solution?


May, 2014 - Permalink

I'm afraid there simply is no general solution to this. What exact sensors are you referring to? Does re-adding the sensors help?


May, 2014 - Permalink

Hello,

Kind of late reply. :)

However, we are still experiencing this error on random servers. We use PRTG for our customers, and each customer has one remote probe installed.

We do have a temporary fix for this issue, but it gets a bit tiring after a while, and our SysAdmins would like a proper fix for this.

The "No Such Name (SNMP error # 2)" error is temporary fixed by either restarting the server (cannot be done 99 out of 100 times) or restarting the IBM Director Services AND the Windows SNMP service.

Some of the other SNMP Errors are temporary fixed by pausing and resuming the actual sensors in PRTG.


Apr, 2015 - Permalink

If restarting the target machines does help, it indicates that they lose their SNMP connectivity, and thus break the monitoring on target side. Please then consult with the vendor(s) of the devices.


Apr, 2015 - Permalink