Results 1 to 6 of 6

Thread: Faulty wowza manifest/chuncklists

  1. #1
    Join Date
    Jul 2012
    Posts
    9

    Default Faulty wowza manifest/chuncklists

    Hi,

    I have a setup where i use a wowza as an origin and varnish as egde.
    I stream an RTMP to the inpoint server and take out HDS/HLS on the edge servers.

    Everything works like a charm and i can view it on tablets, smartphones etc buuuuuuuuuuut it crashes after 1s-3min. I discovered it generate the wrong manifests and chuncklists at random times and that what makes it crash, since it doesnt know what the next 3 .ts files is named.

    Here is an exampel:

    CORRECT:

    curl -i "http://myserver.dk/tv_live1/live/manifest.f4m"
    HTTP/1.1 200 OK
    Content-Type: text/xml
    Server: FlashCom/3.5.7
    Cache-Control: max-age=1
    X-Cacheable: NO:Not Cacheable - HTTP DYNAMIC MANIFEST
    Content-Length: 908
    Accept-Ranges: bytes
    Date: Thu, 18 Apr 2013 07:30:22 GMT
    X-Varnish: 355222798
    Age: 0
    Via: 1.1 varnish
    Connection: keep-alive
    X-Cache: MISS

    <?xml version="1.0" encoding="utf-8"?>
    <manifest xmlns="http://ns.adobe.com/f4m/1.0">
    <id>live</id>
    <width>640</width>
    <height>480</height>
    <mimeType>video/mp4</mimeType>
    <streamType>live</streamType>
    <deliveryType>streaming</deliveryType>
    <media width="640" height="480" bitrate="841" url="media_b861961.abst/">
    <metadata>AgAKb25NZXRhRGF0YQMABmF1dGhvcgIAAAAJY29weXJpZ2h0AgAAAAtkZXNjcmlwdGlvbgIAAAAIa2V5d29yZHMCAA AABnJhdGluZwIAAAAFdGl0bGUCAAAACnByZXNldG5hbWUCAAZDdXN0b20ADGNyZWF0aW9uZGF0ZQIAGVRodSBBcHIgMTggMDk6Mj U6NTAgMjAxMwoAC3ZpZGVvZGV2aWNlAgARSW50ZWdyYXRlZCBXZWJjYW0ACWZyYW1lcmF0ZQBAOQAAAAAAAAAFd2lkdGgAQIQAAA AAAAAABmhlaWdodABAfgAAAAAAAAAMdmlkZW9jb2RlY2lkAgAEYXZjMQANdmlkZW9kYXRhcmF0ZQBAiQAAAAAAAAAIYXZjbGV2ZW wAQD8AAAAAAAAACmF2Y3Byb2ZpbGUAQFCAAAAAAAAAF3ZpZGVva2V5ZnJhbWVfZnJlcXVlbmN5AEAQAAAAAAAAAAAJ</metadata>
    </media>
    <bootstrapInfo profile="named" url="playlist_b861961.abst"/>
    </manifest>


    WRONG:
    curl -i "http://myserver.dk/tv_live1/live/manifest.f4m"
    HTTP/1.1 200 OK
    Content-Type: application/x-fcs
    Server: FlashCom/3.5.7
    Cache-Control: no-cache
    X-Cacheable: NO:Not Cacheable - HTTP DYNAMIC MANIFEST
    Content-Length: 11
    Accept-Ranges: bytes
    Date: Thu, 18 Apr 2013 07:30:42 GMT
    X-Varnish: 2205696223
    Age: 0
    Via: 1.1 varnish
    Connection: keep-alive
    X-Cache: MISS

    1378109815



    And the same goes for the chunklist:

    CORRECT:

    curl -i "http://myserver.dk/tv_live1/live/chunklist.m3u8"
    HTTP/1.1 200 OK
    Content-Type: application/vnd.apple.mpegurl
    Server: FlashCom/3.5.7
    Cache-Control: max-age=1
    X-Cacheable: NO:Not Cacheable - HTTP DYNAMIC MANIFEST
    Content-Length: 188
    Accept-Ranges: bytes
    Date: Thu, 18 Apr 2013 07:40:00 GMT
    X-Varnish: 355627671
    Age: 0
    Via: 1.1 varnish
    Connection: keep-alive
    X-Cache: MISS

    #EXTM3U
    #EXT-X-VERSION:3
    #EXT-X-ALLOW-CACHE:NO
    #EXT-X-TARGETDURATION:42
    #EXT-X-MEDIA-SEQUENCE:6574
    #EXTINF:10.879,
    media_6574.ts
    #EXTINF:7.279,
    media_6575.ts
    #EXTINF:10.959,
    media_6576.ts


    WRONG:

    curl -i "http://myserver.dk/tv_live1/live/chunklist.m3u8"
    HTTP/1.1 200 OK
    Content-Type: application/x-fcs
    Server: FlashCom/3.5.7
    Cache-Control: no-cache
    X-Cacheable: NO:Not Cacheable - HTTP DYNAMIC MANIFEST
    Content-Length: 11
    Accept-Ranges: bytes
    Date: Thu, 18 Apr 2013 07:39:57 GMT
    X-Varnish: 2206067485
    Age: 0
    Via: 1.1 varnish
    Connection: keep-alive
    X-Cache: MISS

    1471303483


    Can anyone tell me why it does generate these faulty manifetes, and what that random number sequeance is?
    Most importantly, how do i fix this?

  2. #2
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    How are you using Varnish? I would try taking that out, it might not to be handling the manifest correctly.

    Richard

  3. #3
    Join Date
    Jul 2012
    Posts
    9

    Default

    Hi Richard,

    Thank your for the feedback.
    I've already tried without varnish, and i cant reproduce the error without it.

    However the file isnt cached and as you see it is fetched everytime from the wowza server, so why how come some of the manifest are faulty?

    Most of the time i see the stream on my phone, i see it calls the chucklist and gets the next 3 chucks. At some point the chucklist replies without any .ts files but withthat random number and then dies.

  4. #4
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Evidently the acceleration features of Varnish do not treat the manifest properly. I'm sure there is not a way to fix that in Wowza, which produces a correct manifest. Maybe Varnish is not appropriate because of the way it works, or it is a bug in Varnish.

    Richard

  5. #5
    Join Date
    Jul 2012
    Posts
    9

    Default

    Yeah, i see...

    But if i do the HLS with IIS Smoothstreaming servers as origin and varnish as egde, we have no problems at all?
    I do not want to say its anybodys fault, i just want to find a solution

  6. #6
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    No fault, it's just a matter of who is handling what. Wowza delivers a full manifest to some interface and it comes out differently on the other end. So that is where to look. All Wowza can do is deliver a proper manifest, it can't affect the processes of the application that consumes it. I suspect that this is a result of how Varnish affects acceleration, i.e., by design. Or it is a bug. They would have to determine. All I know about Varnish is scanning that Wikipedia article.

    Richard

Similar Threads

  1. HDS manifest
    By brayster99 in forum General Forum
    Replies: 5
    Last Post: 12-19-2013, 01:26 PM
  2. vod hds manifest
    By pidboretskyy in forum Video On Demand Streaming Discussion
    Replies: 1
    Last Post: 04-17-2013, 08:02 AM
  3. Replies: 3
    Last Post: 11-20-2011, 06:33 AM

Posting Permissions

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