uwsgi (terminated by SIGKILL)
Komoro2023 opened this issue · comments
root@test-ubuntu:~/submission# docker logs submission
/usr/lib/python3/dist-packages/supervisor/options.py:474: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
self.warnings.warn(
2024-01-03 10:30:53,596 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2024-01-03 10:30:53,596 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2024-01-03 10:30:53,598 INFO RPC interface 'supervisor' initialized
2024-01-03 10:30:53,598 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-01-03 10:30:53,598 INFO supervisord started with pid 1
2024-01-03 10:30:54,600 INFO spawned: 'quit_on_failure' with pid 7
2024-01-03 10:30:54,602 INFO spawned: 'nginx' with pid 8
2024-01-03 10:30:54,603 INFO spawned: 'uwsgi' with pid 9
2024-01-03 10:30:54,604 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-01-03 10:30:54,604 INFO success: uwsgi entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024/01/03 10:30:54 [notice] 8#8: using the "epoll" event method
2024/01/03 10:30:54 [notice] 8#8: nginx/1.23.2
2024/01/03 10:30:54 [notice] 8#8: built by gcc 10.2.1 20210110 (Debian 10.2.1-6)
2024/01/03 10:30:54 [notice] 8#8: OS: Linux 4.15.0-176-generic
2024/01/03 10:30:54 [notice] 8#8: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2024/01/03 10:30:54 [notice] 10#10: start worker processes
2024/01/03 10:30:54 [notice] 10#10: start worker process 11
2024/01/03 10:30:54 [notice] 10#10: start worker process 12
2024-01-03 10:30:54,608 INFO exited: nginx (exit status 0; expected)
[uWSGI] getting INI configuration from /myapp/uwsgi.ini
[uWSGI] getting INI configuration from /etc/uwsgi/uwsgi.ini
;uWSGI instance configuration
[uwsgi]
cheaper = 2
ini = /myapp/uwsgi.ini
module = submission
callable = app
processes = 16
ini = /etc/uwsgi/uwsgi.ini
socket = /tmp/uwsgi.sock
chown-socket = nginx:nginx
chmod-socket = 664
hook-master-start = unix_signal:15 gracefully_kill_them_all
need-app = true
die-on-term = true
show-config = true
;end of configuration
*** Starting uWSGI 2.0.21 (64bit) on [Wed Jan 3 10:30:54 2024] ***
compiled with version: 10.2.1 20210110 on 25 November 2022 15:10:22
os: Linux-4.15.0-176-generic #185-Ubuntu SMP Tue Mar 29 17:40:04 UTC 2022
nodename: fd786c38bcd3
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 16
current working directory: /myapp
detected binary path: /usr/local/bin/uwsgi
your memory page size is 4096 bytes
detected max file descriptor number: 1048576
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /tmp/uwsgi.sock fd 3
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
Python version: 3.6.15 (default, Dec 21 2021, 12:03:22) [GCC 10.2.1 20210110]
*** Python threads support is disabled. You can enable it with --enable-threads ***
Python main interpreter initialized at 0x556ee4966840
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 1239640 bytes (1210 KB) for 16 cores
*** Operational MODE: preforking ***
WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x556ee4966840 pid: 9 (default app)
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 9)
spawned uWSGI worker 1 (pid: 28, cores: 1)
spawned uWSGI worker 2 (pid: 29, cores: 1)
running "unix_signal:15 gracefully_kill_them_all" (master-start)...
2024-01-03 10:30:56,370 INFO success: quit_on_failure entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-03 10:30:56,370 WARN received SIGTERM indicating exit request
2024-01-03 10:30:56,370 INFO waiting for quit_on_failure, uwsgi to die
Wed Jan 3 10:30:56 2024 - graceful shutdown triggered...
Gracefully killing worker 1 (pid: 28)...
Gracefully killing worker 2 (pid: 29)...
worker 1 buried after 1 seconds
worker 2 buried after 1 seconds
goodbye to uWSGI.
2024-01-03 10:30:58,377 INFO stopped: uwsgi (exit status 0)
2024-01-03 10:30:59,378 INFO waiting for quit_on_failure to die
2024-01-03 10:30:59,379 INFO stopped: quit_on_failure (terminated by SIGTERM)
/usr/lib/python3/dist-packages/supervisor/options.py:474: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
self.warnings.warn(
2024-01-03 10:41:21,400 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2024-01-03 10:41:21,401 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2024-01-03 10:41:21,417 INFO RPC interface 'supervisor' initialized
2024-01-03 10:41:21,417 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-01-03 10:41:21,417 INFO supervisord started with pid 1
2024-01-03 10:41:22,419 INFO spawned: 'quit_on_failure' with pid 7
2024-01-03 10:41:22,421 INFO spawned: 'nginx' with pid 8
2024-01-03 10:41:22,422 INFO spawned: 'uwsgi' with pid 9
2024-01-03 10:41:22,467 INFO success: nginx entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-01-03 10:41:22,467 INFO success: uwsgi entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024/01/03 10:41:22 [notice] 8#8: using the "epoll" event method
2024/01/03 10:41:22 [notice] 8#8: nginx/1.23.2
2024/01/03 10:41:22 [notice] 8#8: built by gcc 10.2.1 20210110 (Debian 10.2.1-6)
2024/01/03 10:41:22 [notice] 8#8: OS: Linux 4.15.0-213-generic
2024/01/03 10:41:22 [notice] 8#8: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2024/01/03 10:41:22 [notice] 10#10: start worker processes
2024/01/03 10:41:22 [notice] 10#10: start worker process 11
2024/01/03 10:41:22 [notice] 10#10: start worker process 12
2024/01/03 10:41:22 [notice] 10#10: start worker process 13
2024/01/03 10:41:22 [notice] 10#10: start worker process 14
2024/01/03 10:41:22 [notice] 10#10: start worker process 15
2024/01/03 10:41:22 [notice] 10#10: start worker process 16
2024/01/03 10:41:22 [notice] 10#10: start worker process 17
2024/01/03 10:41:22 [notice] 10#10: start worker process 18
2024/01/03 10:41:22 [notice] 10#10: start worker process 19
2024/01/03 10:41:22 [notice] 10#10: start worker process 20
2024/01/03 10:41:22 [notice] 10#10: start worker process 21
2024/01/03 10:41:22 [notice] 10#10: start worker process 22
2024/01/03 10:41:22 [notice] 10#10: start worker process 23
2024/01/03 10:41:22 [notice] 10#10: start worker process 24
2024/01/03 10:41:22 [notice] 10#10: start worker process 25
2024/01/03 10:41:22 [notice] 10#10: start worker process 26
[uWSGI] getting INI configuration from /myapp/uwsgi.ini
2024-01-03 10:41:22,643 INFO exited: nginx (exit status 0; expected)
[uWSGI] getting INI configuration from /etc/uwsgi/uwsgi.ini
;uWSGI instance configuration
[uwsgi]
cheaper = 2
ini = /myapp/uwsgi.ini
module = submission
callable = app
processes = 16
ini = /etc/uwsgi/uwsgi.ini
socket = /tmp/uwsgi.sock
chown-socket = nginx:nginx
chmod-socket = 664
hook-master-start = unix_signal:15 gracefully_kill_them_all
need-app = true
die-on-term = true
show-config = true
;end of configuration
*** Starting uWSGI 2.0.21 (64bit) on [Wed Jan 3 10:41:22 2024] ***
compiled with version: 10.2.1 20210110 on 25 November 2022 15:10:22
os: Linux-4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023
nodename: fd786c38bcd3
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 16
current working directory: /myapp
detected binary path: /usr/local/bin/uwsgi
your memory page size is 4096 bytes
detected max file descriptor number: 1048576
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /tmp/uwsgi.sock fd 3
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
Python version: 3.6.15 (default, Dec 21 2021, 12:03:22) [GCC 10.2.1 20210110]
*** Python threads support is disabled. You can enable it with --enable-threads ***
Python main interpreter initialized at 0x55674a1fc840
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 1239640 bytes (1210 KB) for 16 cores
*** Operational MODE: preforking ***
2024-01-03 10:41:23,749 INFO success: quit_on_failure entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-03 10:41:23,749 WARN received SIGTERM indicating exit request
2024-01-03 10:41:23,749 INFO waiting for quit_on_failure, uwsgi to die
WSGI app 0 (mountpoint='') ready in 3 seconds on interpreter 0x55674a1fc840 pid: 9 (default app)
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 9)
spawned uWSGI worker 1 (pid: 28, cores: 1)
spawned uWSGI worker 2 (pid: 29, cores: 1)
running "unix_signal:15 gracefully_kill_them_all" (master-start)...
2024-01-03 10:41:27,021 INFO waiting for quit_on_failure, uwsgi to die
2024-01-03 10:41:30,024 INFO waiting for quit_on_failure, uwsgi to die
2024-01-03 10:41:33,028 INFO waiting for quit_on_failure, uwsgi to die
2024-01-03 10:41:34,029 WARN killing 'uwsgi' (9) with SIGKILL
Wed Jan 3 10:41:34 2024 - uWSGI worker 2 screams: UAAAAAAH my master disconnected: i will kill myself !!!
Wed Jan 3 10:41:34 2024 - uWSGI worker 1 screams: UAAAAAAH my master disconnected: i will kill myself !!!
2024-01-03 10:41:34,031 INFO stopped: uwsgi (terminated by SIGKILL)
2024-01-03 10:41:34,032 INFO stopped: quit_on_failure (terminated by SIGTERM)