I'm running 1.36.34 as VM into Proxmox environment.
Every day I found VM stopped, probably a lack of rersources issue.
Where should I start to find the cause (into ZM or Proxmox) ?
Thanks.
Help to diagnose crash
Re: Help to diagnose crash
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 the ZM virtual machine unless you have plenty of RAM in the host. ZM will tend to use all RAM given, much of it for caching because that is the Linux way. Linux caches reads and writes and ZM writes all the time.
As an example, here is my ZM server:
If this were on Proxmox it would be consuming 16GB or RAM from Proxmox.
2nd check the OS logs for the reason of the shutdown. Expected or unexpected?
Ballooning memory enabled? You should not use ballooning memory with the ZM virtual machine unless you have plenty of RAM in the host. ZM will tend to use all RAM given, much of it for caching because that is the Linux way. Linux caches reads and writes and ZM writes all the time.
As an example, here is my ZM server:
Code: Select all
free -m
total used free shared buff/cache available
Mem: 15897 3593 360 383 11943 11582
Swap: 4095 2039 2056
Andy
o||||o
Ubuntu 22.04
ZM 1.36.33
E5-1650-v4 Xeon
16 GB RAM
6 cameras -> 54 FPS modect
o||||o
Ubuntu 22.04
ZM 1.36.33
E5-1650-v4 Xeon
16 GB RAM
6 cameras -> 54 FPS modect