ZoneMinder not starting post-update - no errors in log.

[blackpot]

I recently updated to 1.28.1 from a release a few versions back, as well as the server's OS (was on Fedora 19, now on 22). For the most part, everything was smooth, and I'm now running the ZM binary releases from the ZMREPO. A few config changes had to be made (I was previously compiling my own from source), but I've run into a glitch that I can't seem to solve now.

Whenever I try to start ZoneMinder form the web interface, it doesn't actually start. Even stranger, there's nothing in the log to suggest why this is the case. Every time I try to start it, a single entry is added to the log, with just:

Code: Select all

zmsystemctl	5836	INF	Redirecting command through systemctl	zmsystemctl.pl

However, it never starts (it's always in the "Stopped" state at the top of the console). Everything looks right on the file system & database, however. The socket is opened, the shared memory files are present, the previously recorded events are all present and accounted for. I did read all of /usr/share/doc/zoneminder/README.Fedora, though many of the things it asks for were already done (as this was an upgrade, not a fresh install).

So, where should I begin when troubleshooting this?

Edit: I can also see the zmc/zma processes up and running in top. Everything just looks down from the console.

[blackpot]

Okay, after a reboot to test some other fixes, everything is working now. I'm not sure what was wrong, but I can no longer reproduce the issue.

Sorry, if I wasted anyone's time

[knight-of-ni]

It's good to hear from someone using the Fedora rpms in zmrepo.
I am not sure how many people are using them or using zoneminder on fedora for that matter.

When starting zoneminder, especially for the first time, you should always do it from the command line, rather than from the web console. When you try to start it for the first time from the web console, it does not have the necessary file permission to create the temporary folders it needs to store the pid file, socket file, etc. That is almost certainly what happened in your case.

When you rebooted, the tmpfiles.d service kicked in on bootup and created all the necessary folders, which is why it worked fine afterwards.

Code: Select all

zmsystemctl   5836   INF   Redirecting command through systemctl   zmsystemctl.pl

Working as intended. On machines running systemd, all commands to start, stop, or restart have to go through the systemctl command.