search

openwrt / packages

Community maintained packages for OpenWrt. Documentation for submitting pull requests is in CONTRIBUTING.md
GNU General Public License v2.0
3.98k stars 3.47k forks source link

502 Bad Gateway of nginx #10235

Closed panda-mute closed 5 years ago

panda-mute commented 5 years ago

Maintainer: @Ansuel Environment: (mvebu, OpenWrt latest master version with nginx/uwsgi/cgi-io fix)

Description:

Mon Oct 14 15:06:38 2019 daemon.info uwsgi-emperor: workers have been inactive for more than 360 seconds (1571036798-1571036437)
Mon Oct 14 15:06:38 2019 daemon.info uwsgi-emperor: Mon Oct 14 15:06:38 2019 - [emperor] bringing back instance /etc/uwsgi/vassals/luci-webui.ini to on-demand mode
Mon Oct 14 15:06:38 2019 daemon.info uwsgi-emperor: Mon Oct 14 15:06:38 2019 - received message 0 from emperor
Mon Oct 14 15:06:38 2019 daemon.info uwsgi-emperor: SIGINT/SIGQUIT received...killing workers...
Mon Oct 14 15:06:38 2019 daemon.info uwsgi-emperor: Mon Oct 14 15:06:38 2019 - [emperor] curse the uwsgi instance /etc/uwsgi/vassals/luci-webui.ini (pid: 19560)
Mon Oct 14 15:06:39 2019 daemon.info uwsgi-emperor: worker 1 buried after 1 seconds
Mon Oct 14 15:06:39 2019 daemon.info uwsgi-emperor: goodbye to uWSGI.
Mon Oct 14 15:06:39 2019 daemon.info uwsgi-emperor: VACUUM: unix socket /var/run/luci-webui.socket removed.
Mon Oct 14 15:06:39 2019 daemon.info uwsgi-emperor: unlink(): No such file or directory [core/uwsgi.c line 1660]
Mon Oct 14 15:06:40 2019 daemon.info uwsgi-emperor: [uwsgi-emperor] /etc/uwsgi/vassals/luci-webui.ini -> back to "on demand" mode, waiting for connections on socket "/var/run//luci-webui.socket" ...

Then surf the router web page, report 502 Bad Gateway

root@OpenWrt:~# ls /var/run/*socket /var/run/luci-cgi_io.socket

Ansuel commented 5 years ago

Post your nginx.conf

Is the firmware from latest commit?

Il Lun 14 Ott 2019, 09:25 panda-mute notifications@github.com ha scritto:

Maintainer: @Ansuel https://github.com/Ansuel Environment: (mvebu, OpenWrt latest master version with nginx/uwsgi/cgi-io fix)

Description:

Mon Oct 14 15:06:38 2019 daemon.info uwsgi-emperor: workers have been inactive for more than 360 seconds (1571036798-1571036437) Mon Oct 14 15:06:38 2019 daemon.info uwsgi-emperor: Mon Oct 14 15:06:38 2019 - [emperor] bringing back instance /etc/uwsgi/vassals/luci-webui.ini to on-demand mode Mon Oct 14 15:06:38 2019 daemon.info uwsgi-emperor: Mon Oct 14 15:06:38 2019 - received message 0 from emperor Mon Oct 14 15:06:38 2019 daemon.info uwsgi-emperor: SIGINT/SIGQUIT received...killing workers... Mon Oct 14 15:06:38 2019 daemon.info uwsgi-emperor: Mon Oct 14 15:06:38 2019 - [emperor] curse the uwsgi instance /etc/uwsgi/vassals/luci-webui.ini (pid: 19560) Mon Oct 14 15:06:39 2019 daemon.info uwsgi-emperor: worker 1 buried after 1 seconds Mon Oct 14 15:06:39 2019 daemon.info uwsgi-emperor: goodbye to uWSGI. Mon Oct 14 15:06:39 2019 daemon.info uwsgi-emperor: VACUUM: unix socket /var/run/luci-webui.socket removed. Mon Oct 14 15:06:39 2019 daemon.info uwsgi-emperor: unlink(): No such file or directory [core/uwsgi.c line 1660] Mon Oct 14 15:06:40 2019 daemon.info uwsgi-emperor: [uwsgi-emperor] /etc/uwsgi/vassals/luci-webui.ini -> back to "on demand" mode, waiting for connections on socket "/var/run//luci-webui.socket" ...

Then surf the router web page, report 502 Bad Gateway

root@OpenWrt:~# ls /var/run/*socket /var/run/luci-cgi_io.socket

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openwrt/packages/issues/10235?email_source=notifications&email_token=AE2ZMQX4JQS53COBY3LYIWTQOQNGTA5CNFSM4JALQP72YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HRQMILA, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE2ZMQVDVG552SEWLEX4SZDQOQNGTANCNFSM4JALQP7Q .

panda-mute commented 5 years ago

@Ansuel Yes, it is the latest commit.

root@OpenWrt:~# cat /etc/nginx/nginx.conf

user nobody nogroup; worker_processes 2;

error_log logs/error.log;

error_log logs/error.log notice;

error_log logs/error.log info;

pid /var/run/nginx.pid;

events { worker_connections 1024; }

http { include mime.types; default_type application/octet-stream;

sendfile on;
keepalive_timeout 0;

client_body_buffer_size 10K;
client_header_buffer_size 1k;
client_max_body_size 1G;
large_client_header_buffers 2 1k;

gzip on;
gzip_http_version 1.1;
gzip_vary on;
gzip_comp_level 1;
gzip_proxied any;
gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript application/javascript image/svg+xml;

root /www;

server {
    listen 80 default_server;
    listen [::]:80 default_server;
    server_name  localhost;
    include ariang.conf;

    location ~* .(jpg|jpeg|png|gif|ico|css|js)$ {
        expires 365d;
    }

    include luci_uwsgi.conf;

}

include /etc/nginx/conf.d/*.conf;

}

Ansuel commented 5 years ago

What about the other questions?

Il Lun 14 Ott 2019, 14:57 panda-mute notifications@github.com ha scritto:

''' root@OpenWrt:~# cat /etc/nginx/nginx.conf

user nobody nogroup; worker_processes 2;

error_log logs/error.log;

error_log logs/error.log notice;

error_log logs/error.log info;

pid /var/run/nginx.pid;

events { worker_connections 1024; }

http { include mime.types; default_type application/octet-stream;

sendfile on; keepalive_timeout 0;

client_body_buffer_size 10K; client_header_buffer_size 1k; client_max_body_size 1G; large_client_header_buffers 2 1k;

gzip on; gzip_http_version 1.1; gzip_vary on; gzip_comp_level 1; gzip_proxied any; gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript application/javascript image/svg+xml;

root /www;

server { listen 80 default_server; listen [::]:80 default_server; server_name localhost; include ariang.conf;

location ~* .(jpg|jpeg|png|gif|ico|css|js)$ {
    expires 365d;
}

include luci_uwsgi.conf;

}

include /etc/nginx/conf.d/*.conf;

}

'''

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openwrt/packages/issues/10235?email_source=notifications&email_token=AE2ZMQQICGHBZB6EJMDIYV3QORUDJA5CNFSM4JALQP72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBERTIQ#issuecomment-541661602, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE2ZMQQQJYTN2A46LU5GDM3QORUDJANCNFSM4JALQP7Q .

panda-mute commented 5 years ago

It is the commit.

commit aeb198bb82252e937a122edb2ce47b56a28be7e2 Author: Nikos Mavrogiannopoulos n.mavrogiannopoulos@gmail.com Date: Sun Oct 13 08:06:10 2019 +0200

Merge pull request #10208 from dengqf6/oc

openconnect: update to 8.05
Ansuel commented 5 years ago

As I thought your latest is not latest ahahah Just update the firmware / package Master to that commit lack of a crucial change to nginx (included in later commit)

Il Lun 14 Ott 2019, 15:14 panda-mute notifications@github.com ha scritto:

It is the commit.

commit aeb198b https://github.com/openwrt/packages/commit/aeb198bb82252e937a122edb2ce47b56a28be7e2 Author: Nikos Mavrogiannopoulos n.mavrogiannopoulos@gmail.com Date: Sun Oct 13 08:06:10 2019 +0200

Merge pull request #10208 from dengqf6/oc

openconnect: update to 8.05

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openwrt/packages/issues/10235?email_source=notifications&email_token=AE2ZMQUDQY5C7V5M4PZIQGTQORWCXA5CNFSM4JALQP72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBETYPQ#issuecomment-541670462, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE2ZMQQIWGIJUW6VKF3QSATQORWCXANCNFSM4JALQP7Q .

panda-mute commented 5 years ago

Yestoday, I update all the firmware/package. So I think it include all your fix about nginx/uwsgi/cgi-io, please help to check

Ansuel commented 5 years ago

Again if you build your firmware just update your repo...

Anyway this is missing

https://git.openwrt.org/?p=feed/packages.git;a=commit;h=b9c7a570a2342c65ad049e4e77e038b3f8f3b90a

that got merged AFTER commit that updates openconnect

Il Lun 14 Ott 2019, 15:18 panda-mute notifications@github.com ha scritto:

I think it include all your fix about nginx/uwsgi/cgi-io, please help to check

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openwrt/packages/issues/10235?email_source=notifications&email_token=AE2ZMQW2WRFRJ6CHGBRA74TQORWSXA5CNFSM4JALQP72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBEUKKA#issuecomment-541672744, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE2ZMQWAFIE3JQF5V3BIKD3QORWSXANCNFSM4JALQP7Q .

panda-mute commented 5 years ago

@Ansuel

xw@xw-ubuntu:~/workspace/github/openwrt-master/package$ cat feeds/packages/nginx/files-luci-support/luci_uwsgi.conf location /cgi-bin/luci { index index.html; include uwsgi_params; uwsgi_param SERVER_ADDR $server_addr; uwsgi_modifier1 9; uwsgi_pass unix:////var/run/luci-webui.socket; } location ~ /cgi-bin/cgi-(backup|download|upload) { include uwsgi_params; uwsgi_param SERVER_ADDR $server_addr; uwsgi_modifier1 9; uwsgi_pass unix:////var/run/luci-cgi_io.socket; }

location /luci-static { }

panda-mute commented 5 years ago

This bug is when idle timeout, the /var/run/luci-webui.socket been removed

Ansuel commented 5 years ago

So a uwsgi restart fix it? I'm using it from 2 days and never experienced this problem

Il Lun 14 Ott 2019, 15:50 panda-mute notifications@github.com ha scritto:

This bug is when idle timeout, the /var/run/luci-webui.socket been removed

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openwrt/packages/issues/10235?email_source=notifications&email_token=AE2ZMQWWW2UHSV5GFIXSGQ3QOR2KJA5CNFSM4JALQP72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBEYM5Y#issuecomment-541689463, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE2ZMQRQXEZEZ4PU6NLBQ6TQOR2KJANCNFSM4JALQP7Q .

panda-mute commented 5 years ago

yes, you are right, restart uwsgi
make it work again.

panda-mute commented 5 years ago

Can you check the log I pasted, do you have same log of socket remove releated?

leonardpitzu commented 5 years ago

Sort of the same happens to me but I do not see the socket removed in the log. Restarting uwsgi brings everything back online for a while. I am on openwrt master running on mvebu

edit: i see the same error after all Tue Oct 15 07:33:00 2019 daemon.info uwsgi-emperor: workers have been inactive for more than 360 seconds (1571113980-1571113619) Tue Oct 15 07:33:00 2019 daemon.info uwsgi-emperor: Tue Oct 15 07:33:00 2019 - [emperor] bringing back instance /etc/uwsgi/vassals/luci-webui.ini to on-demand mode Tue Oct 15 07:33:00 2019 daemon.info uwsgi-emperor: Tue Oct 15 07:33:00 2019 - received message 0 from emperor Tue Oct 15 07:33:00 2019 daemon.info uwsgi-emperor: SIGINT/SIGQUIT received...killing workers... Tue Oct 15 07:33:00 2019 daemon.info uwsgi-emperor: Tue Oct 15 07:33:00 2019 - [emperor] curse the uwsgi instance /etc/uwsgi/vassals/luci-webui.ini (pid: 1036) Tue Oct 15 07:33:01 2019 daemon.info uwsgi-emperor: worker 1 buried after 1 seconds Tue Oct 15 07:33:01 2019 daemon.info uwsgi-emperor: goodbye to uWSGI. Tue Oct 15 07:33:01 2019 daemon.info uwsgi-emperor: VACUUM: unix socket /var/run/luci-webui.socket removed. Tue Oct 15 07:33:01 2019 daemon.info uwsgi-emperor: unlink(): No such file or directory [core/uwsgi.c line 1660] Tue Oct 15 07:33:02 2019 daemon.info uwsgi-emperor: [uwsgi-emperor] /etc/uwsgi/vassals/luci-webui.ini -> back to "on demand" mode, waiting for connections on socket "/var/run//luci-webui.socket" ...

Ansuel commented 5 years ago

@peter-stadler any hint on this?

peter-stadler commented 5 years ago

I cannot test it right now, try removing the vacuum line in the uwsgi configurations /etc/uwsgi/vassals/* (For testing it, a smaller timeout could be useful, too. Reset it to a higher value after debugging)

leonardpitzu commented 5 years ago

@peter-stadler same thing, it does not fix it

peter-stadler commented 5 years ago

Reading https://uwsgi-docs.readthedocs.io/en/latest/OnDemandVassals.html I saw that the vassals config should not set the socket. Try to remove that (socket = ... in the /etc/uwsgi/vassals/*). @Ansuel: If that works, a cleaner solution would be if the emperor removes the socket option of the vassals that are activated by socket. I don't know if this is possible.

peter-stadler commented 5 years ago

A possible problem could be that the socket is not chmod (see ls -al /var/run/*.socket). And we cannot use the vacuum, can we?

peter-stadler commented 5 years ago

If it is not working, is the uwsgi log changing? You could enable more verbose logging by uncommenting the logger = syslog:uwsgi-luci line in /etc/uwsgi/vassals/luci-webui.ini, too ...

Ansuel commented 5 years ago

Consider that we must keep the socket or we can't call the app to be started...

Il Mar 15 Ott 2019, 17:01 peter-stadler notifications@github.com ha scritto:

If it is not working, is the uwsgi log changing? You could enable more verbose logging by uncommenting the logger = syslog:uwsgi-luci line in /etc/uwsgi/vassals/luci-webui.ini, too ...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openwrt/packages/issues/10235?email_source=notifications&email_token=AE2ZMQRNFT5ANF7H25WESS3QOXLONA5CNFSM4JALQP72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBJDBQI#issuecomment-542257345, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE2ZMQQ74I75Y5VFX5UHR2LQOXLONANCNFSM4JALQP7Q .

peter-stadler commented 5 years ago

Yes we have to keep the socket, but it must not be created by the vassals (that is how I understand the OnDemandVassals docs). To make the ini files useable with and without emperor some if statement could be useful ...

Ansuel commented 5 years ago

Think the problem here is vassal socket and vacuum

Il Mar 15 Ott 2019, 17:17 peter-stadler notifications@github.com ha scritto:

Yes we have to keep the socket, but it must not be created by the vassals (that is how I understand the OnDemandVassals docs). To make the ini files useable with and without emperor some if statement https://uwsgi-docs.readthedocs.io/en/latest/ConfigLogic.html could be useful ...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openwrt/packages/issues/10235?email_source=notifications&email_token=AE2ZMQVH4BYTBCMY5SMZKRLQOXNIHA5CNFSM4JALQP72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBJE3XQ#issuecomment-542264798, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE2ZMQSWNEMKTLDAS6DFKSDQOXNIHANCNFSM4JALQP7Q .

panda-mute commented 5 years ago

@Ansuel @peter-stadler

Refer to https://stackoverflow.com/questions/45437713/uwsgi-not-restarting-after-being-idle

I try to remove the socket option in /etc/uwsgi/vassals/luci-webui.ini

root@OpenWrt:~# cat /etc/uwsgi/vassals/luci-webui.ini 
[uwsgi]
strict = true
#socket = /var/run/luci-webui.socket
cgi-mode = true
cgi = /www/
chdir = /usr/lib/lua/luci/
buffer-size = 10000
reload-mercy = 8
max-requests = 2000
limit-as = 200
reload-on-as = 256
reload-on-rss = 192
no-orphans = true
vacuum = true
enable-threads = true
post-buffering = 8192
socket-timeout = 120
thunder-lock = true
logger = syslog:uwsgi-luci
disable-logging = true
log-format = %(addr) %(method) %(uri) => generated %(rsize) bytes in %(msecs) msecs
threads = 3
processes = 3
chmod-socket = 666
cheap = true
cheaper-algo = spare
cheaper = 1
cheaper-initial = 2
cheaper-step = 1
master = true

After change this, it seems work well now.

Wed Oct 16 12:35:46 2019 daemon.info uwsgi-luci: workers have been inactive for more than 360 seconds (1571200546-1571200185)
Wed Oct 16 12:35:46 2019 daemon.info uwsgi-emperor: Wed Oct 16 12:35:46 2019 - [emperor] bringing back instance /etc/uwsgi/vassals/luci-webui.ini to on-demand mode
Wed Oct 16 12:35:46 2019 daemon.info uwsgi-luci: Wed Oct 16 12:35:46 2019 - received message 0 from emperor
Wed Oct 16 12:35:46 2019 daemon.info uwsgi-luci: SIGINT/SIGQUIT received...killing workers...
Wed Oct 16 12:35:46 2019 daemon.info uwsgi-emperor: Wed Oct 16 12:35:46 2019 - [emperor] curse the uwsgi instance /etc/uwsgi/vassals/luci-webui.ini (pid: 14261)
Wed Oct 16 12:35:47 2019 daemon.info uwsgi-luci: worker 1 buried after 1 seconds
Wed Oct 16 12:35:47 2019 daemon.info uwsgi-luci: goodbye to uWSGI.
Wed Oct 16 12:35:47 2019 daemon.info uwsgi-luci: VACUUM WARNING: unix socket /var/run//luci-webui.socket changed inode. Skip removal
Wed Oct 16 12:35:48 2019 daemon.info uwsgi-emperor: [uwsgi-emperor] /etc/uwsgi/vassals/luci-webui.ini -> back to "on demand" mode, waiting for connections on socket "/var/run//luci-webui.socket" ...
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-emperor: *** has_emperor mode detected (fd: 10) ***
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-emperor: [uWSGI] getting INI configuration from /etc/uwsgi/vassals/luci-webui.ini
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-emperor: Wed Oct 16 12:38:51 2019 - [emperor] vassal /etc/uwsgi/vassals/luci-webui.ini has been spawned
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: *** Starting uWSGI 2.0.18 (32bit) on [Wed Oct 16 12:38:51 2019] ***
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: compiled with version: 7.4.0 on 13 October 2019 08:57:26
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: os: Linux-4.19.78 #0 SMP Sun Oct 13 08:57:26 2019
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-emperor: Wed Oct 16 12:38:51 2019 - [emperor] vassal /etc/uwsgi/vassals/luci-webui.ini is ready to accept requests
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: nodename: OpenWrt
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: machine: armv7l
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: clock source: unix
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: detected number of CPU cores: 2
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: current working directory: /
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: detected binary path: /usr/sbin/uwsgi
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: !!! no internal routing support, rebuild with pcre support !!!
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: uWSGI running as root, you can use --uid/--gid/--chroot options
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: chdir() to /usr/lib/lua/luci/
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: your processes number limit is 3983
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: limiting address space of processes...
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: your process address space limit is 209715200 bytes (200 MB)
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: your memory page size is 4096 bytes
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: detected max file descriptor number: 1024
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: lock engine: pthread robust mutexes
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: thunder lock: enabled
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: uwsgi socket 0 inherited UNIX address /var/run//luci-webui.socket fd 0
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: uWSGI running as root, you can use --uid/--gid/--chroot options
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: uWSGI running as root, you can use --uid/--gid/--chroot options
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: your server socket listen backlog is limited to 100 connections
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: your mercy for graceful operations on workers is 60 seconds
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: mapped 487200 bytes (475 KB) for 9 cores
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: *** Operational MODE: preforking+threaded ***
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: initialized CGI path: /www/
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: *** no app loaded. going in full dynamic mode ***
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: uWSGI running as root, you can use --uid/--gid/--chroot options
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: *** uWSGI is running in multiple interpreter mode ***
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: spawned uWSGI master process (pid: 17774)
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: cheap mode enabled: waiting for socket connection...
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: spawned uWSGI worker 1 (pid: 17775, cores: 3)
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-luci: announcing my loyalty to the Emperor...
Wed Oct 16 12:38:51 2019 daemon.info uwsgi-emperor: Wed Oct 16 12:38:51 2019 - [emperor] vassal /etc/uwsgi/vassals/luci-webui.ini is now loyal
Wed Oct 16 12:38:53 2019 daemon.info uwsgi-luci: luci: accepted login on / for root from 10.8.0.2
Wed Oct 16 12:45:12 2019 daemon.info uwsgi-luci: workers have been inactive for more than 360 seconds (1571201112-1571200751)
Wed Oct 16 12:45:12 2019 daemon.info uwsgi-emperor: Wed Oct 16 12:45:12 2019 - [emperor] bringing back instance /etc/uwsgi/vassals/luci-webui.ini to on-demand mode
Wed Oct 16 12:45:12 2019 daemon.info uwsgi-luci: Wed Oct 16 12:45:12 2019 - received message 0 from emperor
Wed Oct 16 12:45:12 2019 daemon.info uwsgi-luci: SIGINT/SIGQUIT received...killing workers...
Wed Oct 16 12:45:12 2019 daemon.info uwsgi-emperor: Wed Oct 16 12:45:12 2019 - [emperor] curse the uwsgi instance /etc/uwsgi/vassals/luci-webui.ini (pid: 17774)
Wed Oct 16 12:45:13 2019 daemon.info uwsgi-luci: worker 1 buried after 1 seconds
Wed Oct 16 12:45:13 2019 daemon.info uwsgi-luci: goodbye to uWSGI.
Wed Oct 16 12:45:13 2019 daemon.info uwsgi-luci: VACUUM WARNING: unix socket /var/run//luci-webui.socket changed inode. Skip removal
Wed Oct 16 12:45:14 2019 daemon.info uwsgi-emperor: [uwsgi-emperor] /etc/uwsgi/vassals/luci-webui.ini -> back to "on demand" mode, waiting for connections on socket "/var/run//luci-webui.socket" ...
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-emperor: *** has_emperor mode detected (fd: 10) ***
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-emperor: [uWSGI] getting INI configuration from /etc/uwsgi/vassals/luci-webui.ini
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: *** Starting uWSGI 2.0.18 (32bit) on [Wed Oct 16 12:47:04 2019] ***
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-emperor: Wed Oct 16 12:47:04 2019 - [emperor] vassal /etc/uwsgi/vassals/luci-webui.ini has been spawned
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: compiled with version: 7.4.0 on 13 October 2019 08:57:26
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: os: Linux-4.19.78 #0 SMP Sun Oct 13 08:57:26 2019
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: nodename: OpenWrt
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: machine: armv7l
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: clock source: unix
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: detected number of CPU cores: 2
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: current working directory: /
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: detected binary path: /usr/sbin/uwsgi
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: !!! no internal routing support, rebuild with pcre support !!!
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: uWSGI running as root, you can use --uid/--gid/--chroot options
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: chdir() to /usr/lib/lua/luci/
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: your processes number limit is 3983
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: limiting address space of processes...
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: your process address space limit is 209715200 bytes (200 MB)
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: your memory page size is 4096 bytes
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: detected max file descriptor number: 1024
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: lock engine: pthread robust mutexes
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: thunder lock: enabled
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: uwsgi socket 0 inherited UNIX address /var/run//luci-webui.socket fd 0
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: uWSGI running as root, you can use --uid/--gid/--chroot options
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: uWSGI running as root, you can use --uid/--gid/--chroot options
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: your server socket listen backlog is limited to 100 connections
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: your mercy for graceful operations on workers is 60 seconds
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: mapped 487200 bytes (475 KB) for 9 cores
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: *** Operational MODE: preforking+threaded ***
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: initialized CGI path: /www/
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: *** no app loaded. going in full dynamic mode ***
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: uWSGI running as root, you can use --uid/--gid/--chroot options
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: *** uWSGI is running in multiple interpreter mode ***
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: spawned uWSGI master process (pid: 21257)
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: cheap mode enabled: waiting for socket connection...
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: spawned uWSGI worker 1 (pid: 21258, cores: 3)
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-emperor: Wed Oct 16 12:47:04 2019 - [emperor] vassal /etc/uwsgi/vassals/luci-webui.ini is ready to accept requests
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-luci: announcing my loyalty to the Emperor...
Wed Oct 16 12:47:04 2019 daemon.info uwsgi-emperor: Wed Oct 16 12:47:04 2019 - [emperor] vassal /etc/uwsgi/vassals/luci-webui.ini is now loyal
leonardpitzu commented 5 years ago

i managed only now to get my hand on a computer removing the socket from the vassals solves the issue