2 Replies Latest reply on Apr 19, 2010 7:59 PM by rshin

    HTTP Streaming errors after a few hours of recording

    uconnkoala

      I am publishing a 300/500/800kbps stream from FMLE 3.1 (RTMP) to FMS 3.8.

       

      For playout, I am using the OSMF Player and HTTP dynamic streaming.

       

      After a few hours of the stream being published, it becomes unplayable and freezes whenever you try to access it, and I get the following errors in my Apache logs:

       

      [Mon Apr 19 10:10:48 2010] [error] mod_f4fhttp [500]: Coretech error 72 when processing /live/bbcamerica/streams/bb

      camerica1Seg1-Frag13665

       

       

      Can anyone translate that error ?

       

      Is there additional debugging I can enable to get more log messages and traces?

        • 1. Re: HTTP Streaming errors after a few hours of recording
          uconnkoala Level 1

          I got a response back saying that there is a filesize limit of 2GB when using the mod_f4fhttp.so module in FMS 3.8.

           

          127.0.0.1 - - [19/Apr/2010:15:51:04 -0400] "GET /live/discoveryid/streams/discoveryid1Seg1-Frag1425 HTTP/1.1" 200 1

          296499 "http://192.168.105.103/demoapp-intranet/OSMFPlayer.swf" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) Ap

          pleWebKit/532.5 (KHTML, like Gecko) Chrome/4.1.249.1045 Safari/532.5"

          127.0.0.1 - - [19/Apr/2010:15:51:07 -0400] "GET /live/discoveryid/streams/discoveryid1.bootstrap?rand=1271706669703

          HTTP/1.1" 200 21211 "http://192.168.105.103/demoapp-intranet/OSMFPlayer.swf" "Mozilla/5.0 (Windows; U; Windows NT

          5.1; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.1.249.1045 Safari/532.5"

          127.0.0.1 - - [19/Apr/2010:15:51:07 -0400] "GET /live/discoveryid/streams/discoveryid1Seg1-Frag1426 HTTP/1.1" 500 6

          52 "http://192.168.105.103/demoapp-intranet/OSMFPlayer.swf" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleW

          ebKit/532.5 (KHTML, like Gecko) Chrome/4.1.249.1045 Safari/532.5"


          [Mon Apr 19 15:51:21 2010] [error] mod_f4fhttp [500]: Coretech error 72 when processing /live/discoveryid/streams/d

          iscoveryid1Seg1-Frag1428

           

           

          This will apparently be fixed in a build coming out later this month.

          • 2. Re: HTTP Streaming errors after a few hours of recording
            rshin Level 3

            Yes, that is correct.  There is a file size limit on the recorded file on FMS application side on Beta2.  The next version (RC) will also have an option to record your f4f file segmently.  Using <segementDuration> in your event.xml, you can split up your f4f file size by sec unit in your next release version.

             

            Thanks

             

            Ryan