Public bug reported:

There is a known issue where NGINX will not properly run or install when
IPv6 is fully disabled on a system.

Per Bug #1712696 which first detailed this, these are some 'relevant'
log entries:

Aug 23 23:52:24 thomas-ThinkPad-T430 nginx[20166]: nginx: [emerg] socket() 
[::]:80 failed (97: Address family not supported by protocol)
Aug 23 23:52:24 thomas-ThinkPad-T430 nginx[20166]: nginx: configuration file 
/etc/nginx/nginx.conf test failed
Aug 23 23:52:24 thomas-ThinkPad-T430 systemd[1]: nginx.service: Control process 
exited, code=exited status=1
Aug 23 23:52:24 thomas-ThinkPad-T430 systemd[1]: Failed to start A high 
performance web server and a reverse proxy server.

As you can see the system could not bind to Port 80 on IPv6.

While this is a **nonstandard** setup, there are some systems which are
configured to not have IPv6 support.  It should currently be considered
whether we should test for such 'systems' to see whether IPv6 is enabled
or not, and modify the configuration file accordingly during
install/configure.

This issue happens regardless of the 'supported' operating system status
or not, and is a core NGINX package issue, but also a core 'incompatible
configuration' issue with systems which disable IPv6.

** Affects: nginx (Ubuntu)
     Importance: Low
     Assignee: Thomas Ward (teward)
         Status: Triaged

** Description changed:

  There is a known issue where NGINX will not properly run or install when
  IPv6 is fully disabled on a system.
  
  Per Bug #1712696 which first detailed this, these are some 'relevant'
  log entries:
  
  Aug 23 23:52:24 thomas-ThinkPad-T430 nginx[20166]: nginx: [emerg] socket() 
[::]:80 failed (97: Address family not supported by protocol)
  Aug 23 23:52:24 thomas-ThinkPad-T430 nginx[20166]: nginx: configuration file 
/etc/nginx/nginx.conf test failed
  Aug 23 23:52:24 thomas-ThinkPad-T430 systemd[1]: nginx.service: Control 
process exited, code=exited status=1
  Aug 23 23:52:24 thomas-ThinkPad-T430 systemd[1]: Failed to start A high 
performance web server and a reverse proxy server.
  
  As you can see the system could not bind to Port 80 on IPv6.
  
  While this is a **nonstandard** setup, there are some systems which are
- configured to not have IPv6.  It should currently be considered whether
- we should test for such 'systems' to see whether IPv6 is enabled or not,
- and modify the configuration file accordingly during install/configure.
+ configured to not have IPv6 support.  It should currently be considered
+ whether we should test for such 'systems' to see whether IPv6 is enabled
+ or not, and modify the configuration file accordingly during
+ install/configure.
+ 
+ This issue happens regardless of the 'supported' operating system status
+ or not, and is a core NGINX package issue, but also a core 'incompatible
+ configuration' issue with systems which disable IPv6.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743592

Title:
  NGINX fails to install/upgrade if IPv6 is completely disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1743592/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to