package nginx 1.18.0-0ubuntu1.2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd

Bug #1929878 reported by Luc Dens
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Not been aware of the problem/ No details known to me

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nginx 1.18.0-0ubuntu1.2
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu May 27 10:26:02 2021
ErrorMessage: vereistenproblemen - blijft ongeconfigureerd
InstallationDate: Installed on 2016-08-03 (1758 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.5
SourcePackage: nginx
Title: package nginx 1.18.0-0ubuntu1.2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
UpgradeStatus: Upgraded to focal on 2020-09-29 (240 days ago)

Revision history for this message
Luc Dens (luc-dens) wrote :
Revision history for this message
Thomas Ward (teward) wrote :

Your configuration is pointing to a nonexistent certificate somewhere in the configuration.

This is the relevant section in your logs:

mei 27 10:26:01 Kernoitje2 nginx[12175]: nginx: [emerg] cannot load certificate "/etc/ssl/meet.jit.si.crt": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/ssl/meet.jit.si.crt','r') error:2006D080:BIO routines:BIO_new_file:no such file)

Not a bug.

Changed in nginx (Ubuntu):
status: New → Invalid
Revision history for this message
Luc Dens (luc-dens) wrote : Re: [Bug 1929878] Re: package nginx 1.18.0-0ubuntu1.2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd

Thanks
Maybe the system could just signal : missing certificate instead of system failure?
Friendly  greetings
Luc

⁣BlueMail voor Android downloaden ​

Op 28 mei 2021 01:11, om 01:11, Thomas Ward <email address hidden> schreef:
>Your configuration is pointing to a nonexistent certificate somewhere
>in
>the configuration.
>
>This is the relevant section in your logs:
>
>mei 27 10:26:01 Kernoitje2 nginx[12175]: nginx: [emerg] cannot load
>certificate "/etc/ssl/meet.jit.si.crt": BIO_new_file() failed (SSL:
>error:02001002:system library:fopen:No such file or
>directory:fopen('/etc/ssl/meet.jit.si.crt','r') error:2006D080:BIO
>routines:BIO_new_file:no such file)
>
>
>Not a bug.
>
>** Changed in: nginx (Ubuntu)
> Status: New => Invalid
>
>--
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1929878
>
>Title:
> package nginx 1.18.0-0ubuntu1.2 failed to install/upgrade:
> vereistenproblemen - blijft ongeconfigureerd
>
>Status in nginx package in Ubuntu:
> Invalid
>
>Bug description:
> Not been aware of the problem/ No details known to me
>
> ProblemType: Package
> DistroRelease: Ubuntu 20.04
> Package: nginx 1.18.0-0ubuntu1.2
> ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
> Uname: Linux 5.4.0-73-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27.18
> Architecture: amd64
> CasperMD5CheckResult: skip
> Date: Thu May 27 10:26:02 2021
> ErrorMessage: vereistenproblemen - blijft ongeconfigureerd
> InstallationDate: Installed on 2016-08-03 (1758 days ago)
>InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
>(20160719)
> PackageArchitecture: all
>Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal,
>3.8.2-0ubuntu2
>PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2,
>2.7.17-4
> RelatedPackageVersions:
> dpkg 1.19.7ubuntu3
> apt 2.0.5
> SourcePackage: nginx
>Title: package nginx 1.18.0-0ubuntu1.2 failed to install/upgrade:
>vereistenproblemen - blijft ongeconfigureerd
> UpgradeStatus: Upgraded to focal on 2020-09-29 (240 days ago)
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1929878/+subscriptions

Revision history for this message
Thomas Ward (teward) wrote :

That is something you have to discuss with NGINX and their developers upstream. And is not something that we can do at the Ubuntu level.

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.