Opened 7 years ago

Closed 7 years ago

#131 closed defect (fixed)

Unable to install ubuntu 11.10 package with running apache

Reported by: parallels Owned by: somebody
Priority: blocker Milestone:
Component: nginx-package Version: 1.0.x
Keywords: Cc:
uname -a:
nginx -V: not installed

Description

While testing application template for Virtuozzo (nginx-ubuntu-11.10-x86-ez-4.0.0-1.noarch.rpm):

21.03.2012-20.46.25: Selecting previously deselected package nginx.
21.03.2012-20.46.25: (Reading database ... 22168 files and directories currently installed.)
21.03.2012-20.46.25: Unpacking nginx (from .../nginx_1.0.14-1~oneiric_i386.vz.deb) ...
21.03.2012-20.46.25: ----------------------------------------------------------------------
21.03.2012-20.46.25:
21.03.2012-20.46.25: Thanks for using NGINX!
21.03.2012-20.46.25:
21.03.2012-20.46.25: Check out our community web site:
21.03.2012-20.46.25: * http://nginx.org/en/support.html
21.03.2012-20.46.25:
21.03.2012-20.46.25: If you have questions about commercial support for NGINX please visit:
21.03.2012-20.46.25: * http://www.nginx.com/support.html
21.03.2012-20.46.25:
21.03.2012-20.46.25: ----------------------------------------------------------------------
21.03.2012-20.46.26: Setting up nginx (1.0.14-1~oneiric) ...
21.03.2012-20.46.26: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
21.03.2012-20.46.27: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
21.03.2012-20.46.27: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
21.03.2012-20.46.28: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
21.03.2012-20.46.28: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
21.03.2012-20.46.29: nginx: [emerg] still could not bind()
21.03.2012-20.46.29: invoke-rc.d: initscript nginx, action "start" failed.
21.03.2012-20.46.29: dpkg: error processing nginx (--configure):
21.03.2012-20.46.29: subprocess installed post-installation script returned error exit status 1
21.03.2012-20.46.29: Errors were encountered while processing:
21.03.2012-20.46.29: nginx
21.03.2012-20.46.29: E: Sub-process /usr/bin/dpkg returned an error code (1)
21.03.2012-20.46.29: Error: /usr/bin/apt-get failed, exitcode=100

It looks that the same is now for ubuntu 10.04 (while it had worked before)

Change History (4)

comment:1 Changed 7 years ago by parallels

In 1.0.9 this error was not fatal:

10.11.2011-18.35.54: Unpacking nginx (from .../nginx_1.0.9-1_i386.vz.deb) ...
10.11.2011-18.35.55: Setting up nginx (1.0.9-1) ...
10.11.2011-18.35.56: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
10.11.2011-18.35.56: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
10.11.2011-18.35.57: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
10.11.2011-18.35.57: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
10.11.2011-18.35.58: nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
10.11.2011-18.35.58: nginx: [emerg] still could not bind()
10.11.2011-18.35.58: Installed:
10.11.2011-18.35.58: nginx i386 1.0.9-1

comment:2 Changed 7 years ago by fabler

  • Status changed from new to accepted

It is not fatal in 1.0.14 too, since package is installed actually.
Problem is in automatically generated by debian build tools postinst script. It try to start nginx and returns init script exit status:

invoke-rc.d nginx start || exit $?

I've compared automatically generated postinst with apache postinst, which do not result in fatal error when another process listen 80 port, and found a trick in it:

invoke-rc.d apache2 start || true

It is cheating but it works, so i'll fix nginx package in the same way.

comment:3 Changed 7 years ago by parallels

Thnx

comment:4 Changed 7 years ago by fabler

  • Resolution set to fixed
  • Status changed from accepted to closed

nginx_1.0.14-2~{lucid,oneiric}_{i386,amd64}.deb package fix this problem

Note: See TracTickets for help on using tickets.