Hello,
Using Proxmox VE 8.0.3 on Dell R620 48CPU - 256GB RAM 18 VMs works 7/24, all other 17 VM works perfectly but Zimbra Release 8.8.15.GA.4179.UBUNTU20.64 UBUNTU20_64 FOSS edition, Patch 8.8.15_P46. on Ubuntu 20.04 keeps getting unresponsive randomly.
As usual we thought it could be broken os, or hacking attack or some kind of warez etc. did all the checks as below;
--amavis is up to date
--Licenced Sentinel ONE installed
--Moved WM to another storage
--All mails backed up and freshly installed on Ubuntu 20.04 & Ubuntu 22.04
--Changed WAN ip address
--22 & 7071 (Zimbra management) behind ip tables and only accessible from specific ip addresses.
Plus to above checks we moved the wm to another proxmox ve 8.0.3 for 2 months and it didn't become unresponsive in this period, but when we moved back to our server it started unresponsive 3+ times in 2 weeks.
When it becomes unresponsive CPU & Memory goes to %100, ssh or console connection become impossible only force stop & start with below commands is working:
Strangely /var/log/syslog is always empty, where else i must check to debug further or what else can cause this symptom?
Using Proxmox VE 8.0.3 on Dell R620 48CPU - 256GB RAM 18 VMs works 7/24, all other 17 VM works perfectly but Zimbra Release 8.8.15.GA.4179.UBUNTU20.64 UBUNTU20_64 FOSS edition, Patch 8.8.15_P46. on Ubuntu 20.04 keeps getting unresponsive randomly.
As usual we thought it could be broken os, or hacking attack or some kind of warez etc. did all the checks as below;
--amavis is up to date
--Licenced Sentinel ONE installed
--Moved WM to another storage
--All mails backed up and freshly installed on Ubuntu 20.04 & Ubuntu 22.04
--Changed WAN ip address
--22 & 7071 (Zimbra management) behind ip tables and only accessible from specific ip addresses.
Plus to above checks we moved the wm to another proxmox ve 8.0.3 for 2 months and it didn't become unresponsive in this period, but when we moved back to our server it started unresponsive 3+ times in 2 weeks.
When it becomes unresponsive CPU & Memory goes to %100, ssh or console connection become impossible only force stop & start with below commands is working:
Code:
rm -rfv /var/lock/qemu-server/lock-105.conf
qm unlock 105
qm stop 105
qm start 105Strangely /var/log/syslog is always empty, where else i must check to debug further or what else can cause this symptom?
