Incomplete read of frame image data, 32496 bytes only

[sgocken]

Great product.

One problem I keep seeing in the logs is:

Jul 12 14:55:38 cameras zmf-m1[3418]: ERR [Incomplete read of frame image data, 32496 bytes only]
Jul 12 14:55:39 cameras zma-m1[3422]: ERR [Can't write frame: Broken pipe]
Jul 12 14:55:39 cameras zmf-m1[3418]: INF [Frame server socket open, awaiting images]
Jul 12 14:55:40 cameras zmf-m1[3418]: ERR [Incomplete read of frame image data, 32496 bytes only]
Jul 12 14:55:40 cameras zma-m1[3422]: ERR [Can't write frame: Broken pipe]
Jul 12 14:55:40 cameras zmf-m1[3418]: INF [Frame server socket open, awaiting images]

They come in waves.
This box is more then powerful to run this:

duel Zeon 3.06
2 gig Ram
1 TB Raid Array
Running Red Hat Enterprise ES3
2.4 kernel

[zoneminder]

This is caused by the default buffer size on your system being too small to allow frames to be sent in one go. If you go to Options->System and then click on the help (the '?') for ZM_FRAME_SOCKET_SIZE it explains a bit further. Basically the frame server daemon exists to try and speed up image writes to disk, if the image can't be written in one go then it defeats the object a bit. A simple tweak to a system setting is usally enough to fix it.

Phil,

[sgocken]

Could it be too big? I set that to 134217728, which is the same as my shared memory. But then I read that closer and set it the same as my wmem_max. We will see if that fixes it.

[zoneminder]

Don't set it too large. It's a buffer size that several things may use and you might find all your memory just vanishes if it's massive. It' not connected to shared memory at all. Just try doubling or quadrupling the existing value.

Phil,

[sgocken]

Well I have 2 gig of RAM. I tried setting it to 50000, But I am still getting that error.
What are you using for the buffer size?