package nginx-core 1.18.0-6ubuntu2.2 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1

Bug #1930221 reported by Warren Prince
60
This bug affects 13 people
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Was upgrading to ubuntu 20.10 and error occured.

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: nginx-core 1.18.0-6ubuntu2.2
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon May 31 07:08:52 2021
ErrorMessage: installed nginx-core package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2019-01-02 (879 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt 2.1.10ubuntu0.3
SourcePackage: nginx
Title: package nginx-core 1.18.0-6ubuntu2.2 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to groovy on 2021-05-31 (0 days ago)

Revision history for this message
Warren Prince (wprince) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Simon Déziel (sdeziel) wrote :

Hello Warren,

Looking at the logs, you seem to be referencing a SSL certificate that's nowhere to be found:

nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/collabora.princelaw.com/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/collabora.princelaw.com/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

As such, this is a local configuration problem so I'll mark the bug as invalid.

Regards,
Simon

Changed in nginx (Ubuntu):
status: New → Invalid
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.