Closed syafiqdante closed 5 years ago
Issue-Label Bot is automatically applying the label #bug
to this issue, with a confidence of 0.67. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
No problem @syafiqdante, simple question, just sanity check, do you have statsd
installed on your virtualenv?
No I don't think so...
I have only installed statsd using pip command:
pip3 install statsd
pip3 install python-statsd
How do I install statsd
on virtualenv..?
Ok,
That's installed. Have you managed to run superset ever? if not empty your superset_config.py
file and give a spin. Do you have a statsd server running on your localhost?
https://packaging.python.org/guides/installing-using-pip-and-virtual-environments/
I haven't been able to run superset using command:
gunicorn \
-w 10 \
-k gevent \
--timeout 120 \
-b 0.0.0.0:8088 \
--limit-request-line 0 \
--limit-request-field_size 0 \
superset:app
and
superset run -p 8088 --with-threads --reload --debugger
I have tried running superset with empty superset_config.py still nothing when I try to open the superset page at http://<my_ip:8088>/superset/
from the stacktrace, it seems to be working using the superset run -p 8088 --with-threads --reload --debugger
command:
2019-09-26 09:46:26,277:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
* Serving Flask app "superset:app" (lazy loading)
* Environment: development
* Debug mode: on
2019-09-26 09:46:27,616:INFO:werkzeug: * Running on http://127.0.0.1:8088/ (Press CTRL+C to quit)
2019-09-26 09:46:27,617:INFO:werkzeug: * Restarting with stat
2019-09-26 09:46:29,494:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
2019-09-26 09:46:30,843:WARNING:werkzeug: * Debugger is active!
2019-09-26 09:46:30,850:INFO:werkzeug: * Debugger PIN: 410-272-582
Kinda stuck here for a while now... Please help, Thanks in advance.
The log looks good what do you mean by http://<my_ip:8088>/superset
, have you tried http://127.0.0.1:8088
?
It's installed in remote pc (OS version: Ubuntu 16.04.5 LTS) act as server at at address
Its mind boggling when the log shows superset is running but nothing is on the http://<my_ip>:8088/superset
Using 127.0.0.1
will never work, use 0.0.0.0
. Going to close this issue, feel free to reopen if you need to. Enjoy Superset!
Using
127.0.0.1
will never work, use0.0.0.0
. Going to close this issue, feel free to reopen if you need to. Enjoy Superset!
Using this doesn't work either...
previously, using superset 0.28.1, I was able to open superset at http://<my_ip:8088/superset>
I meant changing to 0.0.0.0 on the server not on the browser, localhost is bound to the loopback net device
Sorry to ask, how do I change it to 0.0.0.0..?
do I change it at superset_config.py
?
maybe youcan try: when gunicorn start add '--statsd-host localhost:xxxx'
No I don't think so... I have only installed statsd using pip command:
pip3 install statsd
pip3 install python-statsd
How do I install
statsd
on virtualenv..?
Just install statsd, it worked for me
It seems like I couldn't run superset 0.34.0 when using the command:
Expected results
Superset starts and running
Actual results
Error in python stacktrace:
Screenshots
If applicable, add screenshots to help explain your problem.
How to reproduce the bug
Environment
(please complete the following information):
0.34.0
Python 3.6.8
v10.16.0
6.9.0
Checklist
Make sure these boxes are checked before submitting your issue - thank you!
Additional context
The same error shown when running celery using command:
celery worker --app=superset.tasks.celery_app:app --pool=prefork -Ofair -c 4 --loglevel=DEBUG --max-tasks-per-child=128
Error shown:
contents of
stats_logger.py
Sorry to disturb you guys, I'm quite new with this superset... Thanks in advance for any help...