Hello!
I see a PVE update I ran a week ago has introduced a new backup hook script phase 'job-init'.
Since my hook script sanitizes its input and job-init isn't included in allowed values, the script exits. The result is that I've had no backups running for a week and I haven't received any e-mail about it.
Can the vzdump script be improved so that it will report backup failures caused by hook scripts by e-mail?
Fortunately I just randomly happened on these failures by looking at PVE web UI.
I see a PVE update I ran a week ago has introduced a new backup hook script phase 'job-init'.
Since my hook script sanitizes its input and job-init isn't included in allowed values, the script exits. The result is that I've had no backups running for a week and I haven't received any e-mail about it.
Can the vzdump script be improved so that it will report backup failures caused by hook scripts by e-mail?
Fortunately I just randomly happened on these failures by looking at PVE web UI.
syslog:Apr 15 03:00:01 node CRON[3346093]: (root) CMD (vzdump --storage local --compress zstd --node node--all 1 --mode snapshot --quiet 1 --mailto me@mine.com --mailnotification always)
syslog:Apr 15 03:00:02 node vzdump[3346094]: <root@pam> starting task UPID:node:00330F53:041D5283:6258B582:vzdump::root@pam:
syslog:Apr 15 03:00:02 node vzdump[3346259]: command '/root/vzdump-hook-script.sh job-init' failed: exit code 1
syslog:Apr 15 03:00:02 node vzdump[3346094]: <root@pam> end task UPID:node:00330F53:041D5283:6258B582:vzdump::root@pam: command '/root/vzdump-hook-script.sh job-init' failed: exit code 1