ANSWER:

I just ran into this same issue and solved it by changing my Listen port arbitrarily.

I had the same error that you had, except that I was using a custom >1024 port in the first place. After changing my choice, Apache also started to write to its error log, which it refused to do apart from the similar

[Fri Sep 09 12:16:19 2011] [alert] (EAI 8)nodename nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of "unknown040cced5b2fe"
Configuration Failed

message. In addition, even though netstat did not show that my port had been busy, Apache was taking quite some time to respond, commonly indicating a socket contention.

by user472876 from http://superuser.com/questions/417388