ZoneMinder Forums

You can also use docker to have this done with two commands and zero headache. Here is the git repo: https://github.com/hrwebasst/docker-zoneminder Or if you're really lazy just install docker and run these two commands (these three commands will do both) sudo wget -qO- https://get.docker.com/ | sh ...

You definitely need more ram than that I would estimate 16-32GB

Github repository is here: https://github.com/hrwebasst/docker-zoneminder With two commands you can now have zoneminder connected to an external database in a separate docker. Full readme is on my github repo. sudo docker run -d -e MYSQL_ROOT_PASSWORD=uberpass -e MYSQL_DATABASE=zm -e MYSQL_USER=zm -...

wow so it looks like this is the problem the whole flipping time!

umount /dev/shm
mount -t tmpfs -o rw,nosuid,nodev,noexec,relatime,size=2048M tmpfs /dev/shm

fixes this problem. Is there a way around this? Any way we can have zoneminder allocate memory differently? the host has 8gb

So this seems to be your problem. You are out of /dev/shm space. Now you are running ubuntu 14 right? And I assume ZM 1.27 or above? In my case (Ubuntu server 14.04) /dev/shm is a pointer to /run/shm (or /var/run/shm which in turn points to /run/shm). In other words, they are all the same. Can you ...

are you getting socket errors in the logs for second monitor? if so it's very common and no fix to date.

having socket errors on in the log for the second monitor? Seems to be pretty common theme no fix around yet.

Those socket errors happen all over the place at the moment. it's a zoneminder issue. There are a few posts here about the socket errors. It seems like the first monitor works fine and any additional throw an error like this: socket_sendto( /var/run/zm/zms-663764s.sock ) failed: No such file or dire...

well if your docker fails everything will be gone just FYI if you don't pass in your configs. if you need to commit changes you've made inside of a docker do the following: run: sudo docker ps this will output something like this: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES e430db294535 hr...

df -h Filesystem Size Used Avail Use% Mounted on none 5.5T 11G 5.4T 1% / tmpfs 1.9G 4.0K 1.9G 1% /dev shm 64M 64M 0 100% /dev/shm /dev/disk/by-uuid/595c5d58-b12c-4cb4-b475-a5ddd716e310 5.5T 11G 5.4T 1% /etc/hosts meminfo: MemTotal: 7794284 kB MemFree: 3537744 kB MemAvailable: 6492104 kB

NICE! glad to know I'm not the only one. First monitor works fine but second fails with socket error.

And for the record yes my remote host name has http on it but this stupid damn forum kept telling me it was "too spammy" and I had to remove anything that remotely looked like a url.

Okay, here's the setup. I'm running ZM in a docker. I can add the first remote monitor (axis 207) totally fine with: Remote host name: myuser:mypass@192.168.0.22 Remote host path: /axis-cgi/mjpg/video.cgi?resolution=640x480 I'm not sure what's going on and google warrioring didn't turn up much. I ha...

Wish I knew too. Let me know if you figure this out. I'm just getting into ZM. It looks good but so little info on this kind of thing...