openclaw - 💡(How to fix) Fix [Bug]: [P0] Config change detection bug: Any modification triggers gateway restart [2 comments, 2 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#72632Fetched 2026-04-28 06:33:53
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Timeline (top)
commented ×2labeled ×2closed ×1cross-referenced ×1

Any configuration file modification (including only enabling/disabling a skill) causes the gateway log to incorrectly report that plugins.entries.ollama.config and plugins.entries.stepfun.config have changed, triggering a forced restart.

The actual configuration diff proves these two plugin configurations have not changed at all, but the config change detection logic erroneously marks them as "modified", causing unnecessary restarts.

Root Cause

Any configuration file modification (including only enabling/disabling a skill) causes the gateway log to incorrectly report that plugins.entries.ollama.config and plugins.entries.stepfun.config have changed, triggering a forced restart.

The actual configuration diff proves these two plugin configurations have not changed at all, but the config change detection logic erroneously marks them as "modified", causing unnecessary restarts.

Code Example

openclaw gateway status
# Expected: Runtime: running

---

# Edit openclaw.json, enable or disable a skill
# Example: set xurl from false to true
vim ~/.openclaw/openclaw.json

---

tail -f /tmp/openclaw/openclaw-$(date +%Y-%m-%d).log

---

config change detected; evaluating reload (skills.entries.xurl.enabled)
config change hot-reloaded (skills.entries.xurl.enabled)

---

[13:41:32] config change detected; evaluating reload (plugins.entries.ollama.config, plugins.entries.stepfun.config)
[13:41:33] config change requires gateway restart (plugins.entries.ollama.config, plugins.entries.stepfun.config)
[13:41:33] received SIGUSR1; restarting
[13:41:33] restart mode: full process restart

### OpenClaw version

2026.4.24

### Operating system

/ubuntu26.04

### Install method

npm global

### Model

step3.5

### Provider / routing chain

openclaw

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Any configuration file modification (including only enabling/disabling a skill) causes the gateway log to incorrectly report that plugins.entries.ollama.config and plugins.entries.stepfun.config have changed, triggering a forced restart.

The actual configuration diff proves these two plugin configurations have not changed at all, but the config change detection logic erroneously marks them as "modified", causing unnecessary restarts.

Steps to reproduce

Step 1: Prepare environment

openclaw gateway status
# Expected: Runtime: running

Step 2: Modify any skill configuration

# Edit openclaw.json, enable or disable a skill
# Example: set xurl from false to true
vim ~/.openclaw/openclaw.json

Step 3: Check logs

tail -f /tmp/openclaw/openclaw-$(date +%Y-%m-%d).log

Expected behavior

Expected (hot-reload):

config change detected; evaluating reload (skills.entries.xurl.enabled)
config change hot-reloaded (skills.entries.xurl.enabled)

Actual behavior

Actual (forced restart):

[13:41:32] config change detected; evaluating reload (plugins.entries.ollama.config, plugins.entries.stepfun.config)
[13:41:33] config change requires gateway restart (plugins.entries.ollama.config, plugins.entries.stepfun.config)
[13:41:33] received SIGUSR1; restarting
[13:41:33] restart mode: full process restart

### OpenClaw version

2026.4.24

### Operating system

/ubuntu26.04

### Install method

npm global

### Model

step3.5

### Provider / routing chain

openclaw

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

```shell

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be mitigated by reviewing and refining the configuration change detection logic to accurately identify modified plugins.

Guidance

  • Review the configuration change detection logic to ensure it correctly handles plugin configurations and doesn't falsely mark plugins.entries.ollama.config and plugins.entries.stepfun.config as modified.
  • Verify the actual configuration diff to confirm that the two plugin configurations have not changed.
  • Check the logging mechanism to ensure it accurately reports configuration changes and restart reasons.
  • Consider adding additional logging or debugging statements to understand why the configuration change detection logic is marking the plugins as modified.

Example

No code snippet is provided as the issue does not contain sufficient information about the configuration change detection logic.

Notes

The provided information suggests a logic error in the configuration change detection mechanism, but without access to the code, it's difficult to provide a precise fix. The steps to reproduce and the expected behavior suggest that the issue is related to the detection logic rather than the configuration files themselves.

Recommendation

Apply workaround: Refine the configuration change detection logic to accurately identify modified plugins, as the current logic is causing unnecessary restarts.

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

Expected (hot-reload):

config change detected; evaluating reload (skills.entries.xurl.enabled)
config change hot-reloaded (skills.entries.xurl.enabled)

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]: [P0] Config change detection bug: Any modification triggers gateway restart [2 comments, 2 participants]