Zentyal does not provide HA. They started down that path a few versions ago before backing away from it. For me Zentyal still manages email and authentication services (AD). I am actively shopping for replacements as Zentyal no longer really fits my needs. I am taking a very hard look at...
Zentyal has a very convoluted way of defining reservations. First you define an object under network and then under dhcp advanced options you can add static reservations for that object. Confusing to say the least.
I have long since moved my dhcp functions over the pfsense. It was a...
Did you actually set the netmask for the proxmox machines to /32 ie 255.255.255.255?
That creates a network of 1. All outbound traffic from 192.168.1.116 would then be sent to the gateway address which you haven't included here.
Going off that assumption I suggest instead setting all...
Eventually you will probably run across the use case of needing the same feature for VM's. This is predicated on the kvm agent being installed.
qm guest exec <vmid> -- "wget" "http://gitlab.myrepo.com/root/my-test-item/-/raw/master/authorized_keys" "-O" "/root/.ssh/authorized_keys"
You can take a look at this thread for another option random-crashing-freezing
Adding alerts to what I have already said in that thread can be found in the Notifications Documentation
ETA change link to point directly to the post in question instead of the thread in general
You can push the desired ssh keys into the running container from the proxmox host with something like
pct push <vmid> authorized_keys /root/.ssh/authorized_keys
That would let you in turn ssh in and start customizing via ansible.
Also, I might suggest setting up an syslog-ng server on another computer and send your logs to it via rsyslog. This might allow the server to gasp out a final message in a situation where the disk subsystem has already expired.
Perhaps adding some monitoring tools could help you identify the issue. You can try adding netdata.
apt install netdata.
You will have to edit the config file to listen on the needed ip addresss (or just 0.0.0.0 for all)
It is reachable from https://your-ip-address:19999/
I would recommend...
Logs should give you some clue as to what has happened.
Is the machine at all responsive?
Can you get num-lock or cap-lock to change state?
I sort of doubt it but if by some miracle you can interact on the commandline with it in this condition try "dmesg -T" to see what may have happened...
There are a lot of variables to chase here. Maybe add some kind of external monitoring like Zabbix or Monit. You could also install Netdata and configure it to persist data locally. It would give you some metrics to eyeball around the time the problem occurs. Have you considered temperature...
While I have not investigated the correct method for doing it from the command line, I have converted lvm stored vms by moving the drive to another medium in the web interface.
Select the VM in question
Select the drive in question.
Above you will see "Move Disk" become...