Is there some MJPEG format unsupported ?

eldertoon · Post by **eldertoon** » Sat Mar 04, 2017 10:16 pm

Hi,

I'm unsure that my issue is related to my camera but I'll try to explain what I've done. I installed Zoneminder 1.30.0 on a brand new Debian stable. I used the unstable packages (so basically my system is now a mix of stable and unstable but that's not the point as some camera works). I have configured 3 types of camera (Honeywell branded) and 1 model is not working. The other two are OK.

In the one OK, I have a remote in simple mode with a mjpeg accessed in http. It's working exactly like when I open the URL in my firefox.

In the one not OK, I have setup exactly the same (remote / simple / http / mjpeg). When I access the URL in my firefox, i get moving frames. When I open the monitor with Zoneminder, I just see the name of the monitor and log is filling up :

Code: Select all

2017-03-04 23:06:56.246548	zms		11111	ERR	Terminating, last frame sent time 1488665215.746471 secs more than maximum of 10.000000	zm_monitor.cpp	4192
2017-03-04 23:06:55.601578	web_js		10939	ERR	getStreamCmdResponse stream error: socket_sendto( /var/run/zm/zms-923745s.sock ) failed: No such file or directory - checkStreamForErrors()	?view=watch	
2017-03-04 23:06:55.485929	web_php		10939	ERR	socket_sendto( /var/run/zm/zms-923745s.sock ) failed: No such file or directory	/usr/share/zoneminder/www/includes/functions.php	1993
2017-03-04 23:06:44.066008	zms		11110	ERR	Terminating, last frame sent time 1488665203.565958 secs more than maximum of 10.000000	zm_monitor.cpp	4192
2017-03-04 23:06:43.497624	web_js		10939	ERR	getStreamCmdResponse stream error: socket_sendto( /var/run/zm/zms-923745s.sock ) failed: No such file or directory - checkStreamForErrors()	?view=watch	
2017-03-04 23:06:43.383788	web_php		10939	ERR	socket_sendto( /var/run/zm/zms-923745s.sock ) failed: No such file or directory	/usr/share/zoneminder/www/includes/functions.php	1993
2017-03-04 23:06:32.993508	zms		11109	ERR	Terminating, last frame sent time 1488665192.493443 secs more than maximum of 10.000000	zm_monitor.cpp	4192

I suppose this is just the result of what I see : there is an issue with my config. If I open the configuration of one of my failling cam and just save, the result is :

Code: Select all

2017-03-04 23:08:20.869253	zmc_m2		11133	INF	Starting Capture version 1.30.0	zmc.cpp	250
2017-03-04 23:08:15.813640	zmdc		10659	WAR	Can't find process with command of 'zma -m 2'	zmdc.pl	
2017-03-04 23:08:15.683770	zmdc		11133	INF	'zmc -m 2' started at 17/03/04 23:08:15	zmdc.pl	
2017-03-04 23:08:15.683770	zmdc		10659	INF	'zmc -m 2' starting at 17/03/04 23:08:15, pid = 11133	zmdc.pl	
2017-03-04 23:08:15.555150	zmdc		10659	INF	'zmc -m 2' crashed, signal 8	zmdc.pl	
2017-03-04 23:08:15.386220	zmdc		10659	WAR	'zmc -m 2' has not stopped at 17/03/04 23:08:15. Sending KILL to pid 10703	zmdc.pl	
2017-03-04 23:08:09.385561	zmc_m2		10703	INF	Got signal 15 (Terminated), exiting	zm_signal.cpp	40
2017-03-04 23:08:09.373500	zmdc		10659	INF	'zmc -m 2' sending stop to pid 10703 at 17/03/04 23:08:09	zmdc.pl	
2017-03-04 23:08:09.243790	zmdc		10659	WAR	Can't find process with command of 'zma -m 2'	zmdc.pl

This I don't have a clue what it means. It's like the process that should monitor my cam is not starting ? Despite my cam is listed in green (source column) and I see a "/usr/bin/zmc -m 2" in my running processes. It is the same after rebooting the server or stopping and starting the service.

My only answer would be that this mjpeg stream is in some way not compatible with what the monitor is able to read ? But how can I know ? This is my only lead as this not working model is the oldest.

Regards,