ZoneMinder Forums

Likely it is the detection threshold. I changed to pixels instead of percent to gain tighter control. My trick is to find a person sized object in the frame and draw a tight zone around it. The zone properties will tell me the pixel count. I delete the test zone and set the detection size to the ...

If the VM is stopped first check the Proxmox logs to see if there is a clue as to the reason of the shutdown. RAM and disks would be my first suspects. 2nd check the OS logs for the reason of the shutdown. Expected or unexpected? Ballooning memory enabled? You should not use ballooning memory with ...

To me it sounds like you have orphaned files somewhere. Scan the drive for files older than 3 months (the point you state video is being deleted) and see what shows up.
The other possibility, though unlikely, is you are using a very large block size and the missing space is slack in the blocks.

What is the keyframe interval? The key frame is a complete picture, the following frames are changes to the key frame. In a static image the key frame will be much larger than the following frames.
I have my key frame interval set to 1 sec.

Then it is down to basic troubleshooting. I would start with pinging a working and troublesome camera just before midnight until the problem occurs to see if the camera remains on-line. This will show if it is ZM or not. If the 2 test cameras use the same AP, this will show if it is the AP or the ...

That looks similar to when my cameras restart once a week. Are your cameras restarting?

What you did looks correct, but if ZM cannot use a storage pool it will try another one.
Perhaps there is a small typo in the path of the storage pool.

It is a Linux thing; unused RAM is wasted RAM. Linux is more or less caching all writes. If you gave it a TB of RAM it would eventually use most of it for cache.
If the host needs more RAM, you can experiment with reducing the RAM on the ZM VM. Mine is happy with 16GB.

Memory usage from Proxmox will only be a small part of the story, and not the useful part. If you look at the VM and run free it will give you better detail. You may find something similar to my system with 6 hi-res and 6 low-res cameras. free -m total used free shared buff/cache available Mem ...

Through my several iterations of ZM, I have come to the conclusion that you need about 1 thread per motion detection. This is not a hard rule, but my experience. My 6 cameras use about 1.5TB per month. 6x 2-8MP motion only and 6x 640x480 continuous recording. The advice for a larger HDD may be wise ...

All of mine are blank. To my knowledge all of those settings are for local cameras. I have never added a second source so I cannot say how ZM will behave with those settings. Edit: I looked up the 2nd source option and found this note: New Feature in ZoneMinder 1.37 Note that the SourceSecondPath ...

The FPS options in the Source tab of the monitors is to control local camera frame rates. They should be left blank for IP cameras. The FPS is controlled by the camera. Since some of your cameras do not allow this I am not sure how you could control the FPS.

I would start with Reference Image Blend %ge on the General tab of the monitor. This controls how long it take ZM to become "used" to the new picture. Lower numbers should result in a longer record time.

The keyframe interval is set on the camera. In my case the lowest value is the FPS setting, so 1 per second. Many other threads about various topics tend to indicate 1 keyframe per second is desirable. I have run ZM on several systems through the years. Anytime I had less than 1 thread per motion ...

Could you post a picture of the zone settings?