dosubot[bot] commented on issue #40047: URL: https://github.com/apache/superset/issues/40047#issuecomment-4430030730
<!-- Answer --> Thanks for the additional context. Given that: - Config is correct - Execution log reset didn't help - Same image works in other deployments - No logs appear after "Running report schedule..." The fact that you get **zero logs** after that point is a strong signal. Here's what happens in the code right after that log line: the system enters a state machine which calls into the screenshot/data generation layer [[1]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/report/execute.py#L894-L896). The screenshot layer has several known silent failure modes where exceptions are caught but **not propagated or logged** — the function just returns `None` and the caller doesn't know it failed [[2]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/utils/webdriver.py#L237-L244) [[3]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/utils/screenshots.py#L260-L277). Here are the most likely culprits for your specific scenario (same image, worked before, now silently stuck): **1. Report execution user issue** — If the user configured as the report executor was deactivated, had a password change, or lost permissions, the WebDriver will load a **login page** instead of the dashboard/chart. It then waits for chart elements that never appear and hangs until timeout — with no useful log output [[4]](https://github.com/apache/superset/discussions/36161). This is the #1 silent failure mode. Verify this user is active and can log in. **2. Selenium/ChromeDriver process hanging** — If ChromeDriver is crashing or hanging on startup (e.g., shared memory issues in Docker, `/dev/shm` too small), the process blocks with no output. Check: - Is `/dev/shm` adequately sized? (Common Docker issue — add `--shm-size=2g` or mount tmpfs) - Can you exec into the worker container and manually run `chromedriver --version`? **3. Network connectivity from the worker** — Since this is the same image working elsewhere, check if the Celery worker can actually reach Superset's web UI internally. The WebDriver navigates to `WEBDRIVER_BASEURL` to capture screenshots. If DNS resolution or network policies changed in this specific deployment ~10 days ago, the page load would hang silently. **Debugging steps I'd recommend:** 1. **Check the report executor user** — log in manually with that user's credentials 2. **Enable DEBUG logging** for `superset.utils.screenshots` — add to your config: ```python ADDITIONAL_MODULE_DS_MAP = { "superset.utils.screenshots": logging.DEBUG, } ``` 3. **Test WebDriver connectivity** — exec into the worker pod and try: ```python from selenium import webdriver # attempt to create a browser session and navigate to WEBDRIVER_BASEURL ``` 4. **Check `/dev/shm`** in the worker container — `df -h /dev/shm` The fact that it broke ~10 days ago without an image change strongly suggests an infrastructure or user/permissions change in that specific environment rather than a code issue. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).* --- Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset). [](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=85c4c2ff-9b5a-4cf0-9932-26d0e8599afc) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
