apache2 fails during upgrade to 22.04: ERROR: Conf javascript-common does not exist

Bug #1986959 reported by Miguel De Leon
92
This bug affects 11 people
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Incomplete
Undecided
Lena Voytek

Bug Description

ubuntu22.04 upgrade

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: apache2 2.4.52-1ubuntu4.1
ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195
Uname: Linux 5.4.0-124-generic x86_64
000-default.conf: Error: [Errno 40] Demasiados niveles de enlaces simbólicos: '/etc/apache2/sites-enabled/000-default.conf'
Apache2ConfdDirListing: False
Apache2Modules:
 AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
 httpd (pid 11160) already running
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Aug 18 11:02:39 2022
ErrorMessage: el subproceso instalado paquete apache2 script post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2020-01-18 (942 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt 2.4.7
SourcePackage: apache2
Title: package apache2 2.4.52-1ubuntu4.1 failed to install/upgrade: el subproceso instalado paquete apache2 script post-installation devolvió el código de salida de error 1
UpgradeStatus: Upgraded to jammy on 2022-08-18 (0 days ago)

Revision history for this message
Miguel De Leon (mdeleon1957) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apache2 (Ubuntu):
status: New → Confirmed
Revision history for this message
Lena Voytek (lvoytek) wrote :

Hello,
Thank you for the bug report. From your logs I see:

info: Executing deferred 'a2enconf javascript-common' for package javascript-common
ERROR: Conf javascript-common does not exist!

It seems that javascript-common may be a new dependency of some plugin for apache2, and since its not installed an error is reported. I was unable to reproduce the error with the default setup of apache2. Are there any additional modules or configuration modifications you use that may cause this?

In the meantime you may be able to fix this issue by installing javascript-common:

sudo apt install javascript-common

Thanks!

summary: - package apache2 2.4.52-1ubuntu4.1 failed to install/upgrade: el
- subproceso instalado paquete apache2 script post-installation devolvió
- el código de salida de error 1
+ apache2 fails during upgrade to 22.04: ERROR: Conf javascript-common
+ does not exist
Lena Voytek (lvoytek)
tags: added: server-triage-discuss
Revision history for this message
Rapper_skull (rapper-skull) wrote :

I also want to add that, after installing javascript-common, apache2 failed to start because it couldn't find the php7.4 module.

Robie Basak (racb)
tags: added: server-todo
removed: server-triage-discuss
Changed in apache2 (Ubuntu):
assignee: nobody → Lena Voytek (lvoytek)
Revision history for this message
Miguel De Leon (mdeleon1957) wrote : Re: [Bug 1986959] Re: apache2 fails during upgrade to 22.04: ERROR: Conf javascript-common does not exist

I solved the problema uninstalling apache and making a New install
I did that with apt autoremove apache2
 - - purge

El mié., 24 ago. 2022 12:15 p. m., Robie Basak <email address hidden>
escribió:

> ** Tags removed: server-triage-discuss
> ** Tags added: server-todo
>
> ** Changed in: apache2 (Ubuntu)
> Assignee: (unassigned) => Lena Voytek (lvoytek)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986959
>
> Title:
> apache2 fails during upgrade to 22.04: ERROR: Conf javascript-common
> does not exist
>
> Status in apache2 package in Ubuntu:
> Confirmed
>
> Bug description:
> ubuntu22.04 upgrade
>
> ProblemType: Package
> DistroRelease: Ubuntu 22.04
> Package: apache2 2.4.52-1ubuntu4.1
> ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195
> Uname: Linux 5.4.0-124-generic x86_64
> 000-default.conf: Error: [Errno 40] Demasiados niveles de enlaces
> simbólicos: '/etc/apache2/sites-enabled/000-default.conf'
> Apache2ConfdDirListing: False
> Apache2Modules:
> AH00558: apache2: Could not reliably determine the server's fully
> qualified domain name, using 127.0.1.1. Set the 'ServerName' directive
> globally to suppress this message
> httpd (pid 11160) already running
> ApportVersion: 2.20.11-0ubuntu82.1
> Architecture: amd64
> CasperMD5CheckResult: unknown
> Date: Thu Aug 18 11:02:39 2022
> ErrorMessage: el subproceso instalado paquete apache2 script
> post-installation devolvió el código de salida de error 1
> InstallationDate: Installed on 2020-01-18 (942 days ago)
> InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
> Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal,
> 3.10.4-0ubuntu2
> PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2,
> 2.7.17-4
> RebootRequiredPkgs: Error: path contained symlinks.
> RelatedPackageVersions:
> dpkg 1.21.1ubuntu2.1
> apt 2.4.7
> SourcePackage: apache2
> Title: package apache2 2.4.52-1ubuntu4.1 failed to install/upgrade: el
> subproceso instalado paquete apache2 script post-installation devolvió el
> código de salida de error 1
> UpgradeStatus: Upgraded to jammy on 2022-08-18 (0 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1986959/+subscriptions
>
>

Revision history for this message
Lena Voytek (lvoytek) wrote :

I was able to reproduce the issue with the following:

lxc launch images:ubuntu/focal test-apache2
lxc exec test-apache2 bash

apt update && apt dist-upgrade -y
apt install ubuntu-release-upgrader-core apport pciutils apache2 javascript-common -y
rm /etc/apache2/conf-available/javascript-common.conf
do-release-upgrade

Miguel and others affected by this issue, do you know if you deleted javascript-common.conf at some point in the past?

Revision history for this message
Miguel De Leon (mdeleon1957) wrote :

No, I didn't.

El jue., 25 ago. 2022 12:50 p. m., Lena Voytek <email address hidden>
escribió:

> I was able to reproduce the issue with the following:
>
> lxc launch images:ubuntu/focal test-apache2
> lxc exec test-apache2 bash
>
> apt update && apt dist-upgrade -y
> apt install ubuntu-release-upgrader-core apport pciutils apache2
> javascript-common -y
> rm /etc/apache2/conf-available/javascript-common.conf
> do-release-upgrade
>
> Miguel and others affected by this issue, do you know if you deleted
> javascript-common.conf at some point in the past?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986959
>
> Title:
> apache2 fails during upgrade to 22.04: ERROR: Conf javascript-common
> does not exist
>
> Status in apache2 package in Ubuntu:
> Confirmed
>
> Bug description:
> ubuntu22.04 upgrade
>
> ProblemType: Package
> DistroRelease: Ubuntu 22.04
> Package: apache2 2.4.52-1ubuntu4.1
> ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195
> Uname: Linux 5.4.0-124-generic x86_64
> 000-default.conf: Error: [Errno 40] Demasiados niveles de enlaces
> simbólicos: '/etc/apache2/sites-enabled/000-default.conf'
> Apache2ConfdDirListing: False
> Apache2Modules:
> AH00558: apache2: Could not reliably determine the server's fully
> qualified domain name, using 127.0.1.1. Set the 'ServerName' directive
> globally to suppress this message
> httpd (pid 11160) already running
> ApportVersion: 2.20.11-0ubuntu82.1
> Architecture: amd64
> CasperMD5CheckResult: unknown
> Date: Thu Aug 18 11:02:39 2022
> ErrorMessage: el subproceso instalado paquete apache2 script
> post-installation devolvió el código de salida de error 1
> InstallationDate: Installed on 2020-01-18 (942 days ago)
> InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
> Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal,
> 3.10.4-0ubuntu2
> PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2,
> 2.7.17-4
> RebootRequiredPkgs: Error: path contained symlinks.
> RelatedPackageVersions:
> dpkg 1.21.1ubuntu2.1
> apt 2.4.7
> SourcePackage: apache2
> Title: package apache2 2.4.52-1ubuntu4.1 failed to install/upgrade: el
> subproceso instalado paquete apache2 script post-installation devolvió el
> código de salida de error 1
> UpgradeStatus: Upgraded to jammy on 2022-08-18 (0 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1986959/+subscriptions
>
>

Revision history for this message
Lena Voytek (lvoytek) wrote :

Thanks for the info, I'll keep digging to find out why that error showed up for you

Revision history for this message
MarkS (mark-marksyms) wrote :

FWIW, I see the same issue and to the best of my knowledge nothing has been done to the server to manually out of band remove files. Purging javascript-common and reinstalling does as noted above then produce a failure with PHP

apache2_reload: apache2: Syntax error on line 146 of /etc/apache2/apache2.conf: Syntax error on line 3 of /etc/apache2/mods-enabled/php7.4.load: Cannot load /usr/lib/apache2/modules/libphp7.4.so into server: /usr/lib/apache2/modules/libphp7.4.so: cannot open shared object file: No such file or directory

Revision history for this message
MarkS (mark-marksyms) wrote :

Removing (and purging) all the PHP 7x packages allows apache 2 to start. Now to fix the apps it was fronting.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

MarkS, can you clarify a bit your steps? You said that purging and reinstalling javascript-common produced a failure in php? What you are pasting does not seem related to the missing config file, it's php7.4 that just cannot be loaded on your system, so it may be unrelated to this bug here.

We are still waiting for consistent steps that reproduce the release upgrade failure *without* the manual removal of /etc/apache2/conf-available/javascript-common.conf, like it's done in comment #6.

Until we get more hints or information towards that end, there isn't much more we can do here on this bug, so I'll mark it as incomplete.

Changed in apache2 (Ubuntu):
status: Confirmed → Incomplete
tags: removed: server-todo
Bryce Harrington (bryce)
Changed in apache2 (Ubuntu):
status: Incomplete → New
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.