nginx upgrade failed

Bug #1295892 reported by Seth Arnold
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When upgrading nginx, I found this:

Setting up nginx-common (1.4.1-3ubuntu1.3) ...
Setting up nginx-light (1.4.1-3ubuntu1.3) ...
 * Starting nginx nginx nginx: [emerg] bind() to 127.0.0.1:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.122.1:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.1.40:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.1.14:80 failed (98: Address already in use)
nginx: [emerg] bind() to 127.0.0.1:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.122.1:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.1.40:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.1.14:80 failed (98: Address already in use)
nginx: [emerg] bind() to 127.0.0.1:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.122.1:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.1.40:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.1.14:80 failed (98: Address already in use)
nginx: [emerg] bind() to 127.0.0.1:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.122.1:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.1.40:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.1.14:80 failed (98: Address already in use)
nginx: [emerg] bind() to 127.0.0.1:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.122.1:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.1.40:80 failed (98: Address already in use)
nginx: [emerg] bind() to 192.168.1.14:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()
invoke-rc.d: initscript nginx, action "start" failed.
dpkg: error processing nginx-light (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of nginx:
 nginx depends on nginx-full | nginx-light; however:
  Package nginx-full is not installed.
  Package nginx-light is not configured yet.

dpkg: error processing nginx (--configure):
 dependency problems - leaving unconfigured
Setting up thunderbird (1:24.4.0+build1-0ubuntu0.13.10.2) ...
No apport report written because MaxReports is reached already
                                                              No apport report written because MaxReports is reached already
          Setting up thunderbird-locale-en (1:24.4.0+build1-0ubuntu0.13.10.2) ...
Setting up thunderbird-gnome-support (1:24.4.0+build1-0ubuntu0.13.10.2) ...
Setting up thunderbird-locale-en-gb (1:24.4.0+build1-0ubuntu0.13.10.2) ...
Setting up thunderbird-locale-en-us (1:24.4.0+build1-0ubuntu0.13.10.2) ...
Errors were encountered while processing:
 nginx-light
 nginx
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: nginx 1.4.1-3ubuntu1.3
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Fri Mar 21 17:11:26 2014
Dependencies:

InstallationDate: Installed on 2012-10-18 (519 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: nginx
UpgradeStatus: Upgraded to saucy on 2013-11-06 (135 days ago)

Revision history for this message
Seth Arnold (seth-arnold) wrote :
Revision history for this message
Thomas Ward (teward) wrote :

What version were you upgrading from?

Revision history for this message
Seth Arnold (seth-arnold) wrote :

Thomas, I was upgrading from version 1.4.1-3ubuntu1.2.

Thanks

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

Seth,

I'll take a poke at this, in a little while, I have to spin up a 13.10 VM for testing.

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

Seth, I was unable to replicate this using the default configurations, are you running any other webservers on your system, or have any special listen statements in your configs?

(This seems like a configuration problem on your setup rather than globally)

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.