<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Stuart,</p>
<p>With my Ubuntu Core Dev hat on and Ubuntu Server Team hat on, the
Ubuntu team decided that disabling IPv6 on a server is an
administrator decision that is "not the defaults" and the default
installation configuration is designed as that - the 'default'
that functions in a standard-expected installation. Full
disabling of IPv6 was considered "atypical default
configuration". This was discussed at length in multiple bugs on
this nature.</p>
<p>With my Debian Maintainer hat on:<br>
</p>
<p>I've discussed this in the #debian-devel channel on IRC, and the
responses I have are: "IPv6 is always enabled, you should use it
in the default config", and "if you disable ipv[46] totaly, I
don't think one can expect the system to work without bugs."</p>
<p>The consensus is identical among multiple users and Debian
Developers, as the configuration you have chosen *diverges* from
the defaults and is a "user/admin decision" that the user/admin
will have to accept consequences for.<br>
</p>
<p>As such, this echoes the Ubuntu Server Team's decision but at the
Debian level, and we're not changing this for Bullseye or any of
the other supported Debian releases.</p>
<p>You need to configure your deployment scripts to ignore the first
package installation failure, replace your configuration entirely,
and *then* `apt install -f` or similar in your deploy script to
*replace* the configuration.</p>
<p>---<br>
</p>
<p>(TL;DR, The default configuration file is made to adapt to
*default* Debian environments, and it's non-standard to disable
ipv[46] entirely at a sysctl and similar level, so you can
*expect* multiple packages to have bugs when these nonstandard
setups are being used. ALTERNATIVELY, your deployment script
should install nginx first, change the configuration, disable
IPv6, then reboot. That's how you *should* do things with an
autodeploy script).</p>
<p><br>
</p>
<p><br>
</p>
<p>Thomas Ward</p>
<p>Ubuntu Core Developer (<a class="moz-txt-link-freetext" href="https://launchpad.net/~teward">https://launchpad.net/~teward</a>)</p>
<p>Debian Maintainer (for nginx package among others)<br>
</p>
<div class="moz-cite-prefix">On 10/7/22 14:37, Stuart Culligan
wrote:<br>
</div>
<blockquote type="cite" cite="mid:43b53d1b-df3a-f45f-9e9c-8eb071314e84@car-part.com">
<p class="message flowed" style="font-family: monospace; padding-top: 8px; margin-top: 0px; border-top: 0px; white-space: pre-wrap; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Ok I guess I should have been more clear.
This is a debian package issue in that the debian package is linking the default site
default -> /etc/nginx/sites-available/default
Which contains 2 listen lines as I listed before</p>
<p class="message flowed" style="font-family: monospace; padding-top: 8px; margin-top: 0px; border-top: 0px; white-space: pre-wrap; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"> listen 80 default_server;
listen [::]:80 default_server;
After digging further into this I discovered it was IPv6 line that was causing the issue.
listen [::]:80 default_server;
We disable IPv6 on our servers.
I did not run into this on Ubuntu 18.04.
It appears there was a lot of changes to how debian packaged nginx between the 2 OS releases.
With these changes there appears to be a lot of changes to the default.
I suggest not trying to link the default and not attempting to do a restart.
Just a suggestion though. </p>
<p class="message flowed" style="font-family: monospace; padding-top: 8px; margin-top: 0px; border-top: 0px; white-space: pre-wrap; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Now I am trying to find a way to get passed this issue as we build an entire server via debian packages.
I can not have a package error out in my build process.</p>
<p class="message flowed" style="font-family: monospace; padding-top: 8px; margin-top: 0px; border-top: 0px; white-space: pre-wrap; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">
</p>
<div class="moz-cite-prefix">On 10/7/2022 11:45 AM, Debian Bug
Tracking System wrote:<br>
</div>
<blockquote type="cite" cite="mid:handler.1021393.D1021393.16651573441996461.notifdone@bugs.debian.org">
<pre class="moz-quote-pre" wrap="">This is an automatic notification regarding your Bug report
which was filed against the nginx-common package:
#1021393: error in package nginx-common_1.18.0-6ubuntu14.2_all.deb for ubuntu 22.04 with default enabled site.
It has been closed by Thomas Ward <a class="moz-txt-link-rfc2396E" href="mailto:teward@thomas-ward.net" moz-do-not-send="true"><teward@thomas-ward.net></a>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Thomas Ward <a class="moz-txt-link-rfc2396E" href="mailto:teward@thomas-ward.net" moz-do-not-send="true"><teward@thomas-ward.net></a> by
replying to this email.
</pre>
</blockquote>
</blockquote>
</body>
</html>