Created 04-21-2017 10:34 AM
Team, i am tracking this error separately, see below. If anybody finds the solution please mark me. Thanks in Advance!!!
https://www.linkedin.com/pulse/hdp-26-issue-druid-superset-start-fail-importerror-module-kumar
Created on 07-08-2017 06:25 AM - edited 08-17-2019 10:47 PM
It worked for me to change the database to mysql.
1.you need to create user and databases named 'superset' using mysql shell
GRANT ALL PRIVILEGES ON *.* TO 'superset'@'%' IDENTIFIED BY '*****' WITH GRANT OPTION;
create database superset;
2. change the config for Druid , set Mysql's hostname port user password .etc
3. start the druid, and it worked!
Created 04-21-2017 12:50 PM
Not sure why the article is protected, but it essentially says to switch the superset database to mysql/postgreSQL instead of sqlite for a temporary work around. You can adjust this in Ambari by going to the druid service and modifying the config for the "Superset Database name".
Created 04-24-2017 10:34 AM
No luck, please see above my reply to Deepesh! Thanks!!!
Created 04-24-2017 01:24 PM
Thanks Devin, I have tried changing database for superset but having similar issue:-
Traceback (most recent call last): File "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py", line 169, in <module> Superset().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 314, in execute method(env) File "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py", line 108, in start self.configure(env, upgrade_type=upgrade_type) File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 117, in locking_configure original_configure(obj, *args, **kw) File "/var/lib/ambari-agent/cache/common-services/DRUID/0.9.2/package/scripts/superset.py", line 84, in configure user=params.druid_user) File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155, in __init__ self.env.run() File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160, in run self.run_action(resource, action) File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124, in run_action provider_action() File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 262, in action_run tries=self.resource.tries, try_sleep=self.resource.try_sleep) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72, in inner result = function(command, **kwargs) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, in checked_call tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, in _call_wrapper result = _call(command, **kwargs_copy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, in _call raise ExecutionFailed(err_msg, code, out, err) resource_management.core.exceptions.ExecutionFailed: Execution of 'source /etc/superset/conf/superset-env.sh ; /usr/hdp/current/druid-superset/bin/superset db upgrade' returned 1. Traceback (most recent call last): File "/usr/hdp/current/druid-superset/bin/superset", line 10, in <module> import gunicorn.app.base ImportError: No module named gunicorn.app.base
Created 04-29-2017 02:29 AM
this is a copy past of response
Answer by Nishant Bangarwa Apr 14 at 09:30 PM
Thanks for reporting this. seems like an issue with the packaging on Centos7. We are working on fixing it.
In the meantime, can you try with changing the superset database type to 'mysql' or 'postgresql' ?
I verified that it works with mysql.
Created 05-03-2017 02:27 AM
Thx, it works when I change the database type to mysql.