From 9e904d23a3328bc5d2e81a5039e6a8f1676ac548 Mon Sep 17 00:00:00 2001 From: Frank Date: Tue, 1 Sep 2026 05:16:27 -0700 Subject: [PATCH] deploy-remote: daemon-reload after copying hermes units, before restarts The first deploy after a unit-file edit restarted with the stale generated unit (generator had not seen the new Volume= paths), crash-looping hermes on statfs ENOENT for the just-renamed data root. Reload between cp and restart. --- scripts/deploy-remote.sh | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/scripts/deploy-remote.sh b/scripts/deploy-remote.sh index 148751f..a29f0e0 100755 --- a/scripts/deploy-remote.sh +++ b/scripts/deploy-remote.sh @@ -694,6 +694,11 @@ deploy_hermes() { for unit in hermes hermes-dashboard hermes-webui; do cp "dankclaw/hermes/quadlet/$unit.container" "$quadlet_unit_dir/" done + # The generator must see the freshly-copied unit files before the + # restarts below; without this reload the first deploy after a unit edit + # restarts with the stale generated ExecStart (statfs ENOENT on renamed + # Volume= sources). + systemctl --user daemon-reload if ! systemctl --user is-active --quiet hermes.service; then podman stop hermes hermes-dashboard hermes-webui 2>/dev/null || true podman rm hermes hermes-dashboard hermes-webui 2>/dev/null || true