GitHub user dosubot[bot] added a comment to the discussion: Superset → PostgreSQL: recurring SSL EOF and connection reset logs
<!-- Answer --> If Celery is fully disabled and you’re still seeing recurring PostgreSQL SSL EOF and connection reset logs, this is likely due to how Superset’s web server manages database connections. By default, Superset uses SQLAlchemy with NullPool, so every metadata DB operation opens and closes a new connection. Each connection triggers a lightweight `SELECT 1` ping (pessimistic connection handling) to validate the connection, which can look like a health check and cause frequent connect/disconnect cycles in your PostgreSQL logs—even without Celery or explicit probes. This is normal behavior for Superset’s web server and not configurable via the Helm chart ([details](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/models/core.py#L129-L538), [pessimistic ping](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/utils/core.py#L628-L683)). To confirm the source, enable detailed PostgreSQL connection logging (log_connections, log_disconnections, log_line_prefix with %h and %u) to see which client IP and user are making the connections. If you want to reduce this churn, you can try switching to a different SQLAlchemy pool class (like QueuePool) by setting `engine_params` in the database’s “extra” field in Superset’s UI or via config. If you have any custom monitoring tools or other Superset-related pods (like the new MCP service), check if they’re also connecting to the database. If you share your (redacted) values.yaml and clarify if any custom plugins or monitoring are in use, I can help review for other possible sources. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/91993d30-3211-4c80-9f78-54dceb9451b3?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/91993d30-3211-4c80-9f78-54dceb9451b3?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/91993d30-3211-4c80-9f78-54dceb9451b3?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/91993d30-3211-4c80-9f78-54dceb9451b3?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/91993d30-3211-4c80-9f78-54dceb9451b3?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/91993d30-3211-4c80-9f78-54dceb9451b3?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/91993d30-3211-4c80-9f78-54dceb9451b3?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=If%20Celery%20is%20fully%20disabled%20and%20you%E2%80%99re%20still%20seeing%20recurring%20PostgreSQL%20SSL%20EOF%20and%20connection%20reset%20logs%2C%20this%20is%20likely%20due%20to%20how%20Superset%E2%80%99s%20web%20server%20manages%20database%20connections.%20By%20default%2C%20Superset%20uses%20SQLAlchemy%20with%20NullPool%2C%20so%20every%20metadata%20DB%20operation%20opens%20and%20closes%20a%20new%20connection.%20Each%20connection%20triggers%20a%20lightweight%20%60SELECT%201%60%20ping%20%28pessimistic%20connection%20handling%29%20to%20validate%20the%20connection%2C%20which%20can%20look%20like%20a%20health%20check%20and%20cause%20frequent%20connect/disconnect%20cycles%20in%20your%20PostgreSQL%20logs%E2%80%94even%20without%20Celery%20or%20explicit%20 probes.%20This%20is%20normal%20behavior%20for%20Superset%E2%80%99s%20web%20server%20and%20not%20configurable%20via%20the%20Helm%20chart%C2%A0%28%5Bdetails%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/models/core.py%23L129-L538%29%2C%20%5Bpessimistic%20ping%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/utils/core.py%23L628-L683%29%29.%0A%0ATo%20confirm%20the%20source%2C%20enable%20detailed%20PostgreSQL%20connection%20logging%20%28log_connections%2C%20log_disconnections%2C%20log_line_prefix%20with%20%25h%20and%20%25u%29%20to%20see%20which%20client%20IP%20and%20user%20are%20making%20the%20connections.%0A%0AIf%20you%20want%20to%20reduce%20this%20churn%2C%20you%20can%20try%20switching%20to%20a%20different%20SQLAlchemy%20pool%20class%20%28like%20QueuePool%29%20by%20setting%20%60engine_params%60%20in%20the%20database%E2%80%99s%20%E2%80%9Cextra%E2%80%9D%20field%20in%20Superset%E2%80%99s%20 UI%20or%20via%20config.%20If%20you%20have%20any%20custom%20monitoring%20tools%20or%20other%20Superset-related%20pods%20%28like%20the%20new%20MCP%20service%29%2C%20check%20if%20they%E2%80%99re%20also%20connecting%20to%20the%20database.%0A%0AIf%20you%20share%20your%20%28redacted%29%20values.yaml%20and%20clarify%20if%20any%20custom%20plugins%20or%20monitoring%20are%20in%20use%2C%20I%20can%20help%20review%20for%20other%20possible%20sources.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/36420) GitHub link: https://github.com/apache/superset/discussions/36420#discussioncomment-15171484 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
