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 #1708622 reported by Vishal N Sanjaria
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

How to solve it?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nginx-core 1.10.3-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Aug 4 14:09:52 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-07-21 (14 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
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)

Revision history for this message
Vishal N Sanjaria (vishal.n.sanjaria) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Ray Haleblian (ray-haleblian) wrote :

Running under VMware Fusion; problem dialog appeared on guest resumption.

Revision history for this message
Thomas Ward (teward) wrote :

Your core issue according to your logs is that you have bad configurations.

Aug 04 14:09:52 tss4 nginx[18947]: nginx: [emerg] "listen" directive is not allowed here in /etc/nginx/nginx.conf:1
Aug 04 14:09:52 tss4 nginx[18947]: nginx: configuration file /etc/nginx/nginx.conf test failed
Aug 04 14:09:52 tss4 systemd[1]: nginx.service: Control process exited, code=exited status=1
Aug 04 14:09:52 tss4 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
-- Subject: Unit nginx.service has failed

These logs indicate your NGINX configuration has things in the wrong locations, which means your config is busted. That's less a package bug and more an issue with your configuration. (Which means I am closing this as "Invalid" as it's a configuration-level issue and not a package bug).

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.