package apache2 2.4.52-1ubuntu4.1 failed to install/upgrade: subproces van pakket apache2 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug

Bug #1991800 reported by Marc Sonius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Upgrading 20.04 Focal Fossa to 22.04 Jammy Jellyfish...
Hope I can now fix all the other issues that arise.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: apache2 2.4.52-1ubuntu4.1
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
Apache2ConfdDirListing: False
Apache2Modules: httpd (pid 1236) already running
ApportVersion: 2.20.11-0ubuntu82.1
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Oct 5 15:51:47 2022
DpkgTerminalLog:
 Instellen van apache2 (2.4.52-1ubuntu4.1) ...
 info: Executing deferred 'a2enconf javascript-common' for package javascript-common
 ERROR: Conf javascript-common does not exist!
 dpkg: fout bij verwerken van pakket apache2 (--configure):
  subproces van pakket apache2 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
ErrorMessage: subproces van pakket apache2 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
InstallationDate: Installed on 2021-01-12 (631 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04
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.8
SourcePackage: apache2
Title: package apache2 2.4.52-1ubuntu4.1 failed to install/upgrade: subproces van pakket apache2 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
UpgradeStatus: Upgraded to jammy on 2022-10-05 (0 days ago)
modified.conffile..etc.apache2.apache2.conf: [modified]
modified.conffile..etc.apache2.envvars: [modified]
modified.conffile..etc.apache2.mods-available.mpm_worker.conf: [modified]
mtime.conffile..etc.apache2.apache2.conf: 2022-10-04T15:57:01.801696
mtime.conffile..etc.apache2.envvars: 2021-01-15T12:42:20.739488
mtime.conffile..etc.apache2.mods-available.mpm_worker.conf: 2021-10-31T16:12:53.877906

Revision history for this message
Marc Sonius (masaia) wrote :
Revision history for this message
Paride Legovini (paride) wrote :

Hello Marc and thanks for this bug report. I tried to reproduce the issue in a clean LXD container by doing the following:

1. Create new Focal container (lxc launch ubuntu:focal paride-f)
2. Jump in the container (lxc exec paride-f bash)
3. apt install apache2 javascript-common
4. a2enconf javascript-common # it was already enabled
5. systemctl restart apache2 # worked fine
6. do-release-upgrade # upgraded fine
7. systemctl status apache2 # in good health
8. a2enconf javascript-common # it was already enabled
9. systemctl restart apache2 # worked fine

This means that we can't tell if the issue you described is a bug in Ubuntu or a problem specificto your system. In order to do so we need some steps to reproduce the issue from a clean start, on the lines of what I provided above. Could you please try to do so and report your findings?

For the moment I'm marking this bug report as Incomplete.

Thanks!

Changed in apache2 (Ubuntu):
status: New → Incomplete
Revision history for this message
Paride Legovini (paride) wrote :

Lena (~lvoytek) pointed out that this is likely a duplicate of LP: #1986959, which she's actively trying to debug/fix. I'm marking this bug report as a duplicate of LP: #1986959; please remove the duplicate flag if you think this is an unrelated issue.

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.