I have noticed with the "Piraside.log" generated by the Pira CZ Silence Detector software that following detection of Silence for the set period of time, the Pira Silence Detector appears to go about its set tasks
exactly as intended with all programmed actions taken (including sending emails) culminating with the problem being corrected. This is a Good Thing!
However, when I subsequently check the "Piraside.log" log file, I see a line which says "Alarm task queue broken".
As the Pira Silence Detector appears to be working as intended, I wonder what is the meaning of "Alarm task queue broken"? Or more particularly, what are the circumstances leading to the logging of that phrase? Is it possible that some error could be occurring that doesn't accord with the actual wording used in the report?
[As an aside, our wireless Studio to Transmitter Link is currently out of action so we are using an Internet Stream to feed our FM Transmitter. As we all know too well, the Internet is not 100% reliable, and every few days we experience a loss of Internet connection either at our Studio or at our Transmitter or even at our Stream Server provider, which results in "silence to air" for a period of time. When this happens, our Pira Silence Detector raises the alarm, and when possible, takes restorative action.]
