package apache2 2.4.41-4ubuntu3.12 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1

Bug #1980620 reported by karthikeyan0795@gmail.com
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

a

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: apache2 2.4.41-4ubuntu3.12
ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-41-generic x86_64
000-default.conf: Error: [Errno 40] Too many levels of symbolic links: '/etc/apache2/sites-enabled/000-default.conf'
Apache2ConfdDirListing: False
ApportVersion: 2.20.11-0ubuntu27.21
AptOrdering:
 apache2:amd64: Install
 apache2-data:amd64: Install
 apache2-utils:amd64: Install
 apache2-bin:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jun 28 07:06:02 2022
ErrorMessage: installed apache2 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-11-25 (220 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.6
SourcePackage: apache2
Title: package apache2 2.4.41-4ubuntu3.12 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
error.log:

[From DpkgTerminal.log]
info: Executing deferred 'a2enconf javascript-common' for package javascript-common
ERROR: Conf javascript-common does not exist!
dpkg: error al procesar el paquete apache2 (--configure):
 el subproceso instalado paquete apache2 script post-installation devolvió el código de salida de error 1

Revision history for this message
karthikeyan0795@gmail.com (karthickeyan0795) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote :

Thanks for taking the time to file this bug and trying to make Ubuntu better.

Checking the logs I can see this error when the apache2 package was installed:

Setting up apache2 (2.4.41-4ubuntu3.12) ...
info: Executing deferred 'a2enmod php7.4' for package libapache2-mod-php7.4
ERROR: Module php7.4 does not exist!
dpkg: error processing package apache2 (--configure):
 installed apache2 package post-installation script subprocess returned error exit status 1

However, I set up a clean Focal container and I was able to install the package and enable the php7.4 module just fine.

From the apache2 modules log we can see this:

Error: command ['/usr/sbin/apachectl', '-D DUMP_MODULES'] failed with exit code 1: 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
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Action '-D DUMP_MODULES' failed.
The Apache error log may have more information.

It seems that you port 80 is already in use. This seems to me a local configuration issue and not a package bug. Due to that I am marking this bug as Incomplete, if you have more information to provide which can help us to reproduce the problem please add a comment and then set the status back to New.

Changed in apache2 (Ubuntu):
status: New → Incomplete
Bryce Harrington (bryce)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for apache2 (Ubuntu) because there has been no activity for 60 days.]

Changed in apache2 (Ubuntu):
status: Incomplete → Expired
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.