ZM shows status failure in openSuSe, but it works

[dc740]

Hello, I tried this steps in openSuSE 13.2 and they worked just fine:
http://www.zoneminder.com/wiki/index.ph ... s_for_SuSE

But I wanted to report that executing systemctl status zm.service shows that ZM is not active. But it is.

Active: failed (Result: resources)

no other errors are shown.

Other than that, the wiki is missing the last step:
Adding the firewall rule to be able to access ZM from another computer. I did it in a headless terminal, so I had to open the port to try it on a browser. It was extremely easy to do from yast2 though.

Thanks!

[knight-of-ni]

You did not state what version of ZoneMinder you are using. Only versions >= 1.28.0 work properly with systemd. The symptoms are exactly as you described.

If you are running a recent enough version of zoneminder, then, when you (re)start zoneminder, you should see an event in the log that says something like "redirecting through systemctl...". If it does not say that, then that is the problem.

On a system running systemd, all start/stop/restart commands must route through systemctl. Otherwise you get exactly what you currently see... zoneminder itself thinks it is running, but systemd will disagree.

Note that a third party maintains the OpenSuse rpm's. You may want to contact the package maintainer.

[dc740]

Sorry, I thought it was implied in the forum category, but I realized I missed some details. This is my current version:

ZoneMinder Console - Running - v1.28.1


I installed ZoneMinder-MP by adding the zm and vlc repositories to openSuSE 13.2 (i586). I'll try to get the third party involved. Thanks!

[knight-of-ni]

I can see why you might think that, but I've spent too much time troubleshooting an issue only to find that the OP wasn't using the version of zoneminder they posted their topic in.

Make sure and look for the "redirecting through systemctl..." message in your logs. That is the key as to whether zoneminder will work properly in systemd environment.

[dc740]

I just did a quick grep, as you correctly pointed out. It's not redirecting it.

I'm also seeing that the /var/log/zm folder is empty, AND the most important problem:

xawtv works with my video card, but as soon as I add a device to the zm interface, the system reboots

I made sure to configure it like this
http://www.zoneminder.com/wiki/index.php/Kodicom_4400r

No logs in system journal

[knight-of-ni]

By default, zoneminder logs events to the database, not the local log files. Change that under options.

The issue with your capture card is completely different. You should create a different topic for that.

[dc740]

Yes, forget about auto-reboot the problem. I fixed it!
as it turns out, if you don't use one of the supported modes, the card will instantly reboot the system. I didn't know about this and used 320x240 as set by default in ZM. Too bad there is no auto-detect or something like that. I wonder how xawtv handles it.

For future reference, here are the supported modes for the Kodicom 4400r:
NTSC: 640x480,320x240,160x120
PAL: 768x576,384x288,192x144

Also, I don't know if it changes anything but I set capture pallete and target colorspace to grey scale. And configured captures per frame to 4


I'll search for the documentation to inspect the logs. Thanks!