repomanz

@dlandon sent you a pm

I believe you're correct here; looking through dlandon's container based on a fresh install (this morning) it appears even eventserver items have been stripped. Therefore within this container; I am unable to configure a remote ML server as that information / configuration exists within the objectconfig.ini which is no longer there. further, the mlapi project looks to have dependencies with zm itself, for example in the documentation states you need to run: python3 mlapi_adduser.py but it errors because the ./db path is empty. I can only assume that is zoneminder's db path which doesn't exist on a separate vm while being used by dlandon's container. I may have to move everything to a separate VM to get going again. Side note; are there any ubuntu 20 containers out there I can install on unraid? I really wanted the GPU configuration of this installation but I can't hook both in containers and vm's at the same time.

So I understand fully; your container will have zm and es? What about hooks or is that part of the ML install?

@dlandon I'm saddened you're dropping ES/ML from your container but definitely understand your view and desire to simplify what you're supporting. Thanks for all you've done! Is it possible those that want to keep ES/ML within this container to do so? I can't really do a VM because within unraid the GPU can't be shared across VM and Docker containers and used at the same time.

This was a fresh install based on yesterday's update. I didn't notice an error when opencv was compiling. Are there any build logs I can provide?

Hi @dlandon Understood. That's what I'm pointing out. I watched the logs during install and opencv took about 20 minutes to compile. I had to add that package specifically into the container in order to fix cv2. Maybe there is a dependency issue with the libraries being called for compile? thx for adding pushover.

@dlandon Does your container contain python cv2 module? Getting this error with ML side of event server. root@43f7cbf04308:/# sudo -u www-data /var/lib/zmeventnotification/bin/zm_detect.py --config /etc/zm/objectconfig.ini --eventid 152 --monitorid 1 --debug Traceback (most recent call last): File "/var/lib/zmeventnotification/bin/zm_detect.py", line 15, in <module> import imutils File "/usr/local/lib/python3.8/dist-packages/imutils/__init__.py", line 8, in <module> from .convenience import translate File "/usr/local/lib/python3.8/dist-packages/imutils/convenience.py", line 6, in <module> import cv2 oot@43f7cbf04308:/# python3 Python 3.8.5 (default, Jul 28 2020, 12:59:40) [GCC 9.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import cv2 Traceback (most recent call last): File "<stdin>", line 1, in <module> ModuleNotFoundError: No module named 'cv2' This is based on the information here: https://zmeventnotification.readthedocs.io/en/latest/guides/hooks.html?highlight=cv2#make-sure-opencv-works This is brand new installation. edit: I think I solved this by going into container and running this command: sudo pip3 install opencv-python Shouldn't this be included in your build process for the container? I also noticed that the pushover py file was missing from /var/lib/zmeventnotification/bin After adding pushover py script and manually adding the opencv-python to the container my complete solution (zm/es/ml) is now working.

Hey everyone - for those doing ES/ML I have a question. I have cuda / gpu enabled zoneminder container; should I be seeing some other process related to el/ml hanging on to the graphics card? the 3 zmc processes you see below are my high res monitors (nodetect) and use gpu to convert the 5mp stream down in size.

good stuff here, possible should be added in first post when people run into the shm / db corrupt issue.

quick update. To test out the shm issue corrupting db I restored an older zoneminder folder and installed again. The upgrade did work. What isn't working post upgrade is object detection / event server related stuff. This was working per the previous zoneminder version (pre template change) Is this what others have experienced? Do you know what the issue is?

going to restore a zoneminder folder from a previous backup, this time using shm 16g. wish me luck

I use those myself. Are you saying the switches are no longer applicable given the new template?

I think something else is going on. For example, my monitor picked up motion and recorded it but I don't see anything in the log ui for zmdetect. Any pointers here?

I'm trying to figure this one out after rebuilding the container from scratch. Anyone here know what this may be about? |----> FORK:garage-low-res (1), eid:96 Not sending event end alarm, as we did not send a start alarm for this, or start hook processing failed

Through unraid ui how does that happen given the template change? I saw the update available in the Unraid UI and updated the container. That's how easy it is to stumble into this issue (assuming improper shm size in template led to db corruption).

This is my favorite unraid docker container and I don't mind rebuilding it but would like to prevent others from likely corruption as it's not obvious. Is there anything in your build process with the new template to prevent people from stumbling into this issue? Meaning they need to set the previous shm value into the new template before the upgrade will even start?

No problem. Is there a way we can debug this? My new install completed including a fresh zoneminder app data directory and it comes up with no problem (except all my configurations / cameras are gone).

In the old directory where I tried to update the flag file is 10.1. Maybe that's the issue?

New version is building now (compiling opencv) but I took a look at the mysql directory and the debian flag file is debian-10.3.flag. Not sure if that matters or not but wanted to point it out. In my old directory it's 10.1

@dlandon I renamed my zoneminder folder (appdata) and doing a completely new install. Not that I wanted to do that but wanted to test. I noticed something in the mysql folder relating to debian and I thought I saw a reference above that the new version uses ubuntu New version is building now (compiling opencv) but I took a look at the mysql directory and the debian flag file is debian-10.3.flag. Not sure if that matters or not but wanted to point it out.

same here. I'm broke currently.

deleted docker, reinstalled with shm set to 16gb. No luck. is that the correct template URL?

Was using the previous one defined in the template before this update. I didn't change anything there. Doing another re-install with the shm defined at the start to see if that does anything different. Update: no change after removing docker and image with fresh installation with shm set to 16g at the start of install.

HI @dlandon Thank you. I tried that and still having issues with mariadb starting. I have 32gb installed and even with shm set at 24G (75%) I still get the error starting up db. Other suggestions? I did notice this however: Starting services... * Starting Apache httpd web server apache2 * * Starting MariaDB database server mysqld * Starting MariaDB database server mysqld Jan 3 15:54:29 2640f3f29b3b web_php[623]: FAT [Failed db connection to ] mariadb starting up twice?