hermes - 💡(How to fix) Fix [Bug] Gateway systemd service fails on Fedora with SELinux enforcing (status 203/EXEC)

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…

Error Message

After doing that, the service status showed the error: Error: Permission denied on python binary in venv 4. Check the systemctl status and see the error systemd service fails to start, see error above.

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Fix Action

Fix / Workaround

System Status: OS - Fedora Workstation 43 SELinux - Enforcing Error: Permission denied on python binary in venv Workaround: disable SELinux (not acceptable to me for this use)

Code Example

System service install requires sudo, so Hermes can't create it from this user session.
    After setup, run: sudo hermes gateway install --system --run-as-user hermes
    Then start it with: sudo hermes gateway start --system

---

May 26 17:44:15 fedora systemd[1]: hermes-gateway.service: Scheduled restart job, restart counter is at 2.
May 26 17:44:15 fedora systemd[1]: Started hermes-gateway.service - Hermes Agent Gateway - Messaging Platform Integration.
May 26 17:44:16 fedora (python)[1841]: hermes-gateway.service: Unable to locate executable '/home/hermes/.hermes/hermes-agent/venv/bin/python': Permission denied
May 26 17:44:16 fedora (python)[1841]: hermes-gateway.service: Failed at step EXEC spawning /home/hermes/.hermes/hermes-agent/venv/bin/python: Permission denied

---

Debug report uploaded:
  Report       https://paste.rs/Drz6Z
  agent.log    https://paste.rs/h0bIG
  gateway.log  https://paste.rs/gK7lz

---
RAW_BUFFERClick to expand / collapse

Bug Description

I'm setting up a fresh install of Hermes, and trying to set up the gateway to run as a systemd service per hermes setup . It fails with a 203/EXEC issue to to SELinux.

I ran this, copied from the setup output:

⚠   System service install requires sudo, so Hermes can't create it from this user session.
    After setup, run: sudo hermes gateway install --system --run-as-user hermes
    Then start it with: sudo hermes gateway start --system

After doing that, the service status showed the error:

May 26 17:44:15 fedora systemd[1]: hermes-gateway.service: Scheduled restart job, restart counter is at 2.
May 26 17:44:15 fedora systemd[1]: Started hermes-gateway.service - Hermes Agent Gateway - Messaging Platform Integration.
May 26 17:44:16 fedora (python)[1841]: hermes-gateway.service: Unable to locate executable '/home/hermes/.hermes/hermes-agent/venv/bin/python': Permission denied
May 26 17:44:16 fedora (python)[1841]: hermes-gateway.service: Failed at step EXEC spawning /home/hermes/.hermes/hermes-agent/venv/bin/python: Permission denied

Temporarily disabling SELinux enforcement allows it to work as expected. This is due to to the target of the systemd service being under the /home directory. The recommended solution to this issue is to move it to a more standard location.

System Status: OS - Fedora Workstation 43 SELinux - Enforcing Error: Permission denied on python binary in venv Workaround: disable SELinux (not acceptable to me for this use)

Debug report uploaded: Report https://paste.rs/Drz6Z agent.log https://paste.rs/h0bIG gateway.log https://paste.rs/gK7lz

Thanks!

Steps to Reproduce

  1. Install hermes on Fedora Workstation using the standard install script
  2. Run hermes setup, and opt to configure the gateway as a systemd service
  3. Run the instructions at the end of the setup wizard to install as the system service
  4. Check the systemctl status and see the error

Expected Behavior

The install/configuration wizard should put the system into a state that it will work after running the instructions given. Or, not offer the option of running as a systemd service.

Actual Behavior

systemd service fails to start, see error above.

Affected Component

Setup / Installation

Messaging Platform (if gateway-related)

No response

Debug Report

Debug report uploaded:
  Report       https://paste.rs/Drz6Z
  agent.log    https://paste.rs/h0bIG
  gateway.log  https://paste.rs/gK7lz

Operating System

Fedora Workstation 43

Python Version

python 3.14

Hermes Version

Hermes Agent v0.14.0 (2026.5.16)

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

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