Plugin Cache Failure | Friends of the Crustacean 🦞🤝 | Page 1

green roost Apr 28, 2026, 10:54 PM

#

I have ran openclaw update multiple times and everything updates fine, except for this error: Completion cache update failed: Error: spawnSync /opt/homebrew/Cellar/node@22/22.22.2_1/bin/node ETIMEDOUT

quiet skyBOT Apr 28, 2026, 10:54 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

indigo rootBOT Apr 28, 2026, 10:55 PM

#

That’s the shell tab-completion cache step timing out, not the main update failing. If everything else updated, you don’t need to keep rerunning openclaw update.

First, can you paste:

openclaw --version

Then try the manual refresh:

openclaw completion --write-state
openclaw doctor

This specific raw spawnSync ... ETIMEDOUT message was improved in 2026.4.27, so if you’re below that, update once more after checking the version. If completion --write-state still hangs/times out, paste:

#

openclaw status --all

Docs: https://docs.openclaw.ai/help/faq

green roost Apr 28, 2026, 10:57 PM

#

OpenClaw 2026.4.26 (be8c246)

That is my current version and the latest, you mentioned 2026.4.27 but I do not see that released yet.

indigo rootBOT Apr 28, 2026, 10:59 PM

#

You’re right — I mixed up the main-branch changelog with the published npm release. Sorry about that. npm view openclaw version dist-tags confirms latest/beta are both 2026.4.26, and public package mirrors only show the 2026.4.26 artifact right now. (fossies.org)

For your actual error: this is just the shell completion cache refresh timing out after update. It should not mean the OpenClaw update failed; tab-completion may just be stale.

Try this once:

time OPENCLAW_COMPLETION_SKIP_PLUGIN_COMMANDS=1 openclaw completion --write-state
openclaw doctor

If that still takes >30s or hangs, paste the output from:

openclaw status --all

#

Docs: https://docs.openclaw.ai/cli/completion

green roost Apr 28, 2026, 11:03 PM

#

It did not hang, should i run openclaw update again?

indigo rootBOT Apr 28, 2026, 11:04 PM

#

No need to run openclaw update again if the manual command finished.

That means the completion cache is now refreshed; the earlier update just hit the 30s automatic timeout for that optional step. I’d do this instead:

openclaw doctor
openclaw status

If those look clean, you’re good. If you do run openclaw update again, it should be harmless, but it’s redundant since you’re already on 2026.4.26.

Docs: https://docs.openclaw.ai/cli/completion

If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow indexes it for future folks. 🦐

green roost Apr 28, 2026, 11:12 PM

#

I am having gateway issues now, openclaw status said it was unreachable. When running openclaw gateway stop it came back with:

Warning: launchctl stop did not fully stop the service; used bootout fallback and left service unloaded
Stopped LaunchAgent (degraded): gui/502/ai.openclaw.gateway

indigo rootBOT Apr 28, 2026, 11:13 PM

#

Yep — after openclaw gateway stop, “unreachable” is expected until it’s started again. That warning means launchd didn’t stop cleanly, so OpenClaw used the bootout fallback and left the LaunchAgent unloaded.

Run:

openclaw gateway start
openclaw gateway status

If it still says unreachable / won’t stay running, paste:

openclaw gateway status --deep
openclaw logs --follow

Also for future restarts, prefer:

#Plugin Cache Failure