You have been subscribed to a public bug by Eric Desrochers (slashd):
[Impact]
Currently, NGINX installations trigger an installation "failure case" when
another process is bound to port 80 and NGINX is trying to use its default
configuration files.
This can lead to installation bug reports which are not actually bugs,
or having to alter configuration files before completing installations.
It might be better for postinst to determine if we actually need to
start or restart the service based on if something is listening on port
80.
[Test Case]
Failure
--------
1. Install haproxy (or apache2)
2. Configure it to bind to port 80 (apache2 will be automatically configured)
3. Install nginx
4. The installation will be broken as it will fail to install.
Success
-------
1. Do (1), (2) and (3) as above.
2. The installation will succeed. nginx won't auto start allowing it do install
correctly even if you have haproxy binding on port 80.
[Regression Potential]
Minimal. This change won't break installation of nginx. In fact it will allow
it to install if another daemon is binding to port 80.
** Affects: nginx (Ubuntu)
Importance: Wishlist
Assignee: Thomas Ward (teward)
Status: Fix Released
** Affects: nginx (Ubuntu Bionic)
Importance: High
Status: In Progress
** Affects: nginx (Ubuntu Cosmic)
Importance: Wishlist
Assignee: Thomas Ward (teward)
Status: Fix Released
--
[SRU] Allow NGINX to install but not start during postinst if another process
is bound to port 80
https://bugs.launchpad.net/bugs/1782226
You received this bug notification because you are a member of STS Sponsors,
which is subscribed to the bug report.
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help : https://help.launchpad.net/ListHelp
