Getting Started - issue httpd #5249
Unanswered
Shab00
asked this question in
Getting started
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Output of
brew config
Output of
brew doctor
Description of issue
The brew install was seemingly broken. The protection on the plist was apparently incorrect, But resolved now.
So everything is running however, brew services shows an error:
httpd error 256 bashaar ~/Library/LaunchAgents/homebrew.mxcl.httpd.plist
php none
and error_log shows:
[Wed Mar 27 08:35:12.526331 2024] [core:notice] [pid 67898] AH00094: Command line: '/usr/local/opt/httpd/bin/httpd -D FOREGROUND'
[Wed Mar 27 09:35:11.817494 2024] [mpm_prefork:notice] [pid 67898] AH00169: caught SIGTERM, shutting down
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.0.7. Set the 'ServerName' directive globally to suppress this message
[Wed Mar 27 09:35:13.069729 2024] [mpm_prefork:notice] [pid 92722] AH00163: Apache/2.4.58 (Unix) configured -- resuming normal operations
[Wed Mar 27 09:35:13.070487 2024] [core:notice] [pid 92722] AH00094: Command line: '/usr/local/opt/httpd/bin/httpd -D FOREGROUND'
[Thu Mar 28 06:59:17.523035 2024] [mpm_prefork:notice] [pid 92722] AH00169: caught SIGTERM, shutting down
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.0.7. Set the 'ServerName' directive globally to suppress this message
[Thu Mar 28 06:59:18.770334 2024] [mpm_prefork:notice] [pid 19772] AH00163: Apache/2.4.58 (Unix) configured -- resuming normal operations
[Thu Mar 28 06:59:18.771428 2024] [core:notice] [pid 19772] AH00094: Command line: '/usr/local/opt/httpd/bin/httpd -D FOREGROUND'
[Thu Mar 28 07:11:42.807512 2024] [mpm_prefork:notice] [pid 19772] AH00169: caught SIGTERM, shutting down
also brew services info httpd output is:
httpd (homebrew.mxcl.httpd)
Running: ✘
Loaded: ✔
Schedulable: ✘
Im on mac intel and the error logs are from a coplue of days ago. is there anyway to resolve this?
Would it be a case of reinstalling brew and packages?
thanks
Beta Was this translation helpful? Give feedback.
All reactions