PRTG not working after upgrade to the 114.2.10.2114

Modified on 2025-06-10 13:45:56 +0200

I had stable 600 SNMP sensors setup until i run upgrade to 14.2.10.2114. Right after the upgrade my sensors started going "down" with errors Error opening snmp session: Unknown host (x.x.x.x:161) (Bad file descriptor) (SNMP error # -2006). Then they randomly come back up and go down again. Operations, like Pause/Resume are slow, take good 10-15 minuted to start a sensor. Does anybody else have this issue with new version? To normalize the setup i had to move scanning to 60 minutes, but as i said, this is defiantly related to software upgrade.

Thanks, Sergiy CCIE #28978

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Please forward us your query as a support ticket to support@paessler.com. Please provide a full support bundle, as outlined under Contacting support.

May, 2014 - Permalink

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.

PRTG not working after upgrade to the 114.2.10.2114

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.