Install Problems

[JonThompson]

Hello,

I have ZM sucessfully Monitoring on one camera...

However, I am getting this message:

Can't get shared memory id '2053971969': No such file or directory

in my logs.

Also, I am having difficulty getting MPEG streaming to work and do not know enough about linux to troubleshoot it.

I am using FC2, and ZM 1.20.1.

[cordel]

Hi Jon,
You might want to take a look at these theads,
http://www.zoneminder.com/forums/viewto ... ry&start=0
and maybe post a snip of your error logs at /var/log/messages and depending on your install rpm version is here for zm /var/log/zm/ or in your /tmp folder if you compiled from source.
That would be the best place to start.
Cordel

[JonThompson]

--Begin /var/log/messages snippet--

Mar 24 20:48:33 <DNSSnip> zmc_d4[3743]: INF [KCCI: 784000 - Capturing at 30.30 fps]
Mar 24 20:49:03 <DNSSnip> zmc_d0[7300]: INF [Driveway: 641000 - Capturing at 29.41 fps]
Mar 24 20:49:07 <DNSSnip> zmc_d4[3743]: INF [KCCI: 785000 - Capturing at 29.41 fps]
Mar 24 20:49:09 <DNSSnip> kernel: bttv4: OCERR @ 2f72d000,bits: HSYNC OCERR*
Mar 24 20:49:36 <DNSSnip> zmc_d0[7300]: INF [Driveway: 642000 - Capturing at 30.30 fps]
Mar 24 20:49:40 <DNSSnip> zmc_d4[3743]: INF [KCCI: 786000 - Capturing at 30.30 fps]
Mar 24 20:50:01 <DNSSnip> sshd(pam_unix)[2778]: session opened for user jon by (uid=500)
Mar 24 20:50:09 <DNSSnip> zmc_d0[7300]: INF [Driveway: 643000 - Capturing at 30.30 fps]
Mar 24 20:50:13 <DNSSnip> zmc_d4[3743]: INF [KCCI: 787000 - Capturing at 30.30 fps]
Mar 24 20:50:43 <DNSSnip> zmc_d0[7300]: INF [Driveway: 644000 - Capturing at 29.41 fps]
Mar 24 20:50:47 <DNSSnip> zmc_d4
[3743]: INF [KCCI: 788000 - Capturing at 29.41 fps]
Mar 24 20:51:16 <DNSSnip> zmc_d0[7300]: INF [Driveway: 645000 - Capturing at 30.30 fps]
Mar 24 20:51:20 <DNSSnip> zmc_d4[3743]: INF [KCCI: 789000 - Capturing at 30.30 fps]

--End /var/log/messages snippet--

--Begin /tmp/zmwatch.log snippet--

Restarting capture daemon ('/usr/local/bin/zmdc.pl restart zmc -d 0'), time since last capture 151 seconds (1111621487-1111621336)
'zmc -d 0' started at 05/03/23 17:44:47
'zmc -d 0' starting at 05/03/23 17:44:47, pid = 5296
Restarting capture daemon ('/usr/local/bin/zmdc.pl restart zmc -d 0'), time since last capture 161 seconds (1111621497-1111621336)
'zmc -d 0' starting at 05/03/23 17:44:57, pid = 5307
'zmc -d 0' started at 05/03/23 17:44:57
Watchdog starting at 05/03/23 17:45:12
Watchdog pausing for 30 seconds
Can't execute: at /usr/local/bin/zmwatch.pl line 120.
Watchdog starting at 05/03/23 19:59:28
Watchdog pausing for 30 seconds
Can't execute: at /usr/local/bin/zmwatch.pl line 120.
Watchdog starting at 05/03/23 20:11:12
Watchdog pausing for 30 seconds
Watchdog starting at 05/03/23 20:23:06
Watchdog pausing for 30 seconds
Can't get shared memory id '2053971969': No such file or directory
Watchdog starting at 05/03/24 13:32:26
Watchdog pausing for 30 seconds

--End /tmp/zmwatch.log snippet--

--Begin /tmp/zmfilter.log snippet--

Scanning for events
Can't execute 'select * from Filters where (AutoArchive = 1 or AutoDelete = 1 or AutoUpload = 1 or AutoEmail = 1 or AutoMessage = 1 or AutoExecute != '') order by Name': at /usr/local/bin/zmfilter.pl line 249.
Scanning for events
Scanning for events
Scanning for events

--End /tmp/smfilter.log snippet--

[cordel]

Well I'm not really sure here so I hope some one can explain.
Both scripts are exiting on this line.
my $res = $sth->execute() or die( "Can't execute '$sql': ".$sth->errstr() );
I think it's calling for information from the database but I haven't learned this far yet to understand what.
Regards,
Cordel

[zoneminder]

I'm not sure about the filter error, as it looks fine to me and doesn't actually have any error message in it. Is it possible that you were doing something to mysql at the time as the other event scans have no errors.

The other errors look a bit more worrying, particularly the one from your bttv driver which implies that it has had some sort of problems syncing with an input. The zmwatch restarts normally are there to prevent capture lockups, which do happen sometimes on some hardware, where the driver just gets stuck. So this would look like what happened in your case, except that it happens twice within 10 seconds which is very odd.

Can you keep an eye on this and report any future funnies, it may be worth looking in zmdc.log also to get a record of what started and stopped when.

Phil

[JonThompson]

-- Begin /tmp/zmdc.log snippet--

Can't find process with command of 'zmf -m 1'
Can't find process with command of 'zma -m 1'
Can't find process with command of 'zmf -m 1'
Can't find process with command of 'zma -m 1'
Can't find process with command of 'zmf -m 1'
'zmc -d 0' stopping at 05/03/24 14:30:49
'zmc -d 0' died at 05/03/24 14:30:49
'zmc -d 0' started at 05/03/24 14:30:49
'zmc -d 0' starting at 05/03/24 14:30:49, pid = 5546
Can't find process with command of 'zma -m 1'
Can't find process with command of 'zmf -m 1'
'zmf -m 1' started at 05/03/24 14:30:49
'zmf -m 1' starting at 05/03/24 14:30:49, pid = 5560
'zma -m 1' started at 05/03/24 14:30:50
'zma -m 1' starting at 05/03/24 14:30:50, pid = 5566
'zmc -d 0' stopping at 05/03/24 14:52:34
'zmc -d 0' died at 05/03/24 14:52:34
'zmc -d 0' starting at 05/03/24 14:52:35, pid = 7300
'zmc -d 0' started at 05/03/24 14:52:35
'zma -m 1' stopping at 05/03/24 14:52:35
'zma -m 1' died at 05/03/24 14:52:35
'zmf -m 1' stopping at 05/03/24 14:52:35
'zmf -m 1' died at 05/03/24 14:52:35

-- end /tmp/zmdc.log snippet --

[zoneminder]

This just seems to confirm what the earlier log showed which is that it appears that the zmc process is getting locked up in the hardware driver somewhere. It's possible to increase the debug level for a particular process by sending it a USR1 signal. It might be worth doing that to the zmc processes and seeing if you can catch one misbehaving with a bit more debug on.

I'll try and have a look over the box anyway in the next day or two.

Phil