I ran the commands but still get the error.

Ensure you are running the commands as your logged-in user, not with `sudo`. Also, verify that your user ID is indeed 1000. If not, adjust `/run/user/1000` to `/run/user/ ` in the commands. Double-check that the `openclaw-gateway.service` file was created correctly in `~/.config/systemd/user/`.

What is `systemctl --user`?

`systemctl --user` manages systemd services that run under your user account, rather than system-wide. These services don't require root privileges but still benefit from systemd's management features like auto-restarts and dependency handling.

Is the placeholder service file safe?

Yes, the placeholder service `ExecStart=/bin/true` is designed to do nothing and immediately exit successfully. It's purely a workaround to satisfy `systemd`'s checks during OpenClaw's installation and setup. It doesn't affect your system's performance or security.

Fix systemctl is-enabled unavailable Error in OpenClaw 2026.3.2

TL;DR — Quick Fix

The 'systemctl is-enabled unavailable' error occurs because systemd is not correctly set up for user services. Run the provided commands to manually configure it.

Run Diagnostics

Next Step

Fix now, then reduce repeat incidents

If this issue keeps coming back, validate your setup in Doctor first, then harden your config.

Open Doctor Harden Config

Error Signal

Error: systemctl is-enabled unavailable: Command failed: systemctl --user is-enabled openclaw-gateway.service

What's Happening

You're seeing the error Error: systemctl is-enabled unavailable: Command failed: systemctl --user is-enabled openclaw-gateway.service after upgrading to OpenClaw 2026.3.2 or during a fresh install, particularly on Ubuntu 24.04. This means OpenClaw's service management is failing because it can't properly check the status of the openclaw-gateway.service user service. It's a regression that affects new installs and upgrades.

The Fix

Thanks to the community, there's a solid workaround. You need to manually set up the user systemd environment. Run these commands:

export XDG_RUNTIME_DIR=/run/user/1000
export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus

mkdir -p ~/.config/systemd/user

cat > ~/.config/systemd/user/openclaw-gateway.service <<'EOF'
[Unit]
Description=OpenClaw Gateway (bootstrap placeholder)

[Service]
Type=oneshot
ExecStart=/bin/true
RemainAfterExit=yes

[Install]
WantedBy=default.target
EOF

systemctl --user daemon-reload
systemctl --user enable --now openclaw-gateway.service

Make sure to run these commands as your regular user, not with sudo (unless your UID is not 1000, in which case adjust the path accordingly).

Why This Occurs

This issue stems from how systemctl --user interacts with the user's systemd session, especially in newer Ubuntu versions or certain environment setups. The is-enabled command fails when it can't properly communicate with the user's D-Bus session or if the runtime directory isn't correctly set up for systemd. The fix involves explicitly setting these environment variables and creating a minimal placeholder service file that satisfies the systemd checks, allowing OpenClaw's setup to proceed.

Prevention

While the official fix is pending, keep your system updated. Regularly check the OpenClaw GitHub repository for updates to this issue. The core problem lies in the setup script's assumptions about the user's systemd environment, which can change between OS versions or configurations.

Last Updated: March 2026

Did this guide solve your problem?