Unable to decode frame

Forum for questions and support relating to the 1.30.x releases only.
Locked
lbm
Posts: 87
Joined: Mon Mar 26, 2018 7:44 pm

Unable to decode frame

Post by lbm »

Debian 9.9 with zoneminder 1.30.4

Im suddently after an server reboot, starting to see quite poor performance, on primarily on one of two webcams.
I have many of these errors in the log:

Any clues, why this happened? As stated, it came "out of the blue", after an server reboot.

Code: Select all

DATE/TIME
COMPONENT	SERVER	PID	LEVEL	MESSAGE	FILE	LINE
2019-05-13 13:22:04.608830	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 13:22:04.583234	zmc_m18		2820	FAT	Unable to decode frame at frame 224	zm_ffmpeg_camera.cpp	178
2019-05-13 13:21:32.131500	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 13:21:32.107847	zmc_m18		2776	FAT	Unable to decode frame at frame 2425	zm_ffmpeg_camera.cpp	178
2019-05-13 13:18:55.438130	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 13:18:55.414539	zmc_m18		2737	FAT	Unable to decode frame at frame 1387	zm_ffmpeg_camera.cpp	178
2019-05-13 13:18:48.453139	web_php		1426	ERR	Socket /var/run/zm/zms-000632s.sock does not exist. This file is created by zms, and since it does not exist, either zms did not run, or zms exited early. Please check your zms logs and ensure that CGI is enabled in apache and check that the PATH_ZMS is set correctly. Make sure that ZM is actually recording. If you are trying to view a live stream and the capture process (zmc) is not running then zms will exit. Please go to http://zoneminder.readthedocs.io/en/latest/faq.html#why-can-t-i-see-streamed-images-when-i-can-see-stills-in-the-zone-window-etc for more information.	/usr/share/zoneminder/www/includes/functions.php	2033
2019-05-13 13:18:48.191450	web_php		772	ERR	Socket /var/run/zm/zms-285838s.sock does not exist. This file is created by zms, and since it does not exist, either zms did not run, or zms exited early. Please check your zms logs and ensure that CGI is enabled in apache and check that the PATH_ZMS is set correctly. Make sure that ZM is actually recording. If you are trying to view a live stream and the capture process (zmc) is not running then zms will exit. Please go to http://zoneminder.readthedocs.io/en/latest/faq.html#why-can-t-i-see-streamed-images-when-i-can-see-stills-in-the-zone-window-etc for more information.	/usr/share/zoneminder/www/includes/functions.php	2033
2019-05-13 13:18:47.110820	web_js		770	ERR	TypeError: undefined is not an object (evaluating 'type.indexOf')	https://zm.mork.xyz/zm/tools/mootools/mootools-core.js	1485
2019-05-13 13:16:58.449830	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 13:16:58.416992	zmc_m18		2688	FAT	Unable to decode frame at frame 2090	zm_ffmpeg_camera.cpp	178
2019-05-13 13:14:13.817520	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 13:14:13.792584	zmc_m18		2589	FAT	Unable to decode frame at frame 4993	zm_ffmpeg_camera.cpp	178
2019-05-13 13:09:36.171830	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 13:09:36.141558	zmc_m18		2329	FAT	Unable to decode frame at frame 11563	zm_ffmpeg_camera.cpp	178
2019-05-13 12:57:12.784570	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 12:57:12.758686	zmc_m18		2292	FAT	Unable to decode frame at frame 1290	zm_ffmpeg_camera.cpp	178
2019-05-13 12:55:24.359800	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 12:55:24.335360	zmc_m18		2288	FAT	Unable to decode frame at frame 420	zm_ffmpeg_camera.cpp	178
2019-05-13 12:54:31.723430	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 12:54:31.695367	zmc_m18		2240	FAT	Unable to decode frame at frame 1693	zm_ffmpeg_camera.cpp	178
2019-05-13 12:51:57.401260	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 12:51:57.374961	zmc_m18		2155	FAT	Unable to decode frame at frame 3469	zm_ffmpeg_camera.cpp	178
2019-05-13 12:47:29.216560	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 12:47:29.185294	zmc_m18		2108	FAT	Unable to decode frame at frame 1574	zm_ffmpeg_camera.cpp	178
2019-05-13 12:45:20.075590	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 12:45:20.047956	zmc_m18		2103	FAT	Unable to decode frame at frame 426	zm_ffmpeg_camera.cpp	178
2019-05-13 12:44:35.132550	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 12:44:35.104798	zmc_m18		2077	FAT	Unable to decode frame at frame 359	zm_ffmpeg_camera.cpp	178
2019-05-13 12:43:58.200440	zmdc		776	ERR	'zmc -m 18' exited abnormally, exit status 255	zmdc.pl	
2019-05-13 12:43:58.176168	zmc_m18		2048	FAT	Unable to decode frame at frame 1120	zm_ffmpeg_camera.cpp	178
Also, whenever, zoneminder is started, I get extremely poor respones (ping timeouts) from the camera.
So, it seems that ZM "drains" much of the network, or performance itself from the camera ?
E.g.
zoneminder started

Code: Select all

 ping 192.168.10.73 -c 10
PING 192.168.10.73 (192.168.10.73) 56(84) bytes of data.
64 bytes from 192.168.10.73: icmp_seq=1 ttl=64 time=103 ms
64 bytes from 192.168.10.73: icmp_seq=2 ttl=64 time=441 ms
64 bytes from 192.168.10.73: icmp_seq=3 ttl=64 time=167 ms
64 bytes from 192.168.10.73: icmp_seq=4 ttl=64 time=792 ms
64 bytes from 192.168.10.73: icmp_seq=6 ttl=64 time=86.7 ms
64 bytes from 192.168.10.73: icmp_seq=7 ttl=64 time=860 ms
64 bytes from 192.168.10.73: icmp_seq=8 ttl=64 time=883 ms
64 bytes from 192.168.10.73: icmp_seq=9 ttl=64 time=906 ms
64 bytes from 192.168.10.73: icmp_seq=10 ttl=64 time=930 ms

--- 192.168.10.73 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9010ms
rtt min/avg/max/mdev = 86.704/574.837/930.845/350.395 ms
zoneminder stopped

Code: Select all

 ping 192.168.10.73 -c 10
PING 192.168.10.73 (192.168.10.73) 56(84) bytes of data.
64 bytes from 192.168.10.73: icmp_seq=1 ttl=64 time=0.567 ms
64 bytes from 192.168.10.73: icmp_seq=2 ttl=64 time=0.803 ms
64 bytes from 192.168.10.73: icmp_seq=3 ttl=64 time=348 ms
64 bytes from 192.168.10.73: icmp_seq=4 ttl=64 time=371 ms
64 bytes from 192.168.10.73: icmp_seq=5 ttl=64 time=0.583 ms
64 bytes from 192.168.10.73: icmp_seq=6 ttl=64 time=0.701 ms
64 bytes from 192.168.10.73: icmp_seq=7 ttl=64 time=0.523 ms
64 bytes from 192.168.10.73: icmp_seq=8 ttl=64 time=0.735 ms
64 bytes from 192.168.10.73: icmp_seq=9 ttl=64 time=0.554 ms
64 bytes from 192.168.10.73: icmp_seq=10 ttl=64 time=0.805 ms

--- 192.168.10.73 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9141ms
rtt min/avg/max/mdev = 0.523/72.590/371.892/143.955 ms
Last edited by lbm on Mon May 13, 2019 1:26 pm, edited 1 time in total.
bbunge
Posts: 2930
Joined: Mon Mar 26, 2012 11:40 am
Location: Pennsylvania

Re: Unable to decode frame

Post by bbunge »

Linux distro and version please?
lbm
Posts: 87
Joined: Mon Mar 26, 2018 7:44 pm

Re: Unable to decode frame

Post by lbm »

bbunge wrote: Mon May 13, 2019 12:22 pm Linux distro and version please?
Ah yes. Its Debian 9.9 with zoneminder 1.30.4, I add it the the description as well.
lbm
Posts: 87
Joined: Mon Mar 26, 2018 7:44 pm

Re: Unable to decode frame

Post by lbm »

Hm. I'm getting signal lost as well..

Again, it was working fine, until an reboot of the server. No changes has been made, not even patching.

Code: Select all

2019-05-13 16:26:13.821369	zma_m18		6766	WAR	Signal: Reacquired	zm_monitor.cpp	1429
2019-05-13 16:26:09.914152	zma_m18		6766	WAR	Signal: Lost	zm_monitor.cpp	
lbm
Posts: 87
Joined: Mon Mar 26, 2018 7:44 pm

Re: Unable to decode frame

Post by lbm »

If I do not use the 802.3ad VLAN bond, I do not have these issues.
So the issue seems to be somehow network related in my setup, with my 802.3ad VLAN on the KVM host, and not ZM related.
Locked