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
