Linked Monitor and High Res not recording

[xefil]

Hi all,
I've again problems with Linked monitor. I must admit that I've added a new camera and due high load I've tried to disable some cams and hope to not have touched too much settings. BTW in addition I've updated to latest zoneminder and the Linked Monitor doesn't work anymore.

Code: Select all

ii  zoneminder                           1.35.18~20210222112703-focal          amd64        video camera security and surveillance solution
ii  zoneminder-doc                       1.35.18~20210222112703-focal          all          ZoneMinder documentation

Goal: register modect of high res monitor when low res monitor detects motion. Low Res should not register to disk, because is registered from high-res on disk.

Settings:

Low-Res CAM
Icon color: green
Zone: 1 - ALL
Source: ffmpeg
Function: Modect
Analysis: ENABLED
Linked: None
Storage
Save JPEGS: Disabled
Video Writer: Disabled
OutputCodec/Encoder/OutputContainer: Auto

High-Res CAM
Icon color: yellow/orange
Zone: 0
Source: ffmpeg
Function: Nodect
Analysis: Disabled
Decoding: Enabled (so I can see Live preview)
Linked: Low-Res CAM
Storage
Save JPEGS: Frames + Analysis
Video Writer: H264 Passtrough
OutputCodec/Encoder/OutputContainer: Auto

Stream (read via vlc):
H264 - MPEG-4 AVC (part10) (h264)
1280 x 720

When a movement happens, the Low-Res records an event, I can see the screenshot of the event, but the video is not shown. That is expected, due the Storage is set to disabled. BTW the High Res cam doesn't increase the event count and nothing is registered in hight res flow.
In addiction i'venoticed this error on the logs:

Code: Select all

zmc_m12[24769].WAR-zm_monitor.cpp/1767 [Shouldn't be doing Analyse when not Enabled]

The cam id 12 (shown on mous hover on the cam via gui) is the High Res Cam which has analysis disabled...

Ideas? What's doing wrong?

Thanks!

Simon

[xefil]

Hello!

Any suggestion or help please?

Thanks!

Simon

[Magic919]

It could just be part of the 1.35.x journey.

Have a look on the Slack channel.

[j4c3]

This is from memory, but the High-Res may need analysis enabled. There may be something there on the help (?) that says if it is disabled the monitor wont check for triggers on linked cameras.

[xefil]

Hello j4c3 , thank you, that was the problem.
I've enabled only the "Analysis Enabled" flag and now it's recording correctly.
The problem is started as soon I've enabled a new CAM. The load seems very high. So Ive tried to disable all cams and I'm starting to enable the cams one by one. What is happening, in addiction, are entries like this:

Can't connect to capture daemon: diffrent ids (5, 7, 9, ...)
[Can't open memory map file /dev/shm/zm.mmap.different ids

Where those ids are from CAMS that are not enabled. So seems they are not enabled, even if:

Code: Select all

root@cctv:/dev/shm# ps -edaf | grep zm
www-data  106560       1  0 Feb24 ?        00:00:13 /usr/bin/perl -wT /usr/bin/zmdc.pl startup
www-data  106590  106560  0 Feb24 ?        00:00:00 /usr/bin/zmcontrol.pl --id 1
www-data  106599  106560  0 Feb24 ?        00:00:00 /usr/bin/zmcontrol.pl --id 3
www-data  106613  106560 13 Feb24 ?        03:51:17 /usr/bin/zmc -m 13
www-data  106617  106560  0 Feb24 ?        00:00:03 /usr/bin/zmcontrol.pl --id 13
www-data  106622  106560  1 Feb24 ?        00:17:54 /usr/bin/perl -wT /usr/bin/zmtrack.pl -m 13
www-data  106638  106560  0 Feb24 ?        00:00:28 /usr/bin/perl -wT /usr/bin/zmwatch.pl
www-data  106648  106560  0 Feb24 ?        00:00:02 /usr/bin/perl -wT /usr/bin/zmstats.pl
www-data  169720  106560  0 00:00 ?        00:00:00 /usr/bin/perl -wT /usr/bin/zmtelemetry.pl
www-data  169788  106560  0 00:01 ?        00:00:06 /usr/bin/perl -wT /usr/bin/zmfilter.pl --filter_id=2 --daemon
www-data  169815  106560  0 00:01 ?        00:00:23 /usr/bin/perl -wT /usr/bin/zmfilter.pl --filter_id=1 --daemon
www-data  238683  106560  0 16:44 ?        00:00:00 /usr/bin/zmcontrol.pl --id 12
www-data  238710  106560  6 16:44 ?        00:00:35 /usr/bin/zmc -m 12
www-data  238922  106560 11 16:47 ?        00:00:37 /usr/bin/zmc -m 3
www-data  239154  106560  1 16:53 ?        00:00:00 /usr/bin/zmc -m 1
root      239156    1083  0 16:53 pts/0    00:00:00 grep --color=auto zm
www-data  239158  239123  2 16:53 ?        00:00:00 /usr/lib/zoneminder/cgi-bin/nph-zms
www-data  239159  239061  2 16:53 ?        00:00:00 /usr/lib/zoneminder/cgi-bin/nph-zms
www-data  239160  239058  3 16:53 ?        00:00:00 /usr/lib/zoneminder/cgi-bin/nph-zms

And the load gets very high and then low, then high again....

Ideas?

I could in case open a new thread.

Thanks, Simon

[j4c3]

Not really. I'm also new to ZM.

But, 1.35 has some threads about high-utilization. There were some changes that are still ongoing with how it is handling buffers, I think.

As for the errors, is it possible that those IDs match a linked cam? Like, one end of the link is enabled and the other isn't, and it is just telling you it can't trigger, because the other isn't running (available in shared memory).

[xefil]

Hello,
Nope, those id-cams are not the linked cams.
BTW after update they went away, but I'm noticing those errors now:


Broadcast message from systemd-journald@cctv (Tue 2021-03-02 09:12:42 CET):
zmc_m3[105153]: ERR [zmc_m3] [Got signal 11 (Segmentation fault), crashing]

Broadcast message from systemd-journald@cctv (Tue 2021-03-02 09:12:42 CET):
zmc_m3[105153]: ERR [zmc_m3] [Signal address is 0xa3080, from 0x55ebbc882122]

I'll open an Issue on github for that, seems more software. First I'll try another update.

Simon