[support] dlandon - Zoneminder 1.36


1083 posts in this topic Last Reply

Recommended Posts

4 minutes ago, Jaburges said:

check the versions all match up (and the files you have in /opencv are correct)

I notice you are using a driver 455.38 (so I think that is Unraid beta build) 

 

opencv variables in the opencv install script too so i'm assuming given the driver version is forced by the unraid build, you'll need to match the CUDA version like the plex one using 11.1

 

my issue is rebuilding FFMPEG to use cuda or cuvid - I have to rebuild it from source, but with all the libraries (and its overly complicated)

 

Yup, they line up.  I did indeed upgrade to 6.9 beta because the nvidia package was pulled from the CE repo and I just installed Unraid like a week ago, so this was the 'recommended' solution.  

 

CUDNN_RUN=libcudnn8_8.0.5.39-1+cuda11.1_amd64.deb
CUDNN_DEV=libcudnn8-dev_8.0.5.39-1+cuda11.1_amd64.deb
CUDA_TOOL=cuda-repo-ubuntu1804-11-1-local_11.1.1-455.32.00-1_amd64.deb
CUDA_PIN=cuda-ubuntu1804.pin
CUDA_KEY=/var/cuda-repo-ubuntu1804-11-1-local/7fa2af80.pub
CUDA_VER=11.1

 

Versions look right.. except 455.32 vs 455.38.  Is that the issue?  Plex must get the right version from someplace. I'll take a look at the plex docker image.. that might give me some insight.  Thanks!

Link to post
  • Replies 1.1k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

I realize that Zoneminder 1.32.0 has been released and I will eventually update the Docker for this new release.  Please don't try to lobby me to update the Docker right away.  I won't update it for a

This is an update of the Zoneminder Docker initially created by aptalca to the latest version of Zoneminder.  You can do an in place update of this Docker and your current configuration will be kept a

Map an external port to the Zoneminder docker port 80.

Posted Images

57 minutes ago, sivart said:

Yup, they line up.  I did indeed upgrade to 6.9 beta because the nvidia package was pulled from the CE repo and I just installed Unraid like a week ago, so this was the 'recommended' solution.  

 


CUDNN_RUN=libcudnn8_8.0.5.39-1+cuda11.1_amd64.deb
CUDNN_DEV=libcudnn8-dev_8.0.5.39-1+cuda11.1_amd64.deb
CUDA_TOOL=cuda-repo-ubuntu1804-11-1-local_11.1.1-455.32.00-1_amd64.deb
CUDA_PIN=cuda-ubuntu1804.pin
CUDA_KEY=/var/cuda-repo-ubuntu1804-11-1-local/7fa2af80.pub
CUDA_VER=11.1

 

Versions look right.. except 455.32 vs 455.38.  Is that the issue?  Plex must get the right version from someplace. I'll take a look at the plex docker image.. that might give me some insight.  Thanks!

I followed this post 

 and now I see CUDA listed in in my nvidia-smi output.  For those wondering, I had to add 3 options to the zoneminder config:

  • extra parameters need to have "--runtime=nvidia"
  • NVIDIA_VISIBLE_DEVICES Docker variable needs to be set with your video cards GUID
  • NVIDIA_DRIVER_CAPABILITIES Docker variable needs to be set to 'all'

I still don't see 'zmc' using the video card though, and ffmpeg doesn't list CUDA as an accelerator... so now I think I am having the same problem...

 

Link to post
2 minutes ago, sivart said:

I followed this post 

  • extra parameters need to have "--runtime=nvidia"
  • NVIDIA_VISIBLE_DEVICES Docker variable needs to be set with your video cards GUID
  • NVIDIA_DRIVER_CAPABILITIES Docker variable needs to be set to 'all'

I still don't see 'zmc' using the video card though, and ffmpeg doesn't list CUDA as an accelerator... so now I think I am having the same problem...

 

yeah that should be everything.

I think (but i'm not sure) unless you watch nvidia-smi when object detection happens you may not see the task? 

 

However, i'm almost convinced i never had to rebuild FFMPEG to use cuda for Hwaccels - but now I do? @dlandon is there anything that may have changed on the FFMPEG side? 

Link to post
4 minutes ago, Jaburges said:

yeah that should be everything.

I think (but i'm not sure) unless you watch nvidia-smi when object detection happens you may not see the task? 

 

However, i'm almost convinced i never had to rebuild FFMPEG to use cuda for Hwaccels - but now I do? @dlandon is there anything that may have changed on the FFMPEG side? 

I am thinking there must be a debian ppa that has an ffmpeg with CUDA support. It looks like the one that is in the base image for zoneminder doesn't have it.  It is 4.3.1 though.  People are reporting the Ubuntu 20.04 works out of the box, probably because ffmpeg is built with CUDA support in that release... so I am gonna see if I can install that.

Link to post
8 minutes ago, sivart said:

I am thinking there must be a debian ppa that has an ffmpeg with CUDA support. It looks like the one that is in the base image for zoneminder doesn't have it.  It is 4.3.1 though.  People are reporting the Ubuntu 20.04 works out of the box, probably because ffmpeg is built with CUDA support in that release... so I am gonna see if I can install that.

FFmpeg 4 with NVIDIA Encoding and Decoding support | TalOrg

interesting - didnt find this on my travels but i notice in the dockerfile:

add-apt-repository ppa:jonathonf/ffmpeg-4

so maybe just the config needs changing and the extra ffmpeg headers for nvidia

Link to post
9 minutes ago, Jaburges said:

FFmpeg 4 with NVIDIA Encoding and Decoding support | TalOrg

interesting - didnt find this on my travels but i notice in the dockerfile:


add-apt-repository ppa:jonathonf/ffmpeg-4

so maybe just the config needs changing and the extra ffmpeg headers for nvidia

That is what I am looking at.  It appears the ffmpeg-4 ppa there doesn't have nvidia support.. but someone has to have one!

 

Link to post
1 hour ago, sivart said:

So this repo has an ffmpeg build that should update the libraries too, but zmc still isn't using the video card

 

https://launchpad.net/~savoury1/+archive/ubuntu/ffmpeg4?field.series_filter=bionic

Ok super weird, built using this, cuda shows up as -hwaccels, but is not being used by Zoneminder.


i remember I used to use cuvid for hwaccels not cuda though. 

Link to post
4 minutes ago, Jaburges said:

Ok super weird, built using this, cuda shows up as -hwaccels, but is not being used by Zoneminder.


i remember I used to use cuvid for hwaccels not cuda though. 

Yeah, it looks like that PPA doesn't include the libraries that zoneminder users.  When I tried to force for CUDA mode in ZM using the ffmpeg option, it just reports this...

 

Screen Shot 2020-12-03 at 20.37.15.png

Link to post
On 11/6/2020 at 6:51 PM, Jaburges said:

@dlandon the issue appears to be that running the opencv.sh doesnt seem to install everything.
i should be able to (I believe) run


nvcc --version

and produce a result, but it does not "nvcc: command not found"

I've attempted this from a fresh docker numerous times. can you confirm

A) if anything changed
B) what cuda verson is recommended

A) Nothing has changed.

B) The cuda version is dependent on your nvidia driver and support for that in cuda.

 

I have no experience with cuda.  I put together the script with input from pliablepixels (the author of ES).  You should go the the Zoneminder forums and discuss your issue there.

Link to post
11 hours ago, Jaburges said:

 is there anything that may have changed on the FFMPEG side? 

No.  The FFMPG in the Zoneminder docker is the built in version of Ubuntu.  You would be better served by posting all this on the Zoneminder forum where you can get the attention of the Zoneminder developers and the ES author.

Link to post
3 hours ago, dlandon said:

A) Nothing has changed.

B) The cuda version is dependent on your nvidia driver and support for that in cuda.

 

I have no experience with cuda.  I put together the script with input from pliablepixels (the author of ES).  You should go the the Zoneminder forums and discuss your issue there.

 

I am new to all this and keep seeing ES referenced.  What is that? 

Link to post
7 hours ago, Jaburges said:

This is the thread on Zoneminder forum:

https://forums.zoneminder.com/viewtopic.php?t=30153
@sivart 

Thanks. I think the real issue is that the version of ubuntu this docker is built on (bionic) does not have the ffmpeg and libav libraries that have CUDA support.  When and if this docker image gets upgraded to 20.04 it should 'just work', but I realize that is probably very low priority and I am ok with that.

Link to post
On 12/4/2020 at 2:01 PM, sivart said:

Thanks. I think the real issue is that the version of ubuntu this docker is built on (bionic) does not have the ffmpeg and libav libraries that have CUDA support.  When and if this docker image gets upgraded to 20.04 it should 'just work', but I realize that is probably very low priority and I am ok with that.

Yeah - still no dice on this. FFMPEG on 18.04 with cuvid is a right cluster! 

Link to post

Hate to trouble people with what I'm sure is me missing something in a config somewhere, but I'm completely stumped why I can't get object recognition working.

 

Context:

-Starting with a working ZM with notifications, images in notifications, proper SSL, basic revprox, etc. all that works.

-I enable hooks and then no notifications, etc

-Just trying to start simple with CPU opencv, Yolo v3 from the default in the objectconfig.ini, comment out monitor-999 stuff at the end

-running in modect for now for debugging (notifications like having unique video sessions hence modect, mocord can make multiple triggers point to the same video session Iand then you don't get the new notification because you already 'read' that ID, end of that tangent)

 

-I get the following in the logs:

Dec 10 11:15:29 bda7008c85ba zma_m1[991]: INF [zma_m1] [Monitor-1: 2250 - Gone into alarm state PreAlarmCount: 0 > AlarmFrameCount:1 Cause:Forced Web]
Dec 10 11:15:29 bda7008c85ba zma_m1[991]: INF [zma_m1] [Monitor-1: 2250 - Opening new event 49, alarm start]
Dec 10 11:15:29 bda7008c85ba zmc_m1[986]: INF [zmc_m1] [Opening video storage stream /var/cache/zoneminder/events/1/2020-12-10/49/49-video.mp4 format: mp4]
Dec 10 11:15:29 bda7008c85ba zmc_m1[986]: INF [zmc_m1] [some options not used, turn on debugging for a list.]
Dec 10 11:15:29 bda7008c85ba zmc_m1[986]: INF [zmc_m1] [Event video offset is -1.735 sec (<0 means video starts early)]
Dec 10 11:15:30 bda7008c85ba zmc_m1[986]: INF [zmc_m1] [Monitor-1: images:2300 - Capturing at 10.00 fps, capturing bandwidth 51431bytes/sec]
Dec 10 11:15:31 bda7008c85ba zmeventnotification[1019]: INF [PARENT: New event 49 reported for Monitor:1 (Name:Monitor-1) Forced Web[last processed eid:48]]
Dec 10 11:15:34 bda7008c85ba zma_m1[991]: INF [zma_m1] [Monitor-1: 2300 - Analysing at 10.00 fps]
Dec 10 11:15:34 bda7008c85ba zma_m1[991]: INF [zma_m1] [Monitor-1: 2302 - Gone into alert state]
Dec 10 11:15:34 bda7008c85ba zma_m1[991]: INF [zma_m1] [Monitor-1: 2300 - Analysing at 10.00 fps]
Dec 10 11:15:34 bda7008c85ba zma_m1[991]: INF [zma_m1] [Monitor-1: 2302 - Gone into alert state]
Dec 10 11:15:37 bda7008c85ba zma_m1[991]: INF [zma_m1] [Monitor-1: 2328 - Left alarm state (49) - 83(52) images]
Dec 10 11:15:37 bda7008c85ba zma_m1[991]: INF [zma_m1] [Monitor-1: 2328 - Closing event 49, alarm end]
Dec 10 11:15:37 bda7008c85ba zma_m1[991]: INF [zma_m1] [Updating frames delta by -1.74 sec to match video file]
Dec 10 11:15:37 bda7008c85ba zmeventnotification[1070]: INF [|----> FORK:Monitor-1 (1), eid:49 Event 49 for Monitor 1 has finished]
Dec 10 11:15:40 bda7008c85ba zmc_m1[986]: INF [zmc_m1] [Monitor-1: images:2400 - Capturing at 10.00 fps, capturing bandwidth 55194bytes/sec]
Dec 10 11:15:41 bda7008c85ba zmeventnotification[1070]: INF [|----> FORK:Monitor-1 (1), eid:49 Not sending event end alarm, as we did not send a start alarm for this, or start hook processing failed]

Dec 10 11:15:44 bda7008c85ba zma_m1[991]: INF [zma_m1] [Monitor-1: 2400 - Analysing at 10.00 fps]
Dec 10 11:15:50 bda7008c85ba zmc_m1[986]: INF [zmc_m1] [Monitor-1: images:2500 - Capturing at 10.00 fps, capturing bandwidth 71043bytes/sec]

Which seems to indicate the detection isn't returning which probably could be from numerous potential errors, so I appreciate that probably isn't so helpful.

 

For context there is a car parked in the cameras view, and once upon a time I remember getting object detection working (before I had revprox/images/etc working and long since killed/lost that config) and it said 'car 99%' or what have so I don't think the error is as daft as 'nothing was detected'.

 

I dug around a little bit in configs looking for the 'flow path' and noticed the base_data_path default points to /var/lib/zmeventnotification, went looking in there (within the container console) and did not find the start or end .py files, which instead are stored in /config/hook.  Tried changing base_data_path to /config/hook but no joy with that change (probably because the changing base_data_path breaks some other file locations).

 

Like I said I'm probably just missing a part of the instructions that say 'oh yah you need to change this part of the default ES/hook config because this is in docker and defaults assume an OS' but I'm pretty stumped.

 

Any help would be much appreciated.

 

EDIT

 

Well, I feel incredibly silly.  Figured it out.

 

Bit of background, one of my followup questions to the above problems was why it seemed like every time I loaded up the container, opencv would have to recompile.  So in an effort to debug I had turned off 'hooks' and 'v3' options thinking 'well, maybe it only needs to install once, or the install scripts are bugged, or I've misconfiged them and they're bugged'.

 

Then I though back to first principles of understanding docker and remembered that the container is transient, don't count on anything 'inside' the docker to survive shutdown, because you might update, change config, etc.  Docker is built on that assumption.

 

So I went back into the container config and turned hooks and yolov3 again, and it's at least preliminarily working, obviously I need some more tuning and config work to my application.  In hind sight it makes total sense with what I realized next.

 

What was probably happening is I was taking 'crimes of opportunity' when I was changing the config files, I probably was also tuning the --cpus= value in the container options because compiling was maxing out the CPU and 'soft crashing' unraid which is why I kept changing that value (and re-issuing the container, triggering a opencv recompile).  Maybe sometimes I wouldn't change the container settings and it wouldn't recompile, but by that point I had learned to make a change and come back in 15 minutes and wasn't paying attention.

 

So yah, only mess with your container or your configs, not both at the same time.  Really, don't mess with you container hardly ever.  And leave your 'installs' on.  And remember that you'll need to recompile opencv each time the container gets issued, and the container gets issued each time you change the config (including updates).

 

Thanks to dlandon for generally having all this stuff glued together well and entertaining numpties like myself on our issues.

Edited by ThreeFN
Link to post

Hey guys,

 

I got Zoneminder up and running with two cameras and it does work so far. 

My plan is, to let the alarm event forward to my telegram-bot to inform me, if something cool happens in my property. I used the great scripts from TheDave1022 you can find here Click at github. I suceeded to send myself the test message.

The point where Im lost is, to setup zm_telegram.service as a service starting when the Zoneminder Docker starts up, since i'm very new to docker and dont know how without the systemd init.

I looked up in the docker documentation and found this: Docker init process

Everything fine, but how do I know, which process manager dlandons Docker image is using or preferring? If anybody got that telegram notifying up an running, i would kiss his eyes to clearify it.

 

Thx friends!

Link to post

Hi, just wondering if anyone has any issues with the different types of objects. Mine currently detects person fine but it never detects a car. It used to and has only stopped recently. 

 

I have it set as

object_detection_pattern=(person|car|motorbike|bus|truck|boat)

using yolov3 full

 

Any ideas? 

 

Thanks 

Link to post
  • 2 weeks later...

i have zm 1.34.22 up and running on Unraid 6.8.3. i only have one camera setup, Wyze cam v2 with the latest 4.28.4.49 RTSP firmware. i have the camera setup as Mocord, so it is continuously recording in 7 minute files as well as detecting motion.

 

my issue is that sometimes, when it does detect motion, the live feed freezes for a minute or two, then it goes to the live feed again. but during that freeze, there is no video being captured, so i am missing that footage. i don't know if this is a zm issue with configuration or a wyzecam issue. here is a piece of the log,

Quote

Date/Time
Component    Server    PID    Level    Message    File    Line
2020-12-29 13:43:41    zmc_m1        27522    INF    Front Yard v2: images:400 - Capturing at 14.29 fps, capturing bandwidth 78990bytes/sec    zm_monitor.cpp    2550
2020-12-29 13:43:38    zma_m1        27524    INF    Front Yard v2: 300 - Analysing at 16.67 fps    zm_monitor.cpp    1305
2020-12-29 13:43:34    zmc_m1        27522    INF    Front Yard v2: images:300 - Capturing at 16.67 fps, capturing bandwidth 78882bytes/sec    zm_monitor.cpp    2550
2020-12-29 13:43:32    zma_m1        27524    INF    Front Yard v2: 200 - Analysing at 14.29 fps    zm_monitor.cpp    1305
2020-12-29 13:43:28    zmc_m1        27522    INF    Front Yard v2: images:200 - Capturing at 14.29 fps, capturing bandwidth 70734bytes/sec    zm_monitor.cpp    2550
2020-12-29 13:43:25    zma_m1        27524    INF    Front Yard v2: 100 - Analysing at 33.33 fps    zm_monitor.cpp    1305
2020-12-29 13:43:22    zmc_m1        27522    INF    Event video offset is -1.056 sec (<0 means video starts early)    zm_ffmpeg_camera.cpp    883
2020-12-29 13:43:22    zmc_m1        27522    INF    some options not used, turn on debugging for a list.    zm_videostore.cpp    440
2020-12-29 13:43:22    zmc_m1        27522    INF    Opening video storage stream /var/cache/zoneminder/events/1/2020-12-29/3523/3523-video.mp4 format: mp4    zm_videostore.cpp    63
2020-12-29 13:43:22    zma_m1        27524    INF    Front Yard v2: 026 - Opening new event 3523, section start    zm_monitor.cpp    1528
2020-12-29 13:43:22    zma_m1        27524    INF    In mode 5/1, warming up    zma.cpp    136
2020-12-29 13:43:21    zmdc        27524    INF    'zma -m 1' started at 20/12/29 13:43:21    zmdc.pl    
2020-12-29 13:43:21    zmdc        13196    INF    'zma -m 1' starting at 20/12/29 13:43:21, pid = 27524    zmdc.pl    
2020-12-29 13:43:21    zmdc        13196    INF    Starting pending process, zma -m 1    zmdc.pl    
2020-12-29 13:43:21    zmc_m1        27522    INF    Front Yard v2: images:100 - Capturing at 20.00 fps, capturing bandwidth 102964bytes/sec    zm_monitor.cpp    2550
2020-12-29 13:43:16    zmc_m1        27522    INF    Front Yard v2: images:1 - Capturing at 0.20 fps, capturing bandwidth 32700bytes/sec    zm_monitor.cpp    2550
2020-12-29 13:43:11    zmdc        13196    ERR    'zma -m 1' exited abnormally, exit status 255    zmdc.pl    
2020-12-29 13:43:11    zmc_m1        27522    INF    Starting Capture version 1.34.22    zmc.cpp    223
2020-12-29 13:43:11    zma_m1        27523    ERR    Shared data not initialised by capture daemon for monitor Front Yard v2    zm_monitor.cpp    501
2020-12-29 13:43:10    zmc_m1        27522    INF    Enabling ffmpeg logs, as LOG_DEBUG+LOG_FFMPEG are enabled in options    zm_ffmpeg.cpp    82
2020-12-29 13:43:10    zmdc        27523    INF    'zma -m 1' started at 20/12/29 13:43:10    zmdc.pl    
2020-12-29 13:43:10    zmdc        13196    INF    'zma -m 1' starting at 20/12/29 13:43:10, pid = 27523    zmdc.pl    
2020-12-29 13:43:10    zmdc        13196    INF    Starting pending process, zma -m 1    zmdc.pl    
2020-12-29 13:43:10    zmdc        13196    INF    'zmc -m 1' starting at 20/12/29 13:43:10, pid = 27522    zmdc.pl    
2020-12-29 13:43:10    zmdc        27522    INF    'zmc -m 1' started at 20/12/29 13:43:10    zmdc.pl    
2020-12-29 13:43:10    zmdc        13196    INF    Starting pending process, zmc -m 1    zmdc.pl    
2020-12-29 13:43:05    zmdc        13196    ERR    'zma -m 1' exited abnormally, exit status 255    zmdc.pl    
2020-12-29 13:43:05    zma_m1        27521    ERR    Got empty memory map file size 0, is the zmc process for this monitor running?    zm_monitor.cpp    582
2020-12-29 13:43:05    zmdc        13196    INF    'zmc -m 1' exited normally    zmdc.pl    
2020-12-29 13:43:05    zmdc        27521    INF    'zma -m 1' started at 20/12/29 13:43:05    zmdc.pl    
2020-12-29 13:43:05    zmdc        13196    INF    'zma -m 1' starting at 20/12/29 13:43:05, pid = 27521    zmdc.pl    
2020-12-29 13:43:05    zmdc        13196    INF    Starting pending process, zma -m 1    zmdc.pl    
2020-12-29 13:43:05    zmdc        13196    ERR    'zma -m 1' exited abnormally, exit status 255    zmdc.pl    
2020-12-29 13:43:05    zma_m1        27520    ERR    Got empty memory map file size 0, is the zmc process for this monitor running?    zm_monitor.cpp    582
2020-12-29 13:43:05    zmdc        27520    INF    'zma -m 1' started at 20/12/29 13:43:05    zmdc.pl    
2020-12-29 13:43:05    zmdc        13196    INF    'zma -m 1' starting at 20/12/29 13:43:05, pid = 27520    zmdc.pl    
2020-12-29 13:43:05    zmdc        13196    INF    'zma -m 1' exited normally    zmdc.pl    
2020-12-29 13:43:05    zmc_m1        27509    WAR    error while decoding MB 114 15, bytestream -9    zm_ffmpeg.cpp    70
2020-12-29 13:43:05    zmdc        13196    INF    'zmc -m 1' sending stop to pid 27509 at 20/12/29 13:43:05    zmdc.pl    
2020-12-29 13:43:05    zma_m1        27512    INF    Updating frames delta by -0.68 sec to match video file    zm_event.cpp    593
2020-12-29 13:43:05    zma_m1        27512    INF    Front Yard v2: image_count:71 - Closing event 3522, shutting down    zm_monitor.cpp    694
2020-12-29 13:43:05    zmdc        13196    INF    'zma -m 1' sending stop to pid 27512 at 20/12/29 13:43:05    zmdc.pl    
2020-12-29 13:43:05    zmwatch        13245    WAR    Restarting capture daemon for Front Yard v2, time since last capture 52 seconds (1609267385-1609267333)    zmwatch.pl    
2020-12-29 13:42:14    zmc_m1        27509    INF    CSeq 8 expected, 0 received.    zm_ffmpeg.cpp    70
2020-12-29 13:42:05    zmc_m1        27509    INF    Event video offset is -0.677 sec (<0 means video starts early)    zm_ffmpeg_camera.cpp    883
2020-12-29 13:42:05    zmc_m1        27509    INF    some options not used, turn on debugging for a list.    zm_videostore.cpp    440
2020-12-29 13:42:05    zmc_m1        27509    INF    Opening video storage stream /var/cache/zoneminder/events/1/2020-12-29/3522/3522-video.mp4 format: mp4    zm_videostore.cpp    63
2020-12-29 13:42:05    zma_m1        27512    INF    Front Yard v2: 026 - Opening new event 3522, section start    zm_monitor.cpp    1528
2020-12-29 13:42:05    zma_m1        27512    INF    In mode 5/1, warming up    zma.cpp    136
2020-12-29 13:42:05    zmdc        27512    INF    'zma -m 1' started at 20/12/29 13:42:05    zmdc.pl    
2020-12-29 13:42:05    zmdc        13196    INF    'zma -m 1' starting at 20/12/29 13:42:05, pid = 27512    zmdc.pl    
2020-12-29 13:42:05    zmdc        13196    WAR    Can't find process with command of 'zma -m 1'    zmdc.pl    
2020-12-29 13:42:04    zmwatch        13245    INF    Restarting analysis daemon for 1 Front Yard v2    zmwatch.pl    
2020-12-29 13:42:04    zmwatch        13245    ERR    Last analyse time for 1 Front Yard v2 was zero.    zmwatch.pl    
2020-12-29 13:42:03    zmc_m1        27509    INF    Front Yard v2: images:1 - Capturing at 0.17 fps, capturing bandwidth 23278bytes/sec    zm_monitor.cpp    2550
2020-12-29 13:41:57    zmc_m1        27509    INF    Starting Capture version 1.34.22    zmc.cpp    223
2020-12-29 13:41:56    zmc_m1        27509    INF    Enabling ffmpeg logs, as LOG_DEBUG+LOG_FFMPEG are enabled in options    zm_ffmpeg.cpp    82
2020-12-29 13:41:56    zmdc        27509    INF    'zmc -m 1' started at 20/12/29 13:41:56    zmdc.pl    
2020-12-29 13:41:56    zmdc        13196    INF    'zmc -m 1' starting at 20/12/29 13:41:56, pid = 27509    zmdc.pl    
2020-12-29 13:41:56    zmdc        13196    INF    Starting pending process, zmc -m 1    zmdc.pl    
2020-12-29 13:41:55    zmdc        13196    INF    'zmc -m 1' exited normally    zmdc.pl    
2020-12-29 13:41:55    zmdc        13196    INF    'zma -m 1' exited normally    zmdc.pl    
2020-12-29 13:41:54    zmdc        13196    INF    'zma -m 1' already running at 20/12/29 11:35:55, pid = 26991    zmdc.pl    
2020-12-29 13:41:54    zmc_m1        26990    WAR    error while decoding MB 79 2, bytestream -15    zm_ffmpeg.cpp    70
2020-12-29 13:41:54    zmdc        13196    INF    'zmc -m 1' sending stop to pid 26990 at 20/12/29 13:41:54    zmdc.pl    
2020-12-29 13:41:54    zma_m1        26991    INF    Updating frames delta by -11.11 sec to match video file    zm_event.cpp    593
2020-12-29 13:41:54    zma_m1        26991    INF    Front Yard v2: image_count:111923 - Closing event 3521, shutting down    zm_monitor.cpp    694
2020-12-29 13:41:54    zmdc        13196    INF    'zma -m 1' sending stop to pid 26991 at 20/12/29 13:41:54    zmdc.pl    
2020-12-29 13:41:54    zmwatch        13245    WAR    Restarting capture daemon for Front Yard v2, time since last capture 46 seconds (1609267314-1609267268)    zmwatch.pl    
2020-12-29 13:41:08    zma_m1        26991    INF    Front Yard v2: 111900 - Analysing at 10.00 fps    zm_monitor.cpp    1305
2020-12-29 13:41:01    zmc_m1        26990    INF    Front Yard v2: images:111900 - Capturing at 14.29 fps, capturing bandwidth 85027bytes/sec    zm_monitor.cpp    2550
2020-12-29 13:40:58    zma_m1        26991    INF    Front Yard v2: 111807 - Gone into alert state    zm_monitor.cpp    1662
2020-12-29 13:40:58    zma_m1        26991    INF    Front Yard v2: 111800 - Analysing at 14.29 fps    zm_monitor.cpp    1305
2020-12-29 13:40:54    zmc_m1        26990    INF    Front Yard v2: images:111800 - Capturing at 14.29 fps, capturing bandwidth 73301bytes/sec    zm_monitor.cpp    2550
2020-12-29 13:40:52    zma_m1        26991    INF    Front Yard v2: 111715 - Gone into alarm state PreAlarmCount: 1 > AlarmFrameCount:2 Cause:Motion Street    zm_monitor.cpp    1568
2020-12-29 13:40:52    zma_m1        26991    INF    Front Yard v2: 111714 - Gone into prealarm state    zm_monitor.cpp    1652
2020-12-29 13:40:51    zma_m1        26991    INF    Front Yard v2: 111700 - Analysing at 14.29 fps    zm_monitor.cpp    1305
2020-12-29 13:40:47    zmc_m1        26990    INF    Front Yard v2: images:111700 - Capturing at 16.67 fps, capturing bandwidth 88990bytes/sec    zm_monitor.cpp    2550
2020-12-29 13:40:44    zma_m1        26991    INF    Front Yard v2: 111586 - Closing event 3520, section end forced 1609267244 - 1609266824 = 420 >= 420    zm_monitor.cpp    1515
2020-12-29 13:40:44    zma_m1        26991    INF    Updating frames delta by -1.10 sec to match video file    zm_event.cpp    593
2020-12-29 13:40:44    zma_m1        26991    INF    Front Yard v2: 111586 - Opening new event 3521, section start    zm_monitor.cpp    1528
2020-12-29 13:40:44    zmc_m1        26990    INF    Re-starting video storage module    zm_ffmpeg_camera.cpp    806
2020-12-29 13:40:44    zmc_m1        26990    INF    Opening video storage stream /var/cache/zoneminder/events/1/2020-12-29/3521/3521-video.mp4 format: mp4    zm_videostore.cpp    63
2020-12-29 13:40:44    zmc_m1        26990    INF    some options not used, turn on debugging for a list.    zm_videostore.cpp    440
2020-12-29 13:40:44    zmc_m1        26990    INF    Didn't find a frame before event starttime. keeping all    zm_packetqueue.cpp    321
2020-12-29 13:40:44    zmc_m1        26990    INF    Event video offset is 407.986 sec (<0 means video starts early)    zm_ffmpeg_camera.cpp    883
2020-12-29 13:40:44    zma_m1        26991    INF    Front Yard v2: 111600 - Analysing at 16.67 fps    zm_monitor.cpp    1305
2020-12-29 13:40:41    zmc_m1        26990    INF    Front Yard v2: images:111600 - Capturing at 14.29 fps, capturing bandwidth 93011bytes/sec    zm_monitor.cpp    2550

 

 

looks like the camera freezes, exit abnormally, then restarts the capture daemon. any idea whats going on? need any more info, let me know. thanks!

 

Link to post

This docker used to work for me fine but recently (last few weeks?) I noticed I've not being receiving any zmNinja alerts.

 

Digging further I notice that something has caused one of the zmninja scripts to fail (this script is used to test your config

# sudo -u www-data /var/lib/zmeventnotification/bin/zm_event_start.sh 1 1
Traceback (most recent call last):
  File "/var/lib/zmeventnotification/bin/zm_detect.py", line 27, in <module>
    import zmes_hook_helpers.utils as utils
ModuleNotFoundError: No module named 'zmes_hook_helpers'

 

So I've just done a brand new install of this docker from scratch (deleted old image and appdata) and enabled hook processing and yolo v4 options on the docker screen. 

 

Once installed I went into ZM options and enabled OPT_USE_EVENTNOTIFICATION, rebooted and then tried the above command again and it fails in the same manner :-(

 

Looks like something has broken the docker ZM event notification ?

 

I did notice some errors relating to scikit-learn failing to install when the docker installed ?

Link to post

Well, just gone through this all again several times with complete cleans installs and still get this error:

 

root@ea33b3d5e334:/var/lib/zmeventnotification/bin# sudo -u www-data ./zm_event_start.sh 1 1
Traceback (most recent call last):
  File "/var/lib/zmeventnotification/bin/zm_detect.py", line 27, in <module>
    import zmes_hook_helpers.utils as utils
ModuleNotFoundError: No module named 'zmes_hook_helpers'

 

Anyone recently done a fresh install of this docker in last few days and got ES working ?

Link to post
3 hours ago, fireplex said:

Well, just gone through this all again several times with complete cleans installs and still get this error:

 


root@ea33b3d5e334:/var/lib/zmeventnotification/bin# sudo -u www-data ./zm_event_start.sh 1 1
Traceback (most recent call last):
  File "/var/lib/zmeventnotification/bin/zm_detect.py", line 27, in <module>
    import zmes_hook_helpers.utils as utils
ModuleNotFoundError: No module named 'zmes_hook_helpers'

 

Anyone recently done a fresh install of this docker in last few days and got ES working ?

This seems to be the fix for the time being:

 

https://github.com/dlandon/zoneminder/issues/145

Link to post
  • dlandon changed the title to [support] dlandon - Zoneminder 1.36

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.