14 replies

Completion cache update failed after update to 2026.2.25

✅Solved

openclaw update
Updating OpenClaw...

│
◇ ✓ Updating via package manager (48.55s)

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

Total time: 48.67s

Updating plugins...
No plugin updates needed.
Completion cache update failed (file:///home/c/.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/c/.npm-global/lib/node_modules/openclaw/dist/entry.js:655:34)
at resolvePreferredOpenClawTmpDir (file:///home/c/.npm-global/lib/node_modules/openclaw/dist/entry.js:669:51)
at file:///home/c/.npm-global/lib/node_modules/openclaw/dist/entry.js:782:25
at ModuleJob.run (node:internal/modules/esm/module_job:413:25)
at async onImport.tracePromise.proto (node:internal/modules/esm/loader:660:26)
at async tryImport (file:///home/c/.npm-global/lib/node_modules/openclaw/openclaw.mjs:39:5)
at async file:///home/c/.npm-global/lib/node_modules/openclaw/openclaw.mjs:50:5

Node.js v24.13.0).

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

Node.js v24.13.0
Daemon restart completed.

I went away and came back smarter. You should try it sometime.

Solution

That error is coming from a new safety check around OpenClaw’s temp dir.

OpenClaw prefers /tmp/openclaw
/tmp/openclaw
, but only if it’s:
- a real directory (not a symlink),
- owned by the current user, and
- not group/other-writable (effectively needs perms like

).

Because your

/tmp/openclaw

/tmp/openclaw

wasn’t considered “secure”, it fell back to /tmp/openclaw-1000
/tmp/openclaw-1000
(your uid), and that directory already exists but is also “unsafe” (wrong owner/perms or symlink) — so it hard-fails with:

Unsafe fallback OpenClaw temp dir: /tmp/openclaw-1000

Unsafe fallback OpenClaw temp dir: /tmp/openclaw-1000

What to do on the host

1) Check what you currently have (paste the output):

id -u
ls -ld /tmp/openclaw /tmp/openclaw-$(id -u)

id -u
ls -ld /tmp/openclaw /tmp/openclaw-$(id -u)

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•2w ago•

14 replies

satsCC

Completion cache update failed after update to 2026.2.25

✅Solved

Unsafe fallback OpenClaw temp dir: ${fallbackPath}

Unsafe fallback OpenClaw temp dir: ${fallbackPath}

Solution

).

Because your

/tmp/openclaw

/tmp/openclaw

Unsafe fallback OpenClaw temp dir: /tmp/openclaw-1000

Unsafe fallback OpenClaw temp dir: /tmp/openclaw-1000

What to do on the host

1) Check what you currently have (paste the output):

id -u
ls -ld /tmp/openclaw /tmp/openclaw-$(id -u)

id -u
ls -ld /tmp/openclaw /tmp/openclaw-$(id -u)

Jump to solution

Completion cache update failed after update to 2026.2.25

What to do on the host

Completion cache update failed after update to 2026.2.25

What to do on the host

Similar Threads

Similar Threads

Similar Threads