Hello. I have set up a FTP Server File Count sensor to check accessibility of FTP service. Now the server was not accessible for a few hours and the sensor started flooding my mailbox with notifications. Checking the sensors log I found following:
1/31/2013 10:14:49 AM FTP Server File Count Down Timeout caused by wait for mutex (code: PE035) 1/31/2013 10:10:00 AM FTP Server File Count Notification Info State Trigger activated (Trigger ID: 4294970171) 1/31/2013 10:10:00 AM FTP Server File Count Unknown No data since 1/31/2013 9:59:49 AM 1/31/2013 10:01:00 AM FTP Server File Count Notification Info State Trigger activated (Trigger ID: 4294970171) 1/31/2013 9:59:49 AM FTP Server File Count Down Timeout caused by wait for mutex (code: PE035) 1/31/2013 9:55:00 AM FTP Server File Count Notification Info State Trigger activated (Trigger ID: 4294970171) 1/31/2013 9:55:00 AM FTP Server File Count Unknown No data since 1/31/2013 9:44:49 AM 1/31/2013 9:46:00 AM FTP Server File Count Notification Info State Trigger activated (Trigger ID: 4294970171) 1/31/2013 9:44:49 AM FTP Server File Count Down Timeout caused by wait for mutex (code: PE035)
The sensor was switching between "Unknown No data since" and "Down Timeout PE015" status.
Is this behavior a bug in the sensors code or is this 'by design'? If it is 'by design' how may I avoid triggering many notifications?
Thanks a lot in advance for your reply thomas gottfried
Add comment