SIGTERM failed to stop container

[inetol]

Version of SearXNG, commit number if you are using on master branch and stipulate if you forked SearXNG

2024.4.24+e0214412f

How did you install SearXNG?

Container (podman)

What happened?

When the SIGTERM signal is sent to the container, uWSGI restarts itself until the 10-second grace period has elapsed and the SIGKILL signal forcibly kills the container.

How To Reproduce

1. Start a simple SearXNG container (https://github.com/searxng/searxng-docker)
2. Stop the container

Expected behavior

Graceful exit

Screenshots & Logs

Apr 26 15:31:22 node1.ch-dc1.gw.inet.lan systemd[750]: Stopping searxng.service...
Apr 26 15:31:22 node1.ch-dc1.gw.inet.lan searxng[36709]: ...brutally killing workers...
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: worker 1 buried after 1 seconds
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: worker 2 buried after 1 seconds
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: binary reloading uWSGI...
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: chdir() to /usr/local/searxng
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: closing all non-uwsgi socket fds > 2 (max_fd = 524288)...
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: found fd 3 mapped to socket 0 (0.0.0.0:8080)
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: running /usr/sbin/uwsgi
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: [uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: [uwsgi-static] added mapping for /static => /usr/local/searxng/searx/static
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: *** Starting uWSGI 2.0.23 (64bit) on [Fri Apr 26 15:31:23 2024] ***
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: compiled with version: 13.2.1 20231014 on 30 November 2023 14:34:33
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: os: Linux-5.14.0-427.el9.aarch64 searxng/searxng#1 SMP PREEMPT_DYNAMIC Fri Feb 23 04:48:58 EST 2024
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: nodename: addd29c1dcbf
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: machine: aarch64
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: clock source: unix
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: pcre jit disabled
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: detected number of CPU cores: 8
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: current working directory: /usr/local/searxng
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: detected binary path: /usr/sbin/uwsgi
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: chdir() to /usr/local/searxng/searx/
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: your processes number limit is 95781
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: your memory page size is 4096 bytes
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: detected max file descriptor number: 524288
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: building mime-types dictionary from file /etc/mime.types...1390 entry found
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: lock engine: pthread robust mutexes
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: thunder lock: disabled (you can enable it with --thunder-lock)
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: uwsgi socket 0 inherited INET address 0.0.0.0:8080 fd 3
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: Python version: 3.11.8 (main, Feb 19 2024, 17:01:17) [GCC 13.2.1 20231014]
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: Python main interpreter initialized at 0xffffaad62600
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: python threads support enabled
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: your server socket listen backlog is limited to 100 connections
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: your mercy for graceful operations on workers is 60 seconds
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: mapped 274704 bytes (268 KB) for 4 cores
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: *** Operational MODE: preforking+threaded ***
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: added /usr/local/searxng/ to pythonpath.
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: gracefully (RE)spawned uWSGI master process (pid: 2)
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: spawned uWSGI worker 1 (pid: 31, cores: 2)
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: spawned uWSGI worker 2 (pid: 32, cores: 2)
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: spawned 4 offload threads for uWSGI worker 1
Apr 26 15:31:23 node1.ch-dc1.gw.inet.lan searxng[36709]: spawned 4 offload threads for uWSGI worker 2
Apr 26 15:31:24 node1.ch-dc1.gw.inet.lan searxng[36709]: 2024-04-26 15:31:24,022 WARNING:searx: Be aware you have activated features intended only for public instances. This force the usage of the limiter and link_token / see https://docs.searxng.org/admin/searx.limiter.html
Apr 26 15:31:24 node1.ch-dc1.gw.inet.lan searxng[36709]: 2024-04-26 15:31:24,022 WARNING:searx: Be aware you have activated features intended only for public instances. This force the usage of the limiter and link_token / see https://docs.searxng.org/admin/searx.limiter.html
Apr 26 15:31:24 node1.ch-dc1.gw.inet.lan searxng[36709]: WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0xffffaad62600 pid: 32 (default app)
Apr 26 15:31:24 node1.ch-dc1.gw.inet.lan searxng[36709]: WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0xffffaad62600 pid: 31 (default app)
Apr 26 15:31:32 node1.ch-dc1.gw.inet.lan searxng[36791]: time="2024-04-26T15:31:32Z" level=warning msg="StopSignal SIGTERM failed to stop container searxng in 10 seconds, resorting to SIGKILL"
Apr 26 15:31:32 node1.ch-dc1.gw.inet.lan podman[36791]: 2024-04-26 15:31:32.489590648 +0000 UTC m=+10.055846951 container died addd29c1dcbf4eb3e0ce02282aa7dd17c8a7bc186bafb65c61e3cd4ea00a091b
Apr 26 15:31:32 node1.ch-dc1.gw.inet.lan podman[36791]: 2024-04-26 15:31:32.672741567 +0000 UTC m=+10.238997830 container remove addd29c1dcbf4eb3e0ce02282aa7dd17c8a7bc186bafb65c61e3cd4ea00a091b
Apr 26 15:31:32 node1.ch-dc1.gw.inet.lan searxng[36791]: addd29c1dcbf4eb3e0ce02282aa7dd17c8a7bc186bafb65c61e3cd4ea00a091b
Apr 26 15:31:32 node1.ch-dc1.gw.inet.lan systemd[750]: searxng.service: Main process exited, code=exited, status=137/n/a
Apr 26 15:31:32 node1.ch-dc1.gw.inet.lan systemd[750]: searxng.service: Failed with result 'exit-code'.
Apr 26 15:31:32 node1.ch-dc1.gw.inet.lan systemd[750]: Stopped searxng.service.

[unixfox]

oops sorry for converting that to a github discussion...

[inetol]

Fixed in #3429