connection refused error from Email Report after upgrading to Latest Superset Version.
See original GitHub issueI am running Superset with Docker.
I was having issues with making celery worker functional with my Superset Version (circa 2019), so I decided to update to the latest release 0.36.0.
I am using the same versions of geckodriver (0.24.0) and firefox (68.5.0esr) as I was using prior to the update. Python (3.6.9) and Selenium (3.141.0) versions are still the same.
However, when trying to send an email, I am getting the following error:
erset-worker_1 | "Flask-Caching: CACHE_TYPE is set to null, "
superset-worker_1 | [2020-04-22 15:36:09,452: ERROR/ForkPoolWorker-8] Task email_reports.send[eb4ddfba-0901-427e-be05-743c9c97a2f5] raised unexpected: WebDriverException('connection refused', None, None)
superset-worker_1 | Traceback (most recent call last):
superset-worker_1 | File "/usr/local/lib/python3.6/site-packages/celery/app/trace.py", line 385, in trace_task
superset-worker_1 | R = retval = fun(*args, **kwargs)
superset-worker_1 | File "/app/superset/app.py", line 114, in __call__
superset-worker_1 | return task_base.__call__(self, *args, **kwargs)
superset-worker_1 | File "/usr/local/lib/python3.6/site-packages/celery/app/trace.py", line 650, in __protected_call__
superset-worker_1 | return self.run(*args, **kwargs)
superset-worker_1 | File "/app/superset/tasks/schedules.py", line 373, in schedule_email_report
superset-worker_1 | deliver_dashboard(schedule)
superset-worker_1 | File "/app/superset/tasks/schedules.py", line 211, in deliver_dashboard
superset-worker_1 | driver = create_webdriver()
superset-worker_1 | File "/app/superset/tasks/schedules.py", line 163, in create_webdriver
superset-worker_1 | driver = driver_class(**kwargs)
superset-worker_1 | File "/usr/local/lib/python3.6/site-packages/selenium/webdriver/firefox/webdriver.py", line 174, in __init__
superset-worker_1 | keep_alive=True)
superset-worker_1 | File "/usr/local/lib/python3.6/site-packages/selenium/webdriver/remote/webdriver.py", line 157, in __init__
superset-worker_1 | self.start_session(capabilities, browser_profile)
superset-worker_1 | File "/usr/local/lib/python3.6/site-packages/selenium/webdriver/remote/webdriver.py", line 252, in start_session
superset-worker_1 | response = self.execute(Command.NEW_SESSION, parameters)
superset-worker_1 | File "/usr/local/lib/python3.6/site-packages/selenium/webdriver/remote/webdriver.py", line 321, in execute
superset-worker_1 | self.error_handler.check_response(response)
superset-worker_1 | File "/usr/local/lib/python3.6/site-packages/selenium/webdriver/remote/errorhandler.py", line 242, in check_response
superset-worker_1 | raise exception_class(message, screen, stacktrace)
superset-worker_1 | selenium.common.exceptions.WebDriverException: Message: connection refused
‘geckodriver.log’:
1587569769443 mozrunner::runner DEBUG Killing process 104
1587569769447 webdriver::server DEBUG <- 500 Internal Server Error {"value":{"error":"unknown error","message":"connection refused","stacktrace":""}}
Why is this error occurring? What change in Superset is affecting the Email Report feature?
All package versions:
- geckodriver – 0.24.0
- python – 3.6.9
- firefox – 68.5.0esr
- selenium – 3.141.0
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
connection refused error from Email Report after upgrading to ...
I am running Superset with Docker. I was having issues with making celery worker functional with my Superset Version (circa 2019), ...
Read more >[GitHub] [incubator-superset] avicenteg commented on issue ...
[GitHub] [incubator-superset] avicenteg commented on issue #9616: connection refused error from Email Report after upgrading to Latest ...
Read more >Superset Reports stopped working, Failed generating ...
I receive an email with the error. So it's not the emailing that's broken, it's the reporting. Screenshots. enter image description here ...
Read more >airbnb/superset - Gitter
I was able to successfully add the datasource however when I try adding a chart, I see a connection refused error. Any pointers...
Read more >Installation & Configuration - apache-superset - Read the Docs
Install and Deploy Superset Locally with Docker. To try Superset locally, the best-supported currently method is via Docker, using docker-compose . Superset ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@poppyc0ck thanks, finally my error was a similar one. My Docker container didn’t use the ip: 0.0.0.0, I changed it by superset-app (the name of the container) and using the 8088 port, and now it is running perfectly.
Hello @avicenteg @poppyc0ck ! Your advice will be very appreciated.
In my case superset and celery don’t bound to 8088. What’s the service stands behind 8088 in your case? I can’t figure out myself.
Thanks!