I have an issue where Apache will not start after updating to High Sierra 10.13.1. There isn't anything showing in the error logs, but when I try to apachectl start
nothing happens. If I run apachectl configtest
I receive "Syntax OK
I have used commands like sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist
to no avail. Apache will not start. I can run sudo launchctl load -w /Library/LaunchDaemons/homebrew.mxcl.httpd.plist
and that is not working either.
I took a look at the brew services list and httpd shows up in the list along with other process (mysql) but httpd's status is showing a yellow "started" instead of a green one.
I have tried many different things, and what I am finding is that if I look into the system.log file I find com.apple.xpc.launchctl[1] (homebrew.mxcl.httpd24[11780]): Service exited with abnormal code:1
If I run apachectl start, the command seems to work, but when I run the stop command I get "httpd (no pid file) not running.
I am also receiving the output of com.;apple.xpc.launchd[1] (org.apache.httpd): Please switch away from OnDemand to KeepAlive.
Is there something with High Sierra that is preventing Apache from running when it ran fine in Sierra?
brew services list' I receive a yellow indicator, I checked with all of the available users and ran
brew services list` and they are all showing the same indicator. As for a setup guide, Ansible was used to set up apache. This has been done on 5 other MacBooks, they are still running Sierra. This one MacBook had an issue and an Apple ran a diagnostic and reset the OS, while updating the OS to High Sierra – Alcyeonnero Nov 17 '17 at 16:45apachectl start
). Same with... configtest
! – klanomath Nov 17 '17 at 16:54httpd
formula, and now apache doesn't respond. When I dobrew services list
, I also get thestarted
for httpd in yellow, and when I runsudo apachectl stop
, it tells me thathttpd (pid 87?) not responding.
– wonder95 Jan 08 '18 at 22:44brew services list
and you get a service listed asstarted
in yellow, it usually means that the plist was loaded correctly, but the active status is currently 'unknown' (per the following block of code in homebrew services https://github.com/Homebrew/homebrew-services/blob/0ce2f592dc22bce1b4aa2268c6dc416fe131abb2/cmd/brew-services.rb#L165-L177). In my case, stopping the apache service, and deleting the PID file per Eduardo's tip helped: https://apple.stackexchange.com/a/326270/19571 – Mike Kormendy Jan 06 '19 at 02:46