Marius 34f91ba206 Fix Oracle DR test cron execution by adding explicit PATH
Problem: The weekly DR test script worked when run manually but failed
when executed via cron with "Failed to start VM 109" error at 0 seconds.

Cause: Cron jobs run with a minimal PATH that doesn't include /usr/sbin
where Proxmox commands (qm, pvesh, etc.) are located. Manual execution
had the full PATH including /usr/sbin.

Solution: Added explicit PATH export at the start of the script to ensure
all required system binaries are accessible regardless of execution context.

Testing: Successfully verified with cron test at 11:32 - VM started properly,
restore process completed normally.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-06 11:37:27 +02:00
2025-10-26 18:52:44 +02:00
2025-09-30 02:06:34 +03:00
Description
No description provided
938 KiB
Languages
Shell 50.4%
PowerShell 15.4%
Python 12.7%
PLSQL 11.2%
Batchfile 10.3%