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

Bug #1730318 reported by Gregor Doroschenko on 2017-11-06
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Undecided
Unassigned

Bug Description

i am using ubuntu 17.10 and nginx core is crashed during the apt-get update

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: nginx-core 1.12.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Thu Nov 2 13:25:42 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt 1.5
SourcePackage: nginx
Title: package nginx-core 1.12.1-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Gregor Doroschenko (bublikxd) wrote :
tags: removed: need-duplicate-check
Joshua Powers (powersj) wrote :

From terminal log:

Nov 02 13:25:41 gregor-linux nginx[8274]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Nov 02 13:25:41 gregor-linux nginx[8274]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 02 13:25:41 gregor-linux nginx[8274]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Nov 02 13:25:42 gregor-linux nginx[8274]: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Nov 02 13:25:42 gregor-linux nginx[8274]: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
Nov 02 13:25:42 gregor-linux nginx[8274]: nginx: [emerg] still could not bind()
Nov 02 13:25:42 gregor-linux systemd[1]: nginx.service: Control process exited, code=exited status=1
Nov 02 13:25:42 gregor-linux systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Nov 02 13:25:42 gregor-linux systemd[1]: nginx.service: Unit entered failed state.
Nov 02 13:25:42 gregor-linux systemd[1]: nginx.service: Failed with result 'exit-code'.

Joshua Powers (powersj) wrote :

Thank you for taking the time to file a bug report.

The attached logs indicate that nginx is not able to bind to the IP and port
specified by your configuration files. Usually, this is due to some other
piece of software on your system already being bound to the port, which makes
this a local system issue, and not a bug in the package.

Since this is most likely the case, I am marking this bug as 'Invalid'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explaining why you believe this is a bug in Ubuntu
rather than a problem specific to your system. Depending on the information
provided, the status will either be set to "Confirmed" if we can reproduce
the issue reported, or we will leave the status as "Invalid" and explain why
this is the case.

For local system issues, you can find assistance here:
http://www.ubuntu.com/support/community

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

Other bug subscribers