Opened 8 years ago
Closed 7 years ago
#52617 closed defect (fixed)
Apache2 won't start on Sierra
Reported by: | voodoodrul@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | sierra | Cc: | Schamschula (Marius Schamschula), pixilla (Bradley Giesbrecht) |
Port: | apache2 |
Description
Starting from a clean Sierra install, and installing apache2, sudo port load apache2
runs and httpd attempts to start. The process stays running for a few seconds and then dies. Nothing is wrong with the config file and this behavior occurs on multiple machines. Worked fine in El Capitan, not so much in Sierra. No obvious errors logged. Manually starting httpd by calling the process directly and leaving it running in the terminal works fine.
Change History (6)
comment:1 Changed 8 years ago by larryv (Lawrence Velázquez)
Keywords: | apache2 removed |
---|---|
Owner: | changed from macports-tickets@… to ryandesign@… |
comment:2 Changed 8 years ago by voodoodrul@…
comment:3 Changed 8 years ago by voodoodrul@…
Disabling mod_unique_id allows it to start.
[Sat Oct 15 13:22:53 2016] [alert] (EAI 8)nodename nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of "Jesses-MacBook-Pro.local" Configuration Failed
Although my ServerName
was set to localhost
, I went ahead and added the FQDN for my hostname to /etc/hosts. With my FQDN in /etc/hosts, it starts even with mod_unique_id enabled.
comment:4 Changed 8 years ago by xmeltrut (Chris Worfolk)
I encountered the same problem. Commenting out mod_unique_id in httpd.conf fixed it for me.
comment:5 Changed 7 years ago by jmroot (Joshua Root)
Cc: | Schamschula pixilla added |
---|
comment:6 Changed 7 years ago by Schamschula (Marius Schamschula)
Resolution: | → fixed |
---|---|
Status: | new → closed |
mod_unique_id
is commented out by default under apache2 2.4.x.
Correction: manually starting httpd from the terminal (
sudo /opt/local/apache2/bin/httpd -k start
) does *not* work. Same behavior. Showing startup errors, I only see modules loading, a "hang" for about 3 seconds, and then crash to prompt: