ZoneMinder
memory map - unexpected size, 5MP camera
Env:
- Version of ZoneMinder [v.1.37.27]
- How you installed ZoneMinder [zmrepo]
- Full name and version of OS: CentOs 7 - 3.10.0-1160.71.1.el7.x86_64
- Browser name and version: chrome Version 108.0.5359.125 (Official Build) (64-bit)
Cam:
- frame rate: 15fps
- resolution: 2592x1944 (5MP)
- ZoneMinder Source Type: TCP (RTSP)
Monitor Settings: cam is in recording mode, ptz => regularly changing position - no analysis needed capturing: always decoding: on demand capture resolution: 2592x1944 (5MP) color depth: 32b analysis: none recording: always Buffers:
- buffers size: 20
- max buffer size: 20
- warmup: 10
- pre-event 15
- post event 300
- stream replay 0
- alarm count 1
Description of the issue: When setting buffer size and max buffer size to a value > 20, an error shows up in zms_m??.log
Got unexpected memory map file size 524046188, expected 423269148
Unable to connect to monitor id ?? for streaming
Monitor shm is not connected
The reported size in the log matches the size of the /dev/shm/ file The "expected size" reported in the logs is the one when the buffer size is set to 20. The shared mem file has the right owner and rights. Stopping zoneminder deletes all shared mem files. Starting zoneminder again, error is still present.
Error goes away when setting the buffer size to 20. Doesn't seem to be any other impact other than the error reported in the log, and of course the status of zoneminder to be permanently in ALARM.
I suspect that the size of the buffers is irrelevant. I suspect that the zms is already running during the change right? So zmc restarts and resizes the mmap, but zms doesn't know about it and so complains. Likely zms isn't reloading the monitor config upon noticing the discrepancy,
zms is a CGI program, so doesn't get restarted when you restart zoneminder. It will restart when you stop viewing the stream.
