Superset 4.11 hangs after a period of user inactivity

[manishtiwari-ie]

I have Superset 4.11 running on gunicorn on Debian. It runs fine while I have users accessing superset and working on the charts and dashboards. However if there is a period of inactivity, it stops responding after a period of time. The processes are running fine, there memory and CPU utilizations are also fine. There is nothing in the superset log. However I find the following messages in the gunicorn logs?

[2025-03-20 06:51:07 +0000] [3796523] [INFO] Worker exiting (pid: 3796523)
[2025-03-20 06:51:07 +0000] [3796524] [ERROR] Exception in worker process
Traceback (most recent call last):
File "/app/superset/venv/lib/python3.11/site-packages/gunicorn/arbiter.py", line 608, in spawn_worker
worker.init_process()
File "/app/superset/venv/lib/python3.11/site-packages/gunicorn/workers/gthread.py", line 94, in init_process
super().init_process()
File "/app/superset/venv/lib/python3.11/site-packages/gunicorn/workers/base.py", line 135, in init_process
self.load_wsgi()
File "/app/superset/venv/lib/python3.11/site-packages/gunicorn/workers/base.py", line 147, in load_wsgi
self.wsgi = self.app.wsgi()
^^^^^^^^^^^^^^^
File "/app/superset/venv/lib/python3.11/site-packages/gunicorn/app/base.py", line 66, in wsgi
self.callable = self.load()
^^^^^^^^^^^
File "/app/superset/venv/lib/python3.11/site-packages/gunicorn/app/wsgiapp.py", line 57, in load
return self.load_wsgiapp()
^^^^^^^^^^^^^^^^^^^
File "/app/superset/venv/lib/python3.11/site-packages/gunicorn/app/wsgiapp.py", line 47, in load_wsgiapp
return util.import_app(self.app_uri)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/superset/venv/lib/python3.11/site-packages/gunicorn/util.py", line 423, in import_app
app = app(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^
File "/app/superset/venv/lib/python3.11/site-packages/superset/app.py", line 37, in create_app
app.config.from_object(config_module)
File "/app/superset/venv/lib/python3.11/site-packages/flask/config.py", line 231, in from_object
obj = import_string(obj)
^^^^^^^^^^^^^^^^^^
File "/app/superset/venv/lib/python3.11/site-packages/werkzeug/utils.py", line 596, in import_string
import(import_name)
File "/app/superset/venv/lib/python3.11/site-packages/superset/config.py", line 1865, in
click.secho(f"Loaded your LOCAL configuration at [{cfg_path}]", fg="cyan")
File "/app/superset/venv/lib/python3.11/site-packages/click/termui.py", line 634, in secho
return echo(message, file=file, nl=nl, err=err, color=color)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/superset/venv/lib/python3.11/site-packages/click/utils.py", line 318, in echo
file.write(out) # type: ignore
^^^^^^^^^^^^^^^
OSError: [Errno 5] Input/output error
[2025-03-20 06:51:07 +0000] [3796524] [INFO] Worker exiting (pid: 3796524)
[2025-03-20 06:51:07 +0000] [3794265] [ERROR] Worker (pid:3796521) exited with code 120
[2025-03-20 06:51:07 +0000] [3794265] [ERROR] Worker (pid:3796521) exited with code 120.
[2025-03-20 06:51:07 +0000] [3796558] [INFO] Booting worker with pid: 3796558
[2025-03-20 06:51:08 +0000] [3794265] [ERROR] Worker (pid:3796522) exited with code 120
[2025-03-20 06:51:08 +0000] [3794265] [ERROR] Worker (pid:3796522) exited with code 120.
[2025-03-20 06:51:08 +0000] [3796559] [INFO] Booting worker with pid: 3796559
[2025-03-20 06:51:08 +0000] [3794265] [ERROR] Worker (pid:3796523) exited with code 120
[2025-03-20 06:51:08 +0000] [3794265] [ERROR] Worker (pid:3796523) exited with code 120.
[2025-03-20 06:51:08 +0000] [3796560] [INFO] Booting worker with pid: 3796560
[2025-03-20 06:51:08 +0000] [3794265] [ERROR] Worker (pid:3796524) exited with code 120
[2025-03-20 06:51:08 +0000] [3794265] [ERROR] Worker (pid:3796524) exited with code 120.
[2025-03-20 06:51:08 +0000] [3796561] [INFO] Booting worker with pid: 3796561

What would be the right configuration fix to address this issue?

[dosubot[bot]]

Hey @manishtiwari-ie! I'm here to help you with any bugs, questions, or contributions you have for Superset. Let's squash those bugs together!

The issue you're experiencing with Superset hanging after a period of inactivity and the Gunicorn workers exiting with code 120 could be related to several factors, including timeout settings or resource limits.

1. Gunicorn Timeout: Ensure that the Gunicorn timeout setting is configured appropriately. The default timeout is 60 seconds, but it can be extended to 300 seconds to accommodate long-running queries. You can adjust this setting in your Gunicorn configuration or command line by using the --timeout option.

2. Worker Connections: If you're using asynchronous workers, such as gevent, ensure that the --worker-connections setting is high enough to handle the number of concurrent connections. A typical configuration might be -w 10 -k gevent --worker-connections 1000 for high concurrency.

3. Logging and Debugging: Since the error involves an OSError: [Errno 5] Input/output error, it might be related to issues with writing logs or output. Ensure that the file system where logs are being written is stable and has sufficient space. Additionally, check if there are any restrictions or issues with the terminal or console where the application is running.

4. Configuration File: Verify that your Superset configuration file is correctly set up and accessible. The error in the logs indicates an issue with loading the configuration, which might be causing the workers to fail.

5. Resource Limits: Check if there are any system-level resource limits (e.g., file descriptors, memory) that might be affecting the Gunicorn workers. Adjust these limits if necessary.

By addressing these areas, you should be able to mitigate the issue of Superset hanging after inactivity and the Gunicorn workers exiting unexpectedly.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[manishtiwari-ie]

I have tried all of the above options. They were presented by ChatGPT too, unfortunately no configuration change has worked so far.