brew services startup issue #6771
-
Additional Info
Output of
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Hi, The issue is that
Most commonly this is caused by:
Here are the steps to diagnose and fix: 1. Check the actual error logs first: journalctl --user -xe -u homebrew.httpd --no-pagerThis will show why the service failed to start. 2. Reload systemd and try starting manually: systemctl --user daemon-reload
systemctl --user start homebrew.httpd
systemctl --user status homebrew.httpd3. Validate your httpd config (common culprit): /home/linuxbrew/.linuxbrew/opt/httpd/bin/httpd -tA misconfigured 4. If you're accessing this from a non-login session, enable linger: loginctl enable-linger $USERWithout this, systemd user services may not persist outside of an active login session. 5. As a quick test, run httpd directly to see raw errors: /home/linuxbrew/.linuxbrew/opt/httpd/bin/httpd -D FOREGROUNDMost likely the |
Beta Was this translation helpful? Give feedback.
-
|
Can you check what is going on there with this command? |
Beta Was this translation helpful? Give feedback.
Hi, The issue is that
brew serviceson Linux uses systemd user services under the hood,and while brew reports success, the service itself is not actually running.
Running: ✔butLoaded: ✘typically means the process failed right after launch.Most commonly this is caused by:
Here are the steps to diagnose and fix:
1. Check the actual error logs first:
This will show why the service failed to start.
2. Reload systemd and try starting manually:
3. Vali…