Public bug reported:
When upgrading nginx packages or booting with nginx configurations that
use `listen` statements or other types of bind locations such as these,
nginx sometimes fails to start because it cannot resolve the hostname:
upstream {
server http://someserver;
}
server {
listen myhostname:80;
# [...]
}
This can prevent package upgrades from working, and can prevent nginx from
loading at boot time.
-----
Bug reporter notes: This issue has shown up numerous times both in
Ubuntu and Debian bugs and is consistently an issue on package
updates/upgrades. While we don't have any bugs as such filed here at
the current time that clearly meet this case, it is known that this does
cause some of the package update/upgrade/install bugs if configurations
matching this format exist in the configurations directories.
** Affects: nginx (Ubuntu)
Importance: Medium
Status: Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1455921
Title:
nginx fails to start during boot or upgrade with hostnames in 'listen'
or 'upstream' bind commands.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1455921/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
