zma crashes for only one monitor

Support and queries relating to all previous versions of ZoneMinder
Locked
mattcamp
Posts: 1
Joined: Mon Mar 21, 2005 9:12 am

zma crashes for only one monitor

Post by mattcamp »

One of my monitors has ceased recording motion in the last 24 hours, after nearly a month of perfect operation.

I have two monitors, on two inputs of a BT878 capture card, both running the same B/W composite cameras.

Now one of them won't record - I can view the live monitor just fine, and when there is no motion, the monitor's 'source' line is green... but when there is motion, the name changes to yellow, and there are no events recorded.

zmdc.log shows:

Code: Select all

encoder:/tmp# tail zmdc.log
'zmf -m 1' crashed at 05/03/21 20:57:51, exit status 11
'zma -m 1' crashed at 05/03/21 20:57:51, exit status 255
Starting pending process, zma -m 1
'zma -m 1' starting at 05/03/21 21:07:51, pid = 6024
Starting pending process, zmf -m 1
'zmf -m 1' starting at 05/03/21 21:07:51, pid = 6025
'zma -m 1' started at 05/03/21 21:07:51
'zmf -m 1' started at 05/03/21 21:07:51
'zmf -m 1' crashed at 05/03/21 21:07:51, exit status 11
'zma -m 1' crashed at 05/03/21 21:07:58, exit status 255
I am running 1.20.1 on Debian linux 2.4.25.

I have manually installed ffmpeg 0.4.8 since installing ZM, which appears to work fine.

Any ideas why this would cease capturing events after nearly 32000 events? (the other monitor is up to 37000+ events)
User avatar
zoneminder
Site Admin
Posts: 5215
Joined: Wed Jul 09, 2003 2:07 pm
Location: Bristol, UK
Contact:

Post by zoneminder »

What can you see in /var/log/messages? Anything useful?

Phil
Solar
Posts: 13
Joined: Fri Aug 18, 2006 11:11 pm
Location: South Africa

Post by Solar »

I've got EXACTLY the same problem. I have 20 cameras set up on a system, and this morning, one of them just decided not to capture events anymore.
All the cameras are IP network cameras, and this specific one has about 16 000 events recorded.

Although in MODECT mode the camera just goes yellow, and won't record anything.

I'm using Fedora Core 6 and get exactly the same error messages as "mattcamp". Either exit status 11 or exit status 255.

Regards,
Christiaan
Locked