Shirish, doesn't matter if your ISP doesn't have IPv6, thats no
reason to disable it system wide and not using it, loopback connections
will use it, as well maybe LAN connections.
Nginx will listen on both IPv4 and IPv6.
You are using a non standard setup so problems like this will happen.
Regarding dh_installinit, I disagree thats the best behavior, for
me it would be best that it complains but continues the configuration
ignoring the error anyway; the init file is correctly installed, it just
failed to start it, thats not an installation problem, there is nothing
wrong with the installation... though that probably should be discussed
in another wishlist report or a mailing list...
This bug should be closed then, thanks very much to everyone!
El 10/03/15 a las 13:08, shirish शिरीष escibió:
at bottom :-
On 3/10/15, Christos Trochalakis <yati...@ideopolis.gr> wrote:
<snipped>
This is definitely the problem, nginx cannot bind an ipv6 socket so it
fails to start.
The package stays in unconfigured state when nginx could not be started,
this is standard behaviour: dh_installinit by default adds a stanga in
the postinst script that runs `invoke-rc.d <service> start || exit $?`.
So when the service fails the script exits with a non-zero exit status.
Please let me know what do you want to do so I know what action I need
to take my end -
a. Wait for you to package a patched version.
b. Think of how I can get IPv6 only on the loopback interface 'lo' .
This is how I had done it
https://wiki.debian.org/DebianIPv6#How_to_turn_off_IPv6
basically
~$ cat /etc/default/grub | grep ipv6
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 init=/lib/systemd/systemd"
You can delete the `listen` ipv6 line from your nginx config (probably
/etc/nginx/sites-enabled/default) and run an `apt-get install` to
reconfigure the package. That should fix the issue for you.
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Hi Christos,
Thank you for taking time off and helping. I don't see IPv6 mentioned
anywhere in the file explicitly but I am guessing you are saying to
delete line 18 from the file.
listen [::]:80 default_server;
If my understanding is correct then the ::: are for IPv6 as the
addresses are pretty large.
It's a good thing that the sites-available/default file is from
nginx-common package
$ dpkg -L nginx-common | grep default
/etc/default
/etc/default/nginx
/etc/nginx/sites-available/default
So I deleted that line and then reinstalled the package.
~$ sudo aptitude install nginx-full
The following partially installed packages will be configured:
nginx-full
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
D000001: ensure_diversions: new, (re)loading
D000001: process queue pkg nginx-full:amd64 queue.len 0 progress 1, try 1
Setting up nginx-full (1.6.2-5) ...
D000001: ensure_diversions: same, skipping
D000001: cmpversions a='0:1.17.24' b='0:1.16' r=1
D000001: cmpversions a='0:1.17.24' b='0:1.16' r=1
D000001: ensure_diversions: new, (re)loading
D000001: cmpversions a='0:1.17.24' b='0:1.16' r=1
D000001: cmpversions a='0:1.17.24' b='0:1.16' r=1
For some reason I like aptitude more than apt-get, does the same
thing, as can be seen it reconfigures the package and doesn't complain
anymore.
Then ran the test :-
$ sudo /usr/sbin/nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
Made sure that dpkg says it is installed just fine :-
$ dpkg -l nginx-full
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Description
+++-==============================-====================-====================-=================================================================
ii nginx-full 1.6.2-5 amd64
nginx web/proxy server (standard version)
So, essentially the work-around works. Now the standard behavior
"should be" that if IPv6 fails, it should fall-back to IPv4 but for
some reason that isn't happening.
Just as a caveat also saw this
http://www.ipv6-test.com/stats/country/IN, so it seems it will take a
few more years for Ipv6 to become dominant at least here in India.
--
Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: iba...@codigolibre.net - http://go.to/ibaldo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
