fix(status): probe system-level systemd unit when user-level unavailable

yiyouguisu · yiyouguisu · commit 0db2a0a7fd16 · 2026-05-22T09:47:55.000+08:00
When the gateway runs under a system-level systemd unit (not user-level), systemctl --user is unavailable and the status check reports "systemd user services unavailable" as a false positive. Instead of relying on INVOCATION_ID detection, directly probe system-level systemctl when user-level fails. If the unit exists and responds at system level, return the actual status. Fixes #85094
diff --git a/src/daemon/systemd.ts b/src/daemon/systemd.ts
@@ -1080,6 +1080,32 @@ export async function readSystemdServiceRuntime(
   try {
     await assertSystemdAvailable(env);
   } catch (err) {
+    // When running under a system-level systemd unit (not user-level),
+    // systemctl --user is unavailable but the gateway may be healthy.
+    // Probe system-level systemctl directly to check the unit status.
+    // See: https://github.com/openclaw/openclaw/issues/85094
+    const serviceName = resolveSystemdServiceName(env);
+    const unitName = `${serviceName}.service`;
+    const systemRes = await execFileUtf8("systemctl", [
+      "show",
+      unitName,
+      "--no-page",
+      "--property",
+      "ActiveState,SubState,MainPID,ExecMainStatus,ExecMainCode",
+    ]).catch(() => null);
+    if (systemRes && systemRes.exitCode === 0) {
+      const parsed = parseSystemdShow(systemRes.stdout || "");
+      const activeState = normalizeLowercaseStringOrEmpty(parsed.activeState);
+      const status = activeState === "active" ? "running" : activeState ? "stopped" : "unknown";
+      return {
+        status,
+        state: parsed.activeState,
+        subState: parsed.subState,
+        pid: parsed.mainPid,
+        lastExitStatus: parsed.execMainStatus,
+        lastExitReason: parsed.execMainCode,
+      };
+    }
     return {
       status: "unknown",
       detail: formatErrorMessage(err),
