Page 1 of 1
Shared memory not valid
Posted: Mon Aug 20, 2007 3:51 pm
by patamar
Hi, i'm having some problems with Zm
configuration:
ZoneMinder v1.22.3
Ubuntu Server 6.06
I used the tutorial of the Ubuntu
I'm using a ip camera Mobotix M22
when I open the window I read only "No main Content type"
that's what logs sais :
==> /tmp/zmwatch.log <==
08/20/07 17:44:00.734992 zmwatch[3964].ERR [Can't get shared memory id '7a6d2002', 2: No such file or directory]
08/20/07 17:44:00.735186 zmwatch[3964].INF [Restarting capture daemon for mobotix, shared memory not valid]
08/20/07 17:44:00.865283 zmwatch[3964].INF ['zmc -m 2' starting at 07/08/20 17:44:00, pid = 4986]
==> /tmp/zmdc.log <==
08/20/07 17:44:21.134479 zmdc[3925].INF ['zmc -m 2' starting at 07/08/20 17:44:21, pid = 5006]
08/20/07 17:44:21.142711 zmdc[3925].ERR ['zmc -m 2' exited abnormally, exit status 255]
I supposed i wrong something in configuration so I try the command
wget -S
http://admin:meinsm@172.17.8.111/record/current.jpg
and in this way I obtain the snapshot..so the camera is working.
I have read all readme, FAQ, forums but haven't found a solution.
please contact me for more informations if needed
Thanks,
Marcello
Posted: Mon Aug 20, 2007 5:15 pm
by jameswilson
wget -S
http://admin:meinsm@172.17.8.111/record/current.jpg
Whats that url. it isnt a zm one
Id suggest you have a capture issue, ie mismatched config on res etc. Either way zm isnt capturing the image. Is it a supported cam?
Posted: Mon Aug 20, 2007 6:57 pm
by cordel
All that these two lines mean:
- 08/20/07 17:44:00.734992 zmwatch[3964].ERR [Can't get shared memory id '7a6d2002', 2: No such file or directory]
08/20/07 17:44:00.735186 zmwatch[3964].INF [Restarting capture daemon for mobotix, shared memory not valid]
Is that zmc was unable to capture an image and place it in shared memory.
What setting do you have for you monitor?
Should be:
- host: admin:meinsm@172.17.8.111
Port: 80
Path: /record/current.jpg
and of course the dimensions have to match.
More informations
Posted: Tue Aug 21, 2007 6:47 am
by patamar
I'm using this configuration:
host:admin:meinsm@172.17.8.111
port:80
path:/record/current.jpg
dimentions are 640x480
"wget -S
http://admin:meinsm@172.17.8.111/record/current.jpg"
I know this not a zm command but I used it to understand if the cam is working and sending jpegs.
p.s. Restarting zm i recive this logs..
==> /tmp/zmdc.log <==
08/21/07 08:45:50.137371 zmdc[3908].INF ['zmupdate.pl -c' stopping at 07/08/21 08:45:50]
08/21/07 08:45:50.138405 zmdc[3908].INF ['zmupdate.pl -c' crashed, signal 14]
08/21/07 08:45:50.138639 zmdc[3908].INF ['zmwatch.pl ' stopping at 07/08/21 08:45:50]
08/21/07 08:45:50.139486 zmdc[3908].INF ['zmwatch.pl ' crashed, signal 14]
08/21/07 08:45:50.139769 zmdc[3908].INF ['zmfilter.pl ' stopping at 07/08/21 08:45:50]
08/21/07 08:45:50.140902 zmdc[3908].INF ['zmfilter.pl ' crashed, signal 14]
08/21/07 08:45:50.141221 zmdc[3908].INF ['zmaudit.pl -c' stopping at 07/08/21 08:45:50]
08/21/07 08:45:50.142043 zmdc[3908].INF ['zmaudit.pl -c' crashed, signal 14]
08/21/07 08:46:00.220196 zmdc[3908].INF [Server shutdown at 07/08/21 08:46:00]
tail: /tmp/zmdc.sock: No such file or directory
08/21/07 08:46:00.481759 zmdc[5192].INF [Server starting at 07/08/21 08:46:00]
tail: /tmp/zmdc.sock: No such device or address
Posted: Tue Aug 21, 2007 7:21 am
by jameswilson
All those are symptoms caused cos zm cant get images. Id suggest that maybe the 640x480 is wrong does the url you post give that res or another. Either way until you get images from the cam then other things will crash, cos there is no image to work on. Its not the crashes that stopping the image its the fact there is no image causing the crashs
Posted: Tue Aug 21, 2007 7:38 am
by patamar
The image I get with wget is a jpg of 640x480. I tried others dimentions but with no results.
follows the complete monitor config:
GENERAL
Source Type : remote
Function: Monitor
Enabled: yes
Linked Monitors: 2
max Fps : 25.00
Alarm..:
Reference Image Blend %ge: 7
Treigger : None available
SOURCE
HostName: admin:meinsm@172.17.8.111
port: 80
path: /record/current.jpg
colors: 24 bit
width: 640
Height: 480
Orientation: Normal
I haven't make changes on Timestamp, Buffers and Misc
Marcello
Posted: Tue Aug 21, 2007 7:57 am
by jameswilson
Maybe the cam isnt compatible, not all are.
Can you adjust the image down to 320x240 and remove the auth till we get it working
Also if you could make your cam public ill test to see if its zm compatible
Posted: Tue Aug 21, 2007 12:32 pm
by patamar
"Can you adjust the image down to 320x240"
done and now it works!
"and remove the auth till..
Also if you could make your cam public ill test to see if its zm compatible"
sorry don't understand it..
is there a reason for the impossibility to use 640x480? It's a very expensive camera and I'd like to use is good quality.
thanks,
Marcello
Posted: Tue Aug 21, 2007 8:53 pm
by jameswilson
there could be many reasons, usually its a shmget issue (see wiki) but i didnt see that in your logs.
If you put your cam on the internet (so i can access it) then ill add it to my zm box and test it at 640x480 for you
Posted: Wed Aug 22, 2007 8:07 am
by patamar
thanks, all u have said was right!!
The problem was in the shared memory, I used this command and now I can see the cam in 640x480
"echo 134217728 >/proc/sys/kernel/shmall && echo 134217728 >/proc/sys/kernel/shmmax"
I added two cameras but now recording and seeing them I have a load around 3-3.5 i suppuse it's too much.
Thanks
marcello
Posted: Wed Aug 22, 2007 12:33 pm
by jameswilson
depends on a quad core no. single core yes id say its too high
Posted: Wed Aug 22, 2007 1:26 pm
by patamar
It's a single core..but not a too old one (Athlon 64 3200 1GB ram). So i need a better CPU or a video card or more ram..
Marcello
Posted: Thu Aug 23, 2007 2:47 am
by Lee Sharp
You do not need a video card at all. I would bump the memory, and set your shared memory to 1 gig.
Posted: Thu Aug 23, 2007 8:55 am
by cordel
Just a note since It's been a while since I reminded any one....
ZM when set to analyze motion can be processor intensive. You can bring down the load by bringing down the amount of frames that are analyzed by adjusting the overall capture fps down.
A big strain also if you have the desktop installed and using Firefox on the same system to view streams..... Run headless