ZoneMinder Forums

Keyframes are set for every two seconds.

So, now that I've "brought the car to the mechanic" it's "stopped making that funny clunking noise". I haven't had a single cam go over 3G in RAM usage since Monday morning.... I haven't changed anything except the logging levels (moved them all from INFO to WARNING in the config in order to prepare ...

All monitors between numbers 10 and 18 share the same network storage, which is a RAID-5 array on an LSI 2308 based controller. If it were slow disk access, all monitors 10 thru 18 would be showing the "backup" The database is running on the VM itself. I do not have a centralized MySQL installation ...

Yeah... Caught this just before ZM crashed, again. Monitor 10 is configured identically to monitors 11-13 and 18. Different cameras, same config, same colordepth, same resolution (these are the Hi-Res nocord that get triggered by their Lo-Res counterparts), same ZM config. I cannot, for the life of ...

The memory usage on .28 as of this morning. I'm still wary of attempting to upgrade to .29 again because of that memory issue.
To get here, I had to restart individual monitors individually. The monitor which was holding more than half the VMs RAM is behaving itself - for now.

Last one I remember not going ape on RAM usage was before .24

Presently one of the zmc processes is holding 13GB res and 15GB virt.

This is on .28 after restoring the VM. I'm not really wanting to reinstall .29 presently, but it was the zmc processes on .29, as well.

I installed the update from 1.36.28 to .29 then rebooted the Ubuntu Server 22.04 VM. Within 5 minutes, the VM crashed. By crashed I mean it was completely unresponsive except for pings (it would respond to pings, but couldn't SSH in, or get any response to input in the hypervisor's VM console). I ...

So I just did as you suggested and reinstalled 1.36 and ran the zmupdate.pl

All the cams came back online without making a single other change.

Just an FYI.

The VMs can ping IPs on every VLAN that is connected to them, including the cameras, the PoE switches, etc. After the install (apt update) I saw the traffic on the cams VLAN go from he usual 8Mbit/s down to zero. ONVIF will not find the cams from within ZM, but onvif apps (and nmap, etc) can see the ...

It started out working great.. I installed 1.37.12 over 1.36.something... 1.37.12 worked OK - had some issues streaming through a reverse proxy, but nothing I couldn't work around. Starting with .14 I could no longer stream to any VLAN other than VLAN 1 - and could not stream the cameras outside of ...

Same issue. Ubuntu 20.04 in a ProxMox VM. At first I thought it was ProxMox doing strange things, but then I ran across this thread. The really strange thing is that, since upgrading from 1.34, /dev/shm is almost untouched. I've considered trying to build under FreeBSD to see if the behavior is ...

This behavior is back.. Chrome on linux and chromebook with ZM on Ubuntu Server 20.04

You didn't turn on debug. That was from syslog, with debug turned on.. believe it or don't. I wasn't just going to blast out the database.. I was planning on removing all vestiges of ZM from the system and re-installing from scratch... Then, if I still have the issue, it'll show. This has only been ...

Oct 30 14:37:50 maximilian zma_m7[93858]: ERR [zma_m7] [Got empty memory map file size 0, is the zmc process for this monitor running?] Oct 30 14:37:51 maximilian zma_m7[93861]: ERR [zma_m7] [Shared data not initialised by capture daemon for monitor CAR-SE] Oct 30 14:37:54 maximilian zmc_m7[93855 ...