| 2015-11-02 12:28:25 |
Thomas Ward |
bug |
|
|
added bug |
| 2015-11-02 12:28:39 |
Thomas Ward |
summary |
Package nginx-* failed to install/upgrade due to Port 80 not being able to be bound to. |
[Master Bug] Package nginx-* failed to install/upgrade due to Port 80 not being able to be bound to. |
|
| 2015-11-02 12:28:46 |
Thomas Ward |
nginx (Ubuntu): status |
New |
Invalid |
|
| 2015-11-02 13:01:52 |
Thomas Ward |
summary |
[Master Bug] Package nginx-* failed to install/upgrade due to Port 80 not being able to be bound to. |
[Master Bug] Package nginx-* failed to install/upgrade due to Port 80 not being able to be bound to, due to "Address In Use" errors. |
|
| 2015-11-02 13:04:25 |
Thomas Ward |
description |
This is a master bug for all package-type nginx bugs with install/upgrade failures as a result of port 80 being already used by another process.
This is not a bug - this is an issue in which the system you are installing NGINX on already has something else listening on port 80.
To fix this issue, you need to first find what is listening on Port 80, and turn it off. At that time, either install NGINX or use 'apt-get install -f' to try and finish configuration. |
This is a master bug for all package-type nginx bugs with install/upgrade failures as a result of port 80 being already used by another process.
This is not a bug - this is an issue in which the system you are installing NGINX on already has something else listening on port 80.
To fix this issue, you need to first find what is listening on Port 80, and turn it off. At that time, either install NGINX or use 'apt-get install -f' to try and finish configuration.
An example of the error logs of this can be seen in Vivid and later with `systemctl -l status nginx.service` which will return something like the attached "systemctl_output.txt" file that is attached to this bug. |
|
| 2015-11-02 13:05:07 |
Thomas Ward |
attachment added |
|
systemctl_output.txt https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1512344/+attachment/4511191/+files/systemctl_output.txt |
|
| 2015-11-02 13:08:42 |
Thomas Ward |
description |
This is a master bug for all package-type nginx bugs with install/upgrade failures as a result of port 80 being already used by another process.
This is not a bug - this is an issue in which the system you are installing NGINX on already has something else listening on port 80.
To fix this issue, you need to first find what is listening on Port 80, and turn it off. At that time, either install NGINX or use 'apt-get install -f' to try and finish configuration.
An example of the error logs of this can be seen in Vivid and later with `systemctl -l status nginx.service` which will return something like the attached "systemctl_output.txt" file that is attached to this bug. |
This is a master bug for all package-type nginx bugs with install/upgrade failures as a result of port 80 being already used by another process. It was created to be a 'master' for all the bugs which are caused by some other service being bound to *:80 (both IPv4 and IPv6) when any of the nginx flavors or server-binary packages are installed, and all subsequent bugs which match this type of issue will be marked as a duplicate of this one.
------
The issue observed is not in and of itself a bug - this is an issue in which the system you are installing NGINX on already has something else listening on port 80.
To fix this issue, you need to first find what is listening on Port 80, and turn it off. At that time, either install NGINX or use 'apt-get install -f' to try and finish configuration.
An example of the error logs of this can be seen in Vivid and later with `systemctl -l status nginx.service` which will return something like the attached "systemctl_output.txt" file that is attached to this bug. |
|
| 2015-11-02 21:00:12 |
Thomas Ward |
summary |
[Master Bug] Package nginx-* failed to install/upgrade due to Port 80 not being able to be bound to, due to "Address In Use" errors. |
[Master Bug] Package nginx-* failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (due to Port 80 being in use) |
|
| 2015-11-02 21:44:24 |
Thomas Ward |
summary |
[Master Bug] Package nginx-* failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (due to Port 80 being in use) |
Package nginx-* failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 |
|
| 2015-11-02 21:48:06 |
Thomas Ward |
summary |
Package nginx-* failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 |
[Master Bug] Package nginx-* failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (due to "Address in Use" issue) |
|
| 2015-11-02 21:50:56 |
Thomas Ward |
description |
This is a master bug for all package-type nginx bugs with install/upgrade failures as a result of port 80 being already used by another process. It was created to be a 'master' for all the bugs which are caused by some other service being bound to *:80 (both IPv4 and IPv6) when any of the nginx flavors or server-binary packages are installed, and all subsequent bugs which match this type of issue will be marked as a duplicate of this one.
------
The issue observed is not in and of itself a bug - this is an issue in which the system you are installing NGINX on already has something else listening on port 80.
To fix this issue, you need to first find what is listening on Port 80, and turn it off. At that time, either install NGINX or use 'apt-get install -f' to try and finish configuration.
An example of the error logs of this can be seen in Vivid and later with `systemctl -l status nginx.service` which will return something like the attached "systemctl_output.txt" file that is attached to this bug. |
This is a master bug for all package-type nginx bugs with install/upgrade failures as a result of port 80 being already used by another process. It was created to be a 'master' for all the bugs which are caused by some other service being bound to *:80 (both IPv4 and IPv6) when any of the nginx flavors or server-binary packages are installed, and all subsequent bugs which match this type of issue will be marked as a duplicate of this one.
A purposely-generated 'package' bug of this type was created, and is located at https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1512484. Bugs of a nature matching that one (an "Address In Use" error) should point to here.
------
The issue observed is not in and of itself a bug - this is an issue in which the system you are installing NGINX on already has something else listening on port 80.
To fix this issue, you need to first find what is listening on Port 80, and turn it off. At that time, either install NGINX or use 'apt-get install -f' to try and finish configuration.
An example of the error logs of this can be seen in Vivid and later with `systemctl -l status nginx.service` which will return something like the attached "systemctl_output.txt" file that is attached to this bug. |
|
| 2015-11-03 05:52:28 |
Alex |
nginx (Ubuntu): status |
Invalid |
Confirmed |
|
| 2015-11-03 11:46:10 |
Thomas Ward |
nginx (Ubuntu): status |
Confirmed |
Invalid |
|
| 2017-06-30 13:20:19 |
Javier Arias |
bug task added |
|
nginx |
|
| 2017-12-09 12:31:48 |
Rakib Hasan |
nginx: status |
New |
Invalid |
|
| 2017-12-09 12:31:48 |
Rakib Hasan |
nginx: assignee |
|
Rakib Hasan (rkb) |
|
| 2017-12-09 13:14:45 |
Thomas Ward |
nginx: assignee |
Rakib Hasan (rkb) |
Thomas Ward (teward) |
|
