enterprise-support team mailing list archive

[Launchpad Bug Tracker <1891760@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

We've had a few systems now over the past couple of days where Apache2 just quit running.
In looking at the systems, the following packages were upgrade using apt-get via apt auto update:


Start-Date: 2020-08-14  04:50:10
Commandline: /usr/bin/apt-get -o quiet=1 upgrade -y -o APT::Get::Show-Upgraded=true
Upgrade: apache2-data:amd64 (2.4.18-2ubuntu3.15, 2.4.18-2ubuntu3.17), apache2-bin:amd64 (2.4.18-2ubuntu3.15, 2.4.18-2ubuntu3.17), apache2:amd64 (2.4.18-2ubuntu3.15, 2.4.18-2ubuntu3.17), apache2-utils:amd64 (2.4.18-2ubuntu3.15, 2.4.18-2ubuntu3.17)

At the tail end of this, you can see there's an error in the sub-process /usr/bin/dpkg:
Error: Sub-process /usr/bin/dpkg returned an error code (1)


This is the first time in the logs this is showing up, all prior updates worked fine and no dpkg error was shown. Here's a snapshot of the prior update:
Start-Date: 2020-08-13  04:16:37
Commandline: /usr/bin/apt-get -o quiet=1 upgrade -y -o APT::Get::Show-Upgraded=true
Upgrade: python3-software-properties:amd64 (0.96.20.9, 0.96.20.10), software-properties-common:amd64 (0.96.20.9, 0.96.20.10)
End-Date: 2020-08-13  04:16:39


Even after this update happened, I saw the error in the logs:
Start-Date: 2020-08-15  04:53:49
Commandline: /usr/bin/apt-get -o quiet=1 autoremove -y
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2020-08-15  04:53:49


After running 'apt upgrade' by hand, I saw php and the linux kernel were to be updated, but during this run I also got prompted about Apache2:

Unpacking php7.4-mysql (7.4.9-1+ubuntu16.04.1+deb.sury.org+1) ...
Preparing to unpack .../php-mysql_2%3a7.4+76+ubuntu16.04.1+deb.sury.org+9_all.deb ...
Unpacking php-mysql (2:7.4+76+ubuntu16.04.1+deb.sury.org+9) over (2:7.3+70+ubuntu16.04.1+deb.sury.org+6) ...
Processing triggers for libc-bin (2.23-0ubuntu11.2) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up apache2 (2.4.18-2ubuntu3.17) ...

Configuration file '/etc/apache2/apache2.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** apache2.conf (Y/I/N/O/D/Z) [default=N] ? 
Setting up libicu65:amd64 (65.1-1+ubuntu16.04.1+deb.sury.org+1) ...
Setting up libxml2:amd64 (2.9.10+dfsg-5+ubuntu16.04.1+deb.sury.org+3) ...
Setting up linux-modules-4.4.0-187-generic (4.4.0-187.217) ...


It seems to point to the fact that during the auto apt upgrade, apt-get even with the -y flag isn't selecting the default option of "n" to answer the prompt, causing dpkg to time out or others fail out in the eyes of the apt auto update. 

I haven't encountered this before at all, so I'm going to have to guess
and update to dpkg, apt, or the apache2 packages is causing some very
expected behavior that's causing the Apache2 service to be stopped but
then never restarted.

** Affects: apache2 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Apache2 2.4.18-2ubuntu3.17 not working with apt autoupdate
https://bugs.launchpad.net/bugs/1891760
You received this bug notification because you are a member of Ubuntu Server/Client Support Team, which is subscribed to apache2 in Ubuntu.