[GitHub] myarnav commented on issue #4612: In the “SQL Lab”, the “Results” section shows “Pending” constantly

[GitBox <gi...@apache.org>]

myarnav commented on issue #4612: In the “SQL Lab”, the “Results” section shows “Pending” constantly
URL: https://github.com/apache/incubator-superset/issues/4612#issuecomment-380419500
 
 
   Hi, I have setup async in SQL Lab, and setup celery with redis. My superset_config.py file is on python path and included below. 
   `superset specific config
   ---------------------------------------------------------
   ROW_LIMIT = 5000
   SUPERSET_WORKERS = 4
   
   You will be serving site on port 8000 from gunicorn which sits in front of flask, and then send to nginx
   SUPERSET_WEBSERVER_PORT = 8000
   
   ---------------------------------------------------------
   ---------------------------------------------------------
   Flask App Builder configuration
   ---------------------------------------------------------
   Your App secret key
   SECRET_KEY = '\2\mthisismyscretkey\1\2\a\b\y\h'
   
   The SQLAlchemy connection string to your database backend
   This connection defines the path to the database that stores your
   superset metadata (slices, connections, tables, dashboards, ...).
   Note that the connection information to connect to the datasources
   you want to explore are managed directly in the web UI
   SQLALCHEMY_DATABASE_URI = 'sqlite:////home/ubuntu/.superset/superset.db'
   
   Flask-WTF flag for CSRF
   CSRF_ENABLED = True
   
   Set this API key to enable Mapbox visualizations
   MAPBOX_API_KEY = ''
   
   CACHE_DEFAULT_TIMEOUT = 86400
   CACHE_CONFIG = {
   'CACHE_TYPE': 'RedisCache',
   'CACHE_DEFAULT_TIMEOUT': 86400,
   'CACHE_KEYPREFIX': 'superset',
   'CACHE_REDIS_HOST': 'localhost',
   'CACHE_REDIS_PORT': 6379,
   'CACHE_REDIS_DB': 1,
   'CACHE_REDIS_URL': 'redis://localhost:6379/1'
   }`
   
   
   As suggested in installation instructions, I have setup celery workers and running "superset worker & to start superset before I run "superset runserver &". When I start the superset workers. I am seeing the following error message :
   
   `--- ** * -- Linux-4.4.0-1052-aws-x86_64-with-Ubuntu-16.04-xenial 2018-04-11 10:31:55
   
   ** ---------- [config]
   ** ---------- .> app: main:0x7f1652b31c50
   ---------- .> transport: amqp://guest:@localhost:5672//
   ** ---------- .> results: disabled://
   --- --- .> concurrency: 32 (prefork)
   -- * ---- .> task events: OFF (enable -E to monitor tasks in this worker)
   -------------- [queues]
   .> celery exchange=celery(direct) key=celery
   
   [2018-04-11 10:31:58,576: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:@127.0.0.1:5672//: [Errno 111] Connection refused.
   Trying again in 32.00 seconds... Cannot connect to amqp://guest:@127.0.0.1:5672//: [Errno 111] Connection refused.
   
   `

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services