package nginx-light 1.10.3-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1709805 reported by machars.H
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

after installed nginx,I can not open system setting

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: nginx-light 1.10.3-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
Uname: Linux 4.10.0-30-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering:
 nginx-full:amd64: Remove
 nginx-light:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Aug 9 01:45:53 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-08-09 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt 1.4
SourcePackage: nginx
Title: package nginx-light 1.10.3-1ubuntu3.1 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
machars.H (machars) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi,
From your log:
Aug 09 01:45:51 ubuntu nginx[12229]: nginx: [emerg] bind() to 0.0.0.0:80 fa…use)

That seems to be another service running and blocking port 80?

You should check what is running there and need to configure the former or the new service to not collide. An example would be installing apache2 and nginx without taking care they don't run into each other.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thank you for your report.

This looks like a local configuration problem, rather than a bug in Ubuntu.

You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu.

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
Revision history for this message
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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.