Linked trigger fails after transient camera error

Forum for questions and support relating to the 1.30.x releases only.
Locked
martian_tom
Posts: 6
Joined: Sun Jan 10, 2016 11:33 pm

Linked trigger fails after transient camera error

Post by martian_tom »

I'm running ZM 1.30.4 on Ubuntu 17.10, both of which I've recently upgraded to from ZM 1.30.0 and Ubuntu 16.10. I have an IP camera which can output multiple versions of the same video (Trendnet TV-IP572PI). To reduce the CPU load of motion detection, I have set up 1 monitor in Zoneminder to receive a low resolution stream in Modect mode, and a second monitor to receive the high resolution stream in Nodect mode with the first monitor set up as a linked monitor. Every time motion is detected, I get 2 events, 1 for each monitor. This setup has been working fine for several years.

Since upgrading, I've noticed that at apparently random times the trigger that creates alarms on the full resolution monitor stops working. After that time I still get events on the low resolution monitor, but nothing on the full resolution one. I can view streams of both monitors fine and if I trigger a manual alarm on the high resolution monitor, it creates an event as expected. If I restart Zoneminder, the linked trigger starts working again.

What I've noticed now on 2 instances is at around the time the triggering stops working, there are some errors in the logs indicating that the low resolution monitor briefly stops working. This is an example, in reverse chronological order (as per the log viewer):

Code: Select all

2017-11-25 16:29:32.383985	zma_m6		13223	INF	netcam_trigger: 1000 - Analysing at 10.10 fps	zm_monitor.cpp	1296
2017-11-25 16:29:27.353586	zmc_m6		13214	INF	netcam_trigger: 1000 - Capturing at 9.17 fps	zm_monitor.cpp	3125
2017-11-25 16:29:15.054320	zmc_m7		2855	INF	netcam_play1: 618000 - Capturing at 10.99 fps	zm_monitor.cpp	3125
2017-11-25 16:28:51.648292	zma_m7		3160	INF	netcam_play1: 617000 - Analysing at 7.87 fps	zm_monitor.cpp	1296
2017-11-25 16:27:53.928323	zma_m6		13223	INF	In mode 3/1, warming up	zma.cpp	142
2017-11-25 16:27:53.848340	zmdc		13223	INF	'zma -m 6' started at 17/11/25 16:27:53	zmdc.pl	
2017-11-25 16:27:53.846910	zmdc		2282	INF	'zma -m 6' starting at 17/11/25 16:27:53, pid = 13223	zmdc.pl	
2017-11-25 16:27:53.837260	zmdc		2282	INF	Starting pending process, zma -m 6	zmdc.pl	
2017-11-25 16:27:53.734480	zmdc		2282	INF	'zma -m 6' exited normally	zmdc.pl	
2017-11-25 16:27:53.718274	zma_m6		3137	INF	Got signal 15 (Terminated), exiting	zm_signal.cpp	40
2017-11-25 16:27:53.714820	zmdc		2282	INF	'zma -m 6' sending stop to pid 3137 at 17/11/25 16:27:53	zmdc.pl	
2017-11-25 16:27:53.573920	zmwatch		2895	INF	Restarting analysis daemon for netcam_trigger	zmwatch.pl	
2017-11-25 16:27:53.568620	zmwatch		2895	ERR	Error getting last capture time for netcam_trigger	zmwatch.pl	
2017-11-25 16:27:44.977921	zma_m7		3160	INF	netcam_play1: 616314 - Gone into prealarm state	zm_monitor.cpp	1689
2017-11-25 16:27:44.973435	zma_m7		3160	WAR	Signal: Reacquired	zm_monitor.cpp	1429
2017-11-25 16:27:44.796900	zmc_m7		2855	INF	Successfully reopened stream.	zm_ffmpeg_camera.cpp	134
2017-11-25 16:27:44.626900	zmc_m7		2855	WAR	Buffer overrun at index 45, image 617005, slow down capture, speed up analysis or increase ring buffer size	zm_monitor.cpp	3094
2017-11-25 16:27:44.591674	zmc_m7		2855	INF	netcam_play1: 617000 - Capturing at 15.87 fps	zm_monitor.cpp	3125
2017-11-25 16:27:44.220209	zmc_m7		2855	WAR	Last image read from shared memory 1 seconds ago, zma may have gone away	zm_monitor.cpp	3100
2017-11-25 16:27:44.217793	zma_m7		3160	WAR	Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size	zm_monitor.cpp	1324
2017-11-25 16:27:44.217437	zmc_m7		2855	WAR	Buffer overrun at index 49, image 616769, slow down capture, speed up analysis or increase ring buffer size	zm_monitor.cpp	3094
2017-11-25 16:27:44.090531	zmc_m7		2855	WAR	Buffer overrun at index 49, image 616689, slow down capture, speed up analysis or increase ring buffer size	zm_monitor.cpp	3094
2017-11-25 16:27:43.965247	zma_m7		3160	WAR	Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size	zm_monitor.cpp	1324
2017-11-25 16:27:43.963134	zmc_m7		2855	WAR	Buffer overrun at index 48, image 616608, slow down capture, speed up analysis or increase ring buffer size	zm_monitor.cpp	3094
2017-11-25 16:27:43.837229	zmc_m7		2855	WAR	Buffer overrun at index 48, image 616528, slow down capture, speed up analysis or increase ring buffer size	zm_monitor.cpp	3094
2017-11-25 16:27:43.712987	zmc_m7		2855	WAR	Buffer overrun at index 49, image 616449, slow down capture, speed up analysis or increase ring buffer size	zm_monitor.cpp	3094
2017-11-25 16:27:43.711637	zma_m7		3160	WAR	Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size	zm_monitor.cpp	1324
2017-11-25 16:27:43.584070	zmc_m7		2855	WAR	Buffer overrun at index 49, image 616369, slow down capture, speed up analysis or increase ring buffer size	zm_monitor.cpp	3094
2017-11-25 16:27:43.454697	zma_m7		3160	WAR	Signal: Lost	zm_monitor.cpp	1429
2017-11-25 16:27:43.424117	zmc_m7		2855	ERR	Unable to read packet from stream 0: error -110 "Connection timed out".	zm_ffmpeg_camera.cpp	167
2017-11-25 16:27:43.420743	zmc_m7		2855	INF	av_read_frame returned "Connection timed out". Reopening stream.	zm_ffmpeg_camera.cpp	163
2017-11-25 16:27:38.184115	zmc_m6		13214	INF	Priming capture from rtsp://tom:amber@192.168.0.40/3gpp	zm_ffmpeg_camera.cpp	104
2017-11-25 16:27:38.181641	zmc_m6		13214	INF	Starting Capture version 1.30.4	zmc.cpp	247
2017-11-25 16:27:38.081560	zmdc		13214	INF	'zmc -m 6' started at 17/11/25 16:27:38	zmdc.pl	
2017-11-25 16:27:38.081540	zmdc		2282	INF	'zmc -m 6' starting at 17/11/25 16:27:38, pid = 13214	zmdc.pl	
2017-11-25 16:27:38.072900	zmdc		2282	INF	Starting pending process, zmc -m 6	zmdc.pl	
2017-11-25 16:27:33.860290	zmdc		2282	ERR	'zmc -m 6' exited abnormally, exit status 255	zmdc.pl	
2017-11-25 16:27:33.665650	zmdc		13212	INF	'zmc -m 6' started at 17/11/25 16:27:33	zmdc.pl	
2017-11-25 16:27:33.665460	zmdc		2282	INF	'zmc -m 6' starting at 17/11/25 16:27:33, pid = 13212	zmdc.pl	
2017-11-25 16:27:33.658170	zmdc		2282	INF	Starting pending process, zmc -m 6	zmdc.pl	
2017-11-25 16:27:33.554630	zmdc		2282	INF	'zmc -m 6' exited normally	zmdc.pl	
2017-11-25 16:27:32.821731	zmc_m6		2837	INF	Got signal 15 (Terminated), exiting	zm_signal.cpp	40
2017-11-25 16:27:32.816850	zmdc		2282	INF	'zmc -m 6' sending stop to pid 2837 at 17/11/25 16:27:32	zmdc.pl	
2017-11-25 16:27:32.599380	zmwatch		2895	INF	Restarting capture daemon for netcam_trigger, time since last capture 9 seconds (1511627252-1511627243)	zmwatch.pl	
2017-11-25 16:26:44.017346	zma_m7		3160	INF	netcam_play1: 616000 - Analysing at 9.90 fps	zm_monitor.cpp	1296
2017-11-25 16:26:42.031575	zma_m6		3137	INF	netcam_trigger: 616000 - Analysing at 9.90 fps	zm_monitor.cpp	1296
2017-11-25 16:26:41.789600	zmc_m7		2855	INF	netcam_play1: 616000 - Capturing at 9.90 fps	zm_monitor.cpp	3125
2017-11-25 16:26:39.982512	zmc_m6		2837	INF	netcam_trigger: 616000 - Capturing at 10.00 fps	zm_monitor.cpp	3125
2017-11-25 16:25:03.110909	zma_m7		3160	INF	netcam_play1: 615000 - Analysing at 9.90 fps	zm_monitor.cpp	1296
2017-11-25 16:25:01.094437	zma_m6		3137	INF	netcam_trigger: 615000 - Analysing at 9.90 fps	zm_monitor.cpp	1296
2017-11-25 16:25:00.874823	zmc_m7		2855	INF	netcam_play1: 615000 - Capturing at 9.90 fps	zm_monitor.cpp	3125
2017-11-25 16:24:59.064715	zmc_m6		2837	INF	netcam_trigger: 615000 - Capturing at 9.90 fps	zm_monitor.cpp	3125
So it appears that monitor 6 (which is called netcam_trigger, the low resolution stream) loses video from the camera, but recovers a few seconds later. that's fine, but why then does the linked monitor stop triggering thereafter?
bbunge
Posts: 2975
Joined: Mon Mar 26, 2012 11:40 am
Location: Pennsylvania

Re: Linked trigger fails after transient camera error

Post by bbunge »

If you look through this forum you will discover many issues with Ubuntu 17.10 and the Zoneminder 1.30.4 that comes with it. As you did an upgrade from 16.10 I would guess Zoneminder upgraded itself and therefore you have inherited a mess! Your best bet is to go back to Ubuntu 16.04 for the long haul or see the install procedure on the WIKI for Ubuntu 17.10: https://wiki.zoneminder.com/Ubuntu_Serv ... e_easy_way

This setup does work but I can't guarantee you will be able to upgrade it successfully to the next Ubuntu release.
Locked