ZoneMinder Forums

Hi,

I am srill having problems with shared memory.

I have followed instructions and increased shmmax etc. to no avail.

A sample of what is happening.

Mar 18 22:39:03 ob1 zmdc[2061]: INF ['zmc -m 1' started at 06/03/18 22:39:03]
Mar 18 22:39:03 ob1 zmdc[1372]: INF ['zmc -m 1' starting at 06/03/18 22:39:03, pid = 2061]
Mar 18 22:39:03 ob1 zmc_m1[2061]: INF [Debug Level = 0, Debug Log = <none>]
Mar 18 22:39:03 ob1 zmdc[1372]: INF ['zmc -m 1' died, signal 6]
Mar 18 22:39:03 ob1 zmwatch[1411]: INF ['zmc -m 1' started at 06/03/18 22:39:03]
Mar 18 22:39:08 ob1 zmu[2069]: ERR [Shared memory not initialised by capture daemon]
Mar 18 22:39:11 ob1 zmu[2076]: ERR [Shared memory not initialised by capture daemon]
Mar 18 22:39:13 ob1 zmwatch[1411]: INF [Restarting capture daemon for NC1000, shared memory not valid]


It appears that the memory segment is being created:
ipcc -m gives:
0x7a6d2001 38862853 www-data 700 127148 0

zmu -m 1 -q -v -U fred -P frog gives:
Mar 18 22:48:15 ob1 zmu[2415]: ERR [Shared memory not initialised by capture daemon]

Any help appreciated.

Thanks

Grahame

im assuming that this happens when you try to view you cam. It looks like you arnt getting any images into zm, thus no shared mem is initialised. What cam you got?

jordg wrote:Mar 18 22:39:03 ob1 zmdc[1372]: INF ['zmc -m 1' died, signal 6]

This is the key issue, the shared memory message is because the process that sets it up has died. Ideally we need to figure out why zmc is crashing, gdb would be the best method.

The best thing to try is to run zmc directly from gdb. So get a command shell up and do

Code:
gdb /<pathto>/zmc
> run -m 1

and then wait for it to exit/crash. When it does, type 'bt' to get a backtrace and post it here.

It is quick to die

root@ob1:~# gdb /usr/local/bin/zmc
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) run -m 1
Starting program: /usr/local/bin/zmc -m 1
[Thread debugging using libthread_db enabled]
[New Thread -1222895936 (LWP 17920)]

Program exited with code 0377.
(gdb)

That implies a normal exit with an error, rather than a crash. Was there anything in your logs to correspond with this? Failing that type before you type run which shoul dbreak the process on exit and then type 'bt'.