Results 1 to 2 of 2

Thread: LiveStreamRecord Module - Recording randomly stops

  1. #1

    Default LiveStreamRecord Module - Recording randomly stops

    Hi There,

    I have an XL CPU 64 Bit instance running on AWS EC2 w/ Lickey Licensing.... I'm transcoding usually 6 Streams using the transcoder Add on... I'm also using the LiveStreamRecord Module and HTTP commands via a cron job to start and stop .MP4 recordings which are saving the content into folders created in the [WowzaInstal]/content folder. Each record session is setup for 2 hours at a time at either 1280x720 Res, 2Mbps BR and 12 or 15FPS or 1024x576, 1.5Mbps BR and 15 or 12 FPS. This instance (Northern CA) which I call Transcoder1 is pulling the streams directly from Sony SNC H.264 Network cams located in China and Denmark. Transcoder1 is setup to transcode the source stream to 640x360 (_360p) and 942x530 (_942p). The HTTP command triggers the LiveStreamRecord Module to record the _source stream which is setup to simply pass through the H.264. The _360p and _530p streams are pulled from Transcoder1 by another instance called origin1 which is also running the loadbalancer sender... 10+ Edge servers pull the streams from origin1 and that is working great.

    Now my problem... Unfortunately, I am seeing the recording just stop at random times. In Denmark, we are pulling two streams. It seems that one stream is more stable and records longer than the other before just stopping.

    I'm seeing entries like the following in the error log:

    WARN server comment 2012-03-23 13:45:01 - - - - - 319265.159 - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear1_source
    WARN server comment 2012-03-23 14:00:01 - - - - - 320164.614 - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear1_942p

    WARN server comment 2012-03-24 13:45:01 - - - - - 405664.921 - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear1_source
    WARN server comment 2012-03-24 14:00:01 - - - - - 406564.892 - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear1_942p

    WARN server comment 2012-03-24 13:45:01 - - - - - 405665.124 - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear2_source
    WARN server comment 2012-03-24 14:00:01 - - - - - 406565.124 - - - ModuleStreamRecord.stopRecording: stream recorder not found: exp-d-bear2_942p


    I can send you the full log file if you like.... Any assistance or direction you can point me in would be appreciated.

    Thanks,

    Tim

  2. #2

    Default

    Do the logs indicate anything out of the ordinary? Is it possible that the source cameras are experiencing connectivity events that make the Wowza server think the stream has ended, thereby causing it to close off the recorded file?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •