On Tue, Jun 28, 2016 at 06:38:17AM -0400, Sam Varshavchik wrote:
David A. De Graaf writes:
> On a newly installed F24 ...
>
> 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.
>
> It can be started manually later, readily enough, with
> systemctl start httpd
> but that's a PITA.
>
httpd.service needs to be fixed. I just reported, and had fixed, the same
bug with privoxy. See bug 1350097.
Although this is a packaging problem, it's exacerbated by systemd's
lackluster documentation, and as a result a large number of packages are
broken, and nobody knows about it until the package gets configured to
listen on a specific IP address.
Anything that can be configured to listen on a specific IP address CANNOT be:
After=network.target
It must be:
Wants=network-online.target
After=network-online.target
Thanks, Sam. Apparently systemd cannot properly start a whole bunch
of processes. (see 1119787, as well as your 1350097)
Now there's mine, as well - 1352139. We'll see what happens...
Unfortunately, I tried your suggested fix, but it didn't work for me.
I probably did something wrong; that's easy with systemd.
--
David A. De Graaf DATIX, Inc. Hendersonville, NC
dad(a)datix.us
www.datix.us
Talk is cheap because supply always exceeds demand.
Most people feel that everyone is entitled to their opinion.
If you live in a country run by committee, be on the committee.
You ain't learning nothing when you're talking.