Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Gateway service check fails with "No medium found" on WSL2 despite systemd running correctly [1 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#69695•Fetched 2026-04-22 07:49:18
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
janfel1112-progjanfel1112-prog
Participants
janfel1112-progjanfel1112-prog
Timeline (top)
labeled ×2

On WSL2 with systemd enabled, the gateway health check repeatedly reports "No medium found" every ~10 seconds despite the gateway being fully reachable and all services running correctly.

Error Message

  1. Observe repeated error in logs: "Gateway service check failed: systemctl is-enabled unavailable: Failed to connect to bus: No medium found"

Root Cause

On WSL2 with systemd enabled, the gateway health check repeatedly reports "No medium found" every ~10 seconds despite the gateway being fully reachable and all services running correctly.

Code Example

Gateway service │ systemd installed · enabled · running (pid 81232, state active)
Gateway         │ reachable 54ms · auth token OK
Telegram        │ ON · OK

DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
XDG_RUNTIME_DIR=/run/user/1000/
systemctl is-enabled openclaw-gateway → enabled (works fine manually)
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

On WSL2 with systemd enabled, the gateway health check repeatedly reports "No medium found" every ~10 seconds despite the gateway being fully reachable and all services running correctly.

Steps to reproduce

  1. Install OpenClaw on WSL2 with systemd=true in /etc/wsl.conf
  2. Run openclaw-gateway as a systemd user service
  3. Observe repeated error in logs: "Gateway service check failed: systemctl is-enabled unavailable: Failed to connect to bus: No medium found"

Expected behavior

Health check probe should succeed or be treated as non-fatal when gateway is confirmed running and reachable.

Actual behavior

Gateway is reachable (54ms), auth OK, Telegram OK, but health check probe repeatedly reports "No medium found" every ~10 seconds in logs.

OpenClaw version

2026.4.15 (041266a)

Operating system

WSL2 - linux 6.6.87.2-microsoft-standard-WSL2 (x64)

Install method

npm global

Model

ollama/qwen-lowctx

Provider / routing chain

openclaw -> ollama

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Gateway service │ systemd installed · enabled · running (pid 81232, state active)
Gateway         │ reachable 54ms · auth token OK
Telegram        │ ON · OK

DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
XDG_RUNTIME_DIR=/run/user/1000/
systemctl is-enabled openclaw-gateway → enabled (works fine manually)

Impact and severity

Affected: Single user, WSL2 user service setup Severity: Annoying (does not block workflow, gateway runs normally) Frequency: Always, every ~10 seconds Consequence: Log spam makes it harder to identify real issues

Additional information

Running systemctl is-enabled manually from terminal succeeds. Both DBUS_SESSION_BUS_ADDRESS and XDG_RUNTIME_DIR are present in the session. Suspected cause: health check subprocess does not inherit user session environment variables when spawned from the systemd user service context.

extent analysis

TL;DR

The health check subprocess likely fails to inherit the user session environment variables, causing the "No medium found" error, and setting the DBUS_SESSION_BUS_ADDRESS environment variable for the systemd user service may resolve the issue.

Guidance

  • Verify that the DBUS_SESSION_BUS_ADDRESS environment variable is set correctly for the systemd user service by checking the service file or using systemctl show.
  • Try setting the DBUS_SESSION_BUS_ADDRESS environment variable explicitly in the systemd user service file to ensure it is inherited by the health check subprocess.
  • Check the systemd user service configuration to see if there are any options to inherit the user session environment variables.
  • Test running the health check subprocess manually with the DBUS_SESSION_BUS_ADDRESS environment variable set to see if it resolves the issue.

Example

No code snippet is provided as it is not clearly supported by the issue, but an example of setting the DBUS_SESSION_BUS_ADDRESS environment variable in a systemd service file could be:

[Service]
Environment=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus

Notes

The issue seems to be specific to the WSL2 environment with systemd enabled, and the solution may not apply to other environments.

Recommendation

Apply workaround: Set the DBUS_SESSION_BUS_ADDRESS environment variable explicitly in the systemd user service file, as it is likely that the health check subprocess is not inheriting the user session environment variables.

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

Health check probe should succeed or be treated as non-fatal when gateway is confirmed running and reachable.

#api#installation#tensor shape#autograd error#environment variable

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 service check fails with "No medium found" on WSL2 despite systemd running correctly [1 participants]