Localhost down | MacPorts LAMP

Scott Haneda talklists at newgeo.com
Sun Feb 28 18:26:34 PST 2010


On Feb 28, 2010, at 1:27 AM, Jasper Frumau wrote:

> Just tried to access my localhost and got a 304. Then I ran sudo /opt/local/apache2/bin/apachectl restart and Apache restarted. I wonder why Apache stopped in the first place so I checked the error log and found these errors before I restarted the server:
> 
> [Fri Feb 26 14:12:24 2010] [warn] child process 1807 still did not exit, sending a SIGTERM
> [Fri Feb 26 14:12:26 2010] [error] child process 225 still did not exit, sending a SIGKILL
> [Fri Feb 26 14:12:26 2010] [error] child process 226 still did not exit, sending a SIGKILL
> [Fri Feb 26 14:12:26 2010] [error] child process 227 still did not exit, sending a SIGKILL
> [Fri Feb 26 14:12:26 2010] [error] child process 228 still did not exit, sending a SIGKILL
> [Fri Feb 26 14:12:26 2010] [error] child process 229 still did not exit, sending a SIGKILL
> [Fri Feb 26 14:12:26 2010] [error] child process 1983 still did not exit, sending a SIGKILL
> [Fri Feb 26 14:12:26 2010] [error] child process 1946 still did not exit, sending a SIGKILL
> [Fri Feb 26 14:12:26 2010] [error] child process 1805 still did not exit, sending a SIGKILL
> [Fri Feb 26 14:12:26 2010] [error] child process 2494 still did not exit, sending a SIGKILL
> [Fri Feb 26 14:12:26 2010] [error] child process 1807 still did not exit, sending a SIGKILL
> [Fri Feb 26 14:12:27 2010] [notice] caught SIGTERM, shutting down
> [Fri Feb 26 14:13:52 2010] [alert] (EAI 8)nodename nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of "Jaspers-MacBook-Pro.local"
> Configuration Failed
> 
> Child process issues were mentioned repeatedly - more than I pasted in this email -  last Friday. What does that mean?

I have had this too, and I also have had Apache2 not start after a power cycle on the machine.  Both on PPC and Intel.  I am not sure if it is Mac OS X specific, or specific to the current version of Apache2 that MacPorts is using.  Probably the former though.  It always starts right up with `sudo port load apache2` though.

Whenever I see the log lines you see, I generally see close by, this issue:
https://issues.apache.org/bugzilla/show_bug.cgi?id=48045

"nodename nor servname provided, or not known" also does not seem to be an Apache error, as much as it is an error that is sent to Apache from some other app.  I have seen on another mailing list, that same error reported for an ftp app.

Maybe it has something to do with getaddrinfo() on OS X.  I seemed to solve it by adding an entry to /etc/hosts for my bonjour name to map to localhost.  In your case, something like this:
127.0.0.1	Jaspers-MacBook-Pro.local

I just found this, which seems to confirm my method of solving it, and even is targeted at BSD:
http://www.hardforums.com/showthread.php?t=935096

Hope that helps.
-- 
Scott * If you contact me off list replace talklists@ with scott@ * 



More information about the macports-users mailing list