ZoneMinder Forums

Ok. I have ZM all up and running. We are trying to monitor at 1920 x 1080. 3 cameras it works fine. Once I change the 4th from 1080x720 to 1920 x 1080 I start getting crashes in the log:

'zmc -m 2' crashed, signal 6

So that pointed me in the direction of maxed out resources somewhere. I read somewhere about increasing tmpfs but that doesn't seem to the the issue here (unless I don't understand that tmpfs relates to the /run/shm). Any help would be greatly appreciated as we are SO close to having this ready to rock and roll!

So with only 3 cameras running df -h shows this

Filesystem Size Used Avail Use% Mounted on
/dev/sda1 228G 1.9G 214G 1% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 986M 4.0K 986M 1% /dev
tmpfs 200M 580K 199M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 997M 816M 181M 82% /run/shm
none 100M 0 100M 0% /run/user

Then with 4 cameras

/dev/sda1 228G 1.9G 214G 1% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 986M 4.0K 986M 1% /dev
tmpfs 200M 580K 199M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 997M 997M 0 100% /run/shm
none 100M 0 100M 0% /run/user

Ok I keep digging into this and I have it fixed temporarily.

I saw this command posted somewhere:

mount -o remount,size=2G /dev/shm


and thought I might as well try:

mount -o remount,size=2G /run/shm

and it worked immediately....but it is only temporary and will go away if the server is rebooted. I am guessing this is something that should go in fstab but my fstab looks like this and I just don't know where or how to put this in:


# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=32ed5e80-2562-4a59-9471-e2c0a8f7fa6a / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=c8c9355f-583d-479b-b7f4-1502a98442f2 none swap sw 0 0

The thing you haven't told us is how much physical memory you have in your system.

A typical limit on the size of /dev/shm is %50 of your physical ram. If you are hitting that limit, you could increase the limit like you have done, but that could cause other problems. You may want to consider adding more memory.