ZM 1.37.16-1.177 (Fedora 36) with Recording set to "Always" - repeatedly fails with backtraces

Current Development version likely to have breaking changes
Post Reply
jnikolich
Posts: 2
Joined: Fri Jun 17, 2022 3:53 am

ZM 1.37.16-1.177 (Fedora 36) with Recording set to "Always" - repeatedly fails with backtraces

Post by jnikolich »

Hello all;

(Please note - this relates to GitHub issue GitHub Issue #3497).

As described in the GH issue, the problem occurs on a freshly-installed Fedora-36 (x86_64) host that has ZM 1.37.16-1.177.20220604gitg4be56ec67 (and several subsequent version) installed. A single monitor (Inesun IPD-D53M02-BS) has been configured. As long as Recording -> Recording is set to None, everything works as expected. Live view is visible and stable.

As soon as the Recording setting is changed to Always, zmc_m1 crashes with a segment-violation (signal 11). Shortly afterward zmc_m1 is auto-restarted, and immediately crashes again, with the cycle repeating endlessly. The log data looks similiar to:

Code: Select all

06/04/22 12:15:34.760585 zmc_m1[36268].DB1-zm_event.cpp/648 [Using storage area at /var/data/zm_data/events/1/2022-06-04/34]
06/04/22 12:15:34.760597 zmc_m1[36268].DB4-zm_swscale.cpp/33 [SWScale object created]
06/04/22 12:15:34.760602 zmc_m1[36260].DB3-zm_monitor.cpp/1888 [signal and capturing and doing motion detection 2]
06/04/22 12:15:34.760607 zmc_m1[36260].DB1-zm_monitor.cpp/1902 [Assigning instead of Detecting]
06/04/22 12:15:34.760609 zmc_m1[36260].DB1-zm_monitor.cpp/1912 [assigning refimage from snap->image]
06/04/22 12:15:34.760614 zmc_m1[36268].DB1-zm_videostore.cpp/113 [Opening video storage stream /var/data/zm_data/events/1/2022-06-04/34/incomplete.mp4 format: mp4]
06/04/22 12:15:34.760682 zmc_m1[36268].ERR-zm_signal.cpp/50 [Got signal 11 (Segmentation fault), crashing]
06/04/22 12:15:34.761306 zmc_m1[36268].DB1-zm_signal.cpp/57 [Signal information: number 11 code 2 errno 0 pid -1465762868 uid 32605 status 0]
06/04/22 12:15:34.761320 zmc_m1[36268].ERR-zm_signal.cpp/80 [Signal address is 0x7f5da8a23bcc, from 0x56317748173e]
06/04/22 12:15:34.761826 zmc_m1[36268].ERR-zm_signal.cpp/101 [Backtrace 0: /usr/bin/zmc(+0x8fabf) [0x563177387abf]]
06/04/22 12:15:34.761913 zmc_m1[36268].ERR-zm_signal.cpp/101 [Backtrace 1: /lib64/libc.so.6(+0x3ea70) [0x7f5da67d0a70]]
06/04/22 12:15:34.761953 zmc_m1[36268].ERR-zm_signal.cpp/101 [Backtrace 2: /usr/bin/zmc(+0x18973e) [0x56317748173e]]
06/04/22 12:15:34.761997 zmc_m1[36268].ERR-zm_signal.cpp/101 [Backtrace 3: /usr/bin/zmc(+0x16c529) [0x563177464529]]
06/04/22 12:15:34.762036 zmc_m1[36268].ERR-zm_signal.cpp/101 [Backtrace 4: /lib64/libstdc++.so.6(+0xdbb73) [0x7f5da6b6cb73]]
06/04/22 12:15:34.762073 zmc_m1[36268].ERR-zm_signal.cpp/101 [Backtrace 5: /lib64/libc.so.6(+0x8ce1d) [0x7f5da681ee1d]]
06/04/22 12:15:34.762112 zmc_m1[36268].ERR-zm_signal.cpp/101 [Backtrace 6: /lib64/libc.so.6(+0x1125e0) [0x7f5da68a45e0]]
06/04/22 12:15:34.762145 zmc_m1[36268].INF-zm_signal.cpp/108 [Backtrace complete, please execute the following command for more information: addr2line -e /usr/bin/zmc 0x563177387abf 0x7f5da67d0a70 0x56317748173e 0x563177464529 0x7f5da6b6cb73 0x7f5da681ee1d 0x7f5da68a45e0]
Event subdirectories are created in the expected location (i.e. /var/data/zm_data/events/...), however they remain empty - not populated with any data.

Permissions on the above directory appear correct (apache:apache, drwxr-xr-x), and match the user that ZM is running as.

I've saved a full lvl-4 zmc_m1 debug log, available on Pastebin here.

I'm hoping someone can suggest either a solution or some troubleshooting steps I could take, because as things are this is a 100% show-stopper as far as ZM 1.37 goes. Note that with ZM 1.36, everything works fine, including recording.

Thank you very much
User avatar
iconnor
Posts: 2879
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: ZM 1.37.16-1.177 (Fedora 36) with Recording set to "Always" - repeatedly fails with backtraces

Post by iconnor »

Unfortunately backtraces have been useless for years. A better option would be turn on debug logging at level 3 and see what is happening right before the crash. Or install valgrind and run it under that.

EDIT: You did turn on debug, I can see that now. So it crashed when starting up opening up the mp4. I suspect it's an ffmpeg 5 issue.

I will likely have to spin up a fedora 36 vm and test myself. Stay tuned.
jnikolich
Posts: 2
Joined: Fri Jun 17, 2022 3:53 am

Re: ZM 1.37.16-1.177 (Fedora 36) with Recording set to "Always" - repeatedly fails with backtraces

Post by jnikolich »

Thanks very much for taking a look at things. FWIW, I've listed all packages that have been installed on the Fedora 36 host I observed the problem on, and listed them in this pastebin. I've also put a link to the same pastebin into GH Issue #3497 for better issue-tracking.

If you need any other information from me, or would like me to perform any other tests, config-changes, etc, I'm happy to do so.

Thanks again, very much.
Post Reply