Shared memory not initialised by capture daemon

MartinB · Post by **MartinB** » Wed Jan 11, 2006 12:33 am

zm-1.21.4
Linux Mandrake 10.1

I can't see any reference to this particular error anywhere.

ipcs shows:
key shmid owner perms bytes nattch status
0x7a6d2001 19300355 apache 700 3041828 0

cat /proc/sys/kernel/shmmax
33554432

so it doesn't look like it's unable to allocate the shared memory.

Any suggestions?

jameswilson · Post by **jameswilson** » Wed Jan 11, 2006 12:34 am

whats your shmall?

MartinB · Post by **MartinB** » Wed Jan 11, 2006 12:39 am

root@seagoon zm-1.21.4]# cat /proc/sys/kernel/shmall
2097152

?

jameswilson · Post by **jameswilson** » Wed Jan 11, 2006 12:44 am

is every thing else ok. I have seen this before when there is a streaming issue (i have seen it when i have asked for non existant cams on stream or a cam with an error)

James

MartinB · Post by **MartinB** » Wed Jan 11, 2006 12:48 am

Hard to say. I've just installed and configured the system. Everything looked OK until I went in to view the monitor. I haven't tested the cam itself with xawtv or anything.

jameswilson · Post by **jameswilson** » Wed Jan 11, 2006 12:52 am

so you havnt got an image?

MartinB · Post by **MartinB** » Wed Jan 11, 2006 12:55 am

Image doesn't download to the viewer window.

jameswilson · Post by **jameswilson** » Wed Jan 11, 2006 1:00 am

ok then the reason you have this shared mem error is because the mem is not being used as it contains no image. When zms (the streaming part that pulls your image out of shared me to display in the browser) tries to get this image, the shared mem segment does not exist and thus you get that error.

That answers the post. lol

Now you need to find out why your camera isnt working with zm.
what is it, how is it connected, what are your settings. You say you havnt tested it with tvtime etc so we might have a bit of work to do here!

James

MartinB · Post by **MartinB** » Wed Jan 11, 2006 1:49 am

Many thanks. I'll have a good look at that.

MartinB · Post by **MartinB** » Thu Jan 12, 2006 2:05 am

Just to resolve the issue - there were permission problems on the log files which was crashing some child process and ... somehow resulting in the shared memory errors as well.

Fixed the permissions - all works fine now. EXCELLENT PIECE OF SOFWTARE!