What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Port sensor down and not notifying when message is (connection timed out (socket error # 10060)

Votes:

0

I have set a port sensor properly with command sending and timeout (20s). I also had set a notification for when sensor is down send email to a group. The problem is: When the sensor is down and the message is (connection timed out (socket error # 10060), PRTG not notify.

connection-timed-out--socket-error-#-100 port-sensor-down-and-not-notifying port-sensor-notification

Created on Oct 16, 2017 11:55:30 AM



3 Replies

Votes:

0

Hello there,

In this case it would be interesting to see tabs "Overview", "Logs" and "Notifications" of the related sensor to see what the issue might be. You can also send it to us by email:

Thank you & kind regards,

Erhard

Created on Oct 17, 2017 10:47:47 AM by  Erhard Mikulik [Paessler Support]



Votes:

0

Hi Erahard.

Thank you for the assistance. The notificatioon is working pretty well after change notification settings to trigger "when sensor state is Down for at least 0 seconds" instead 1, 5 or N seconds.

Created on Oct 23, 2017 4:51:37 PM



Votes:

0

Hello Vitor,

You're welcome.

For anyone else interested in what happened: When configuring notification triggers like "When sensor is down for x seconds...", make sure that "x" is either a multiple of the scanning interval or set it otherwise to 0 seconds instead. Otherwise the thread responsible for sending notifications might run into issues not triggering as it should. So basically let's say you scan every 60 seconds with a sensor, there is no reason to set a trigger like "When sensor is down for 5 seconds....", set it to "When sensor is down for 0 seconds....." instead or as mentioned before use multiples of the scanning interval (60/120/180/.....).

Kind regards,

Erhard

Created on Oct 24, 2017 8:22:14 AM by  Erhard Mikulik [Paessler Support]




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.