Frame server

Forum for questions and support relating to the 1.24.x releases only.
Locked
NicoArias
Posts: 4
Joined: Thu Nov 12, 2009 1:14 pm

Frame server

Post by NicoArias »

Hello.

i have a dual quad core server with centos 5 and 24 cameras doing movent detection.

Some cameras haves a lot of movement and looks like its dropping events becouse the capture daemon gets locked tryng to write to disk. So, to improve this, i switched on the frame server, but when i do it i get:

zma_m27[3690]: ERR [Incomplete frame write: 16128 of 26610 bytes written]

my sysctl -a is http://pastebin.com/m1844320b

Image Buffer Size = 50
frame_socket_size = 531072


turning off OPT_FRAME_SERVER goes back to the normal -dropping events- state.

any hint?, the number 16128 keeps repeating, looks like theres a limit somewhere, but i cant find it.

cheers!
User avatar
knight-of-ni
Posts: 2406
Joined: Thu Oct 18, 2007 1:55 pm
Location: Shiloh, IL

Post by knight-of-ni »

Sounds like we both have the same issue. I've been meaning to post this for some time now, but until now I had not yet done so...

I'm running two small Zoneminder systems at two locations. Location #1 runs zm 1.23.3 on an Ubuntu 9.04 Desktop (Athlon X2 w/ 1GB RAM). Location #2 runs zm 1.24.2 on a CentOS 5.4 Server (two 2.8GHz dual core Opterons w/ 4GB RAM). Both systems are 64bit.

Following advice found in this forum, I have done the following to both systems.

Increased the following buffer sizes in sysctl.conf:

Code: Select all

net.core.wmem_max = 524286
net.core.wmem_default = 262143
net.core.rmem_max = 524286
net.core.rmem_default = 262143
From the zoneminder Options -> System tab, I have enabled OPT_FRAME_SERVER and set FRAME_SOCKET_SIZE to 262143 (I have also tried 524286 with no difference).

Note that the average jpeg size of captured images on both systems is less than 30KB.

Following a reboot, the frame server works great at Location #1 with 1.23.3. However, the frame server produces many incomplete read/write errors at Location #2 with 1.24.2 similar to the following:

Code: Select all

Nov  9 08:13:08 bauerhaus zmf_m1[15967]: ERR [Incomplete read of frame image data, 15960 bytes only]
Nov  9 08:13:08 bauerhaus zma_m1[15969]: ERR [Incomplete frame write: 16000 of 29832 bytes written]
Same as NicoArias, these errors disappear completely if I turn the frame server back off.

At this point I don't know if there is some limit in the operating system that we are not aware of, or if the frame server is just plain broken in the latest version of zm. One of these days I'm going to spend some time with a couple of CentOS and Ubuntu virtual sessions and figure this out, but in the meantime it would be good to get some feedback from anyone who is running zm 1.24.2 and is successfully using the frame buffer.

I've got a feeling that few people use it nowadays, but I'm hoping I'm wrong about that.
coke
Posts: 518
Joined: Wed Jan 30, 2008 5:53 pm
Location: St. Louis, MO, USA

Post by coke »

Ditto for me, though I hadn't tried it on 1.23.x, only 1.24.x. Tried turning it on to speed the system which had started to choke when I added too many megapixel cameras, and ended up with the same incomplete frame errors the above two have mentioned.
gsaraber
Posts: 2
Joined: Thu Dec 03, 2009 8:54 pm

Same

Post by gsaraber »

I'm having the same problem:
Zoneminder 1.24.1
Server: Dual Intel Xeon Quad core 1.6Ghz E5310 (so 8 total cores)
4GB memory
Writing to NFS (ugh, its part of the problem, so I wanted to try out the frame server)

I changed wmax and rmax to 512000...

and here's the log:
Dec 03 14:52:48 [zmf_m3] INF [Frame server socket open, awaiting images]
Dec 03 14:52:57 [zmf_m3] ERR [Incomplete read of frame image data, 31704 bytes only]
Dec 03 14:52:58 [zma_m3] ERR [Can't write frame: Broken pipe]
Dec 03 14:52:58 [zmf_m3] INF [Frame server socket open, awaiting images]
Dec 03 14:52:58 [zmf_m3] ERR [Incomplete read of frame image data, 31704 bytes only]
Dec 03 14:52:58 [zma_m3] ERR [Can't write frame: Broken pipe]
Dec 03 14:52:58 [zmf_m3] INF [Frame server socket open, awaiting images]
Dec 03 14:53:00 [zma_m8] INF [Package_area: 28250 - Gone into alert state]
Dec 03 14:53:01 [zma_m8] INF [Package_area: 28260 - Left alarm state (1543735) - 698(672) images]
Dec 03 14:53:01 [zma_m8] INF [Package_area: 28260 - Closing event 1543735, alarm end]
Dec 03 14:53:01 [zma_m8] INF [Package_area: 28267 - Gone into alarm state]
Dec 03 14:53:01 [zma_m8] INF [Package_area: 28267 - Opening new event 1543736, alarm start]
Dec 03 14:53:05 [zmf_m8] ERR [Incomplete read of frame image data, 31704 bytes only]
Dec 03 14:53:05 [zma_m8] ERR [Can't write frame: Broken pipe]
Dec 03 14:53:05 [zmf_m8] INF [Frame server socket open, awaiting images]
genanr
Posts: 9
Joined: Tue Apr 08, 2008 9:49 pm

Post by genanr »

I posted a patch in the user contributions forum to fix the "Incomplete frame" problem. Here is a link to my post:

http://www.zoneminder.com/forums/viewtopic.php?t=15255

Andy
Locked