Page 1 of 1

shared mem issues

Posted: Tue Oct 18, 2005 8:47 pm
by jameswilson
i havnt got a problem that i can tell but i have a half completed zm working fine but loads of
Oct 18 21:27:00 localhost zms[21833]: ERR [Shared memory not initialised by capture daemon]
Oct 18 21:27:00 localhost zms[21838]: ERR [Shared memory not initialised by capture daemon]
Oct 18 21:27:01 localhost zms[21865]: ERR [Shared memory not initialised by capture daemon]
Oct 18 21:27:02 localhost zma_m12[3295]: INF [Cam_11: 1255 - Gone into alert state]
Oct 18 21:27:02 localhost zms[21891]: ERR [Shared memory not initialised by capture daemon]
Oct 18 21:27:02 localhost zms[21893]: ERR [Shared memory not initialised by capture daemon]
Oct 18 21:27:02 localhost zma_m12[3295]: INF [Cam_11: 1256 - Gone back into alarm state]
Oct 18 21:27:03 localhost zma_m12[3295]: INF [Cam_11: 1257 - Gone into alert state]
Oct 18 21:27:03 localhost zms[21921]: ERR [Shared memory not initialised by capture daemon]
Oct 18 21:27:03 localhost zma_m16[3395]: INF [Cam_15: 1140 - Gone into alarm state]
Oct 18 21:27:03 localhost zma_m12[3295]: INF [Cam_11: 1258 - Gone back into alarm state]
Oct 18 21:27:03 localhost zma_m16[3395]: INF [Cam_15: 1141 - Gone into alert state]
Oct 18 21:27:03 localhost zms[21945]: ERR [Shared memory not initialised by capture daemon]
Oct 18 21:27:04 localhost zms[21963]: ERR [Shared memory not initialised by capture daemon]
Oct 18 21:27:04 localhost zms[21964]: ERR [Shared memory not initialised by capture daemon]
Oct 18 21:27:05 localhost zma_m12[3295]: INF [Cam_11: 1262 - Gone into alert state]
Oct 18 21:27:05 localhost zms[22005]: ERR [Shared memory not initialised by capture daemon]
Oct 18 21:27:06 localhost zms[22011]: ERR [Shared memory not initialised by capture daemon]
Oct 18 21:27:06 localhost zma_m12[3295]: INF [Cam_11: 1263 - Gone back into alarm state]
Oct 18 21:27:06 localhost zms[22032]: ERR [Shared memory not initialised by capture daemon]
in the messages log. I cant seem to find anything else related.

James

Posted: Tue Oct 18, 2005 8:50 pm
by jameswilson
ah rethink just fount this
'zma -m 19' starting at 05/10/18 21:17:51, pid = 3893
'zma -m 19' started at 05/10/18 21:17:51
'zma -m 8' crashed at 05/10/18 21:17:51, exit status 255
'zma -m 8' starting at 05/10/18 21:17:51, pid = 3894
'zma -m 8' started at 05/10/18 21:17:51
'zma -m 9' crashed at 05/10/18 21:17:51, exit status 255
'zma -m 9' starting at 05/10/18 21:17:51, pid = 3897
'zma -m 9' started at 05/10/18 21:17:51
'zma -m 4' crashed at 05/10/18 21:17:51, exit status 255
'zma -m 4' starting at 05/10/18 21:17:51, pid = 3898
'zma -m 4' started at 05/10/18 21:17:51
'zma -m 5' crashed at 05/10/18 21:17:51, exit status 255
'zma -m 5' starting at 05/10/18 21:17:51, pid = 3903
'zma -m 5' started at 05/10/18 21:17:51
'zmc -d 2' stopping at 05/10/18 21:38:02
'zmc -d 2' died at 05/10/18 21:38:03
'zmc -d 2' starting at 05/10/18 21:38:03, pid = 14608
'zmc -d 2' started at 05/10/18 21:38:03

Posted: Tue Oct 18, 2005 11:15 pm
by cordel
Okay James,
But what is this on????
Is this CTU Core?
I assume not since you say it's half compiled, so then what distro?
Apache, php versions etc???
Regards,
Cordel

Posted: Tue Oct 18, 2005 11:20 pm
by jameswilson
good questions, very good questions lol.

distro pclinuxos
kernel 2.6.12 4 gig

Posted: Tue Oct 18, 2005 11:22 pm
by jameswilson
good questions, very good questions lol.

distro pclinuxos
kernel 2.6.12 4 gig

Posted: Tue Oct 18, 2005 11:22 pm
by jameswilson
good questions, very good questions lol.

distro pclinuxos
kernel 2.6.12 4 gig

Apache version 2.0.53

MySQL version 4.1.12

php-cgi 4.3.11

Posted: Tue Oct 18, 2005 11:39 pm
by jameswilson
dont know how i did that sorry. Cordel compiled, you are crediting me with way too much knowledge there, i dont know how to compile anything. Its half completed as in on site but with 4 cams yet to be connected. Will total 21 when complete.

Posted: Wed Oct 19, 2005 7:57 am
by jameswilson
update.

Checked logs this morning machine had errors etc till 8:02 then stopped time now 8:55 was doing about 8 a second before that so im completly confues now.

Posted: Wed Oct 19, 2005 8:14 am
by jameswilson
Think i got it. Appears security guard that came in last night selected a 36 way view (from my damn viewer) that was requesting images from zms from cameras that are not configured yet. As zms then i assume tried to get the image and it wasnt started obviously it could access the shared mem. Phil would it be possible to add the monitor name to the zms error that is logged, that way i could have seen what cams it was that were causign this error.

James

Posted: Wed Oct 19, 2005 8:22 am
by cordel
It should show in the error the camera ID (MonitorID) I belive as part of the error

Code: Select all

zmc -m 8' starting at 05/10/17 11:57:34, pid = 8905
'zmc -m 8' died at 05/10/17 11:57:35, signal 6
Command 'zmc -m 8' removed from pending list at 05/10/17 11:59:26
Shows that Monitor ID 8 has started, stoped, and removed.
From when I was playing with that panasonic camera.

Regards,
Cordel

Posted: Wed Oct 19, 2005 8:26 am
by jameswilson
your probably rights and i did get some errors about that but assumed due to the number of shared mem errors and the crashing deamon being from hours ago that they wernt related.
Motto check logs, check logs again, look for more logs you didny know existed, check these again, and check some more.

James