Zoneminder RPM & SRPMS for Red Hat & CentOS 6

[Ruler]

Thanks - installed & configuring now.

[Ruler]

Got it installed and working on CentOS6.4 here. It was MUCH faster & easier than I remember installing on Slackware all those years ago! I have noticed a couple small oddities:

First and most frustrating is that I cannot get the source to turn green. The zmc daemon, when run manually in the same manner as zmdc does, produces an 'illegal instruction' error. There isn't even any debug information written to the file before it dies when debugging is turned on and cranked up to level 9. Not certain if it's specific to the two spectra-8 (4 x bt878 chips) cards in this system or something more generic; with it not dumping out ANY debugging info, I'd guess the latter. Going to try compiling from source to see if that fixes things. Question - what options did you pass to configure to build the RPMs?

Second, ZM tells me that 1.26.4 is out and to download it when logging in. Coming here, 1.26.3 is current, both with these RPMs and on the source code download page. Minor and something that's already been shut off, but thought you should know about. (Don't know if it's specific to the RPM packages or more general though.)

[knight-of-ni]

Kyle has released 1.26.4 as a draft for the moment:
https://github.com/ZoneMinder/ZoneMinder/releases

I guess that triggered the update notification.

After it is made an official release, I will roll a 1.26.4 rpm for it. Rolling the rpm is a manual process so there will be a delay from when 1.26.4 is official and when the 1.26.4 rpm will show up.

Thanks for the tip about SELinux and the auto-probe. I need to add to the SELinux ruleset.

PS: replied to your other thread.

[knight-of-ni]

New RPMS are available for the 1.26.4 Release!

https://github.com/ZoneMinder/ZoneMinder/releases

[DigitalDeviant]

I just ran zoneminder-1.26.4-1.el6.x86_64.rpm to upgrade from 1.26.3 and everything looks like it should have updated OK but it's still showing as 1.26.3 in the web interface.

[knight-of-ni]

Please post the output of zmupdate.pl, including how you executed the command.

[DigitalDeviant]

-bash-4.1# zmupdate.pl --version 1.26.3

Database already at version 1.26.3, update aborted.

[knight-of-ni]

1) Please verify you have followed the upgrade steps exactly:
https://github.com/ZoneMinder/ZoneMinde ... DME.CentOS

2) Was the previous version of zoneminder installed by source or by package?

3) Please post the output of this:

Code: Select all

rpm -qa |grep zoneminder

[DigitalDeviant]

I installed 1.26.3 with the rpm package. 1.26.4 seemed to install OK, rpm -qa |grep zoneminder shows zoneminder-1.26.4-1.el6.x86_64

Since I added the ALTER permissions with the 1.26.3 upgrade I skipped that part of the instructions.

[knight-of-ni]

Ok, then do this for me.

Verify you only have one zm.conf on your system and it is under /etc/:

sudo updatedb
sudo locate zm.conf

Once that has been verified, open /etc/zm.conf and make sure this variable is set correctly:
ZM_VERSION=1.26.4

[DigitalDeviant]

I did find some old zm.conf in an older git build directory and some rmpsave files. I deleted everything except the current zm.conf in /etc. I reran the commands and verified the old files were deleted. Then I checked zm.conf and it lists 1.26.3.

[knight-of-ni]

If you found a zm.conf.rpmnew then that actually was the correct file to keep.
When rpm installs a package, if it detects a config file has been modified by a human, it will save the new config file as filename.rpmnew. Often this is the safest thing to do. However, in your case you actually want it to overwrite the zm.conf file with the new one.

To fix, you might be able to get away with just updating the version string to 1.26.4 in zm.conf, but you should really reinstall the rpm to make sure nothing else in zm.conf is incorrect. It probably isn't but do this to be safe:

Code: Select all

rpm -Uvh --force zoneminder-1.26.4-1.el6.x86_64.rpm

Watch the screen. It will say something like "saved zm.conf as zm.conf.rpmsave".

Once you reinstall, look in zm.conf. If it still says 1.26.3 then do this:

Code: Select all

ls /etc/zm.*

Look for zm.conf.rpmnew.
overwrite zm.conf with zm.conf.rpmnew:

Code: Select all

sudo mv /etc/zm.conf.rpmnew /etc/zm.conf

CORRECTION:
I originally got the definition of rpmsave backwards. The text has been corrected. Here is the official definition:

An .rpmnew file contains the new default configuration file and leaves your original configuration file untouched. By contrast, and .rpmsave file is a copy of your original configuration file, which has been replaced by the new default file.

[DigitalDeviant]

I reinstalled the rpm. No rpmnew or rpmsave. I manually backed up the old zm.conf and reinstalled. This time I got a new default config so I plugged in the db password and now I show version 1.26.4 with one issue. I noticed in the web interface that the version number was red and clicking on it indicated I was running db version 1.26.3. I tried to run zmupdate.pl --version 1.26.4 but it told me I was running 1.26.4 already. I tried to restart the zoneminder servie and now it fails to start with an error in my logs about the version mismatch and to run zmupdate.pl. I ran it without any flags and it upgraded the db without issue, even reporting 1.26.3 before the upgrade. Seems to be fixed.

[echu2013]

Hi!! I'm new at this forum, i've been using zoneminder for a while and i wanted to share my experience with "zmfilter.pl" which wasn't working using latest 1.26-4 rpm build onto a Centos 6.4 64-bit SO.

Well, i have noticed that filters running in background never deleted events as i configured it...
Take a look at /var/log/httpd/error_log ..
i saw this:

Name "Net::SFTP::Foreign::debug" used only once: possible typo at /usr/bin/zmfilter.pl line 812.
Undefined subroutine &Date::Manip::UnixDate called at /usr/bin/zmfilter.pl line 135.

First line it's just a warning which i get rid by adding no warnings 'once'; to /usr/bin/zmfilter.pl at line 802, it just need to be into "else" statement that is warning us (line 812). That wasn't the issue but by adding these we prevent perl from warning us this.

this is what i saw on a forum:

The reason the filer ran into this issue on Debian was he used SysV timezone naming which wasn't supported. However, I'm running into this error not because of illegal naming (using America/Los_Angeles), but because /etc/timezone does not exist in Arch. Instead we set in in rc.conf.
When I manually created /etc/timezone with "America/Los_Angeles" in it, the error went away, so some package must be hardwired to look at /etc/timezone.

So I just create /etc/timezone (with my actual timezone as in /etc/php.ini file) and zmfilter.pl started to do it's job!

Hope it helps!!!

I'am really thankful for who created these rpm to make us much easier to install zoneminder, it's actually an excelent program!

Regards!

[knight-of-ni]

hi echu2013,
Thanks for the feedback.
I've read through a few references to this issue, but the strange thing is that I can't reproduce it on my 64bit CentOS production server nor on my development virtual machine. zmfilter appears to be working fine and there are no zmfilter errors in any of the log files.

What version of perl is on your system?
Are you using the version from the base repo?