I couldn't get nginx running until I was able to stop and disable the pywwetha service. From what I see it is something related to the siduction installation and documentation.
I couldn't find with with netstat as it simply appeared as init. It was systemctl list-sockets which helped someone help me identify it and disable it.
Isn't it better to set it to run on a different less used port?
If you would be a long term user i would use swear words - but as you are a newbie i only like to give an important advise:
Please consider that *:80 is fucking bullshit and you really don't want nginx listen to all local ipadresses:80 and the random:80 - thank you in advance :) - it's btw the same bullshit as in apache and possible lighty - whoever think that *:80 is a good default should never be allowed to write a default configuration again :D
nginx/sites-available/default: listen 80 default_server;
nginx/sites-available/default: listen [::]:80 default_server;
nginx/sites-available/default:# listen 80;
nginx/sites-available/default:# listen [::]:80;
and of course
$ ls /etc/nginx/sites-enabled/ -lia
insgesamt 8
2900008 drwxr-xr-x 2 root root 4096 Nov 8 02:54 .
2897154 drwxr-xr-x 6 root root 4096 Nov 8 02:54 ..
2895811 lrwxrwxrwx 1 root root 34 Nov 8 02:54 default -> /etc/nginx/sites-available/default
really nice, isn't it - i would suggest to bind default to 127.0.0.1:80 and [::1]:80 - solved and btw - pywwetha is bound to 127.0.0.86 ff i guess - so it should not disturb any normal configured webserver 8)
As I mentioned earlier my problem was being unable to discover what has listening on port 80 with the tools I am familiar with, netstat and lsof . Only a query on stackexchange helped.
http://unix.stackexchange.com/questions/241444/why-is-init-listening-on-port-80
Quote from: melmarker on 2015/11/08, 03:00:04
If you would be a long term user i would use swear words - but as you are a newbie i only like to give an important advise:
Please consider that *:80 is fucking bullshit and you really don't want nginx listen to all local ipadresses:80 and the random:80 - thank you in advance :) - it's btw the same bullshit as in apache and possible lighty - whoever think that *:80 is a good default should never be allowed to write a default configuration again :D
nginx/sites-available/default: listen 80 default_server;
nginx/sites-available/default: listen [::]:80 default_server;
nginx/sites-available/default:# listen 80;
nginx/sites-available/default:# listen [::]:80;
and of course
$ ls /etc/nginx/sites-enabled/ -lia
insgesamt 8
2900008 drwxr-xr-x 2 root root 4096 Nov 8 02:54 .
2897154 drwxr-xr-x 6 root root 4096 Nov 8 02:54 ..
2895811 lrwxrwxrwx 1 root root 34 Nov 8 02:54 default -> /etc/nginx/sites-available/default
really nice, isn't it - i would suggest to bind default to 127.0.0.1:80 and [::1]:80 - solved and btw - pywwetha is bound to 127.0.0.86 ff i guess - so it should not disturb any normal configured webserver 8)
$ sudo netstat -tulpen | grep :80
tcp 0 0 127.0.0.86:80 0.0.0.0:* LISTEN 0 1268706 18549/python
$ ps -faux | grep 18549
agaida 9605 0.0 0.0 16924 2256 pts/0 S+ 14:29 0:00 \_ grep --color=auto 18549
www-data 18549 0.0 0.0 59268 15884 ? Ss 14:12 0:00 /usr/bin/python /usr/share/pywwetha/source/pywwetha.py
$ apt-file search /usr/share/pywwetha/source/pywwetha.py
pywwetha: /usr/share/pywwetha/source/pywwetha.py
$ LANG=C aptitude show pywwetha
Package: pywwetha
State: installed
Automatically installed: no
Version: 2015.10.08
Priority: optional
Section: httpd
Maintainer: J. Hamatoma <hama@siduction.net>
Architecture: all
Uncompressed Size: 87.0 k
Depends: init-system-helpers (>= 1.18~), python, python-support, sudo
PreDepends: sidu-base (>= 2014.04.11)
Description: simple webserver for static html, CGI and WSGI.
This webserver can issue static files and CGI created pages. Main usage: Building dynamic pages for life CDs or local usage. pywwetha
can handle WSGI and Django applications. In addition pywwetha contains Djinn, a very little WSGI middleware which can replace Django
in some cases.
Homepage: http://siduction.org
$ apt-cache rdepends pywwetha
pywwetha
Reverse Depends:
sidu-manual
sidu-installer
sidu-base
sidu-base
sidu-installer2
hello vonh,
you are right. siduction comes with a tiny webserver which serves the offline manual and the installer.
So the siduction default configuration purposely breaks the debian packages apache2 and nginx
and renders every tutorial for those debian packages useless.
One example is our own manual: http://manual.siduction.org/lamp-apache (http://manual.siduction.org/lamp-apache)
I admit this is ugly for beginners and i consider this behaviour a bug in pywwetha (http://bugs.siduction.org/issues/1800).
The situation gets worse when simple questions get rude answers by the siduction devs.
Fact is: We break debian defaults and we yell at users questioning it. It happens every single time.
greetings
musca
@musca: we break the most stupid defaults ever made in debian - and we decided not to use the normal 127.0.0.1 and ::1 - so the most tutorials out there should not be broken by us. We discussed this behaviour of pywwetha several times here in the forum, so a little bit of research ...
@vonh: the netstat manpage is very clear about root to geht process informations, esp. names
EDIT: And i can't say it in other words: The guy who had written the debian defaults for apache2, esp the *:80 part should never ever write defaults again - I'm struggle with this for several years now and it sucks more each year i have to deal with it.
wow, I can't believe it; I think I will migrate away from siduction after seeing this response.
That a dev would yell at a user because a simple apt-get install fails, rather than possibly the other way around is just incomprehensible.
That you consider the defaults poor is understandable; surely then siduction should fork the packages in question and correct the defaults. But to consider intentionally introducing breakage, and moreover give dismissive and annoyed responses when asked about this speaks volumes about the development practices here.
farewell - not to bad for a first post
Good luck with your migration, Guest.
melmarker may be blunt at times but his responses are always true, and he is a sweetheart compared to some posters I've seen on other distro forums.
Quote from: sunrat on 2016/03/28, 02:03:18
Good luck with your migration, Guest.
melmarker may be blunt at times but his responses are always true, and he is a sweetheart compared to some posters I've seen on other distro forums.
+1 to that, melmarker's humor can be rather offputting to those that aren't familiar with him.