package nginx-extras (not installed) failed to install/upgrade: installed nginx-extras package post-installation script subprocess returned error exit status 1

Bug #1874631 reported by Paul Dorman on 2020-04-24

This bug report will be marked for expiration in 18 days if no further activity occurs. (find out why)

10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Undecided
Unassigned

Bug Description

Bug encountered during distribution upgrade

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nginx-extras (not installed)
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr 24 18:50:02 2020
ErrorMessage: installed nginx-extras package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2019-01-21 (459 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2
SourcePackage: nginx
Title: package nginx-extras (not installed) failed to install/upgrade: installed nginx-extras package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Paul Dorman (paul-dorman) wrote :
tags: removed: need-duplicate-check
Simon Déziel (sdeziel) wrote :

Looks like some other process was left behind listening on the socket thus preventing nginx from binding that IP/port:

Apr 24 18:49:59 xeonux systemd[1]: Starting A high performance web server and a reverse proxy server...
Apr 24 18:49:59 xeonux nginx[22466]: nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
...
Apr 24 18:50:02 xeonux nginx[22466]: nginx: [emerg] still could not bind()

Are you aware of any other web servers you might have been running at the time of the update? If not, it's possible it was an old instance of nginx that was not stopped properly and conflicted with the new one. This could happen if you had manually started nginx (without systemctl/service) for example. I'm mark the bug as incomplete while waiting for more details from you. Thanks!

Changed in nginx (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers