Processed: Re: Bug#779825: no port attached to webserver
Processing commands for cont...@bugs.debian.org: severity 779825 important Bug #779825 [nginx-full] nginx-full: Unable to install nginx-full, does not get configured at end. Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 779825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
severity 779825 important
thanks
Setting severity to important as per discussion above.
On Wed, Mar 11, 2015 at 12:28 AM, Michael Lustfield
mich...@lustfield.net wrote:
I've seen this in other packages such as mysql. Admittedly, it can be a bit
frustrating that an inability to cleanly update/install a package can cause
issues during an upgrade.
However, it is possible that something else may depend on a package cleanly
upgrading before it can proceed. I can think of a few cases where this could
happen.
To be perfectly honest, I'd like to make an inability to start not prevent a
clean upgrade as well. We'll definitely need to discuss it a bit. I do wish
there was a Debian policy about this because we've really just stuck with
how most packages behave.
--
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
On Mon, Mar 09, 2015 at 10:58:52PM +0530, shirish शिरीष wrote: at bottom :- On 3/9/15, Ivan Baldo iba...@adinet.com.uy wrote: Ok, decided to check current Debian Policy Manual and there isn't a specific mention of what to do when starting a service after dpkg's configuration phase and that service fails. So I guess is up to maintainers of this package to decide. For what is worth, I vote for just continuing anyway and let the sysadmin fix it later, since it surely will see that the webserver isn't starting... Thanks for your consideration! El 09/03/15 a las 10:14, Ivan Baldo escibió: Hello Shirish! Good news, thats it, you don't have IPv6 at all configured, not even for the loopback interface, which is a pretty non standard setup nowadays so be careful, other services could act badly. I don't know what the Policy document says about this situation, but shouldn't the install succeed even if Nginx couldn't be started? For example, suppose that I want to remove all IPv6 support from a server, I think the package should install correctly anyway and let me fix the configuration later myself to avoid listening on IPv6 and listen only in IPv4. Or what happens if I have something else listening on port 80 (a reverse proxy for example) and I want to install Nginx and then change it to listen on port 81 instead? This is not a bug on _installation_ but on _startup_, there's a difference. Of course this is my own personal opinion and haven't read the Policy document in years... Thanks all, have a great day everybody! Hi all, Can everybody (i.e. Ivan, Norbert and Kartik) can you all reproduce the issue if IPv6 is not set does the installation and configuration fail in that condition. It would be nice if people see if they run into the same issue, then we found the root cause. @Kartik, please see if the issue happens if IPv6 is not configured. If it is please re-word the bug title, rework the severity if you think it should not be an RC bug or/and patch the package. 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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
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. D01: ensure_diversions: new, (re)loading D01: process queue pkg nginx-full:amd64 queue.len 0 progress 1, try 1 Setting up nginx-full (1.6.2-5) ... D01: ensure_diversions: same, skipping D01: cmpversions a='0:1.17.24' b='0:1.16' r=1 D01: cmpversions a='0:1.17.24' b='0:1.16' r=1 D01: ensure_diversions: new, (re)loading D01: cmpversions a='0:1.17.24' b='0:1.16' r=1 D01: 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,
Bug#779825: no port attached to webserver
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. D01: ensure_diversions: new, (re)loading D01: process queue pkg nginx-full:amd64 queue.len 0 progress 1, try 1 Setting up nginx-full (1.6.2-5) ... D01: ensure_diversions: same, skipping D01: cmpversions a='0:1.17.24' b='0:1.16' r=1 D01: cmpversions a='0:1.17.24' b='0:1.16' r=1 D01: ensure_diversions: new, (re)loading D01: cmpversions a='0:1.17.24' b='0:1.16' r=1 D01: 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. -- 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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
I've seen this in other packages such as mysql. Admittedly, it can be a bit frustrating that an inability to cleanly update/install a package can cause issues during an upgrade. However, it is possible that something else may depend on a package cleanly upgrading before it can proceed. I can think of a few cases where this could happen. To be perfectly honest, I'd like to make an inability to start not prevent a clean upgrade as well. We'll definitely need to discuss it a bit. I do wish there was a Debian policy about this because we've really just stuck with how most packages behave.
Bug#779825: no port attached to webserver
Hello. Maybe you don't have IPv6 at all configured, not even in the lo interface? Whats the output of ip -6 addr? Thanks! -- 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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
Hi Ivan, The output is :- $ ip -6 addr $ On 3/9/15, Ivan Baldo iba...@adinet.com.uy wrote: Hello. Maybe you don't have IPv6 at all configured, not even in the lo interface? Whats the output of ip -6 addr? Thanks! -- 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 -- 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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
Hello Shirish! Good news, thats it, you don't have IPv6 at all configured, not even for the loopback interface, which is a pretty non standard setup nowadays so be careful, other services could act badly. I don't know what the Policy document says about this situation, but shouldn't the install succeed even if Nginx couldn't be started? For example, suppose that I want to remove all IPv6 support from a server, I think the package should install correctly anyway and let me fix the configuration later myself to avoid listening on IPv6 and listen only in IPv4. Or what happens if I have something else listening on port 80 (a reverse proxy for example) and I want to install Nginx and then change it to listen on port 81 instead? This is not a bug on _installation_ but on _startup_, there's a difference. Of course this is my own personal opinion and haven't read the Policy document in years... Thanks all, have a great day everybody! El 09/03/15 a las 09:59, shirish शिरीष escibió: Hi Ivan, The output is :- $ ip -6 addr $ On 3/9/15, Ivan Baldo iba...@adinet.com.uy wrote: Hello. Maybe you don't have IPv6 at all configured, not even in the lo interface? Whats the output of ip -6 addr? Thanks! -- 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 -- 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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
Ok, decided to check current Debian Policy Manual and there isn't a specific mention of what to do when starting a service after dpkg's configuration phase and that service fails. So I guess is up to maintainers of this package to decide. For what is worth, I vote for just continuing anyway and let the sysadmin fix it later, since it surely will see that the webserver isn't starting... Thanks for your consideration! El 09/03/15 a las 10:14, Ivan Baldo escibió: Hello Shirish! Good news, thats it, you don't have IPv6 at all configured, not even for the loopback interface, which is a pretty non standard setup nowadays so be careful, other services could act badly. I don't know what the Policy document says about this situation, but shouldn't the install succeed even if Nginx couldn't be started? For example, suppose that I want to remove all IPv6 support from a server, I think the package should install correctly anyway and let me fix the configuration later myself to avoid listening on IPv6 and listen only in IPv4. Or what happens if I have something else listening on port 80 (a reverse proxy for example) and I want to install Nginx and then change it to listen on port 81 instead? This is not a bug on _installation_ but on _startup_, there's a difference. Of course this is my own personal opinion and haven't read the Policy document in years... Thanks all, have a great day everybody! El 09/03/15 a las 09:59, shirish शिरीष escibió: Hi Ivan, The output is :- $ ip -6 addr $ On 3/9/15, Ivan Baldo iba...@adinet.com.uy wrote: Hello. Maybe you don't have IPv6 at all configured, not even in the lo interface? Whats the output of ip -6 addr? Thanks! -- 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 -- 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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
at bottom :- On 3/9/15, Ivan Baldo iba...@adinet.com.uy wrote: Ok, decided to check current Debian Policy Manual and there isn't a specific mention of what to do when starting a service after dpkg's configuration phase and that service fails. So I guess is up to maintainers of this package to decide. For what is worth, I vote for just continuing anyway and let the sysadmin fix it later, since it surely will see that the webserver isn't starting... Thanks for your consideration! El 09/03/15 a las 10:14, Ivan Baldo escibió: Hello Shirish! Good news, thats it, you don't have IPv6 at all configured, not even for the loopback interface, which is a pretty non standard setup nowadays so be careful, other services could act badly. I don't know what the Policy document says about this situation, but shouldn't the install succeed even if Nginx couldn't be started? For example, suppose that I want to remove all IPv6 support from a server, I think the package should install correctly anyway and let me fix the configuration later myself to avoid listening on IPv6 and listen only in IPv4. Or what happens if I have something else listening on port 80 (a reverse proxy for example) and I want to install Nginx and then change it to listen on port 81 instead? This is not a bug on _installation_ but on _startup_, there's a difference. Of course this is my own personal opinion and haven't read the Policy document in years... Thanks all, have a great day everybody! Hi all, Can everybody (i.e. Ivan, Norbert and Kartik) can you all reproduce the issue if IPv6 is not set does the installation and configuration fail in that condition. It would be nice if people see if they run into the same issue, then we found the root cause. @Kartik, please see if the issue happens if IPv6 is not configured. If it is please re-word the bug title, rework the severity if you think it should not be an RC bug or/and patch the package. 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 -- 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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
at bottom :-
On 3/9/15, Kartik Mistry kartik.mis...@gmail.com wrote:
On Mon, Mar 9, 2015 at 12:08 PM, shirish शिरीष shirisha...@gmail.com
wrote:
AFA /etc/nginx/nginx.conf test failure is concerned, I haven't changed
anything at that file, it's in the default state.
It should not fail if in default state,
_ ~/ 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
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
I am guessing the reason for that is none of the packages which nginx
needs to be is installed.
$ apt-file search /usr/sbin/nginx
nginx-extras: /usr/sbin/nginx
nginx-full: /usr/sbin/nginx
nginx-light: /usr/sbin/nginx
I had a look at all the packages which are broken, the few which are
broken are those which depend on network-manager and my system is good
enough with dhcp. This shouldn't affect anything on nginx, at least
the depends don't show network-manager anywhere.
$ ps aux | grep dhcp
root 635 0.0 0.0 25388 136 ?Ss 13:39 0:00
dhclient -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
root 717 0.0 0.0 2538816 ?Ss 13:39 0:00
dhclient -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
root 769 0.0 0.0 25388 204 ?Ss 13:39 0:00
dhclient -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
shirish 6542 0.0 0.1 12724 2156 pts/2S+ 13:57 0:00 grep
--color=auto dhcp
Just showing the depends which nginx-full shows.
Depends: nginx-common (= 1.6.2-5), libc6 (= 2.14), libexpat1 (=
2.0.1), libgd3 (= 2.1.0~alpha~), libgeoip1, libpam0g (= 0.99.7.1),
libpcre3 (= 8.35), libssl1.0.0 (= 1.0.1), libxml2 (= 2.7.4),
libxslt1.1 (= 1.1.25), zlib1g (= 1:1.2.0)
--
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
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
Hi all, First of all thank you Norbert Fischer and Kartik for jumping on this quickly. For some reason I am not subscribed to the bug even though I reported this, hence have tried to subscribe to it let's see what happens. I had a look at the questions asked :- a. Have you made an aptitude update and aptitude safe-upgrade with non-CD sources before trying to install nginx? Ans. This is actually a wheezy install which was updated to jessie about a year back or so. So, in answer to your question, yes have done multiple rounds of aptitude update and aptitude safe-upgrade and do it whenever I have free time. This is a mixed system with majority of packages from testing, a few from sid or experimental (browsers mainly). b. Also, are there any broken packages on your system? You can try detecting and fixing those by issuing: aptitude -f install. Ans. - I would try this but shouldn't aptitude say that at the end as well. I am in the middle of a big update (kernel binaries, grub and few other other things) so will try that at the end. Although I do remember aptitude telling if something is off at the very end, as of the last aptitude run it showed me the following at the very end :- Current status: 42 updates [-40]. AFAIK this does conclude that there are no broken packages, but as have shared above will still try to run it after the end of the aptitude run to see explicitly if there are any broken packages. c. Have you already started another web server which has been bound to TCP port 80? You should stop any of those services beforehand. Bound ports can be seen by issuing sudo netstat -ntlp which also gives you the name of the service. Ans - I was running apache but had purged it as well as got rid of all the configuration files I could find in accordance to that. I ran sudo netstat -ntlp but unfortunately I didn't find either apache/httpd or anything else that was bound to port 80 :( d. Are there any related entries in /var/log/nginx/error.log? If the start script for nginx fails, there's probably some information in the error.log. Ans - There was nothing in error.log but did see some errors in error.log.1 :- /var/log/nginx# cat error.log.1 2015/03/05 14:56:39 [emerg] 24761#0: socket() [::]:80 failed (97: Address family not supported by protocol) 2015/03/05 14:56:46 [emerg] 25074#0: socket() [::]:80 failed (97: Address family not supported by protocol) umm could it be because I am using ipv4 and not ipv6 (My ISP has not moved to IPv6 and guess it will be a long time before they do.) Other than that, see no reason for the above error logs. e. Checking /var/log/syslog and /var/log/messages could give helpful messages as well. Ans. - I found the same errors in /var/log/syslog as well :- $ sudo zcat /var/log/syslog.2.gz | grep 'nginx' Mar 5 14:48:33 debian nginx[19817]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) Mar 5 14:48:33 debian nginx[19817]: nginx: configuration file /etc/nginx/nginx.conf test failed Mar 5 14:48:40 debian nginx[20214]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) Mar 5 14:48:40 debian nginx[20214]: nginx: configuration file /etc/nginx/nginx.conf test failed Mar 5 14:56:39 debian nginx[24761]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) Mar 5 14:56:39 debian nginx[24761]: nginx: configuration file /etc/nginx/nginx.conf test failed Mar 5 14:56:46 debian nginx[25074]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) Mar 5 14:56:46 debian nginx[25074]: nginx: configuration file /etc/nginx/nginx.conf test failed I grepped through all of /var/log/messages but didn't file anything useful. AFA /etc/nginx/nginx.conf test failure is concerned, I haven't changed anything at that file, it's in the default state. Please let me know if any more info. is needed. -- 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 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779825: no port attached to webserver
On Mon, Mar 9, 2015 at 12:08 PM, shirish शिरीष shirisha...@gmail.com wrote:
AFA /etc/nginx/nginx.conf test failure is concerned, I haven't changed
anything at that file, it's in the default state.
It should not fail if in default state,
_ ~/ 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
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
