package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[Tobias Stöckler]

This happened after a fresh install of Ubuntu 15.04. I had previously run
sudo apt-get install dnsmasq
in the terminal and then
sudo apt-get install nginx apache2
which lead to the failure.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: nginx-core 1.6.2-5ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Sat May 2 23:59:19 2015
DuplicateSignature: package:nginx-core:1.6.2-5ubuntu3:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2015-05-02 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt 1.0.9.7ubuntu4
SourcePackage: nginx
Title: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

[Tobias Stöckler (tstoeckler)]

So stopping the apache service fixes this problem. While I guess it's not the usual case, I do think it should be possible to install two web servers on the same machine. I guess it's fine (although unfortunate) to not allow having them running at the same time, but at least installing it should work. It generally makes sense I guess that installing apache2 starts the respective service, but still...

[Thomas Ward (teward)]

Not a bug.

This is a case of two web servers both fighting to bind to *:80.

We've seen this race condition for binding before but it's not something fixable in the package.

You can run two web servers but you would achieve it by binding to different IPs for each (rather than any IP). This however is not a bug, and a sysadmin-needs-to-configure-things issue so the Apache default and the nginx defaults aren't fighting each other.

[Thomas Ward (teward)]

You could also achieve this by having the web servers listen on different ports, or have one reverse proxy to the other on the differing port.

In either case this remains not-a-bug and a networking fundamentals problem of two things binding to the same IP/port combo.