Skip navigation
breslev
Currently Being Moderated

After update to FMS 4.5.2 HLS live streaming stoped working

Apr 18, 2012 2:56 AM

log file: "GET /hls-live/livepkgrRadio/_definst_/liveevent/livestream1_audio_only.m3 u8 HTTP/1.1" 404 353 "-" "AppleCoreMedia/1.0.0.9A405 (iPhone; U; CPU OS 5_0_1 like Mac OS X; he_il)"

 
Replies
  • Currently Being Moderated
    Apr 18, 2012 4:02 AM   in reply to breslev

    Few queries from my side, before diving more into your issue:

    • What was your last version which you have updated to FMS4.5.2
    • What platform are you using?
    • Was it working earlier and update to FMS4.5.2 made it stopped?
    • If you changethe URL to ......./hds-live/livepkgrRadio/_definst_/liveevent/livestream1_audio_ only.f4m , then in that case can you verify that HDS streaming is happening?
    • I dont understand why your url has a space between "m3' and 'u8", is it hand-written or directly copied from log file?

     

    Regards,

    Shiraz Anwar

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 18, 2012 4:29 AM   in reply to breslev
    • Can you make sure your event.xml and manifest.xml are confgured properly? Sometimes, if streamname is not registered in Manifest.xml, we run into issues.
    • Also make sure that there are no *.stream file inside ..\applications\livepkgr\events\_definst_\liveevent folder.
    • Also, when doing a FMS restart please cleanup the streams folder inside ..\applications\livepkgr\

    You may try these options if everything is configured correctly then you should be able to fetch m3u8 file.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 18, 2012 5:16 AM   in reply to breslev

    Few more queries:

    • Please provide the error logs details.
    • What metod have you used to upgrade from FMS4.5.1 to FMS4.5.2
    • Are you publishing Audio only stream, or using MBR feature to access the audio only stream?
    • Are you using FMLE to publish on livepkgr?
    • Hopefully you are using AAC audio codec only.
     
    |
    Mark as:
  • Currently Being Moderated
    May 1, 2012 9:56 AM   in reply to breslev

    I am also having this issue.  Version jump from 4.5.0 r 297  

     

    I have followed all the steps as suggested earlier, removed the manifest file, etc.  ver 4.5.0 HLS works  4.5.2. on iPad and iPhone "The operation could not be completed"  similar to an issue if the .m3u8 is improperly configured.  I know they aren't improperly configured as they function flawlessly on version 4.5.0 

     

    Something is missing or has been changed with this new version and there is no documentation to support it........

     
    |
    Mark as:
  • Currently Being Moderated
    May 2, 2012 9:57 AM   in reply to iGoez

    I am also having the exact same problem. Without the Manifest.xml in the event folder, requesting the m3u8 for the stream results in a 404 message.

     

    Using CentOS 5 and FMS 4.5.2.

     

    Everything works without the Manifest.xml in FMS 4.5.1 with the same stream configuration.

     
    |
    Mark as:
  • Currently Being Moderated
    May 2, 2012 10:27 AM   in reply to dbsn

    Hey guys,

     

    This is a known issue with FMS 4.5.2. If you request m3u8 from the server and no Manifest.xml is available for that particular event, you may land into errors.

    Please make sure you create a copy of manifest.xml for the event you are using and place it inside application/livepkgr/event/_definst_/<your-event-name>/ directory. 

     

    We are tracking this issue and it will be fixed in the new updated version of FMS which will be released soon.

     

    Regards.

     
    |
    Mark as:
  • Currently Being Moderated
    May 2, 2012 11:34 AM   in reply to Apoorva Arora

    So the Manifest.xml file _DOES_ need to be in place.

     

    I'm assuming that file should be edited so that the bitrates match what you've entered into the set-level manifest files, as well as what you're streaming out from the FMLE, correct?

     
    |
    Mark as:
  • Currently Being Moderated
    May 10, 2012 12:13 PM   in reply to breslev

    It probably does need to be set to the same levels because it doesn't work for us with the original manifest. I will report our findings once we test with the edited manifest

     

     

     

    For the record I am also using CentOS 6.2

     
    |
    Mark as:
  • Currently Being Moderated
    May 2, 2012 10:51 PM   in reply to mrwizzer2

    It is a good practice to keep the bitrates in manifest.xml same as the ones with which you are publishing from FMLE. However, this itself will not cause any problems if the bitrates do not match.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points