We've been using Silence Detector successfully at our community radio station for many many months. I initially set it up to send an email when silence was detected, and it has been doing that reliable.
Until now. I've added a second Alarm Task to perform if it detects silence: Issue a DOC command to reboot a computer on the network, THEN and send the alert email.
The tasks are in that order.
The first task completes successfully -- Silence Detector reboots the "trouble" computer.
But the emails aren't going out -- the second task.
Once the stream goes back up, the Return Task "Stream Detected" email goes out, and from the Alarm Tasks panel, the Test button works, too, so there's nothing wrong with Silence Detector's emails settings.
And once the trouble computer boots back up, the Return Task "Stream Detected" email goes out
I enabled the logfile, and it reports simply that there was an error sending the email.
Example:
2015-06-27 20:16:26; Pira CZ Silence Detector v. 1.3a starting up...
2015-06-30 08:47:55; Alarm activated (silent channel(s): Left and Right)
2015-06-30 08:48:05; An error occured when trying to send email: Connect timed out.
2015-06-30 08:52:15; Returned from alarm condition
2015-07-02 09:19:34; Alarm activated (silent channel(s): Left and Right)
2015-07-02 09:19:46; An error occured when trying to send email: Socket Error # 11004
2015-07-02 09:28:00; Returned from alarm condition
I reckon I will reverse the order of tasks: send email THEN issue reboot. Will advise.
