package nginx-core 1.9.3-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1495805 reported by Kaanpakpum Kamonrotchai
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

NA

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: nginx-core 1.9.3-1ubuntu1
Uname: Linux 4.2.0-040200rc8-lowlatency x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Tue Sep 15 12:28:59 2015
DuplicateSignature: package:nginx-core:1.9.3-1ubuntu1:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2015-08-28 (17 days ago)
InstallationMedia: Ubuntu-Kylin 15.10 "Wily Werewolf" - Alpha amd64 (20150826)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu3
 apt 1.0.9.10ubuntu6
SourcePackage: nginx
Title: package nginx-core 1.9.3-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Kaanpakpum Kamonrotchai (kaanpakpum) wrote :
Revision history for this message
Steve Beattie (sbeattie) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
tags: removed: need-duplicate-check
Revision history for this message
Thomas Ward (teward) wrote :

Do you have Apache or some other service set up and running on Port 80 already?

If so, disable that service (or at least stop the service) before running `apt-get install -f` or similar to finish configuration. You have a "cannot bind to port" error as a result of something else being bound to the port already, which does not indicate a bug in this package.

(Check the output of `systemctl status -l nginx` to see the error messages which point out the failure code.)

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.