ZoneMinder Forums

I have increased both net.core.rmem_max and net.core.wmem_max from 65535 to 131072 and changed ZM_FRAME_SOCKET_SIZE to 131072 in Options but I still get the occasional incomplete frame write as you can see in the attached log.
I thought it might have something to do with 2 cameras being in alarm state at the same time but that condition happens later in the log without a problem.
Is it just a question of increasing the buffer size until it never happens again, or could something else be causing this occasional occurrence?

Oct 20 08:10:00 zedz zma-m2[913]: INF [FrontDoor: 87352 - Gone into alarm state]
Oct 20 08:10:02 zedz zma-m5[933]: INF [Bullet: 87356 - Gone into alarm state]
Oct 20 08:10:02 zedz zma-m5[933]: ERR [Incomplete frame write: 48960 of 72851 bytes written]
Oct 20 08:10:02 zedz zmf-m5[929]: ERR [Incomplete read of frame image data, 48944 bytes only]
Oct 20 08:10:02 zedz zmf-m5[929]: INF [Frame server socket open, awaiting images]
Oct 20 08:10:09 zedz zma-m5[933]: INF [Bullet: 87374 - Left alarm state (19814) - 30(3) images]
Oct 20 08:10:09 zedz zma-m2[913]: INF [FrontDoor: 87377 - Left alarm state (19813) - 40(10) images]
Oct 20 08:10:20 zedz zma-m5[933]: INF [Bullet: 87405 - Gone into alarm state]
Oct 20 08:10:20 zedz zma-m2[913]: INF [FrontDoor: 87407 - Gone into alarm state]
Oct 20 08:10:28 zedz zma-m5[933]: INF [Bullet: 87426 - Left alarm state (19815) - 33(6) images]
Oct 20 08:10:41 zedz zma-m2[913]: INF [FrontDoor: 87464 - Left alarm state (19816) - 72(27) images]
Oct 20 08:10:46 zedz zma-m2[913]: INF [FrontDoor: 87478 - Gone into alarm state]
Oct 20 08:11:01 zedz zma-m2[913]: INF [FrontDoor: 87519 - Left alarm state (19817) - 56(23) images]
Oct 20 08:11:44 zedz zma-m1[903]: INF [DriveWay: 87636 - Gone into alarm state]
Oct 20 08:11:48 zedz zma-m5[933]: INF [Bullet: 87643 - Gone into alarm state]
Oct 20 08:12:05 zedz zma-m1[903]: INF [DriveWay: 87691 - Left alarm state (19818) - 70(37) images]
Oct 20 08:12:07 zedz zma-m5[933]: INF [Bullet: 87697 - Left alarm state (19819) - 66(39) images]

thanks
tommy

Have you changed the buffer size in the sysconfig file or just in /proc? One has immediate effect, the other only after a reboot.

Phil,

I've changed the /etc/sysctl.conf.
My machine boots up with the values 131072.

Here's a portion of sysctl -a after a boot.

net.core.netdev_max_backlog = 300
net.core.dev_weight = 64
net.core.rmem_default = 65535
net.core.wmem_default = 65535
net.core.rmem_max = 131072
net.core.wmem_max = 131072
vm.max_map_count = 65536
vm.max-readahead = 31
vm.min-readahead = 3

tommy

Here is another occurrence with a little more info.
The error occurred at 12:50:10. Three cameras alarmed about a minute later with no error. What's peculiar is that when I do "ls /tmp/zm* -l",
it shows the update time as 12:50 for zmf-1, the time of the error, but still shows the startup time for the other sockets. Looks like they weren't touched even though there were subsequent alarms. Does this indicate anything to you?

Oct 22 12:50:10 zedz zma-m1[876]: INF [DriveWay: 3306 - Gone into alarm state]
Oct 22 12:50:10 zedz zma-m1[876]: ERR [Incomplete frame write: 16320 of 84094 bytes written]
Oct 22 12:50:10 zedz zma-m1[876]: WAR [Can't connect to frame server: Connection refused]
Oct 22 12:50:10 zedz last message repeated 7 times
Oct 22 12:50:10 zedz zmf-m1[872]: ERR [Incomplete read of frame image data, 16304 bytes only]
Oct 22 12:50:10 zedz zmf-m1[872]: INF [Frame server socket open, awaiting images]
Oct 22 12:50:22 zedz zma-m1[876]: INF [DriveWay: 3337 - Left alarm state (19949) - 46(14) images]
Oct 22 12:51:07 zedz zma-m5[906]: INF [Bullet: 3449 - Gone into alarm state]
Oct 22 12:51:07 zedz zma-m1[876]: INF [DriveWay: 3451 - Gone into alarm state]
Oct 22 12:51:12 zedz zma-m2[886]: INF [FrontDoor: 3463 - Gone into alarm state]
Oct 22 12:51:17 zedz zma-m1[876]: INF [DriveWay: 3477 - Left alarm state (19951) - 41(11) images]
Oct 22 12:51:21 zedz zma-m5[906]: INF [Bullet: 3485 - Left alarm state (19950) - 48(20) images]
Oct 22 12:51:23 zedz zma-m2[886]: INF [FrontDoor: 3492 - Left alarm state (19952) - 44(14) images]
Oct 22 13:08:34 zedz -- MARK --

ls /tmp/zm* -l
-rw-r--r-- 1 www-data www-data 6011 2004-10-22 12:43 /tmp/zmaudit.log
-rw-r--r-- 1 www-data www-data 1352 2004-10-22 12:28 /tmp/zmdc.log
srwxr-xr-x 1 www-data www-data 0 2004-10-22 12:28 /tmp/zmdc.sock
srwxr-xr-x 1 www-data www-data 0 2004-10-22 12:50 /tmp/zmf-1.sock
srwxr-xr-x 1 www-data www-data 0 2004-10-22 12:28 /tmp/zmf-2.sock
srwxr-xr-x 1 www-data www-data 0 2004-10-22 12:28 /tmp/zmf-4.sock
srwxr-xr-x 1 www-data www-data 0 2004-10-22 12:28 /tmp/zmf-5.sock
-rw-r--r-- 1 www-data www-data 20 2004-10-22 12:28 /tmp/zmfilter.log
-rw-r--r-- 1 www-data www-data 1623 2004-10-22 12:28 /tmp/zmpkg.log
-rw-r--r-- 1 www-data www-data 71 2004-10-22 12:28 /tmp/zmwatch.log

thanks
tommy