Page 1 of 1

Zoneminder on Centos 5.4 with Panasonic BL-C131A

Posted: Sun Feb 28, 2010 9:27 pm
by luvablemarmot
My zoneminder set up started acting wierd today and I can't pin down the issue. While I have not changed anything on the zoneminder side I have upgraded the Panasonic firmware to Version 3.52R01.

I get the following error in my logs when attempting to do mo-cap

Code: Select all

Feb 28 16:17:43 cctv zmc_m1[5618]: INF [Starting Capture]
Feb 28 16:17:43 cctv zmc_m1[5618]: ERR [Select timed out]
Feb 28 16:17:43 cctv zmc_m1[5618]: ERR [Unable to read header]
Feb 28 16:17:43 cctv zmc_m1[5618]: ERR [Unable to get response]
Feb 28 16:17:43 cctv zmc_m1[5618]: ERR [Failed to capture image from monitor 1 (0/1)]
Feb 28 16:17:43 cctv zmdc[4074]: ERR ['zmc -m 1' exited abnormally, exit status 255] 
Feb 28 16:17:53 cctv zmdc[4074]: INF [Starting pending process, zmc -m 1] 
Feb 28 16:17:53 cctv zmdc[5645]: INF ['zmc -m 1' started at 10/02/28 16:17:53] 
Feb 28 16:17:53 cctv zmdc[4074]: INF ['zmc -m 1' starting at 10/02/28 16:17:53, pid = 5645] 
Feb 28 16:17:53 cctv zmc_m1[5645]: INF [Debug Level = 0, Debug Log = <none>]
Feb 28 16:17:53 cctv zmc_m1[5645]: INF [Starting Capture]
Feb 28 16:17:53 cctv zmc_m1[5645]: ERR [Select timed out]
Feb 28 16:17:53 cctv zmc_m1[5645]: ERR [Unable to read header]
Feb 28 16:17:53 cctv zmc_m1[5645]: ERR [Unable to get response]
Feb 28 16:17:53 cctv zmc_m1[5645]: ERR [Failed to capture image from monitor 1 (0/1)]
Feb 28 16:17:53 cctv zmdc[4074]: ERR ['zmc -m 1' exited abnormally, exit status 255] 
Feb 28 16:17:54 cctv zmdc[4074]: INF [Command 'zmc -m 1' removed from pending list at 10/02/28 16:17:54] 
Feb 28 16:17:54 cctv zmdc[4074]: INF ['zma -m 1' stopping at 10/02/28 16:17:54] 
Feb 28 16:17:54 cctv zma_m1[5601]: INF [Got signal 15 (Terminated), exiting]
Feb 28 16:17:54 cctv zmdc[4074]: INF ['zma -m 1' exited normally] 
Been trying to figure it out all day. Re-started the VM, restarted the router, checked the network connection from the VM to the camera. Checked the camera's output. Everything has been normal.

Any ideas what is happening here?

Thanks.

Posted: Sun Feb 28, 2010 10:53 pm
by cordel
Feb 28 16:17:43 cctv zmc_m1[5618]: INF [Starting Capture]
Feb 28 16:17:43 cctv zmc_m1[5618]: ERR [Select timed out]
Feb 28 16:17:43 cctv zmc_m1[5618]: ERR [Unable to read header]
Feb 28 16:17:43 cctv zmc_m1[5618]: ERR [Unable to get response]
That's saying that your camera is not responding at all, and or it can't be reached.
Causes:
Network problems, cat5 cable unplugged, no route to host, bad configuration like a wrong IP, camera power not plugged in, etc, etc.

Posted: Mon Mar 01, 2010 12:10 am
by luvablemarmot
cordel wrote:
Feb 28 16:17:43 cctv zmc_m1[5618]: INF [Starting Capture]
Feb 28 16:17:43 cctv zmc_m1[5618]: ERR [Select timed out]
Feb 28 16:17:43 cctv zmc_m1[5618]: ERR [Unable to read header]
Feb 28 16:17:43 cctv zmc_m1[5618]: ERR [Unable to get response]
That's saying that your camera is not responding at all, and or it can't be reached.
Causes:
Network problems, cat5 cable unplugged, no route to host, bad configuration like a wrong IP, camera power not plugged in, etc, etc.
Camera is reachable with no issues. I can login view the streaming images. I also can use another 3rd party camera solution to hook into the camera and use it to do mocap.

edit!

Actually you're on to something. I kinda think this might be a vmware issue since updating to fusion 3.0.2.

None of the other servers are dropping packets but the vmware server running on my mac is, see below:

Code: Select all

[root@cctv ~]# ping 192.168.1.253
PING 192.168.1.253 (192.168.1.253) 56(84) bytes of data.
From 192.168.1.113 icmp_seq=1 Destination Host Unreachable
64 bytes from 192.168.1.253: icmp_seq=2 ttl=255 time=41.2 ms
From 192.168.1.113 icmp_seq=3 Destination Host Unreachable
64 bytes from 192.168.1.253: icmp_seq=4 ttl=255 time=3.11 ms
From 192.168.1.113 icmp_seq=5 Destination Host Unreachable
64 bytes from 192.168.1.253: icmp_seq=6 ttl=255 time=4.55 ms
64 bytes from 192.168.1.253: icmp_seq=7 ttl=255 time=3.96 ms
From 192.168.1.113 icmp_seq=8 Destination Host Unreachable
64 bytes from 192.168.1.253: icmp_seq=9 ttl=255 time=42.3 ms
From 192.168.1.113 icmp_seq=10 Destination Host Unreachable
64 bytes from 192.168.1.253: icmp_seq=11 ttl=255 time=19.5 ms
64 bytes from 192.168.1.253: icmp_seq=12 ttl=255 time=2.69 ms