You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2019/05/16 05:02:02 UTC

[GitHub] [incubator-superset] hellohappy0 opened a new issue #7522: ModuleNotFoundError: No module named 'gevent'

hellohappy0 opened a new issue #7522:  ModuleNotFoundError: No module named 'gevent'
URL: https://github.com/apache/incubator-superset/issues/7522
 
 
   I have reproduced the issue with at least the latest released version of superset.
   I have checked the issue tracker for the same issue and I haven't found one similar.
   
   ### Expected results
   
   superset starts up without error.
   
   ### Actual results
   
   /usr/lib/python2.7/site-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.22) or chardet (2.2.1) doesn't match a supported version!
     RequestsDependencyWarning)
   Starting superset_postgres_1 ... done
   Starting superset_redis_1    ... done
   Recreating superset_superset_1 ... done
   Attaching to superset_postgres_1, superset_redis_1, superset_superset_1
   postgres_1  | 2019-05-16 04:51:54.489 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
   postgres_1  | 2019-05-16 04:51:54.489 UTC [1] LOG:  listening on IPv6 address "::", port 5432
   postgres_1  | 2019-05-16 04:51:54.502 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
   postgres_1  | 2019-05-16 04:51:54.519 UTC [21] LOG:  database system was shut down at 2019-05-16 04:48:03 UTC
   postgres_1  | 2019-05-16 04:51:54.530 UTC [1] LOG:  database system is ready to accept connections
   redis_1     | 1:C 16 May 04:51:54.449 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
   redis_1     |                 _._                                               
   redis_1     |            _.-``__ ''-._                                          
   redis_1     |       _.-``    `.  `_.  ''-._           Redis 3.2.12 (00000000/0) 64 bit
   redis_1     |   .-`` .-```.  ```\/    _.,_ ''-._                                
   redis_1     |  (    '      ,       .-`  | `,    )     Running in standalone mode
   redis_1     |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
   redis_1     |  |    `-._   `._    /     _.-'    |     PID: 1
   redis_1     |   `-._    `-._  `-./  _.-'    _.-'                                
   redis_1     |  |`-._`-._    `-.__.-'    _.-'_.-'|                               
   redis_1     |  |    `-._`-._        _.-'_.-'    |           http://redis.io     
   redis_1     |   `-._    `-._`-.__.-'_.-'    _.-'                                
   redis_1     |  |`-._`-._    `-.__.-'    _.-'_.-'|                               
   redis_1     |  |    `-._`-._        _.-'_.-'    |                               
   redis_1     |   `-._    `-._`-.__.-'_.-'    _.-'                                
   redis_1     |       `-._    `-.__.-'    _.-'                                    
   redis_1     |           `-._        _.-'                                        
   redis_1     |               `-.__.-'                                            
   redis_1     |
   redis_1     | 1:M 16 May 04:51:54.451 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
   redis_1     | 1:M 16 May 04:51:54.451 # Server started, Redis version 3.2.12
   redis_1     | 1:M 16 May 04:51:54.451 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
   redis_1     | 1:M 16 May 04:51:54.451 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
   redis_1     | 1:M 16 May 04:51:54.451 * DB loaded from disk: 0.000 seconds
   redis_1     | 1:M 16 May 04:51:54.451 * The server is now ready to accept connections on port 6379
   superset_1  | + '[' 0 -ne 0 ']'
   superset_1  | + '[' development = development ']'
   superset_1  | + celery worker --app=superset.sql_lab:celery_app --pool=gevent -Ofair
   superset_1  | + cd superset/assets/
   superset_1  | + npm ci
   superset_1  | Traceback (most recent call last):
   superset_1  |   File "/usr/local/bin/celery", line 10, in <module>
   superset_1  |     sys.exit(main())
   superset_1  |   File "/usr/local/lib/python3.6/site-packages/celery/__main__.py", line 14, in main
   superset_1  |     maybe_patch_concurrency()
   superset_1  |   File "/usr/local/lib/python3.6/site-packages/celery/__init__.py", line 142, in maybe_patch_concurrency
   superset_1  |     patcher()
   superset_1  |   File "/usr/local/lib/python3.6/site-packages/celery/__init__.py", line 110, in _patch_gevent
   superset_1  |     import gevent
   superset_1  | ModuleNotFoundError: No module named 'gevent'
   
   #### Screenshots
   
   If applicable, add screenshots to help explain your problem.
   
   #### How to reproduce the bug
   
   1. Go to '...'
   2. Click on '....'
   3. Scroll down to '....'
   4. See error
   
   ### Environment
   
   (please complete the following information):
   
   - superset version: [e.g. `v0.29`, `master`, `commit`]
   - python version: `python --version`
   - node.js version: `node -v`
   - npm version: `npm -v`
   
   ### Checklist
   
   Make sure these boxes are checked before submitting your issue - thank you!
   
   - [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
   - [ ] I have reproduced the issue with at least the latest released version of superset.
   - [ ] I have checked the issue tracker for the same issue and I haven't found one similar.
   
   ## Additional context
   ###Steps to reproduce:
   git clone https://github.com/apache/incubator-superset/
   cd incubator-superset/contrib/docker
   docker-compose run --rm superset ./docker-init.sh
   docker-compose up
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org