Files
ProxmoxVE/tools
MickLesk ec1a852d9b monitor-all: decide on flag values, not on key presence
template and onboot are booleans, and Proxmox writes template: 0 for
plain containers instead of omitting the key, so the presence check
classified every one of them as a template and skipped it.

Read the value for both flags, match mon-restart against a whole
semicolon separated tag entry, skip instances whose config disappeared
between listing and reading, start instances that are stopped instead
of forcing a failing exec and ping first, and resolve the container
address from the first global one rather than assuming eth0.

The unit looped with its own five minute sleep, so the accompanying
timer could only ever start a service that was already running; drop
it and order the service after pve-cluster instead, which is what
actually has to be up before /etc/pve can be read.
2026-09-14 16:01:14 +02:00
..
2026-09-11 10:17:05 +02:00
2026-09-11 10:18:07 +02:00