GitHub user dosubot[bot] added a comment to the discussion: Superset → PostgreSQL: recurring SSL EOF and connection reset logs
<!-- Answer --> The recurring PostgreSQL logs are likely caused by Superset's Celery background tasks that periodically connect to the metadata database. The main candidates are: the cache-warmup task (which queries charts/dashboards and warms up their cache), report scheduling and execution tasks (`reports.scheduler`, `reports.execute`), and log/query pruning tasks (`reports.prune_log`, `prune_query`, `prune_logs`). Their frequency is set by the Celery beat schedule in your Superset config—if any are set to run every minute, that would match your log pattern. To pinpoint which task is responsible, check the logs of your Celery worker and beat pods in Kubernetes (`kubectl logs <pod-name>`) and consider setting `SUPERSET_LOG_LEVEL=debug` for more detail. These logs will show when each background task runs and can help you correlate with the PostgreSQL connection events ([cache-warmup](https://github.com/apache/superset/blob/master/superset/tasks/cache.py), [scheduler/prune tasks](https://github.com/apache/superset/blob/master/superset/tasks/scheduler.py)). <!-- 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/ebc97f93-fa2f-4ec4-9dfd-bd26ae567d90?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ebc97f93-fa2f-4ec4-9dfd-bd26ae567d90?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ebc97f93-fa2f-4ec4-9dfd-bd26ae567d90?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ebc97f93-fa2f-4ec4-9dfd-bd26ae567d90?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ebc97f93-fa2f-4ec4-9dfd-bd26ae567d90?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ebc97f93-fa2f-4ec4-9dfd-bd26ae567d90?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ebc97f93-fa2f-4ec4-9dfd-bd26ae567d90?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=The%20recurring%20PostgreSQL%20logs%20are%20likely%20caused%20by%20Superset%27s%20Celery%20background%20tasks%20that%20periodically%20connect%20to%20the%20metadata%20database.%20The%20main%20candidates%20are%3A%20the%20cache-warmup%20task%20%28which%20queries%20charts/dashboards%20and%20warms%20up%20their%20cache%29%2C%20report%20scheduling%20and%20execution%20tasks%20%28%60reports.scheduler%60%2C%20%60reports.execute%60%29%2C%20and%20log/query%20pruning%20tasks%20%28%60reports.prune_log%60%2C%20%60prune_query%60%2C%20%60prune_logs%60%29.%20Their%20frequency%20is%20set%20by%20the%20Celery%20beat%20schedule%20in%20your%20Superset%20config%E2%80%94if%20any%20are%20set%20to%20run%20every%20minute%2C%20that%20would%20match%20your%20log%20pattern.%20%0A%0A To%20pinpoint%20which%20task%20is%20responsible%2C%20check%20the%20logs%20of%20your%20Celery%20worker%20and%20beat%20pods%20in%20Kubernetes%20%28%60kubectl%20logs%20%3Cpod-name%3E%60%29%20and%20consider%20setting%20%60SUPERSET_LOG_LEVEL%3Ddebug%60%20for%20more%20detail.%20These%20logs%20will%20show%20when%20each%20background%20task%20runs%20and%20can%20help%20you%20correlate%20with%20the%20PostgreSQL%20connection%20events%C2%A0%28%5Bcache-warmup%5D%28https%3A//github.com/apache/superset/blob/master/superset/tasks/cache.py%29%2C%20%5Bscheduler/prune%20tasks%5D%28https%3A//github.com/apache/superset/blob/master/superset/tasks/scheduler.py%29%29.) [](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-15170747 ---- 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]
