Not really MacPorts problem, I don't think.

[Ryan Schmidt]

On Jan 22, 2015, at 11:47 AM, William H. Magill wrote:
> 
> I don't know what MacPorts can do about this one.
> 
> I have the MacPorts version of Apache2 installed.
> - Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1k DAV/2 PHP/5.6.4 configured 
> 
> If I power-cycle my machine, when it comes back up, Apache2  has failed to start.
> 
> If I then try to load Apache2 -- it is reported as already running.
> 
> $ sudo port load apache2
> $ Password:
> $ /opt/local/etc/LaunchDaemons/org.macports.apache2/org.macports.apache2.plist: Operation already in progress
> 
> So I unload, then load and Apache starts with no problems.
> 
> What is happening is apparently a timing problem. I.e. it fails on boot, but works fine after OSX is up and running.
> 
> The error is "simple" -- 
> 
> [Thu Jan 22 02:17:12 2015] [info] mod_ssl/2.2.29 compiled against Server: Apache/2.2.29, Library: OpenSSL/1.0.1j
> [Thu Jan 22 02:17:19 2015] [notice] Digest: generating secret for digest authentication ...
> [Thu Jan 22 02:17:19 2015] [notice] Digest: done
> [Thu Jan 22 02:17:19 2015] [alert] (EAI 8)nodename nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of "shianbrae.mcgillsociety.org"
> Configuration Failed
> 
> Shianbrae.mcgillsociety.org is the FQDN of the server.
> 
> ServerName is configured: 
>     ServerName localhost:80
> 
> From trying to deal with the local host issue from before.

So launchd is launching apache too early. I believe there are some keys one can use in a launchd plist that would affect when launchd tries to launch a service. If you can find a launchd plist key/value that fixes this issue, MacPorts could be enhanced to offer portfile authors a way to use that key, or to use that key/value by default even.