openclaw - 💡(How to fix) Fix [Bug]: Gateway liveness watchdog restarting the gateway after every few minutes. (2026.5.6) [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

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#78601Fetched 2026-05-07 03:34:49
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
2
Timeline (top)
commented ×2labeled ×2assigned ×1unassigned ×1

The logs show what happened:

At 21:21:27, the gateway's own liveness monitor detected a severe event-loop freeze: eventLoopDelayMaxMs=23622ms, eventLoopUtilization=0.98 (98%) 24 seconds later at 21:21:51, the gateway's built-in self-preservation mechanism sent itself SIGTERM with "restarting" It then waited up to 5 minutes to drain active work, but didn't finish in time, so systemd killed it after 30s and restarted it This is OpenClaw's own liveness watchdog doing exactly what it's designed to do — recover from event-loop starvation. The gateway saw its event loop was 98% utilized with 23-second delays and decided to restart. Version went from 2026.5.5 → 2026.5.6.

Root Cause

The logs show what happened:

At 21:21:27, the gateway's own liveness monitor detected a severe event-loop freeze: eventLoopDelayMaxMs=23622ms, eventLoopUtilization=0.98 (98%) 24 seconds later at 21:21:51, the gateway's built-in self-preservation mechanism sent itself SIGTERM with "restarting" It then waited up to 5 minutes to drain active work, but didn't finish in time, so systemd killed it after 30s and restarted it This is OpenClaw's own liveness watchdog doing exactly what it's designed to do — recover from event-loop starvation. The gateway saw its event loop was 98% utilized with 23-second delays and decided to restart. Version went from 2026.5.5 → 2026.5.6.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

The logs show what happened:

At 21:21:27, the gateway's own liveness monitor detected a severe event-loop freeze: eventLoopDelayMaxMs=23622ms, eventLoopUtilization=0.98 (98%) 24 seconds later at 21:21:51, the gateway's built-in self-preservation mechanism sent itself SIGTERM with "restarting" It then waited up to 5 minutes to drain active work, but didn't finish in time, so systemd killed it after 30s and restarted it This is OpenClaw's own liveness watchdog doing exactly what it's designed to do — recover from event-loop starvation. The gateway saw its event loop was 98% utilized with 23-second delays and decided to restart. Version went from 2026.5.5 → 2026.5.6.

Steps to reproduce

Not sure just work then you get the message gateway is being restarted.

Expected behavior

Do we really need to say that rebooting and hanging is not expected behavior?

Actual behavior

At 21:21:27, the gateway's own liveness monitor detected a severe event-loop freeze: eventLoopDelayMaxMs=23622ms, eventLoopUtilization=0.98 (98%) 24 seconds later at 21:21:51, the gateway's built-in self-preservation mechanism sent itself SIGTERM with "restarting" It then waited up to 5 minutes to drain active work, but didn't finish in time, so systemd killed it after 30s and restarted it This is OpenClaw's own liveness watchdog doing exactly what it's designed to do — recover from event-loop starvation. The gateway saw its event loop was 98% utilized with 23-second delays and decided to restart. Version went from 2026.5.5 → 2026.5.6.

OpenClaw version

2026.5.6

Operating system

Ubuntu

Install method

Script

Model

minimax m2.7

Provider / routing chain

minimax m2.7

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

I hope the OpenClaw team can get its act together. I am seriously thinking that doing an engineering course and making my own version would be quicker than you fixing these stability issues.

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…

FAQ

Expected behavior

Do we really need to say that rebooting and hanging is not expected behavior?

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Gateway liveness watchdog restarting the gateway after every few minutes. (2026.5.6) [2 comments, 3 participants]