Zoneminder(HOW TO)

From SME Server
Revision as of 08:23, 16 January 2016 by RequestedDeletion (talk | contribs) (Start Zoneminder at boot)



ZoneMinder is intended for use in single or multi-camera video security applications, including commercial or home CCTV, theft prevention and child, family member or home monitoring and other domestic care scenarios such as nanny cam installations. It supports capture, analysis, recording, and monitoring of video data coming from one or more video or network cameras attached to a Linux system. ZoneMinder also support web and semi-automatic control of Pan/Tilt/Zoom cameras using a variety of protocols. It is suitable for use as a DIY home video security system and for commercial or professional video security and surveillance. It can also be integrated into a home automation system via X.10 or other protocols.

Important.png Note:
Zoneminder is available as a contribs, but that is a very old one for SME server 7. Today, Zoneminder has it's own easy repository, and hopefully these instructions can be turned into a new updated contrib. For now, this how-to is intended to be used with IP camera's only.



Zoneminder is available from the Zoneminder repository. You need to configure the zmrepo as explained here.

Install Zoneminder from the zmrepo

yum install zoneminder --enablerepo=zmrepo

Zoneminder's configuration file is located at /etc/zm.conf. Not really known if it is required, but you can change the Apache user in the zm.conf file from apache:apache to www:www, and double check the database credentials in the same file with the ones you have used.

MySQL database

Zoneminder works 'best' with InnodeDB enabled. As root issue:

db configuration setprop mysqld InnoDB enabled
expand-template /etc/my.cnf
sv t /service/mysqld

Zoneminder uses MySQL for the storage of picture data, so we need to create a new database. As root issue:

create database zm;
grant all privileges on zm.* to zmuser identified by 'zmpass';
flush privileges;

Then we populate the new database:

mysql zm < /usr/share/zoneminder/db/zm_create.sql

The above bold credentials should be replaced by your own information.

Important.png Note:
Once somebody starts creating a contrib, the above credentials should be in a db key e.g. zoneminder and DBUser, DBPass, so the configuration files will be templated and auto generated by an event

Create custom templates

mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/
cp /etc/httpd/conf.d/zoneminder.conf /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/98zoneminder
rm -f /etc/httpd/conf.d/zoneminder.conf
sed -i "18i AddType application/x-httpd-php .php" /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/98zoneminder
sed -i "19i AuthBasicProvider external" /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/98zoneminder 
sed --in-place '/DELETE/d' /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/98zoneminder
expand-template /etc/httpd/conf/httpd.conf
service httpd-e-smith restart
Important.png Note:
Please note that the above templates do not implement any authentication to access the Zoneminder portal (webinterface). Options could be specific users (e.g. admin) or all valid SME users.

Start Zoneminder at boot

config set zoneminder service status enabled 
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S98zoneminder
Important.png Note:
Need the find out the correct way to start the service for the mysqlinit process (which starts after the zoneminder service) will have MySQL restarted whilst Zoneminder is using it. The Zoneminder service has to be restarted manually.

Important.png Note:
We still need to add the various TCPPort(s) to the db to open up the firewall if remote (off LAN) camera's are being used.

You can now start Zoneminder manually:

service zoneminder start

And access the Zoneminder portal at, and login as admin admin

Acces Zoneminder via sub domain

Instead of accessing the Zoneminder portal at, it is possible to change this to e.g. For this the easiest and comfortable way is to use the webapps-common contrib.

Important.png Note:
This part assumes you have followed the complete above installation procedure.

Install the webapps-common contrib according to the how-to. Then (as per example for issue the following as root:

db domains set domain Description "CCTV" Content Primary \
Nameservers internet TemplatePath WebAppVirtualHost \
DocumentRoot /usr/share/zoneminder/www RequireSSL enabled
signal-event domain-create

Next you need to adjust the existing (from above) custom template (make a backup copy first):

sed --in-place '/Alias/d' /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/98zoneminder

Followed by:

signal-event webapps-update

to activate all changes. Now you can reach your zoneminder portal at


To uninstall Zoneminder and all it's dependencies, we will use the yum history to uninstall all dependencies that came with the initial installation, but are no longer required as we remove Zoneminder. Stop Zoneminder:

service zoneminder stop

First we need to check the yum transaction ID that installed Zoneminder. As root issue:

yum history package-info zoneminder

the result is all yum knows about the Zoneminder package. We are interested in the Transaction ID. Next we uninstall Zoneminder and all it's dependencies based on the number of the Transaction ID:

yum history undo Transaction ID number

and confirm the uninstallation of Zoneminder and all dependencies.

Important.png Note:
The removal of the Zoneminder RPM will fail due to a dependency on SELinux which SME Server does not use. An additional command is required to uninstall the Zoneminder RPM. To ensure proper removal of all dependencies, only the Zoneminder RPM will be removed without executing the uninstall scripts included in the RPM.

yum --setopt=tsflags=noscripts remove zoneminder

Then we need to remove the custom template, the symlink that we created to start Zoneminder at boot and the subdomain that we may have created:

rm -f /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/98zoneminder
rm -f /etc/rc7.d/S98zoneminder
signal-event domain-delete
signal-event webapps-update

Now to cleanup everything you may want to perform the usual post-upgrade and reboot events. All that is left is the MySQL database zm and the logfiles. It's up to you what to do with them.