autostarting zoneminder and its monitoring

[tkalfaoglu]

Hi there.. Currently when my fedora 20 goes down, I have to do a
/usr/bin/perl -wT /usr/local/bin/zmdc.pl startup
to start zoneminder.. Worse, it stays in "stopped" mode and I have to go into its web interface and start its monitoring.

Any ideas on how to automate these?

Many thanks, -t

[knight-of-ni]

Hi there.. Currently when my fedora 20 goes down, I have to do a
/usr/bin/perl -wT /usr/local/bin/zmdc.pl startup
to start zoneminder.. Worse, it stays in "stopped" mode and I have to go into its web interface and start its monitoring.

Any ideas on how to automate these?

Many thanks, -t

Fedora 20 uses systemd instead of init, which means unfortunately that you are creating the problem by starting/stopping zoneminder using any method other than the systemctl tool. This includes starting and stopping zoneminder from the web console since the web console does not know anything about systemd.

For example, from a clean boot you start zoneminder for the first time by executing "sudo systemctl start zoneminder". It should start fine if you have just booted up. Now let's say you issue "sudo zmpkg restart" from the commandline instead of using systemctl. Since systemd is looking at the previous PID (the one you just killed), it marks the service as failed. This causes subsequent attempts at using systemctl to manage the zoneminder service to fail as well.

We are working on a solution that makes zoneminder more friendly on distros with systemd.

Laslty, don't forget to disable selinux since that can cause similar issues with starting the service.