[support] dlandon - Zoneminder 1.36


Recommended Posts

finally got round to sorting out a GPU so looking at the openCV components. Everything except the CUDNN is reporting as YES and getting this error:

 

Could NOT find CUDNN (missing: CUDNN_LIBRARY CUDNN_INCLUDE_DIR) (Required is at least version "7.5")

 

however the runtime and developer libraries are in the /config/opencv folder and correctly match the name of the entries in opencv.sh

Link to comment
3 hours ago, Jaburges said:

finally got round to sorting out a GPU so looking at the openCV components. Everything except the CUDNN is reporting as YES and getting this error:

 

Could NOT find CUDNN (missing: CUDNN_LIBRARY CUDNN_INCLUDE_DIR) (Required is at least version "7.5")

 

however the runtime and developer libraries are in the /config/opencv folder and correctly match the name of the entries in opencv.sh

Be sure you have the run time and dev packages.  Version 10.2.

Link to comment
1 hour ago, dlandon said:

Be sure you have the run time and dev packages.  Version 10.2.

Yep I had the right files in opencv.
The build failed previously so I needed to rebuild the container before trying again. 
Once rebuilt, running the opencv.sh seems to be progressing nicely :) Fingers crossed

 

EDIT: Build completed successfully! 

Edited by Jaburges
updated after build
Link to comment

2 questions when you get a chance:

1. Now I've got OpenCV installed do I need to do anything inform the eventservice workflow to use it? Is it really that simple?

2. Is there much benefit in installing OpenCV >4.2 (in the docs you mention >4.3 to use CSPR over YOLO)

Link to comment

Been using the container for  a while with object detection. I did a fresh install.  I noticed object detection was not working.  Dropped into the container command line to execute imageproxy.php?img=&key=e5eec7c5c933ca16imageproxy.php?img=&key=e5eec7c5c933ca16

bash zm_event_start.sh 834 2

from /var/lib/bash zm_event_start.sh 834 2  and go no permission

had to do chmod +x *.*   then it started working .

WHen I updated to the new version yesterday I had to do the same thing.

 

HOw can I make sure this get executed when I download the new image

 

Edited by Faspina
Link to comment
1 hour ago, Faspina said:

Been using the container for  a while with object detection. I did a fresh install.  I noticed object detection was not working.  Dropped into the container command line to execute imageproxy.php?img=&key=e5eec7c5c933ca16imageproxy.php?img=&key=e5eec7c5c933ca16

bash zm_event_start.sh 834 2

from /var/lib/bash zm_event_start.sh 834 2  and go no permission

had to do chmod +x *.*   then it started working .

WHen I updated to the new version yesterday I had to do the same thing.

 

HOw can I make sure this get executed when I download the new image

 

Read the first post about 'User Script'.

Link to comment

@dlandon Not sure if you can help or not but I seem to have GPU support up and running and I confirmed at the end of the opencv compile that CUDA support was enabled.

 

I am running into an issue where the monitor is up and in modetect.  It sees the alarm but when it invokes the object detection, there seems to be a timeout.  I just don't know where.

 

Here is the logs...

 

May 12 10:55:12 immagine-zoneminder zmeventnotification[690]: INF [PARENT: New event 21 reported for Monitor:1 (Name:Amcrest Test) Motion All[last processed eid:]]
May 12 10:55:13 immagine-zoneminder /zm_detect.py[713]: INF [zmesdetect_m1] [---------| hook version: 5.13.3, ES version: 5.13-Docker , OpenCV version: 4.2.0-dev|------------]
May 12 10:55:13 immagine-zoneminder /zm_detect.py[713]: INF [zmesdetect_m1] [Importing local classes for Yolo/Face]
May 12 10:55:13 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 400 - Analysing at 33.33 fps]
May 12 10:55:14 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:500 - Capturing at 33.33 fps, capturing bandwidth 1140084bytes/sec]
May 12 10:55:17 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 500 - Analysing at 25.00 fps]
May 12 10:55:18 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:600 - Capturing at 25.00 fps, capturing bandwidth 924088bytes/sec]
May 12 10:55:20 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 564 - Left alarm state (21) - 255(3) images]
May 12 10:55:20 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 564 - Closing event 21, alarm end]
May 12 10:55:21 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 600 - Analysing at 25.00 fps]
May 12 10:55:21 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:700 - Capturing at 33.33 fps, capturing bandwidth 1040577bytes/sec]
May 12 10:55:24 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:800 - Capturing at 33.33 fps, capturing bandwidth 1139824bytes/sec]
May 12 10:55:24 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 700 - Analysing at 33.33 fps]
May 12 10:55:28 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:900 - Capturing at 25.00 fps, capturing bandwidth 924154bytes/sec]
May 12 10:55:28 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 800 - Analysing at 25.00 fps]
May 12 10:55:31 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:1000 - Capturing at 33.33 fps, capturing bandwidth 1038018bytes/sec]
May 12 10:55:31 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 900 - Analysing at 33.33 fps]
May 12 10:55:34 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:1100 - Capturing at 33.33 fps, capturing bandwidth 1144528bytes/sec]
May 12 10:55:35 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 1000 - Analysing at 25.00 fps]
May 12 10:55:38 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:1200 - Capturing at 25.00 fps, capturing bandwidth 917746bytes/sec]
May 12 10:55:39 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 1100 - Analysing at 25.00 fps]
May 12 10:55:41 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:1300 - Capturing at 33.33 fps, capturing bandwidth 1031943bytes/sec]
May 12 10:55:42 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 1200 - Analysing at 33.33 fps]
May 12 10:55:44 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:1400 - Capturing at 33.33 fps, capturing bandwidth 1127522bytes/sec]
May 12 10:55:44 immagine-zoneminder /zm_detect.py[713]: ERR [zmesdetect_m1] [Error downloading files: <urlopen error [Errno 110] Connection timed out>]
May 12 10:55:44 immagine-zoneminder /zm_detect.py[713]: FAT [zmesdetect_m1] [animation: Traceback:Traceback (most recent call last):
  File "/usr/lib/python3.6/urllib/request.py", line 1325, in do_open
    encode_chunked=req.has_header('Transfer-encoding'))
  File "/usr/lib/python3.6/http/client.py", line 1264, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/lib/python3.6/http/client.py", line 1310, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.6/http/client.py", line 1259, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.6/http/client.py", line 1038, in _send_output
    self.send(msg)
  File "/usr/lib/python3.6/http/client.py", line 976, in send
    self.connect()
  File "/usr/lib/python3.6/http/client.py", line 948, in connect
    (self.host,self.port), self.timeout, self.source_address)
  File "/usr/lib/python3.6/socket.py", line 724, in create_connection
    raise err
  File "/usr/lib/python3.6/socket.py", line 713, in create_connection
    sock.connect(sa)
TimeoutError: [Errno 110] Connection timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/var/lib/zmeventnotification/bin/zm_detect.py", line 218, in <module>
    args)
  File "/usr/local/lib/python3.6/dist-packages/zmes_hook_helpers/utils.py", line 145, in download_files
    input_file = opener.open(url)
  File "/usr/lib/python3.6/urllib/request.py", line 526, in open
    response = self._open(req, data)
  File "/usr/lib/python3.6/urllib/request.py", line 544, in _open
    '_open', req)
  File "/usr/lib/python3.6/urllib/request.py", line 504, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.6/urllib/request.py", line 1353, in http_open
    return self.do_open(http.client.HTTPConnection, req)
  File "/usr/lib/python3.6/urllib/request.py", line 1327, in do_open
    raise URLError(err)
urllib.error.URLError: <urlopen error [Errno 110] Connection timed out>
]
May 12 10:55:44 immagine-zoneminder zmeventnotification[709]: INF [|----> FORK:Amcrest Test (1), eid:21 Event 21 for Monitor 1 has finished]
May 12 10:55:46 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 1300 - Analysing at 25.00 fps]
May 12 10:55:48 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:1500 - Capturing at 25.00 fps, capturing bandwidth 936160bytes/sec]
May 12 10:55:50 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 1400 - Analysing at 25.00 fps]
May 12 10:55:50 immagine-zoneminder zmeventnotification[709]: INF [|----> FORK:Amcrest Test (1), eid:21 Not sending event end alarm, as we did not send a start alarm for this, or start hook processing failed]

Any ideas?

Link to comment
8 hours ago, edif30 said:

@dlandon Not sure if you can help or not but I seem to have GPU support up and running and I confirmed at the end of the opencv compile that CUDA support was enabled.

 

I am running into an issue where the monitor is up and in modetect.  It sees the alarm but when it invokes the object detection, there seems to be a timeout.  I just don't know where.

 

Here is the logs...

 


May 12 10:55:12 immagine-zoneminder zmeventnotification[690]: INF [PARENT: New event 21 reported for Monitor:1 (Name:Amcrest Test) Motion All[last processed eid:]]
May 12 10:55:13 immagine-zoneminder /zm_detect.py[713]: INF [zmesdetect_m1] [---------| hook version: 5.13.3, ES version: 5.13-Docker , OpenCV version: 4.2.0-dev|------------]
May 12 10:55:13 immagine-zoneminder /zm_detect.py[713]: INF [zmesdetect_m1] [Importing local classes for Yolo/Face]
May 12 10:55:13 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 400 - Analysing at 33.33 fps]
May 12 10:55:14 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:500 - Capturing at 33.33 fps, capturing bandwidth 1140084bytes/sec]
May 12 10:55:17 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 500 - Analysing at 25.00 fps]
May 12 10:55:18 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:600 - Capturing at 25.00 fps, capturing bandwidth 924088bytes/sec]
May 12 10:55:20 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 564 - Left alarm state (21) - 255(3) images]
May 12 10:55:20 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 564 - Closing event 21, alarm end]
May 12 10:55:21 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 600 - Analysing at 25.00 fps]
May 12 10:55:21 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:700 - Capturing at 33.33 fps, capturing bandwidth 1040577bytes/sec]
May 12 10:55:24 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:800 - Capturing at 33.33 fps, capturing bandwidth 1139824bytes/sec]
May 12 10:55:24 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 700 - Analysing at 33.33 fps]
May 12 10:55:28 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:900 - Capturing at 25.00 fps, capturing bandwidth 924154bytes/sec]
May 12 10:55:28 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 800 - Analysing at 25.00 fps]
May 12 10:55:31 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:1000 - Capturing at 33.33 fps, capturing bandwidth 1038018bytes/sec]
May 12 10:55:31 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 900 - Analysing at 33.33 fps]
May 12 10:55:34 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:1100 - Capturing at 33.33 fps, capturing bandwidth 1144528bytes/sec]
May 12 10:55:35 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 1000 - Analysing at 25.00 fps]
May 12 10:55:38 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:1200 - Capturing at 25.00 fps, capturing bandwidth 917746bytes/sec]
May 12 10:55:39 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 1100 - Analysing at 25.00 fps]
May 12 10:55:41 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:1300 - Capturing at 33.33 fps, capturing bandwidth 1031943bytes/sec]
May 12 10:55:42 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 1200 - Analysing at 33.33 fps]
May 12 10:55:44 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:1400 - Capturing at 33.33 fps, capturing bandwidth 1127522bytes/sec]
May 12 10:55:44 immagine-zoneminder /zm_detect.py[713]: ERR [zmesdetect_m1] [Error downloading files: <urlopen error [Errno 110] Connection timed out>]
May 12 10:55:44 immagine-zoneminder /zm_detect.py[713]: FAT [zmesdetect_m1] [animation: Traceback:Traceback (most recent call last):
  File "/usr/lib/python3.6/urllib/request.py", line 1325, in do_open
    encode_chunked=req.has_header('Transfer-encoding'))
  File "/usr/lib/python3.6/http/client.py", line 1264, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/lib/python3.6/http/client.py", line 1310, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.6/http/client.py", line 1259, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.6/http/client.py", line 1038, in _send_output
    self.send(msg)
  File "/usr/lib/python3.6/http/client.py", line 976, in send
    self.connect()
  File "/usr/lib/python3.6/http/client.py", line 948, in connect
    (self.host,self.port), self.timeout, self.source_address)
  File "/usr/lib/python3.6/socket.py", line 724, in create_connection
    raise err
  File "/usr/lib/python3.6/socket.py", line 713, in create_connection
    sock.connect(sa)
TimeoutError: [Errno 110] Connection timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/var/lib/zmeventnotification/bin/zm_detect.py", line 218, in <module>
    args)
  File "/usr/local/lib/python3.6/dist-packages/zmes_hook_helpers/utils.py", line 145, in download_files
    input_file = opener.open(url)
  File "/usr/lib/python3.6/urllib/request.py", line 526, in open
    response = self._open(req, data)
  File "/usr/lib/python3.6/urllib/request.py", line 544, in _open
    '_open', req)
  File "/usr/lib/python3.6/urllib/request.py", line 504, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.6/urllib/request.py", line 1353, in http_open
    return self.do_open(http.client.HTTPConnection, req)
  File "/usr/lib/python3.6/urllib/request.py", line 1327, in do_open
    raise URLError(err)
urllib.error.URLError: <urlopen error [Errno 110] Connection timed out>
]
May 12 10:55:44 immagine-zoneminder zmeventnotification[709]: INF [|----> FORK:Amcrest Test (1), eid:21 Event 21 for Monitor 1 has finished]
May 12 10:55:46 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 1300 - Analysing at 25.00 fps]
May 12 10:55:48 immagine-zoneminder zmc_m1[661]: INF [zmc_m1] [Amcrest Test: images:1500 - Capturing at 25.00 fps, capturing bandwidth 936160bytes/sec]
May 12 10:55:50 immagine-zoneminder zma_m1[665]: INF [zma_m1] [Amcrest Test: 1400 - Analysing at 25.00 fps]
May 12 10:55:50 immagine-zoneminder zmeventnotification[709]: INF [|----> FORK:Amcrest Test (1), eid:21 Not sending event end alarm, as we did not send a start alarm for this, or start hook processing failed]

Any ideas?

I can't offer any support for ES.  Check the ES link on the first post for support.

Link to comment
  • 2 weeks later...

I just installed this docker a couple days ago and am learning a bit as I go here.  Long time zoneminder user, but noob with dockers.  By following the first post and related links, to my surprise, I already have Object detection functioning and am working on face detection, but so far no luck.  CUDA stuff will be next and I have set all the Docker ENV variables to yes to install so YOLO, CUDA, face detection software etc, in theory, should all be there.

 

To help in my troubleshooting I just want to ask if anyone can confirm they have face detection actually working on the latest docker version.  Does anyone have it working right now?  That will help me narrow down to just config or if possibly some file or libraries etc could be missing or something in the actual docker container too.  So far I see docker logs of the object detection running on an event but when I would expect the face detection to kick in there's just nothing/blank in the logs. Not even an error to go off so far.

 

-EDIT- Did a force update/rebuild of the docker and face detection is now functional.

Edited by mikeg_321
Update / answer to question.
Link to comment

I have managed to now get GPU support mostly working by following the first post instructions as well.  That said, I noticed by running watch nvidia-smi on my unRaid box that you can see the GPU working when using YOLO, but not when running face recognition.  Again curious as to whether anyone else sees this or if I have done something incorrect.  Some googling lead me to this link:  Get CUDA working...  I believe the DLIB section is pertinent, but not 100% sure.  When I do ">>> dlib.DLIB_USE_CUDA" in Python/Docker it comes back False and maybe should be True.  Any comments as to getting face recognition to work via GPU?  

Link to comment
  • 2 weeks later...

Hello all, having an issue setting up cron for Zoneminder, when I run the commands manually they work, however I continually receive the "no crontab for root" error when I run crontab -l within the console.

 

My file is currently named as 'cron.cron' within the appdata/Zoneminder/ folder.

 

I have tried creating this document 5 ways to Sunday, using:

Notepad

Notepad ++

binhex-Krusader

 

And nothing has worked for me. I have read @dlandon first post multiple times and do not understand what I could be doing wrong.

 

Any help from you linux Gurus would be fantastic as I really don't have much of a linux background.

 

My current cron file includes the following:

 

# Daytime camera operation away
30 6 * * * /usr/bin/zmpkg.pl away

# Daytime camera operation home
0 17 * * * /usr/bin/zmpkg.pl home

# Nightime Camera operation sleep
0 21 * * * /usr/bin/zmpkg.pl sleep

 

cron.cron

Link to comment
25 minutes ago, crspangenberg said:

Hello all, having an issue setting up cron for Zoneminder, when I run the commands manually they work, however I continually receive the "no crontab for root" error when I run crontab -l within the console.

 

My file is currently named as 'cron.cron' within the appdata/Zoneminder/ folder.

 

I have tried creating this document 5 ways to Sunday, using:

Notepad

Notepad ++

binhex-Krusader

 

And nothing has worked for me. I have read @dlandon first post multiple times and do not understand what I could be doing wrong.

 

Any help from you linux Gurus would be fantastic as I really don't have much of a linux background.

 

My current cron file includes the following:

 


# Daytime camera operation away
30 6 * * * /usr/bin/zmpkg.pl away

# Daytime camera operation home
0 17 * * * /usr/bin/zmpkg.pl home

# Nightime Camera operation sleep
0 21 * * * /usr/bin/zmpkg.pl sleep

 

cron.cron 211 B · 0 downloads

Your file does not have Linux new lines.  Linux new lines are line feeds only.  You need to be sure the editor is creating the file with Linux new lines only.

See attached file that I converted.

cron.cron

Link to comment

@dlandon thank you for the response, I used this file and am still receiving the same error after both restarting the container and stopping and starting the container. 

 

As far as the line feeds, I have notepad++ set to Linux for EOL. I will continue to google that information to gain a better understanding.

 

I have attached the console error as well as the current file structure location for the cron file.

 

 

noCrontab.PNG

file location.PNG

Link to comment
11 minutes ago, crspangenberg said:

@dlandon thank you for the response, I used this file and am still receiving the same error after both restarting the container and stopping and starting the container. 

 

As far as the line feeds, I have notepad++ set to Linux for EOL. I will continue to google that information to gain a better understanding.

 

I have attached the console error as well as the current file structure location for the cron file.

 

 

noCrontab.PNG

file location.PNG

The file name is cron, not cron.cron.

Link to comment

Loving the setup of my new unRAID server and found this docker to be super useful for setting up my home cctv/security system... Thank you.... Really struggling to find information about how to set up ZM ninja properly for use when I'm not in my local network. From what i can find. I need to use duckdns and lets encrypt along with some port forwarding. Spaceinvader One's video covers the basic setup. But I have no clue how to make the custom subdomain.conf file for Zoneminder. Tested several variations with no success. Can someone please point me in the right direction. zmNinja has some documentation here but again I'm pretty noob to all of this. TIA.  

Link to comment
On 4/16/2017 at 5:11 AM, dlandon said:

There is a 'hook' feature of zmeventnotification where processing after an event can be hooked for custom processing.  An appdata/Zoneminder/hook folder is created and the files installed that you will need for custom event processing.  The hook models can be downloaded and installed for you by setting two environment variables.  You can install either the Tiny Yolo or the Yolo models or both.

 

Set INSTALL_TINY_YOLO="1" to install the Tiny Yolo model.  Set INSTALL_YOLO="1" to install the Yolo model.

 

The hook files require additional python modules.  The Docker will load the hook modules and run 'setup.py' if you set an environment variable INSTALL_HOOK="1".  The initial install takes a long time.

 Hi everyone, I'm looking to switch from shinobi over to zoneminder (like 30 minutes new to ZM).  I have a fresh ZM install where i've set the variables to install yolo and hook.   What I'm not clear on at the moment is how to enable the hooks / object detection / processing

  1. Does the unraid install xml _also_ configure zoneminder with this stuff already enabled / configured?
  2. If not, do I need to get into the zm container via shell and update some ini files to enable?
  3. When configured, do i need to make specific camera changes to enable hook / object detention processing (or is that already happening based on event id or is that some setting in the zm guide?

 

I did browse through a couple of the links the dev/op mentioned but still a little fuzzy about it.   Any direction regarding the above configuration would be appreciated.


 

Edited by repomanz
Link to comment
8 hours ago, repomanz said:

Does the unraid install xml _also_ configure zoneminder with this stuff already enabled / configured?

ES (Event Server) is installed but not enabled until you enable it through a configuration setting in ZM.  The hook processing requires additional setup through the .ini files in the appdata/Zoneminder folder after you install the docker with the environment variables set for your needs.

8 hours ago, repomanz said:

If not, do I need to get into the zm container via shell and update some ini files to enable?

The nice thing about this docker is that you don't need to get inside the docker image and make changes.  All configuration settings are in the appdata/Zoneminder forlder.

8 hours ago, repomanz said:

When configured, do i need to make specific camera changes to enable hook / object detention processing (or is that already happening based on event id or is that some setting in the zm guide?

The cameras don't need any special setup.  ZM collects the images from the cameras, creates the event and ES picks up the events and does it's processing.

Link to comment

Hi Everyone.

 

I'm trying to troubleshoot why my pushover.net functionality is not working.  This is in zm log:


PARENT: Pushes will be sent through APIs and will use /var/lib/zmeventnotification/bin/pushapi_pushover.py

 

going into appdata/Zoneminder doesn't have this script, neither is it in the container itself.   Files in the path above (inside container):

 

/var/lib/zmeventnotification/bin# ls -l
total 16
lrwxrwxrwx 1 root root 25 Jun 13 15:35 zm_detect.py -> /config/hook/zm_detect.py
lrwxrwxrwx 1 root root 28 Jun 13 15:35 zm_event_end.sh -> /config/hook/zm_event_end.sh
lrwxrwxrwx 1 root root 30 Jun 13 15:35 zm_event_start.sh -> /config/hook/zm_event_start.sh
lrwxrwxrwx 1 root root 30 Jun 13 15:35 zm_train_faces.py -> /config/hook/zm_train_faces.py


within secrets.ini I have updated the last two lines with my user and app key based on my pushover.net account.   I have pushover installed on my android phone as well.  further; I have enabled in the zmeventnotifiction.ini

 

[push]
# This is to enable sending push notifications via any 3rd party service.
# Typically, if you enable this, you might want to turn off fcm
# Note that zmNinja will only receive notifications via FCM, but other 3rd
# party services have their own apps to get notifications


use_api_push = yes


# This is the script that will send the notification
# Some sample scripts are provided, write your own
# Each script gets:
# arg1 - event ID
# arg2 - Monitor ID
# arg3 - Monitor Name
# arg4 - alarm cause
# arg5 - Type of event (event_start or event_end)
# arg6 (optional) - image path


api_push_script=/var/lib/zmeventnotification/bin/pushapi_pushover.py

So, it appears as if the container is missing the pushapi_pushover.py or it's pointed to the wrong path.  Whats the correct path?
 

**edit, i found the plugin for this and have added it specifically into the container.  Should I make this accessible like the other configuration files so i can get to it via /appdata/Zoneminder/push?  If so what's the correct symbolic link syntax?  I tried ln -s source target but didn't seem to work correctly in the container.

@dlandon would you mind including this script in the build container sometime?


 

Edited by repomanz
Link to comment
  • 2 weeks later...
22 minutes ago, dlandon said:

The Docker does not install that file.  You'll have to download the pushapi_pushover.py and install it at /var/lib/zmeventnotification/bin/pushapi_pushover.py.

 

I'll have to look at updating the Docker to install that file.

Thanks for the consideration!

Link to comment
On 2/24/2019 at 8:29 PM, Mlatx said:

Thanks.  I did some more research and got a working zoneminder.subdomain.conf file (I am using my own subdomain).

 

I have the following:

 

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name zoneminder.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location /zm {
        include /config/nginx/proxy.conf;
        proxy_pass https://IPADDRESSOFYOURSERVER:8443/zm;
    }
}
 

Just wanted to say Thanks for providing this .conf output! I was able to use it and now have it configured to use with zmNinja away from home.

Link to comment

I have everything setup and currently only testing with one camera (only have a total of 4) but I would like to store data to an unassigned 3TB drive instead of my 500gb ssd cache. I'm not finding any documentation on how to change the storage. I tried under Settings and Storage but it's not seeing the unassigned drive. I then modified the container "Data Path" and was not able to launch the URL. Do I need to move the current data from /mnt/user/appdata/Zoneminder/data/ to the unassigned disk then make the change to the container? I would like to just move the 'Events' folder to the unassigned disk if possible.

Link to comment
6 hours ago, fonz88 said:

I have everything setup and currently only testing with one camera (only have a total of 4) but I would like to store data to an unassigned 3TB drive instead of my 500gb ssd cache. I'm not finding any documentation on how to change the storage. I tried under Settings and Storage but it's not seeing the unassigned drive. I then modified the container "Data Path" and was not able to launch the URL. Do I need to move the current data from /mnt/user/appdata/Zoneminder/data/ to the unassigned disk then make the change to the container? I would like to just move the 'Events' folder to the unassigned disk if possible.

You need to move the data, but you can't just move Events.  You need to move the complete data/ folder.  The database will be out of synch if you don't.

 

I would:

- Remove the Docker.

- Move the data/ folder to your UD Disk.

- Reinstall the Docker and map the data to your UD disk.

Link to comment

Had an issue with the Facial recognition script. When it detects an unknown face it stores it in /var/lib/zmeventnotifications/unknown_faces however it couldnt create the folder due to permissions issues. I created the folder and set up a symlink to the appdata folder so I can view them easily and copied the permisions from the known_faces folder using chmod. Is this something that can be put in the dock container?

Link to comment
  • 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.