package nginx-core 1.10.3-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1709617 reported by Dinali on 2017-08-09
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Undecided
Unassigned

Bug Description

I get this error most oftenly

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nginx-core 1.10.3-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Aug 8 11:35:09 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.24
SourcePackage: nginx
Title: package nginx-core 1.10.3-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Dinali (wso2dinali) wrote :
tags: removed: need-duplicate-check
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

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

Hi Dinali,
this bug seems to reported quite a while after the actual issue.
So most logs attached are now showing a happy nginx running fine.

What happened is that on upgrade a service has to be restarted.
If e.g. the config at that time is broken the restart will fail and such an error occurs.

You either have fixed your configuration and things are good now or there was a transient issue back when you upgraded.
In any case if it happens again try to report e.g. ''systemctl status nginx" right after the error.
That most often shows why it didn't start and you can fix it.
Once done the uprgade would work.

ChristianEhrhardt (paelzer) wrote :

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

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: Confirmed → Incomplete
Paul Vaughan (paulieboo) wrote :

I got this error after installing nginx on a system that already had Apache2 running on port 80. When I changed the nginx default site config to run on an unused port, it started up just fine.

Thomas Ward (teward) on 2017-10-03
Changed in nginx (Ubuntu):
status: Incomplete → Invalid
status: Invalid → Incomplete
Launchpad Janitor (janitor) wrote :

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

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

Other bug subscribers