Monitored stream goes dark but no email sent

[Dave Labrecque]

This only seems to happen in the middle of the night. I'll log in in the morning and notice that the player I use to create the audio for the Silence Detector to monitor has stopped playing, but I've received no email from the Pira app, which is sitting there with no meter deflection.

When I test it, either with the test button or by actually interrupting the input to Pira, it works fine.

Any ideas?

[Jan]

You can track the events in the SD log file. The log must be enabled first.

[Dave Labrecque]

Yeah, I just turned on the log feature. I guess I'll see if it reveals anything. Thanks. More when I know more...

[Dave Labrecque]

"2014-06-02 08:43:28; An error occured when trying to send email: Socket Error # 11004"

That's what the log says when this happens.

Can anyone tell me what this means? Is there a list of error codes somewhere? Any idea what may cause this failure?

Thanks.

[Jan]

OK, so the silence is detected but the email cannot be sent due to a network problem. The reason is outside the SD.

There is some useful information that can be found by google https://www.google.com/search?q=Socket+Error+11004

It seems you can solve the issue if you type the smtp server in IP address form (xxx.xxx.xxx.xxx) rather than host name form. You may try other smtp server as well because your existing smtp server may be out of service during the night. Also check your firewall/antivirus settings.

[Dave Labrecque]

Super. Thanks so much for the info (and legwork?). Very much appreciated.

I've changed the smtp server name to the ip address. The test emails work, so we'll see if that circumnavigates the sporadic mail sending problem. If not, I'll try changing to a different smtp server as you suggest.

Again, many thanks for your help. 

[Dave Labrecque]

Well, I guess I've figured out the problem. Duh.

My monitoring configuration has some limitations. That's because I'm using the computer that's uploading the stream to a streaming server as the stream playback platform and a second computer (on the same LAN) to run the Pira monitor app (with an audio cable between them). So -- when the local Internet goes down or has some kind of hiccup, yes, the stream stops and, yes, the alarm 'sounds', but an alert email can't get out -- because the Internet is down. 

I guess the way to do this properly is to have an off-site computer(s) handle the stream monitoring. Lesson learned.

[Jan]

A bit funny story But yes, it's an interesting experience, it gives a sense and it would be helpful for others...