Page 1 of 2

a black screen in the video area

Posted: Mon Apr 03, 2006 7:27 am
by rsadanan
sir,

i installed zoneminder ctu

and connected axis camera 210

and i entered the ip address like this userid:password@192.168.0.90

remote host path

i tried with the following /jpg/image.jpg and also with the other path

/axis-cgi/mjpg/video.cgi

but I get a black screen on the video area


can anybody help me regarding this question

Posted: Thu Apr 06, 2006 8:12 am
by cordel
What errors are you getting in /var/log/zm/zmdc.log /var/log/httpd/error_log etc?

Regards,
Corey

Posted: Fri Apr 07, 2006 12:21 pm
by rsadanan
[root@localhost ~]# /var/log/zm/zmdc.log
bash: /var/log/zm/zmdc.log: Permission non accordée(no permission)
[root@localhost ~]# /var/log/httpd/error_log
bash: /var/log/httpd/error_log: Permission non accordée(no permission)

can you help me;

Posted: Fri Apr 07, 2006 4:08 pm
by jameswilson
I think you need to modify the permixsions on your zm folder to be the same as whatever user is running apache (usually apache) but check

Posted: Tue Apr 11, 2006 7:52 am
by rsadanan
sir,

i got the following

[root@localhost ~]# tail -f /var/log/zm/zmdc.log
'zmc -m 2' starting at 06/04/11 09:43:04, pid = 3166
'zmc -m 2' started at 06/04/11 09:43:04
'zma -m 2' started at 06/04/11 09:43:04
'zma -m 2' starting at 06/04/11 09:43:04, pid = 3171
'zmfilter.pl' started at 06/04/11 09:43:05
'zmfilter.pl' starting at 06/04/11 09:43:05, pid = 3177
'zmaudit.pl -d 900 -y' started at 06/04/11 09:43:06
'zmaudit.pl -d 900 -y' starting at 06/04/11 09:43:06, pid = 3182
'zmwatch.pl' started at 06/04/11 09:43:07
'zmwatch.pl' starting at 06/04/11 09:43:07, pid = 3188


[root@localhost ~]# tail -f /var/log/httpd/error_log
[Tue Apr 11 09:23:25 2006] [notice] caught SIGTERM, shutting down
[Tue Apr 11 09:42:52 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Apr 11 09:42:53 2006] [notice] Digest: generating secret for digest authentication ...
[Tue Apr 11 09:42:53 2006] [notice] Digest: done
[Tue Apr 11 09:42:53 2006] [notice] LDAP: Built with OpenLDAP LDAP SDK
[Tue Apr 11 09:42:53 2006] [notice] LDAP: SSL support unavailable
[Tue Apr 11 09:42:53 2006] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Tue Apr 11 09:42:53 2006] [notice] Apache/2.0.52 (Fedora) configured -- resuming normal operations
[Tue Apr 11 09:43:38 2006] [error] [client 192.168.1.66] File does not exist: /var/www/html/favicon.ico
[Tue Apr 11 09:43:39 2006] [error] [client 192.168.1.66] File does not exist: /var/www/html/favicon.ico
[Tue Apr 11 09:49:11 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... 0&control=

[root@localhost ~]# tail -f /var/log/messages
Apr 11 09:50:41 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:50:41 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:50:42 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:42 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:43 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:43 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:44 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:44 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:45 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:45 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:46 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:46 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:47 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:47 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:50:47 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:47 localhost zmc_m2[3166]: ERR [Invalid response status 210357616: Bad Request]
Apr 11 09:50:47 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:50:48 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:48 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:49 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:50:49 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:49 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:50 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:50 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:50:50 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:51 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:51 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:52 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:50:52 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:52 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:53 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:53 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:54 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:54 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:55 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:55 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:56 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:56 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:50:56 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:57 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:57 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:58 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:58 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:50:59 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:50:59 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:50:59 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:00 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:00 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:01 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:01 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:02 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:02 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:03 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:51:03 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:51:03 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:03 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:04 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:04 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:05 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:05 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:06 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:51:06 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:06 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:07 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:07 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:08 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:08 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:09 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:09 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:10 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:10 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:11 localhost kernel: printk: 3 messages suppressed.
Apr 11 09:51:11 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:51:11 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:11 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:12 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:12 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:13 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:13 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:14 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:14 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:15 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:15 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:16 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:16 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:17 localhost kernel: ip_conntrack: table full, dropping packet.
Apr 11 09:51:17 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:17 localhost zma_m2[3171]: WAR [Waiting for capture daemon]
Apr 11 09:51:18 localhost zma_m1[3161]: WAR [Waiting for capture daemon]
Apr 11 09:51:18 localhost zma_m2[3171]: WAR [Waiting for capture daemon]

sir please help

Posted: Tue Apr 11, 2006 8:33 am
by jameswilson
i have never seen this but it doesnt look good. Can you view your camera on the zm box with a browser?
Apr 11 09:51:11 localhost kernel: ip_conntrack: table full, dropping packet.

Posted: Tue Apr 11, 2006 10:51 am
by zoneminder
Before the section of /var/log/messages posted there should be one or more attempts to start zmc. This should give a bit more information. The section posted is just zma waiting for zmc to start up again.

Posted: Tue Apr 11, 2006 12:38 pm
by rsadanan
sir,

i again made all the commands

[root@localhost ~]# tail -f /var/log/zm/zmdc.log
'zmwatch.pl' running at 06/04/11 13:47:30, pid = 5075, valid
'zmfilter.pl' running at 06/04/11 13:47:28, pid = 5063, valid
'zma -m 2' running at 06/04/11 13:55:58, pid = 5313, valid
'zmc -m 2' running at 06/04/11 13:55:56, pid = 5305, valid
'zmaudit.pl -d 900 -y' running at 06/04/11 13:47:29, pid = 5068, valid
'zmc -m 1' running at 06/04/11 14:11:29, pid = 5827, valid
'zmwatch.pl' running at 06/04/11 13:47:30, pid = 5075, valid
'zmfilter.pl' running at 06/04/11 13:47:28, pid = 5063, valid
'zma -m 2' running at 06/04/11 13:55:58, pid = 5313, valid
'zmc -m 2' running at 06/04/11 13:55:56, pid = 5305, valid

[root@localhost ~]# tail -f /var/log/httpd/error_log
[Tue Apr 11 14:17:04 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... 0&control=
[Tue Apr 11 14:18:14 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... 0&control=
[Tue Apr 11 14:19:01 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... id=1&mode=
[Tue Apr 11 14:19:02 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... id=2&mode=
[Tue Apr 11 14:19:15 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... ode=stream
[Tue Apr 11 14:19:18 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... ode=stream
[Tue Apr 11 14:19:28 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... id=1&mode=
[Tue Apr 11 14:19:28 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... id=2&mode=
[Tue Apr 11 14:22:26 2006] [error] [client 192.168.1.66] File does not exist: /var/www/html/favicon.ico
[Tue Apr 11 14:24:29 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... 0&control=

[root@localhost ~]# /usr/lib/zm/bin/zmc -m 1

this stops for a long time;


[root@localhost ~]# tail -f /var/log/messages
Apr 11 14:35:55 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:55 localhost last message repeated 11 times
Apr 11 14:35:55 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:55 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:55 localhost last message repeated 16 times
Apr 11 14:35:55 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:55 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:55 localhost last message repeated 16 times
Apr 11 14:35:55 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:55 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 13 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 17 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 16 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 15 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 12 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 16 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 16 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 2 times
Apr 11 14:35:56 localhost zma_m2[5313]: WAR [Waiting for capture daemon]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 13 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 17 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 16 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 15 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 16 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 17 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 16 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 16 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 16 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 16 times
Apr 11 14:35:57 localhost zma_m2[5313]: WAR [Waiting for capture daemon]
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 17 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]

Posted: Tue Apr 11, 2006 12:47 pm
by rsadanan
sir,

i again made all the commands

[root@localhost ~]# tail -f /var/log/zm/zmdc.log
'zmwatch.pl' running at 06/04/11 13:47:30, pid = 5075, valid
'zmfilter.pl' running at 06/04/11 13:47:28, pid = 5063, valid
'zma -m 2' running at 06/04/11 13:55:58, pid = 5313, valid
'zmc -m 2' running at 06/04/11 13:55:56, pid = 5305, valid
'zmaudit.pl -d 900 -y' running at 06/04/11 13:47:29, pid = 5068, valid
'zmc -m 1' running at 06/04/11 14:11:29, pid = 5827, valid
'zmwatch.pl' running at 06/04/11 13:47:30, pid = 5075, valid
'zmfilter.pl' running at 06/04/11 13:47:28, pid = 5063, valid
'zma -m 2' running at 06/04/11 13:55:58, pid = 5313, valid
'zmc -m 2' running at 06/04/11 13:55:56, pid = 5305, valid

[root@localhost ~]# tail -f /var/log/httpd/error_log
[Tue Apr 11 14:17:04 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... 0&control=
[Tue Apr 11 14:18:14 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... 0&control=
[Tue Apr 11 14:19:01 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... id=1&mode=
[Tue Apr 11 14:19:02 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... id=2&mode=
[Tue Apr 11 14:19:15 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... ode=stream
[Tue Apr 11 14:19:18 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... ode=stream
[Tue Apr 11 14:19:28 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... id=1&mode=
[Tue Apr 11 14:19:28 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... id=2&mode=
[Tue Apr 11 14:22:26 2006] [error] [client 192.168.1.66] File does not exist: /var/www/html/favicon.ico
[Tue Apr 11 14:24:29 2006] [error] [client 192.168.1.66] (70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://192.168.1.66:8087/zm/index.php?v ... 0&control=

[root@localhost ~]# /usr/lib/zm/bin/zmc -m 1

this stops for a long time;


[root@localhost ~]# tail -f /var/log/messages
Apr 11 14:35:55 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:55 localhost last message repeated 11 times
Apr 11 14:35:55 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:55 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:55 localhost last message repeated 16 times
Apr 11 14:35:55 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:55 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:55 localhost last message repeated 16 times
Apr 11 14:35:55 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:55 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 13 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 17 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 16 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 15 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 12 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 16 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 16 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 2 times
Apr 11 14:35:56 localhost zma_m2[5313]: WAR [Waiting for capture daemon]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 13 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 17 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost last message repeated 16 times
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 15 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 16 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 17 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 16 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 16 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 16 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 16 times
Apr 11 14:35:57 localhost zma_m2[5313]: WAR [Waiting for capture daemon]
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:57 localhost last message repeated 17 times
Apr 11 14:35:57 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]




i cannot view it through the zm

Posted: Wed Apr 12, 2006 2:42 pm
by rsadanan
sir,

i can see the images the problem is the resolution of the camera

but i have a problem that the first camera works and the second i cannot

my ram is 512mb i cannot find what is the problem

if any please help

Posted: Mon Apr 17, 2006 8:32 pm
by zoneminder
Apr 11 14:35:56 localhost zmc_m1[5827]: ERR [Invalid response status 210365808:Bad Request]
Apr 11 14:35:56 localhost zmc_m2[5305]: ERR [Invalid response status 210365808:Bad Request]
This implies you are gettign an unexpected response from your camera. Can you do a

Code: Select all

zmu -q -v -m <your monitor id>
and post the results?

Posted: Mon Apr 24, 2006 8:07 am
by rsadanan
sorry sir, i was on leave now its is working. i just restarted.

now i have problem, that is i can view french pages in the server that is

where i installed zoneminder. but when i login the page in windows it

page little bit corrupted and whe i click on new monitors it enters into the

first page and when i click to add th ip address on the status bar it shows

error on the page. in english it works well.

please help.

Posted: Mon Apr 24, 2006 1:57 pm
by zoneminder
Can you post what the errors you are getting are?

Posted: Tue Apr 25, 2006 10:33 am
by rsadanan
sir,

i can't find what is the error .

in the new monitor window

when the language preference is in fr_fr

the window opens and the rest of the does't work

now i copied the whole contents zm _lang_fr_fr_html.php to

zm _lang_en_gb_html.php and tried it works well.


i searched for the errors no idea


the error is Javascript error on page this was shown on the status bar the page does't change

Posted: Tue Apr 25, 2006 10:10 pm
by zoneminder
I've have tried using French with no problems. Can you be more specific about the JavaScript errors you get? Even just a line number and the exact screen you are on would help.