Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This has come up before. The current expectation is that if you choose
to customize your system to have Apache bind on a particular IP address,
you must also override the systemd service to wait for the network-
online target. You can do this in /etc/ overriding just this one thing -
see the systemd documentation for details.
The problem is that people use services in a variety of different ways.
We can't predict what you're going to require from the service in terms
of dependencies when you customize your configuration. if (for example)
somebody is using apache just to serve localhost for web development.
Blocking on network-online.target by default on Ubuntu would break in
this use case.
The ideal solution is documented on the systemd page you found, and
needs implementing upstream.
In the meantime, I think the only thing that Ubuntu can realistically do
is to require users making these customizations to also adjust the
systemd configuration as needed at the same time.
Since this means that there is no action in Ubuntu, I'm setting this bug
to Invalid. If you disagree, I encourage you to start a thread on
ubuntu-server@, since this is a wider general issue than just your
specific apache2 package case, and it would be useful to have a
discussion on how to handle this in Ubuntu generally and then we can all
refer to that thread when the question inevitably comes up again.
** Tags added: triage
** Changed in: apache2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786675
Title:
Apache will not start on boot if bound to a fixed IP address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1786675/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
