A server locked up in my ZFS cluster recently. It was over the weekend when I run backups to an NFS share.
The oddity is that 3 different servers in 2 different clusters (zfs & Lvm) have been affected.
The only commonality I can find is running backups to an NFS share on a Synology.
I had similar issues with Proxmox 8.x. I backup to a synology nas via NFS and a host completely froze up during backup.
I also had migration issues, both live and cold would randomly crash.
Backup restores displayed the same symptoms as migrations.
However:
I had 2 clusters: one using LVM...
Thanks for the response. The question was not "does the backup also contain messages from the spam quarantine?"
The issue is that restoring rules from a backup would make the quarantine suddenly lose all of its mail, which is what happened to me.
I take it those messages, that were once in the...
I made a backup of my rules before making some modifications. Later when I restored the rules from backup the spam quarantine was suddenly empty.
Sometimes important mail ends up in the quarantine. Is there a way to recover these messages so they can be released?
You will likely run into other issues, for example with migration from one node to another.
i think you must change the name and IP when reinstalling proxmox.
following the line of thought regarding permissions I changed the apps to run as root, then opened up permissions on the system tools and nagios and zabbix files. The issue still exists. The issue seems to be *isolated* to LXC containers as both apps *with default permissions* work fine in a...
Thanks for the reply. The containers are not firewalled, and I can manually ping other systems from these LXC containers using the shell (command line). The issues seem to arise when the command is initiated by zabbix or nagios.
I'm trying to get Nagios and Zabbix running within LXC containers. Ping tests initiated by these monitoring systems don't seem to be working when running inside LXC. Manually ping from the command line works fine. Does anyone know a workaround?
The products work fine in KVM/Qemu.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.