openclaw - 💡(How to fix) Fix v2026.4.26: gateway restart can hang ~3-4 min before new process starts [11 comments, 11 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#73303Fetched 2026-04-29 06:21:14
View on GitHub
Comments
11
Participants
11
Timeline
15
Reactions
2
Timeline (top)
commented ×11subscribed ×3cross-referenced ×1

On macOS (LaunchAgent mode), restarting Gateway on v2026.4.26 can sometimes take ~3-4 minutes before the new process starts, even though normal startup is only a few seconds.

Error Message

A restart is requested (SIGTERM), but old process appears to linger for minutes before fresh startup begins.

Root Cause

On macOS (LaunchAgent mode), restarting Gateway on v2026.4.26 can sometimes take ~3-4 minutes before the new process starts, even though normal startup is only a few seconds.

Fix Action

Fix / Workaround

Request

Could you help check:

  1. whether shutdown path in 2026.4.26 can block launchd supervisor restart;
  2. whether plugin/channel teardown has a long timeout path without intermediate logs;
  3. whether this is a known regression in 2026.4.26 and if a patch/workaround exists.
RAW_BUFFERClick to expand / collapse

Summary

On macOS (LaunchAgent mode), restarting Gateway on v2026.4.26 can sometimes take ~3-4 minutes before the new process starts, even though normal startup is only a few seconds.

Environment

  • OpenClaw: 2026.4.26 (be8c246)
  • OS: macOS 15/26 (arm64)
  • LaunchAgent label: ai.openclaw.gateway
  • Active channel plugins include: openclaw-weixin, telegram

Observed behavior

A restart is requested (SIGTERM), but old process appears to linger for minutes before fresh startup begins.

Example timeline from logs:

  • 12:57:37 [gateway] received SIGTERM; restarting
  • 13:01:15 [gateway] loading configuration…
  • 13:01:38 [gateway] ready

So total restart wall time is ~4 min, while internal startup path is fast:

  • http server listening (...; 3.4s)

Additional signal

During startup there is also a silent gap before weixin provider init:

  • 13:01:18.780 hooks loaded
  • 13:01:38.209 weixin provider starting (~20s no logs)

Not sure if related, but the main pain is the pre-start delay between SIGTERM and fresh config load.

Also seen in same logs

Config warning for plugin manifest metadata:

  • channel plugin manifest declares openclaw-weixin without channelConfigs metadata

(We tested adding channelConfigs: {} locally, but restart latency behavior still reproduced.)

Impact

Operationally painful for frequent restarts/debugging; perceived as "restart is stuck".

Request

Could you help check:

  1. whether shutdown path in 2026.4.26 can block launchd supervisor restart;
  2. whether plugin/channel teardown has a long timeout path without intermediate logs;
  3. whether this is a known regression in 2026.4.26 and if a patch/workaround exists.

If useful, I can provide full redacted log slice around restart.

extent analysis

TL;DR

Investigate the shutdown path in version 2026.4.26 to determine if it blocks the launchd supervisor restart, potentially causing the delay.

Guidance

  • Review the shutdown logic in version 2026.4.26 to check for any blocking calls or long-running operations that could prevent the launchd supervisor from restarting the process.
  • Examine the plugin and channel teardown processes to see if there are any long timeouts or asynchronous operations that could cause a delay without generating intermediate logs.
  • Check the logs for any other clues or patterns that might indicate what is causing the delay, such as errors or warnings related to the shutdown or restart process.
  • Consider providing the full redacted log slice around the restart to help with further debugging and analysis.

Notes

The issue seems to be specific to version 2026.4.26 and the LaunchAgent mode on macOS, so any solution or workaround may need to be tailored to this specific environment and configuration.

Recommendation

Apply a workaround by investigating and potentially modifying the shutdown path in version 2026.4.26 to prevent it from blocking the launchd supervisor restart, as this is the most likely cause of the delay.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING