mirror of
https://github.com/MacRimi/ProxMenux.git
synced 2026-06-03 21:54:42 +00:00
17c5b89cc8
The v1.2.2 install layout extracts the AppImage into /usr/local/share/proxmenux/monitor-app/ and runs AppRun out of that directory — but install_proxmenux_monitor's update branch only called create_monitor_service on fresh installs, leaving the inherited unit's `ExecStart=/usr/local/share/proxmenux/ProxMenux-Monitor.AppImage` in place. That path used to be the FUSE-mounted AppImage entry point, which v1.2.2 deliberately replaced to clear a Wazuh rule-521 false positive on /tmp/.mount_*. On PVE 9.x / Debian 13 the bare AppImage fails to exec straight away (status=203/EXEC) so the service entered the activating loop reported in #222 and never came back up. Always rewrite the unit before the post-update `systemctl start` — idempotent for installs whose unit is already correct, recovering for those whose isn't. The new helper `_proxmenux_rewrite_monitor_unit_for_apprun` mirrors the unit body the fresh-install path emits in `create_monitor_service`, with the same template-from-repo / inline-fallback fork, so both paths converge on the same content. Reproduced and validated on PVE 9.x lab: before: Process: ExecStart=/usr/local/share/proxmenux/ProxMenux-Monitor.AppImage (code=exited, status=203/EXEC) Active: activating (auto-restart) after: ExecStart=/usr/local/share/proxmenux/monitor-app/AppRun Active: active (running) Bumps version.txt to 1.2.2.1 so the existing menu update path picks this up automatically. For users already stuck on a broken v1.2.2, re-running the installer manually applies the same fix: bash -c "$(wget -qLO - https://raw.githubusercontent.com/MacRimi/ProxMenux/main/install_proxmenux.sh)" Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2 lines
8 B
Plaintext
2 lines
8 B
Plaintext
1.2.2.1
|