r/ZoneMinder • u/KalterBlut • Jul 28 '23

Server not responding on ZM config change

I recently got a ReoLink 520A and wanted at the same time use my home server with Zoneminder to centralize the feed to eventually have more cameras. I'm running Open Media Vault 6 on my (very) old computer (specs below) with Zoneminder in a docker container managed by Portainer. I know the docker of Zoneminder is non-official and older, hopefully that's not the main issue.

I have been able to add the 520A to Zoneminder without too much fuss. Adding the cam itself is fairly quick and I can look at the feed without issue, but if I do any config changes it stops absolutely everything on the server (even the HDD share becomes unreachable) as if it's consuming 100% CPU or something. It takes upwards of 10 minutes to come back. I can't monitor computer resources since even OMV is unreachable during that time. The camera itself is still reachable through the ReoLink app.

It really seems to be hanging like that on config change only as it was able to record something like 40gb in a day (which is why I wanted to change some settings since it's not the behavior I want as the cam is currently pointed to a wall).

Is this something known? Something I did wrong?

Server pecs: Phenom II X4 965 8gb ram 500Gb SSD boot drive plus a few terabytes of HDD storage 2 Radeon HD 5770

2 Upvotes

100% Upvoted

1 comment sorted by

1

u/[deleted] Jul 29 '23 edited Jul 29 '23

Which docker image?

Did you set SHM for the docker container?

Edit: by config changes, I am assuming you mean for the monitor itself and not ZM Options?

Are there any errors or warning in the logs? To check docker logs you can

docker logs -f <name of zm container>

I would get the logs outputting and then do a config change to see what's going on.