package nginx-core 1.10.0-0ubuntu0.16.04.4 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

Bug #1700017 reported by NDIAYE Dame on 2017-06-23

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

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

Bug Description

Affichage récurrente d'une fenetre d'erreur lors du démarrage.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nginx-core 1.10.0-0ubuntu0.16.04.4
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Tue Jun 20 16:17:29 2017
ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
InstallationDate: Installed on 2017-06-19 (3 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.20
SourcePackage: nginx
Title: package nginx-core 1.10.0-0ubuntu0.16.04.4 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
UpgradeStatus: No upgrade log present (probably fresh install)

NDIAYE Dame (jailbreaker) wrote :
ChristianEhrhardt (paelzer) wrote :

Hi Ndiaye,

From the log:
jailbreaker nginx[28347]: nginx: [emerg] listen() to [::]:80, backlog 511 failed (98: Address already in use)

That seems like a configuration issue of either nginx or another service that blocks this port.

ChristianEhrhardt (paelzer) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

Changed in nginx (Ubuntu):
status: New → Incomplete
ChristianEhrhardt (paelzer) wrote :

The reason this continuously pop's up is that it fails over and over to upgrade this package for the outlined reasons until you resolved the configurations that block each other.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers