Intermitten Red Cameras???

[maximus]

I know that this has been asked i have searched.

we changed our ver of zm from 1.23.x to 1.24.2 we are currently running it on mint debian, we ran jaunty before.

The problem:
we have abour 45 cameras connected some will connect (green) then disconnect(red) intermittently.

checked log's
saw the

Code: Select all

03/29/11 14:37:18.902787 zmwatch[2942].ERR [Can't get shared memory id '7a6d0010', 16: No such file or directory]
03/29/11 14:37:28.911407 zmwatch[2942].ERR [Can't get shared memory id '7a6d0010', 16: No such file or directory]
03/29/11 14:37:38.922528 zmwatch[2942].ERR [Can't get shared memory id '7a6d0010', 16: No such file or directory]
03/29/11 14:37:48.934485 zmwatch[2942].ERR [Can't get shared memory id '7a6d0010', 16: No such file or directory]
03/29/11 14:37:58.947592 zmwatch[2942].ERR [Can't get shared memory id '7a6d0010', 16: No such file or directory]
03/29/11 14:38:08.957710 zmwatch[2942].ERR [Can't get shared memory id '7a6d0010', 16: No such file or directory]
03/29/11 14:38:18.966174 zmwatch[2942].ERR [Can't get shared memory id '7a6d0010', 16: No such file or directory]
03/29/11 14:38:28.975617 zmwatch[2942].ERR [Can't get shared memory id '7a6d0010', 16: No such file or directory]

this are errors after calculating for /etc/sysctl.conf.

Code: Select all

~ # cat /etc/sysctl.conf|grep kernel.sh*
kernel.shmall = 2048000
kernel.shmmax = 4194304000

this was our sysctl.conf on jaunty also this is based on 50 camera setup running with 8bg mem 640x480.

if can double check or have insight as to why im getting errors i apriciate this thanks. or can this be due to anything else?

ps: we also have a couple of client pc's that connect all day to zm montage to show certain cams.

[maximus]

All camera's are network camera's. i have check all logs for zm the only error's i see are the shared mem issue.

[bb99]

I don't think shared memory is the issue here. The "Can't get shared memory id '7a6d0010'" complaint from zmwatch on a working system can be as simple as there is nothing at the base (SHM_KEY value) to get. Another cause can be monitor configuration mismatches with the camera configuration; in this case what is in shared memory is not what was expected. I don't have any experience on a system this large but load, collisions, store and forward timing, etc. come to mind. There are a couple of regulars here that do deal with this type of a set up, they'll chime in just be patient.

[maximus]

Thanks I really appreciate your input that is what i figured that maybe it is not a shared memory issue.

[maximus]

saw this in the am this morning @ log's

Code: Select all

Apr  4 08:12:17 fbc33 zmc_m17[23477]: INF [Got signal 15 (Terminated), exiting]
Apr  4 08:12:17 fbc33 zmc_m17[23477]: ERR [Select error: Interrupted system call]
Apr  4 08:12:17 fbc33 zmc_m17[23477]: ERR [Unable to read content]
Apr  4 08:12:17 fbc33 zmc_m17[23477]: ERR [Unable to get response]
Apr  4 08:12:17 fbc33 zmc_m17[23477]: ERR [Failed to capture image from monitor 17 (0/1)]
Apr  4 08:12:17 fbc33 zmdc[21855]: ERR ['zmc -m 17' exited abnormally, exit status 255]

[DREMA]

You said they're all network cameras, maybe you have a problem with the bandwich, or some collisions. 50 cameras at 640x480 are a lot of data to handle. It also could be your hard drives not being fast enought.

Try turning on the extra loggin to check for extra errors.

[maximus]

You said they're all network cameras, maybe you have a problem with the bandwich, or some collisions. 50 cameras at 640x480 are a lot of data to handle. It also could be your hard drives not being fast enought.

Try turning on the extra loggin to check for extra errors.

bandwidth and collision was initial thoughts i used wireshark to do some network testing all i saw a couple cameras multcasting etc witch get blocked by our switches anyways.

as for the hard drives 3 tb and sda1

Code: Select all

fbc33 ~ # sudo hdparm -tT /dev/sda1
/dev/sda1:
 Timing cached reads:   14936 MB in  1.99 seconds = 7492.02 MB/sec
 Timing buffered disk reads:  362 MB in  3.00 seconds = 120.49 MB/sec

also we have ran with this setup before fine for a year or two just on 1.23.3

should be fast enough yesterday i had to reboot the machine witch when booting got stuck at loading kernel modules. after giving error

Code: Select all

 findfs : unable to resolve uuid=" " for the drive 

im guessing that is from changing from ubuntu to debian mint.

[DREMA]

Mmm I see. If you keep getting the "03/29/11 14:37:18.902787 zmwatch[2942].ERR [Can't get shared memory id '7a6d0010', 16: No such file or directory]" errors, yu could try using the nmap memory instead to discard this from the problem list.

[maximus]

Mmm I see. If you keep getting the "03/29/11 14:37:18.902787 zmwatch[2942].ERR [Can't get shared memory id '7a6d0010', 16: No such file or directory]" errors, yu could try using the nmap memory instead to discard this from the problem list.

thanks for your input i apriciate that i actually reverted to 1.23.3, i will take a mint debian pc to see if i get same result for some monitor and also test out the nmap memory.