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

[Chris Green]

On Wed, Oct 27, 2021 at 03:31:42PM +0100, Colin Law wrote:
> On Wed, 27 Oct 2021 at 14:44, Chris Green <cl at isbd.net> wrote:
> > ...
> > Yes, here's the whole file:-
> >
> >     root at esprimo# more ./systemd/system/multi-user.target.wants/apache2.service
> >     [Unit]
> >     Description=The Apache HTTP Server
> >     After=network.target remote-fs.target nss-lookup.target
> >     Documentation=https://httpd.apache.org/docs/2.4/
> >
> >     [Service]
> >     Type=forking
> >     Environment=APACHE_STARTED_BY_SYSTEMD=true
> >     ExecStart=/usr/sbin/apachectl start
> >     ExecStop=/usr/sbin/apachectl graceful-stop
> >     ExecReload=/usr/sbin/apachectl graceful
> >     KillMode=mixed
> >     PrivateTmp=true
> >     Restart=on-abort
> >
> >     [Install]
> >     WantedBy=multi-user.target
> >
> 
> Have you configured apache to bind to a specific address?  Is so then
> see https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1786675
> 
Aha! Thank you, that's it.  I'd been playing with making Apache listen
to specific addresses a while ago and, presumably, hadn't rebooted the
system until just recently.  I had just been making changes to the
apache configuration and restarting apache which, of course, works OK.

My desktop is powered up all the time as it's (among other things) my
mail server.  It got rebooted recently when I tripped the house
circuit breaker when doing some wiring changes in the garage!

I don't actually need apache to listen only to specific addresses
(I've done what I was trying to do by other means for the moment) so I
have simply switched it back to the default port 80 with no IP address
and everything is OK again now.


Thanks again! :-)

-- 
Chris Green