IntroAfter getting feed up with Windows 10 issues I'm checking out Zoneminder. First things first start with a clean CentOS 7 install since I ran into all kinds of conflicts trying to install on boxes with other things already running. xrdp for instance will keep you from installing vlc which Zoneminder needs.
Installing base CentOS 7
These instructions are great other than instead of minimal configuration, select Gnome desktop and select all sub packages, otherwise follow the instructions in the link
After it reboots accept the EULA and take defaults for basic config. Check for and install any outstanding updates.
The rest of the set up can be done remotely as root logged in via ssh
Create user with sudo access
If system uses the simple wheel group membership you can use
usermod -aG wheel username
Otherwise edit /etc/sudoers to get granular.
To avoid conflicts DO NOT install anything else before Zoneminder!
Install ZoneminderFollow the instructions from here.
sudo yum install --nogpgcheck zmrepo-7-9.el7.centos.noarch.rpm
sudo yum install zoneminder
The last line above is more instructions. Follow them with these caveats:
sudo dnf install mariadb-server should be
sudo yum install mariadb-server
Note it is important to install mariadb-server and NOT mysqld or try and use a remote db since this seems to currently keep Zomeminder from starting.
Note when you see something like
mysql -uroot -p -e "grant all on zm.* to \
'zmuser'@localhost identified by 'zmpass';"
It is better to enter as
mysql -uroot -p -e "grant all on zm.* to 'zmuser'@localhost identified by 'zmpass';"
since \ seems to get lost sometimes when copy pasting into ssh sessions.
At sudo systemctl start zoneminder is where you know if things worked.
Note if you want to be able to access Zoneminder other than from a browser on the box itself also run the commands
sudo firewall-cmd --permanent --zone=public --add-port=80/tcp
sudo firewall-cmd --permanent --zone=public --add-port=443/tcp
sudo firewall-cmd --reload
You can now go to the console via your browser. If you are on the box you can use the IP address of 127.0.0.1 otherwise substitute your server's IP address for 10.10.2.191 in this URL
Setting up camerasFor details check out the Getting Started section of the user guide. Note the set up section appears to be out of date as some of the tabs had different or more options when I setup a camera for this test.
Setup is not nearly as simple as Blue Iris which generally just figures it out from an IP address and a login. Since you will probably end up Googling what to use to make it work with your camera I won't go into steps here.
First impressionsI got Zoneminder to work by spinning up a new copy of CnetOS 7 on one of my test PCs.
The interface is no where near as finished or as easy to use as Blue Iris. Plan on looking up what to put into config boxes and playing with options to get them to work. For example to configure the video stream on ZomeMinder per their Wiki looks like this
The equivalent window on Blue Iris looks like this
Load wise a single Amcrest 2K cam on Zoneminder appears to max out a Core 2.
For comparison that same camera plus 12 others are recording 24/7 with motion detection on the i7 server now with an average core load of 46%.
Granted the i7 is faster but not that much faster. About 3 times faster according to this.
Finally for me I'm looking for something that lets me have a monitor (3 actually) showing the cams so I can just glance up when I get an alert or hear the dogs barking that something is happening.
The Zoneminder interface seems to be oriented to record now and watch later. That is fine if that is all you need but if you want to be able actively monitor multiple cams it won't cut it.
- moving the swap file to another hard drive
- running hardware diagnostics
- Windows troubleshooters
- trying fixes I found on line
- reinstalling Blur Iris
- and even swapping out the graphics card, since the symptoms were the Blue Iris console locking up and Windows programs not updating bits of the screen
I ended up restoring from the restore disks which put the system back to Windows 7. After installing upgrades and all the software (Blue Iris, apcupsd, cygwin and ODrive) it is working great again. Kind of confirms it was a Windows 10 issue.