Recently apache2 fails to start at boot, but can be started OK manually

[Karl Auer]

On Tue, 2021-10-26 at 13:59 +0100, Chris Green wrote:
> make_sock: could not bind to address

This almost always means something else is already listening on that
address and port. If you can start Apache2 later, then it would appear
that whatever else was listening has stopped listening by then.

You can confirm this by configuring Apache2 to use a different port,
like 81, and see if it then starts properly on boot. If the same
problem still happens, it is a resource issue of some kind, or possibly
permissions.

Think back to two weeks ago; did you install anything new that might be
listening for a while on port 80? Also check the logs for something
dying during startup.

Can you start later Apache2 using "systemctl start apache2" instead of
"/etc/init.d/apache2"?

Is it possible that the address 192.168.1.3 does not exist at the time
Apache2 first starts?

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer

GPG fingerprint: 61A0 99A9 8823 3A75 871E 5D90 BADB B237 260C 9C58
Old fingerprint: 2561 E9EC D868 E73C 8AF1 49CF EE50 4B1D CCA1 5170