So I have 60 second scans. 60 second timeout. Warn 4 before down. Sensor is HTTP. So you should always get down and notification at the 5 min mark.
If the server responds but does a 404 or 500 error everything works like it should. You see the issue every 1 min. It goes to warn and then down 5 mins later.
If the server is completely down and you timeout it doesn't really check every 1 min. More like every 3 mins. So it takes like 15 mins before you really go to down and get the alert.
In the logs you can see on each attempt it tries several times. Not sure why since it's once every 60 sec not 5 times.
Failed to establish secure connection [Step 0] Socket Error # 10060 Connection timed out. [Step 1] Socket Error # 10060 Connection timed out. [Step 2] Socket Error # 10060 Connection timed out. [Step 3] Socket Error # 10060 Connection timed out. [Step 4] Socket Error # 10060 Connection timed out. [Step 5] Socket Error # 10060 Connection timed out. [Unsecure] IOHandler value is not valid
Hi there,
Thank you for reaching out to us.
In order to analyze this further, we please need more information.
Please follow the steps below and send uns the files to support@paessler.com, please refer to the ticket "PAE986806":
- please recreate the issue with one sensor
- create a RAW Historic Data Export from this sensor - to do so, please navigate to the sensors "Historic Data" tab, choose "1 Day" as range and "No intervall / Display Raw Data" as Average Interval. Please send us the HTML file afterwards.
- a screenshot of the sensor's "Log" tab
- screenshot of "Setup | System Administration | Notifications" -> details of the Notification you are using
- screenshot of "Setup | Account Settings | Notification Contacts"
Thank you!
Best Regards
Andreas Günther
Jan, 2018 - Permalink