ZoneMinder Forums

I just ran into this same issue.
Not sure how to tackle this error

Seems the Dockerfile is missing. Found zmdockerfiles https://github.com/ZoneMinder/zmdockerfiles/blob/master/buildsystem/ubuntu/impish/Dockerfile With the following result : ~/dev/zoneminder$ docker build -t linuxlover9/zm-1.36.33-chk . [+] Building 4.1s (7/10) docker:default => [internal] load ...

OK, I have test docker running from source zoneminderhq/zoneminder:latest-ubuntu18.04.
How can I run my local code?
Do I have to do a cmake? what are the options?

At https://github.com/ZoneMinder/zoneminder/wiki/Docker it describes the setup of a dev environment in docker. I'm trying to follow it, and it's complaining about : chris@aurora:~/dev/zm-docker$ docker buildx build -t='linuxlover9/release-1.36.33' github.com/ZoneMinder/zoneminder [+] Building 8.6s ...

That would be great!
If you can give me a hint, I can try to do a pull request and have a go at it.
I've never looked at the code, but could give it a try...

While running in a docker container, there is no syslog logs to check for permission failures - that I have found thus far. After explicitly setting the owner to www-data the trigger started to fire : root@023c028759ee:/# chown www-data /var/www/scripts/* root@023c028759ee:/# ls -l /var/www/scripts ...

I'm trying to create an action for a trigger of one alarm zone and not another alarm zone : zm-error-filter1.png This is the debug : SQL SELECT E.,M.Name AS MonitorName,M.DefaultScale FROM Monitors AS M INNER JOIN Events AS E ON (M.Id = E.MonitorId) WHERE E.TotScore > '30' and / AlarmedZoneId ...

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2451688 root 20 0 47088 36480 2432 R 93.8 0.2 498:19.77 zmaudit.pl 2612198 911 20 0 7032 5760 1152 R 78.0 0.0 3:21.84 rm 2456700 911 20 0 2601296 2.0g 38528 S 72.1 13.1 341:37.29 zmc 1352027 911 20 0 621832 219352 11984 S 1.5 1.4 100:03.61 zmc ...

My diskspace fulled up as the purge filters did not work properly, so I had to manually delete events to allow enough space for ZM to restart. Now I'm getting constantly these warnings in the logs, and they don't seem to disappear. I first though it just would purge the indexes of all the deleted ...

iconnor wrote: ↑Wed Mar 13, 2024 1:19 pm Your script has to get return a value of 0 for success. You don't explicitly set a return value, so it will be whatever the return value of the last line is.

Thank you, that makes sense.

I'm still not sure it's working, due to filled up logs. Will open a separate thread for that.

I just upgraded to docker version 1.36.33 from 1.36.32 to see if this fixed my issue, but to no avail. I have a folder : root@023c028759ee:/# ls -l /var/www/scripts/ total 8 -rwxrwxr-x 1 1000 1000 118 Mar 12 22:48 trigger.sh -rwxrwxr-x 1 1000 1000 32 Mar 12 23:08 zm-approach -rw-rw-r-- 1 1000 1000 0 ...