Q: Update to 5.1 produces apache errors
After the update the web error log was flooded with the following and websites were not available
AH00015: Unable to open logs AH00558: httpd: Could not reliably determine the server's
fully qualified domain name,using <our_FDQN>.
Set the 'ServerName'directive globally to suppress this message(48)Address already in use:
AH00072: make_sock: could not bind to address 127.0.0.1:34580 no listening sockets available, shutting down
After a bit of rooting around in /Library/Server/Web/Config/apache2/sites and seeing nothing immediately responsible, and nothing that related to the ServerName error message, I restarted the Mac Mini hosting OS X Server and the problem was resolved.
I cannot explain why, and I cannot recall whether I rebooted once or twice - whatever I did was probably not as superstitious as it may seem, as on several update occasions before, complex Apple updates behind the scenes have taken a while to take effect. So call it behaviour with empirical motivation! I've been caught out before by being too enthusiastic to "improve" the generated apache configuration.
Just thought I'd add this note to deter others from making difficult-to-reverse apache config changes in response to the error log, only to find that the Apple update may eventually work anyway. Have faith! ... at least for a couple of reboots!
Message was edited by: Trismegister - fix typos and html formatting
Mac mini (Late 2014), OS X El Capitan (10.11.4), null
Posted on Mar 28, 2016 12:52 PM