On a newly installed F24 I have a /home/... directory with a collection of movie files - *.m4v and such, that I want to googlecast to a TV for viewing. I've configured a private httpd setup to display this directory listing when the local machine name is entered in the address line of google-chrome, and when a file is clicked, it plays and can be "cast" to the TV. Neat!
However, when the machine boots (quiet, without rhgb) the messages include [FAILED] Failed to start The Apache HTTP Server. See 'systemctl status httpd.service' for details. and, sure enough, httpd isn't running.
journalctl -b shows this: Jun 27 10:33:17 garfield httpd[1100]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address 192.168.10.99:80 Jun 27 10:33:17 garfield httpd[1100]: no listening sockets available, shutting down Jun 27 10:33:17 garfield httpd[1100]: AH00015: Unable to open logs ... Jun 27 10:33:17 garfield systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE Jun 27 10:33:17 garfield systemd[1]: Failed to start The Apache HTTP Server. Jun 27 10:33:17 garfield systemd[1]: httpd.service: Unit entered failed state. Jun 27 10:33:17 garfield systemd[1]: httpd.service: Failed with result 'exit-code'.
It can be started manually later, readily enough, with systemctl start httpd but that's a PITA.
So, why could httpd not "make_sock: could not bind to address 192.168.10.99:80" Could it just be that the network isn't up yet? Why isn't httpd more patient and persistent?
This seems like yet another systemd problem. Can anyone suggest how to fix this?