ZMS crashing when using Modect

[Clutch]

Hello all,

I've been using ZoneMinder (1.25.0) on Ubuntu 13.04 for about a week now with pretty good results in Mocord mode. I misunderstood what this mode really meant, and realized after a couple days (and a few gigs of data!) that what I really wanted to use was Modect. Unfortunately this mode doesn't work for me, and I can't seem to find any data online referencing the specific error. Here's where the fun starts:

Code: Select all

2013-10-31 23:41:03.332007	zma_m1	8075	INF	RPi: 31000 - Processing at 29.41 fps	zm_monitor.cpp	1055
2013-10-31 23:41:02.889616	zmc_m1	8071	INF	RPi: 31000 - Capturing at 30.30 fps	zm_monitor.cpp	2598
2013-10-31 23:40:40.453939	zms	8340	INF	Got signal 15 (Terminated), exiting	zm_signal.cpp	44
2013-10-31 23:40:37.211650	zms	8340	INF	Authenticated user 'admin'	zm_user.cpp	231
2013-10-31 23:40:29.814880	zma_m1	8075	INF	RPi: 30000 - Processing at 30.30 fps	zm_monitor.cpp	1055
2013-10-31 23:40:29.370649	zmc_m1	8071	INF	RPi: 30000 - Capturing at 29.41 fps	zm_monitor.cpp	2598
2013-10-31 23:39:56.360470	zma_m1	8075	INF	RPi: 29000 - Processing at 29.41 fps	zm_monitor.cpp	1055

Immediately after setting mode to Modect I start seeing the messages above about zms in tandem and repeating. No events get created and nothing records. If I switch to Mocord it will start recording just as it always did, it just will not in this mode.

In a bout of frustration I completely removed, purged and deleted all configuration and cache related to zoneminder, reinstalled and still receive this error when using Modect.

Any ideas?

[Clutch]

Quick update, maybe obvious to others but the "Authenticated user 'admin'" message is a red herring. If I turn off authentication this message goes away, however the "Got signal 15 (Terminated)" messages continue.

[Clutch]

Posted bug on this issue here:

Edit: My post looks too "spamy" for a new user, the Ubuntu bug number is #1247720.

I've narrowed it down to looking at the live feed via clicking on the monitor link. If I switch to a non-motion detection mode and leave the software alone it will continue to do its job. I can even look at the events view and timeline without causing the error. I can recreate the issue by looking at the live feed every time.

[mikb]

Have another red herring ...

I get this all the time in my logs, and learned to stop worrying about it

If you look at the live feed, a process is created and you get the images/video. When you click "close", the process is TERMinated, sent signal 15, sent to meet the great bitbucket in the sky. I don't think it's actually an ERROR.

Note that it says "INF" -- Informational. Not WARning, or ERRor.

Looking at the logs, you logged in and authenticated to get the video stream, then, killed it off.

As to why you're not getting motion detection, look elsewhere I think ... You've got capturing and processing, it seems like no actual changes are being seen in the video stream?

[Clutch]

Ok, I will write that message off to normal operation. I didn't examine the log that closely before I started experiencing the problem, so that's likely why I attributed this issue to the message.

I'll try turning on some more debugging and see if I can come up with something useful.

Thanks!