Page 1 of 3
zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Mon Jun 06, 2022 6:41 pm
by hotelmode
Code: Select all
{
"Date/Time": "2022-06-06 14:20:59",
"Component": "zmc_m3",
"Server": "",
"PID": 41976,
"Level": "WAR",
"Message": "pkt.dts(46738350) must be",
"File": "zm_videostore.cpp",
"Line": 1343
},
{
"Date/Time": "2022-06-06 14:20:59",
"Component": "zmc_m3",
"Server": "",
"PID": 41976,
"Level": "WAR",
"Message": "non increasing dts, fixing. our dts 46738260 stream 0 last_dts 46738350",
"File": "zm_videostore.cpp",
"Line": 1332
}
The error happens pretty regularly. I believe I had the same type of error message on 1.36.17, but it's still there after upgrading to 1.36.18.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Mon Jun 06, 2022 6:56 pm
by Magic919
Sounds like a camera problem.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Mon Jun 06, 2022 7:17 pm
by iconnor
It's a predictive frame problem. If your came is sending a high profile stream, or h265, then ffmpeg will return out of order packets. Problem is, when writing they have to be in-order. So we have to sort them. I've tried a couple of approaches that didn't work. Havn't had time to try again. Not sure how many packets I need to queue in order to ensure I can sort them.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Mon Jun 06, 2022 7:35 pm
by hotelmode
Both cameras are H.264, with one of them being H.264H. I've rebooted both cameras and switched the H.264H cam to H.264 to see if that helps. Thanks.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Tue Jun 07, 2022 2:24 am
by hotelmode
I narrowed it down to my 4MP camera. I changed it from H.264H to H.264, and decreased the quality from 6 to 5. I also tried switching to H.264B. Same error keeps popping up no matter what I do. Oh well.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Tue Jun 07, 2022 3:45 pm
by citrusvatten
So I also have this problem, and it might be worthwhile to add what I've found out so far. I'm running two streams from one camera, one high res (that does not get decoded) and one low res (that is decoded). I have the high res stream in Nodect and low res in Mocord. I only get this warning on the cameras that are on low resolution and thus running Mocord:
Code: Select all
Date/Time Component PID Level Message File Line
2022-06-07 17:38:56 zmc_m4 17619 WAR pkt.dts(50625767) must be zm_videostore.cpp 1343
2022-06-07 17:38:56 zmc_m4 17619 WAR non increasing dts, fixing. our dts 50604891 stream 0 last_dts 50625767 zm_videostore.cpp 1332
If I change the mode on the camera to Monitor or even Modect the warning disappears. I have tried to restart the cameras and the server but the same error comes up. I'm currently on 1.36.19, but it appeared on 1.36.17 but not on 1.36.12 or 13, which I used before upgrading a few days ago.
There is no apparent problem, it's just that it clutters the logs that are annoying, so everything works fine.
EDIT: It turns out that when there is an alarm the same warning comes up for the high res cams, which is understandable as it isn't decoded all the time.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Tue Jun 07, 2022 4:26 pm
by Magic919
Might be worth trying a shorter key frame interval.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Thu Jun 09, 2022 11:01 pm
by hotelmode
Magic919 wrote: ↑Tue Jun 07, 2022 4:26 pm
Might be worth trying a shorter key frame interval.
My cameras are set to 15fps with a the frame interval set to 15, which is the lowest setting. I'll try lowering everything to 10 and see what happens.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Fri Jun 10, 2022 12:27 am
by iconnor
Don't waste your time. It has nothing to do with keyframe interval.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Thu Jun 16, 2022 9:58 am
by ameterasu
I'm having the same errors on a fresh install, 1.36.19.
Currently there are 23 1080P 10fps cameras, all record with analysis disabled.
5 out of 23 are Uniview cameras, rest are Hikvision.
errors are coming from Uniview cameras, tried all kinds of different settings on the uniview page. Can not resolve.
The big issue is I can not watch events on these monitors. Downloaded Mp4's return "cannot render the file" error on media player classic.
There are no other errors or warnings other than these.
Lastly, there was no issue on 1.36.16. EDIT: I'm not exacly sure about this. Have been struggling to run zoneminder since 1.34, multiple updates and fresh installs. However I'm exacly sure I had exporting work flawlessly for these cameras somewhere in 1.36.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Mon Jun 20, 2022 11:19 pm
by _LD
I'm pretty sure I started noticing these errors filling the web log in 1.36.16; because everything's ostensibly still working, I haven't bothered to troubleshoot it myself.
My cameras are set to Modect on the low-res streams and Nodect on the high-res.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Mon Jun 20, 2022 11:58 pm
by Andyrh
Interesting thing I found about 'non increasing dts, fixing' warning.
I recently built my new ZM server, I restored the DB so the configuration is the same. The servers are currently running in parallel. The old server does not have the error, the new server has many of them.
The known differences:
0. Old - New
1. Ubuntu 20.04.4 - 22.04
2. Same VLAN as cameras - Different VLAN
3. i7-2700K - Xeon E5-1630
4. Both running 1.36.19
Could it be caused by the packet routing?
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Tue Jun 21, 2022 12:12 am
by iconnor
I think something changed in ffmpeg, causing it to decode and have out of order packets. I have today pushed to master some code to buffer and reorder the packets.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Fri Jul 15, 2022 8:44 pm
by hotelmode
Installed 1.36.20 and added "reorder_queue_size=15" to encoder settings (same as the frame interval) for the camera that was throwing the errors. Appears to be fixed. Thanks. Haven't seen a green "Log" shortcut in a little while! It's nice.
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Sat Jul 23, 2022 9:53 pm
by Andyrh
I am still seeing this error with 1.36.20 and "reorder_queue_size={key frame interval}"
It is less frequent and only on 1 camera, 2 had the issue originally, the reorder command is now in both.
I am going to set it to key frame X 2 (16) and see if that helps or should I do something different?
Thank you,