nDVR Chunklist 404 not found

Wowza Streaming Engine
1

Hello all!

I just upgraded my Wowza instance to 4.7.4 from 4.7.1 and suddenly the 24/7 live stream I have on our website no longer works. Chrome’s dev tools shows:

https://ssdcougars.tv/?page_id=261

Failed to load resource: the server responded with a status of 404 (Not Found)

https://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/chunklist_w1322350481_b2128000_DVR.m3u8

The stream IS working, when I use Test Players the various transcoded streams work fine. When I launch the Wowza Player wizard, the stream works fine there as well.

My JWPlayer does not.

Odd thing is, if I disable DVR the stream works again (albeit without the DVR ability)

Logs show only this at time of accessing stream: (Newest to Oldest)

I notice the URI listed in the log is http:// not https:// – the coding on my website is https:// so I don’t know if that is an issue?

2018-02-15
23:44:55 (EST)

connect
cupertino (200)

x-ctx: 1197919931,x-vhost: defaultVHost,x-app: live,x-appinst:definst,x-duration: 2043.735,s-ip: wowza.ssdcougars.tv,**s-port:**8443,**s-uri:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8?DVR,c-ip: XX.XX.XX.XX,c-proto: http (cupertino),c-referrer: https://ssdcougars.tv/?page_id=261,**c-user-agent:**Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36,c-client-id: 1197919931,cs-bytes: 0,sc-bytes: 0,x-spos: 0,x-sname: VGADVIstream_all,x-sname-query: DVR,**x-suri:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8?DVR,**x-suri-stem:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8,x-suri-query: DVR,**cs-uri-stem:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8,cs-uri-query: DVR

2018-02-15
23:41:39 (EST)

disconnect
cupertino (200)

x-ctx: 1322350481,x-vhost: defaultVHost,x-app: live,x-appinst:definst,x-duration: 1847.174,s-ip: wowza.ssdcougars.tv,**s-port:**8443,**s-uri:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8?DVR,c-ip: XX.XX.XX.XX,c-proto: http (cupertino),c-referrer: https://ssdcougars.tv/?page_id=261,**c-user-agent:**Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36,c-client-id: 1322350481,cs-bytes: 0,sc-bytes: 1155,x-spos: 0,x-sname: VGADVIstream_all,x-sname-query: DVR,**x-suri:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8?DVR,**x-suri-stem:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8,x-suri-query: DVR,**cs-uri-stem:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8,cs-uri-query: DVR

2018-02-15
23:41:39 (EST)

destroy
stream (200)

x-ctx: VGADVIstream_all,x-vhost: defaultVHost,x-app: live,x-appinst: definst,x-duration: 42.361,**s-ip:**wowza.ssdcougars.tv,s-port: 8443,**s-uri:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8?DVR,c-ip: XX.XX.XX.XX,c-proto: http (cupertino),c-referrer: https://ssdcougars.tv/?page_id=261,**c-user-agent:**Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36,c-client-id: 1322350481,cs-bytes: 0,sc-bytes: 1155,**x-stream-id:**28,x-spos: 0,cs-stream-bytes: 0,sc-stream-bytes: 0,**x-sname:**VGADVIstream_all,x-sname-query: DVR,**x-suri:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8?DVR,**x-suri-stem:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8,x-suri-query: DVR,**cs-uri-stem:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8,cs-uri-query: DVR

2018-02-15
23:41:05 (EST)

comment
server (200)

HTTPStreamerAdapterCupertinoStreamer.service: Request timeout: 8000

x-duration: 1813.233

2018-02-15
23:40:57 (EST)

create
stream (200)

x-ctx: VGADVIstream_all,x-vhost: defaultVHost,x-app: live,x-appinst: definst,x-duration: 0.004,s-ip: wowza.ssdcougars.tv,s-port: 8443,**s-uri:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8?DVR,c-ip: XX.XX.XX.XX,c-proto: http (cupertino),c-referrer: https://ssdcougars.tv/?page_id=261,**c-user-agent:**Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36,c-client-id: 1322350481,cs-bytes: 0,sc-bytes: 0,x-stream-id: 28,x-spos: 0,cs-stream-bytes: 0,sc-stream-bytes: 0,**x-sname:**VGADVIstream_all,x-sname-query: DVR,**x-suri:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8?DVR,**x-suri-stem:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8,x-suri-query: DVR,**cs-uri-stem:**http://wowza.ssdcougars.tv:8443/live/ngrp:VGADVIstream_all/playlist.m3u8,cs-uri-query: DVR

2

Hello,

Thanks for contacting the Wowza Community.

I see you already have a ticket open regarding this issue and it will be handled there.

regards,
Jermaine

3

I have the same problem with 4.7.4. We have to uninstall last version and go back to 4.7.3. It is working without problems with 4.7.3. Probably some error with last version.

4

Add me to the list. Rollback to 4.7.3.01 fixed it.

5

same problem here! did anyone get it working???

7

removing “?DVR” from the stream url allows the stream to work. obviously disabling dvr functionality for the end user.

8

I am also wondering if it is being caused by JWPlayer itself. JWPlayer just released vs. 8.1.10 that says in the changelog:

  • “Fixed an issue where autostarting JW Live streams that return a 404 did not display the fatal error after setting up, resulting in a blank screen.”

It’s absolutely related to the combination of transcoding/transrating with DVR. If the DVR is turned off, then the issue disappears, or at least that is the only solution that worked for me. Other forums state that the smil file is incorrect. I don’t know what the answer is.

I don’t want to reinstall 4.7.4 and test the new version of JWPlayer 8.1.10 as I only have a production server. Anyone else?

9

I can verify that it is not only a JWPlayer compatability issue as we use Wowza player.

10

Official response from wowza support…

"Thank you for contacting Wowza support.

We are actively working on a fix for this and will keep you informed of any progress. Thanks for your patience in this matter.

Note that one workaround for now is to only provide DVR playback of a single stream (i.e. don’t prefix the stream with ngrp: and just reference the stream or one of the transcoded streams in your playback URL). I understand this isn’t ideal but it should provide you with a working stream while we continue to investigate and resolve this issue."

So, with this update, you can pick DVR or MBR streaming. You can’t have both!

My fix was to uninstall 4.7.4 (going back to 4.7.1).

I think it’s crazy that they still even offer such a broken “update” knowing that it is flawed.

11

Do we all need to open tickets?

12

I think that’s a crazy answer to remove functionality in order to make an update work.

13

Hello,

Thanks for the +1s.

This is a known issue and we are actively working on this. No timeline on resolution, but be on the look out for an update that will resolve this:
https://www.wowza.com/docs/wowza-streaming-engine-software-updates

Once it is released, I will also update this thread.

regards,
Jermaine

14

Actively working on ? Why no update for over 11 days… I will say that this is a major bug…

15

my update… wowza sent me patched update to fix the issue (via support ticket). It actually made things worse! MBR streaming didn’t work at all. So once again, I’m back at 4.7.1.

16

4.7.5 is out - Anyone tested if this still is a problem ?

17

I have not tried 4.7.5 yet and I’m also interested if it fixed this issue for anyone else. I really do not want to be Wowza’s guinea pig!

18

Hi,

Has this been fixed in 4.7.8?

19

This appears to be an alignment issue with the adaptive bitrate streams. When too far out of alignment, nDVR fails to find the correct chunk resulting in the 404 messages seen. As stated in this thread, this does not occur with single bitrate streams and does not occur with adaptive bitrate streams that are not using the nDVR functionality. Adding the following Properties has helped for some customers experiencing this problem.

Path: /Root/Application/DVR

Name: dvrMbrMinimumPacketTimeGapSize

Value: [SameAsChunkDurationForNDVR]

Type: Integer

Path: /Root/Application/DVR

Name: dvrMbrMinimumUtcTimeGapSize

Value: [SameAsChunkDurationForNDVR]

Type: Integer

If you have not edited the nDVR chunk duration, the value can be set as 2000 (milliseconds) for both properties.

If your issue continues, it’s strongly recommended that you open a support ticket as differences to your configuration may change the advice provided.