17 replies

Im Back, Every update...

✅Solved

So yesterday @krill you helped me fix the root update issue i was having, and you told me to do openclaw update for next updates.

This time I did just that OpenClaw update got an error:
keith@racknerd-f652ce7:~$ openclaw update
Updating OpenClaw...

│
◇ ✓ Updating via package manager (61.15s)

Update Result: OK
Root: /home/keith/.npm-global/lib/node_modules/openclaw
Before: 2026.2.24
After: 2026.2.25

Total time: 61.48s

Updating plugins...
No plugin updates needed.
Completion cache update failed (file:///home/keith/.npm-global/lib/node_modules/openclaw/dist/entry.js:655
if (state === "invalid") throw new Error(

Unsafe fallback OpenClaw temp dir: ${fallbackPath}

Unsafe fallback OpenClaw temp dir: ${fallbackPath}

);
^

Error: Unsafe fallback OpenClaw temp dir: /tmp/openclaw-1000
at ensureTrustedFallbackDir (file:///home/keith/.npm-global/lib/node_modules/openclaw/dist/entry.js:655:34)
at resolvePreferredOpenClawTmpDir (file:///home/keith/.npm-global/lib/node_modules/openclaw/dist/entry.js:669:51)
at file:///home/keith/.npm-global/lib/node_modules/openclaw/dist/entry.js:782:25
at ModuleJob.run (node:internal/modules/esm/module_job:343:25)
at async onImport.tracePromise.proto (node:internal/modules/esm/loader:665:26)
at async tryImport (file:///home/keith/.npm-global/lib/node_modules/openclaw/openclaw.mjs:39:5)
at async file:///home/keith/.npm-global/lib/node_modules/openclaw/openclaw.mjs:50:5

Node.js v22.22.0).
Regenerating shell completion cache...

Restarting service...
Failed to refresh gateway service environment from updated install: Error: updated install refresh failed (/home/keith/.npm-global/lib/node_modules/openclaw/dist/entry.js): at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:117:5)

Node.js v22.22.0

And now it will not boot.

Solution

That

gateway status

gateway status

output (“service appears running” but port 18789 is not listening) usually just means: systemd is keeping the unit “active”, but the Node process is still crashing immediately (so nothing ever binds).

Given your earlier

ls

ls

:

-

/tmp/openclaw

/tmp/openclaw

is OK (

)
-

/tmp/openclaw-1000

/tmp/openclaw-1000

is NOT OK (

= group-writable) and OpenClaw will hard-fail if it ever has to fall back to it.

Do this:

# make both temp dirs "trusted"
sudo chown keith:keith /tmp/openclaw /tmp/openclaw-1000 2>/dev/null || true
sudo chmod 700 /tmp/openclaw /tmp/openclaw-1000 2>/dev/null || true

# verify
ls -ld /tmp/openclaw /tmp/openclaw-1000 2>/dev/null || true

# make both temp dirs "trusted"
sudo chown keith:keith /tmp/openclaw /tmp/openclaw-1000 2>/dev/null || true
sudo chmod 700 /tmp/openclaw /tmp/openclaw-1000 2>/dev/null || true

# verify
ls -ld /tmp/openclaw /tmp/openclaw-1000 2>/dev/null || true

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•2w ago•

17 replies

Ablac

Im Back, Every update...

✅Solved

Unsafe fallback OpenClaw temp dir: ${fallbackPath}

Unsafe fallback OpenClaw temp dir: ${fallbackPath}

Solution

That

gateway status

gateway status

ls

ls

:

-

/tmp/openclaw

/tmp/openclaw

is OK (

)
-

/tmp/openclaw-1000

/tmp/openclaw-1000

is NOT OK (

= group-writable) and OpenClaw will hard-fail if it ever has to fall back to it.

Do this:

# make both temp dirs "trusted"
sudo chown keith:keith /tmp/openclaw /tmp/openclaw-1000 2>/dev/null || true
sudo chmod 700 /tmp/openclaw /tmp/openclaw-1000 2>/dev/null || true

# verify
ls -ld /tmp/openclaw /tmp/openclaw-1000 2>/dev/null || true

# make both temp dirs "trusted"
sudo chown keith:keith /tmp/openclaw /tmp/openclaw-1000 2>/dev/null || true
sudo chmod 700 /tmp/openclaw /tmp/openclaw-1000 2>/dev/null || true

# verify
ls -ld /tmp/openclaw /tmp/openclaw-1000 2>/dev/null || true

Jump to solution

Im Back, Every update...

Im Back, Every update...

Similar Threads

Similar Threads

Similar Threads