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 2020/05/21 22:26:17 UTC
[GitHub] [incubator-superset] smirs opened a new issue #9880: Installing Superset via Docker-compose Up
smirs opened a new issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880
I am on ubuntu. I am following the instructions to install Superset via docker via this link:
https://superset.incubator.apache.org/installation.html#start-with-docker
### Expected results
I expect after these steps if I open http://localhost:8088, I see Superset UI
### Actual results
I see a blank page at http://localhost:8088
#### Screenshots
#### How to reproduce the bug
1. Go to a computer with Ubuntu installed on it
2. Follow the exact instructions at https://superset.incubator.apache.org/installation.html#start-with-docker
3. You may get some error messages asking for installing docker and its dependencies and creating and running one. Please do those.
4. See error
### Environment
(please complete the following information):
- superset version: not-installed!!! [trying to install]
- python version: Python 3.7.4
- node.js version: v8.10.0
- npm version: 3.5.2
### Checklist
Make sure these boxes are checked before submitting your issue - thank you!
- [X] I have checked the superset logs for python stacktraces and included it here as text if there are any.
- [X] I have reproduced the issue with at least the latest released version of superset.
- [X] I have checked the issue tracker for the same issue and I haven't found one similar.
### Additional context
Here is the full log:
'(base) smirs@emarats-brain:~/incubator-superset$ sudo docker-compose up
Starting superset_db ... done
Starting superset_cache ... done
Starting superset_tests_worker ... done
Starting superset_worker ... done
Starting superset_init ... done
Starting superset_node ... done
Starting superset_app ... done
Attaching to superset_db, superset_cache, superset_tests_worker, superset_worker, superset_init, superset_node, superset_app
superset_db |
superset_db | PostgreSQL Database directory appears to contain a database; Skipping initialization
superset_db |
superset_db | 2020-05-21 19:17:21.482 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
superset_cache | 1:C 21 May 19:17:22.498 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
superset_db | 2020-05-21 19:17:21.482 UTC [1] LOG: listening on IPv6 address "::", port 5432
superset_db | 2020-05-21 19:17:21.484 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 1/4 [Starting] -- Setting up admin user ( admin / admin )
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_cache | 1:M 21 May 19:17:22.499 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
superset_cache | 1:M 21 May 19:17:22.499 # Server can't set maximum open files to 10032 because of OS error: Operation not permitted.
superset_cache | 1:M 21 May 19:17:22.499 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
superset_db | 2020-05-21 19:17:21.497 UTC [25] LOG: database system was shut down at 2020-05-21 19:17:17 UTC
superset_cache | _._
superset_cache | _.-``__ ''-._
superset_cache | _.-`` `. `_. ''-._ Redis 3.2.12 (00000000/0) 64 bit
superset_cache | .-`` .-```. ```\/ _.,_ ''-._
superset_cache | ( ' , .-` | `, ) Running in standalone mode
superset_cache | |`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
superset_cache | | `-._ `._ / _.-' | PID: 1
superset_cache | `-._ `-._ `-./ _.-' _.-'
superset_cache | |`-._`-._ `-.__.-' _.-'_.-'|
superset_cache | | `-._`-._ _.-'_.-' | http://redis.io
superset_cache | `-._ `-._`-.__.-'_.-' _.-'
superset_cache | |`-._`-._ `-.__.-' _.-'_.-'|
superset_cache | | `-._`-._ _.-'_.-' |
superset_cache | `-._ `-._`-.__.-'_.-' _.-'
superset_cache | `-._ `-.__.-' _.-'
superset_cache | `-._ _.-'
superset_cache | `-.__.-'
superset_cache |
superset_cache | 1:M 21 May 19:17:22.500 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
superset_db | 2020-05-21 19:17:21.513 UTC [1] LOG: database system is ready to accept connections
superset_cache | 1:M 21 May 19:17:22.500 # Server started, Redis version 3.2.12
superset_cache | 1:M 21 May 19:17:22.500 # 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.
superset_cache | 1:M 21 May 19:17:22.500 # 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.
superset_cache | 1:M 21 May 19:17:22.500 * DB loaded from disk: 0.000 seconds
superset_cache | 1:M 21 May 19:17:22.500 * The server is now ready to accept connections on port 6379
superset_tests_worker | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_db | 2020-05-21 19:17:24.857 UTC [32] FATAL: database "test" does not exist
superset_tests_worker | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_tests_worker | "Flask-Caching: CACHE_TYPE is set to null, "
superset_tests_worker | ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (psycopg2.OperationalError) FATAL: database "test" does not exist
superset_tests_worker |
superset_tests_worker | (Background on this error at: http://sqlalche.me/e/e3q8)
superset_tests_worker | Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
superset_worker | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_tests_worker exited with code 1
superset_init | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_app | * Serving Flask app "superset.app:create_app()" (lazy loading)
superset_app | * Environment: development
superset_app | * Debug mode: on
superset_app | * Running on http://0.0.0.0:8088/ (Press CTRL+C to quit)
superset_app | * Restarting with stat
superset_app | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init | Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
superset_init | Recognized Database Authentications.
superset_init | Error! User already exists admin
superset_init | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_init | "Flask-Caching: CACHE_TYPE is set to null, "
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 1/4 [Complete] -- Setting up admin user
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 2/4 [Starting] -- Applying DB migrations
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_worker | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_worker | "Flask-Caching: CACHE_TYPE is set to null, "
superset_worker | [2020-05-21 19:17:27,512: INFO/MainProcess] Connected to redis://redis:6379/0
superset_worker | [2020-05-21 19:17:27,524: INFO/MainProcess] mingle: searching for neighbors
superset_app | * Debugger is active!
superset_app | * Debugger PIN: 294-670-256
superset_worker | [2020-05-21 19:17:28,544: INFO/MainProcess] mingle: all alone
superset_worker | [2020-05-21 19:17:28,552: INFO/MainProcess] celery@6f1df210e742 ready.
superset_app | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_init | "Flask-Caching: CACHE_TYPE is set to null, "
superset_init | INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
superset_init | INFO [alembic.runtime.migration] Will assume transactional DDL.
superset_init | Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 2/4 [Complete] -- Applying DB migrations
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 3/4 [Starting] -- Loading examples
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_app | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_app | "Flask-Caching: CACHE_TYPE is set to null, "
superset_app | 172.18.0.1 - - [21/May/2020 19:17:34] "GET / HTTP/1.1" 302 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:17:34] "GET / HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [21/May/2020 19:17:34] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:17:34] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:17:34] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:17:34] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_init | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_init | "Flask-Caching: CACHE_TYPE is set to null, "
superset_init | DEBUG:superset.models.core:Database.get_sqla_engine(). Masked URL: postgresql://superset:XXXXXXXXXX@db:5432/superset
superset_init | Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
superset_init | Loading examples metadata and related data into examples
superset_init | Creating default CSS templates
superset_init | Loading energy related dataset
superset_init | Creating table [wb_health_population] reference
superset_init | Loading [World Bank's Health Nutrition and Population Stats]
superset_init | Creating table [wb_health_population] reference
superset_init | Creating slices
superset_init | Creating a World's Health Bank dashboard
superset_init | Loading [Birth names]
superset_init | Creating some slices
superset_init | Creating a dashboard
superset_init | Loading [Unicode test data]
superset_init | Creating table [unicode_test] reference
superset_init | Creating a slice
superset_init | Creating a dashboard
superset_init | Loading [Random time series data]
superset_init | Creating table [random_time_series] reference
superset_init | Creating a slice
superset_init | Loading [Random long/lat data]
superset_init | Creating table reference
superset_init | Creating a slice
superset_init | Loading [Country Map data]
superset_init | Creating table reference
superset_init | Creating a slice
superset_init | Loading [Multiformat time series]
superset_init | Creating table [multiformat_time_series] reference
superset_init | Creating Heatmap charts
superset_init | Loading [Paris GeoJson]
superset_init | Creating table paris_iris_mapping reference
superset_init | Loading [San Francisco population polygons]
superset_init | Creating table sf_population_polygons reference
superset_init | Loading [Flights data]
superset_init | Done loading table!
superset_init | Loading [BART lines]
superset_init | Creating table bart_lines reference
superset_init | Loading [Multi Line]
superset_init | Creating table [wb_health_population] reference
superset_init | Creating slices
superset_init | Creating a World's Health Bank dashboard
superset_init | Creating some slices
superset_init | Creating a dashboard
superset_init | Loading [Misc Charts] dashboard
superset_init | Creating the dashboard
superset_init | Loading DECK.gl demo
superset_init | Loading deck.gl dashboard
superset_init | Creating Scatterplot slice
superset_init | Creating Screen Grid slice
superset_init | Creating Hex slice
superset_init | Creating Grid slice
superset_init | Creating Polygon slice
superset_init | Creating Arc slice
superset_init | Creating Path slice
superset_init | Creating a dashboard
superset_init | Loading [Tabbed dashboard]
superset_init | Creating a dashboard with nested tabs
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 3/4 [Complete] -- Loading examples
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 4/4 [Starting] -- Setting up roles and perms
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_init | "Flask-Caching: CACHE_TYPE is set to null, "
superset_init | INFO:superset.security.manager:Syncing role definition
superset_init | INFO:superset.security.manager:Syncing Admin perms
superset_init | INFO:superset.security.manager:Syncing Alpha perms
superset_init | INFO:superset.security.manager:Syncing Gamma perms
superset_init | INFO:superset.security.manager:Syncing granter perms
superset_init | INFO:superset.security.manager:Syncing sql_lab perms
superset_init | INFO:superset.security.manager:Fetching a set of all perms to lookup which ones are missing
superset_init | INFO:superset.security.manager:Creating missing datasource permissions.
superset_init | INFO:superset.security.manager:Creating missing database permissions.
superset_init | INFO:superset.security.manager:Creating missing metrics permissions
superset_init | INFO:superset.security.manager:Cleaning faulty perms
superset_init | Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
superset_init |
superset_init | ######################################################################
superset_init |
superset_init |
superset_init | Init Step 4/4 [Complete] -- Setting up roles and perms
superset_init |
superset_init |
superset_init | ######################################################################
superset_init |
superset_init exited with code 0
superset_app | 127.0.0.1 - - [21/May/2020 19:17:54] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:17:54] "GET /health HTTP/1.1" 200 -
superset_node | npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
superset_node | npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
superset_app | 172.18.0.1 - - [21/May/2020 19:18:15] "GET / HTTP/1.1" 302 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:18:15] "GET / HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [21/May/2020 19:18:15] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:18:15] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:18:15] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:18:15] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | 172.18.0.1 - - [21/May/2020 19:18:19] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:18:19] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:18:19] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:18:19] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | 127.0.0.1 - - [21/May/2020 19:18:24] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:18:24] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:18:55] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:18:55] "GET /health HTTP/1.1" 200 -
superset_node | npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
superset_node | npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
superset_app | 127.0.0.1 - - [21/May/2020 19:19:25] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:19:25] "GET /health HTTP/1.1" 200 -
superset_node | /usr/local/bin/webpack -> /usr/local/lib/node_modules/webpack/bin/webpack.js
superset_node | /usr/local/bin/webpack-cli -> /usr/local/lib/node_modules/webpack-cli/bin/cli.js
superset_node | npm WARN notsup Unsupported engine for watchpack-chokidar2@2.0.0: wanted: {"node":"<8.10.0"} (current: {"node":"10.20.1","npm":"6.14.4"})
superset_node | npm WARN notsup Not compatible with your version of node/npm: watchpack-chokidar2@2.0.0
superset_node | npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/webpack/node_modules/chokidar/node_modules/fsevents):
superset_node | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
superset_node | npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/webpack/node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):
superset_node | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
superset_node |
superset_node | + webpack-cli@3.3.11
superset_node | + webpack@4.43.0
superset_node | updated 2 packages in 123.688s
superset_app | 127.0.0.1 - - [21/May/2020 19:19:55] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:19:55] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:20:25] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:20:25] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:20:56] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:20:56] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:21:26] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:21:26] "GET /health HTTP/1.1" 200 -
superset_node | npm WARN tarball tarball data for ramda@0.26.1 (sha512-hLWjpy7EnsDBb0p+Z3B7rPi3GDeRG5ZtiI33kJhTt+ORCd38AbAIjB/9zRIUoeTbE/AVX5ZkU7m6bznsvrf8eQ==) seems to be corrupted. Trying one more time.
superset_app | 127.0.0.1 - - [21/May/2020 19:21:56] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:21:56] "GET /health HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET / HTTP/1.1" 302 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET / HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /superset/welcome HTTP/1.1" 302 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /superset/welcome HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /login/ HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /login/ HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/datepicker/bootstrap-datepicker.css HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/datepicker/bootstrap-datepicker.css HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/css/flags/flags16.css HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/css/flags/flags16.css HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/select2/select2.css HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/select2/select2.css HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/css/ab.css HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/css/ab.css HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/css/font-awesome.min.css HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/css/font-awesome.min.css HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/css/bootstrap.min.css HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/css/bootstrap.min.css HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/js/ab_filters.js HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/js/ab_filters.js HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/js/ab_actions.js HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/js/ab_actions.js HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/js/jquery-latest.js HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/js/jquery-latest.js HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/js/bootstrap.min.js HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/js/bootstrap.min.js HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/datepicker/bootstrap-datepicker.js HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/datepicker/bootstrap-datepicker.js HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/assets/images/superset-logo@2x.png HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/assets/images/superset-logo@2x.png HTTP/1.1" 404 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/img/flags/flags16.png HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/img/flags/flags16.png HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/js/ab.js HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/js/ab.js HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/select2/select2.js HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:14] "GET /static/appbuilder/select2/select2.js HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:15] "GET /static/appbuilder/fonts/fontawesome-webfont.woff2?v=4.7.0 HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:15] "GET /static/appbuilder/fonts/fontawesome-webfont.woff2?v=4.7.0 HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:15] "GET /static/assets/images/favicon.png HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:15] "GET /static/assets/images/favicon.png HTTP/1.1" 404 -
superset_node | npm WARN tarball tarball data for h3-js@3.6.3 (sha512-sSfUD4WrqKDoGsGjeY/ih2kbl/HqunGzdAr4NL8Q1qHSAyGMvev3jABbsMvK9wJGmnGuGhIzgxX9kCbUsYcnwg==) seems to be corrupted. Trying one more time.
superset_app | 172.18.0.1 - - [21/May/2020 19:22:22] "POST /login/ HTTP/1.1" 302 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:22] "POST /login/ HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:22] "GET /login/ HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:22] "GET /login/ HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:22] "GET /static/assets/images/superset-logo@2x.png HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:22] "GET /static/assets/images/superset-logo@2x.png HTTP/1.1" 404 -
superset_app | 127.0.0.1 - - [21/May/2020 19:22:26] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:22:26] "GET /health HTTP/1.1" 200 -
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/brace-3d4c8edd/mode/perl.js'
superset_node | npm WARN tarball tarball data for gl-matrix@3.2.1 (sha512-YYVO8jUSf6+SakL4AJmx9Jc7zAZhkJQ+WhdtX3VQe5PJdCOX6/ybY4x1vk+h94ePnjRn6uml68+QxTAJneUpvA==) seems to be corrupted. Trying one more time.
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/moment-c2e9eafd/min/moment-with-locales.min.js'
superset_node | npm WARN The package @types/classnames is included as both a dev and production dependency.
superset_node | npm WARN The package @types/react-json-tree is included as both a dev and production dependency.
superset_node |
superset_node | npm ERR! code EAI_AGAIN
superset_node | npm ERR! errno EAI_AGAIN
superset_node | npm ERR! request to https://registry.npmjs.org/h3-js/-/h3-js-3.6.3.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-9ca519da/client/library.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/datamaps-264ee032/src/js/data/hrv.topo.json'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/proposals/using-statement.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/es/array/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/es/array/virtual/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/es/instance/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/es/object/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/es/typed-array/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/features/array/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/features/array/virtual/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/features/instance/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/features/object/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/features/typed-array/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/stable/array/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/stable/array/virtual/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/stable/instance/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/stable/object/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/stable/typed-array/values.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.dom-collections.for-each.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.dom-collections.iterator.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.immediate.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.queue-microtask.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.timers.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.url-search-params.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.url.js'
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/babel-polyfill-0be08a64/dist/polyfill.min.js'
superset_app | 172.18.0.1 - - [21/May/2020 19:22:52] "POST /login/ HTTP/1.1" 302 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:52] "POST /login/ HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:52] "GET /login/ HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:52] "GET /login/ HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:52] "GET /static/assets/images/superset-logo@2x.png HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:52] "GET /static/assets/images/superset-logo@2x.png HTTP/1.1" 404 -
superset_app | 127.0.0.1 - - [21/May/2020 19:22:57] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:22:57] "GET /health HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:58] "POST /login/ HTTP/1.1" 302 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:58] "POST /login/ HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:58] "GET /login/ HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:58] "GET /login/ HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:22:58] "GET /static/assets/images/superset-logo@2x.png HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:22:58] "GET /static/assets/images/superset-logo@2x.png HTTP/1.1" 404 -
superset_node | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/ansi-colors-2f753b4b/symbols.js'
superset_node |
superset_node | npm ERR! A complete log of this run can be found in:
superset_node | npm ERR! /root/.npm/_logs/2020-05-21T19_22_41_844Z-debug.log
superset_node exited with code 1
superset_app | 172.18.0.1 - - [21/May/2020 19:23:04] "POST /login/ HTTP/1.1" 302 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:23:04] "POST /login/ HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [21/May/2020 19:23:04] "GET / HTTP/1.1" 302 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:23:04] "GET / HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [21/May/2020 19:23:05] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:23:05] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:23:05] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:23:05] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | 127.0.0.1 - - [21/May/2020 19:23:27] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:23:27] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:23:57] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:23:57] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:24:27] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:24:27] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:24:58] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:24:58] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:25:28] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:25:28] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:25:58] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:25:58] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:26:28] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:26:28] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:26:58] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:26:58] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:27:29] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:27:29] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:27:59] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:27:59] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:28:29] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:28:29] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:28:59] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:28:59] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:29:29] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:29:29] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:30:00] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:30:00] "GET /health HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:30:14] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:30:14] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [21/May/2020 19:30:14] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [21/May/2020 19:30:14] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | 127.0.0.1 - - [21/May/2020 19:30:30] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:30:30] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:31:00] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:31:00] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:31:30] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:31:30] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:32:01] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:32:01] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:32:31] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:32:31] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:33:01] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:33:01] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:33:31] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:33:31] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:34:02] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:34:02] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:34:32] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:34:32] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:35:02] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:35:02] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:35:32] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:35:32] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:36:02] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:36:02] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:36:33] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:36:33] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:37:03] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:37:03] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:37:33] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:37:33] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:38:03] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:38:03] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:38:34] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:38:34] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:39:04] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:39:04] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:39:34] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:39:34] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:40:04] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:40:04] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:40:34] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:40:34] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:41:05] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:41:05] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:41:35] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:41:35] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:42:05] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:42:05] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:42:35] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:42:35] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:43:06] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:43:06] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:43:36] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:43:36] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:44:06] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:44:06] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:44:36] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:44:36] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:45:06] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:45:06] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:45:37] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:45:37] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:46:07] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:46:07] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:46:37] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:46:37] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:47:07] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:47:07] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:47:38] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:47:38] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:48:08] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:48:08] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:48:38] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:48:38] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:49:08] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:49:08] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:49:39] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:49:39] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:50:09] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:50:09] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:50:39] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:50:39] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:51:09] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:51:09] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:51:40] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:51:40] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:52:10] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:52:10] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:52:40] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:52:40] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:53:10] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:53:10] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:53:40] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:53:40] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:54:11] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:54:11] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:54:41] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:54:41] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:55:11] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:55:11] "GET /health HTTP/1.1" 200 -
superset_cache | 1:M 21 May 19:55:37.863 * 100 changes in 300 seconds. Saving...
superset_cache | 1:M 21 May 19:55:37.863 * Background saving started by pid 16
superset_cache | 16:C 21 May 19:55:37.866 * DB saved on disk
superset_cache | 16:C 21 May 19:55:37.867 * RDB: 0 MB of memory used by copy-on-write
superset_cache | 1:M 21 May 19:55:37.965 * Background saving terminated with success
superset_app | 127.0.0.1 - - [21/May/2020 19:55:41] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:55:41] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:56:12] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:56:12] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:56:42] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:56:42] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:57:12] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:57:12] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:57:42] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:57:42] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:58:13] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:58:13] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:58:43] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:58:43] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:59:13] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:59:13] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 19:59:43] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 19:59:43] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:00:14] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:00:14] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:00:44] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:00:44] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:01:14] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:01:14] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:01:44] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:01:44] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:02:14] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:02:14] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:02:45] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:02:45] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:03:15] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:03:15] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:03:45] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:03:45] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:04:15] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:04:15] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:04:46] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:04:46] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:05:16] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:05:16] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:05:46] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:05:46] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:06:16] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:06:16] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:06:47] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:06:47] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:07:17] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:07:17] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:07:47] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:07:47] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:08:17] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:08:17] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:08:48] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:08:48] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:09:18] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:09:18] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:09:48] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:09:48] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:10:18] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:10:18] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:10:48] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:10:48] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:11:19] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:11:19] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:11:49] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:11:49] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:12:19] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:12:19] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:12:49] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:12:49] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:13:20] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:13:20] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:13:50] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:13:50] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:14:20] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:14:20] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:14:50] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:14:50] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:15:21] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:15:21] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:15:51] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:15:51] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:16:21] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:16:21] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:16:51] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:16:51] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:17:22] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:17:22] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:17:52] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:17:52] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:18:22] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:18:22] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:18:52] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:18:52] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:19:23] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:19:23] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:19:53] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:19:53] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:20:23] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:20:23] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:20:53] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:20:53] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:21:24] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:21:24] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:21:54] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:21:54] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:22:24] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:22:24] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:22:54] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:22:54] "GET /health HTTP/1.1" 200 -
superset_app | 127.0.0.1 - - [21/May/2020 20:23:25] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [21/May/2020 20:23:25] "GET /health HTTP/1.1" 200 -
'
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] foodata commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
foodata commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-659311952
same problem +1
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] zhenbo commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
zhenbo commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-681059161
Same here
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] PhucNgo1711 edited a comment on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
PhucNgo1711 edited a comment on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-673135532
I'm having this issue as well. This is my log. I also nuked the volumes, reran compose up, and pulled the lastest from master.
EDIT: Also got this issue when I followed [this](https://github.com/apache/incubator-superset/blob/master/CONTRIBUTING.md#flask-server)
But [this](https://superset.incubator.apache.org/installation.html#python-s-setup-tools-and-pip) worked.
```
superset_app | INFO:werkzeug:172.18.0.1 - - [12/Aug/2020 22:09:09] "GET / HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | 127.0.0.1 - - [12/Aug/2020 22:09:20] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [12/Aug/2020 22:09:20] "GET /health HTTP/1.1" 200 -
```
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] thanwin edited a comment on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
thanwin edited a comment on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-683278397
same on fresh install ubuntu 18.04 LTS vm. install via github.
```
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:27] "GET /static/assets/images/favicon.png HTTP/1.1" 404 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:40] "POST /login/ HTTP/1.1" 302 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:40] "GET / HTTP/1.1" 302 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:41] "GET /superset/welcome HTTP/1.1" 200 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:41] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:52] "GET /superset/welcome HTTP/1.1" 200 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:52] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:28:54] "GET /superset/welcome HTTP/1.1" 200 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:28:54] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:33:57] "GET /superset HTTP/1.1" 404 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:33:57] "GET /favicon.ico HTTP/1.1" 404 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:34:05] "GET / HTTP/1.1" 302 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:34:05] "GET /superset/welcome HTTP/1.1" 200 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:34:05] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
```
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] siarcarse commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
siarcarse commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-679297535
Same here!. The problem was the amount of memory allocated to Docker. I increased ram and cpu and solved.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] nytai commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
nytai commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-730008125
We have switched over to using prebuilt images hosted on docker hub, see https://github.com/apache/incubator-superset/pull/11707
@korridor can you try pulling the latest master and running docker-compose again?
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] belal-mazlom edited a comment on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
belal-mazlom edited a comment on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-749204279
I found myself forced to enter to `superset-frontend` and run `npm run build`
To make assets available
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] korridor commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
korridor commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-730006565
I think I have the same problem I also get `ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/...` errors during the npm build.
I am using Docker Desktop 2.5.0.1 on Mac. I gave Docker 16GB RAM, 4GB Swap, 6 CPUs and more then enough disk space so I hope missing resources is not the problem.
This is the logfile:
[superset.log](https://github.com/apache/incubator-superset/files/5563182/superset.log)
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] andrewhaighcell commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
andrewhaighcell commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-709503173
I experienced the same kind of behaviour, restarted my docker machine vbox image with 4Gb memory and 2 cpus and left it for an hour or so. The static assets now appear to be present.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] heyhpython edited a comment on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
heyhpython edited a comment on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-744387028
superset_node container memory up to 4G solve this in my case
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] mistercrunch commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
mistercrunch commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-716987088
My guess is that given that the build operation is super io-heavy and that virtualization, depending the platform you're on (say docker on windows, or docker-in-docker, or whatever) can make certain io operations sluggish, and really slow down the build process. Looks like the `node_modules/` folder contains a quarter million files (!)
```bash
$ find superset-frontend/node_modules/ | wc -l
240901
```
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] heyhpython commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
heyhpython commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-744387028
superset_node container memory up to 4G solve this
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] nattapon4erudite edited a comment on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
nattapon4erudite edited a comment on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-704192198
Wait around 5 minutes until it stop printing on the screen, then you're all set. But it may use large amount of ram so you might increase docker ram to 16GB like others said.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] jinhuang11 edited a comment on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
jinhuang11 edited a comment on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-700160952
Worked for me now after reinstalling Docker, increasing Docker memory to 16GB, running "docker-compose up" and waiting for about 15 minutes after superset-frontend node_module build complete. Thanks for sharing the tips @guys.
The authentication is ready earlier in the process, the frontend along with all the super rich data/dashboard taking time to process, maybe a placeholder message in UI and server log will help
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] opzetto edited a comment on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
opzetto edited a comment on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-691636631
> I have experienced similar issue when trying to setup superset for the first time. Hopefully this could be resolved so we can lower the barrier for people who is excited about superset's potential
I am facing the same issue, may I ask how did you solve the problem?
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] belal-mazlom commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
belal-mazlom commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-749204279
I found myself forced to enter to `superset-frontend` and run `npm run build`
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] Lynnhan95 commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
Lynnhan95 commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-739444624
I have run into this issue, and it worked after installing the latest NPM and node.js.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] craig-rueda commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
craig-rueda commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-653687512
Could be related to the node modules volume? Try re-pulling master and re-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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] jinhuang11 commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
jinhuang11 commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-682116211
I also experienced the same issue when trying to deploy on my MacBook Pro. Tried a few things, no luck yet. Will keep trying. Any suggetions?
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] mistercrunch commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
mistercrunch commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-709387677
We've noticed in the past that building the javascript bundles is pretty io intensive and that docker in some context doesn't do io as well. OSx used to be pretty bad and things could degrade while in container-in-container mode. Unclear how Docker on Windows does with this. Unclear if that's the part of the issue or not, but something to keep in mind.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] zhenbo commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
zhenbo commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-681933996
I have experienced similar issue when trying to setup superset for the first time. Hopefully this could be resolved so we can lower the barrier for people who is excited about superset's potential
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] thanwin commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
thanwin commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-683278397
same on fresh install ubuntu 18.04 LTS vm. install via github.
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:27] "GET /static/assets/images/favicon.png HTTP/1.1" 404 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:40] "POST /login/ HTTP/1.1" 302 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:40] "GET / HTTP/1.1" 302 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:41] "GET /superset/welcome HTTP/1.1" 200 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:41] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:52] "GET /superset/welcome HTTP/1.1" 200 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:27:52] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:28:54] "GET /superset/welcome HTTP/1.1" 200 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:28:54] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:33:57] "GET /superset HTTP/1.1" 404 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:33:57] "GET /favicon.ico HTTP/1.1" 404 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:34:05] "GET / HTTP/1.1" 302 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:34:05] "GET /superset/welcome HTTP/1.1" 200 -
INFO:werkzeug:192.168.122.1 - - [29/Aug/2020 11:34:05] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] kaovilai commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
kaovilai commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-708718087
Facing similar issue on Ubuntu 20.04 LTS via WSL 2 on Docker for Windows with WSL 2 Integration
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] nattapon4erudite commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
nattapon4erudite commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-704192198
Wait around 5 minutes until you see this in terminal.
```
######################################################################
Init Step 4/4 [Complete] -- Loading examples
######################################################################
```
Then you're all set. But it may use large amount of ram so you might increase docker ram to 16GB like others said.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] siben168 commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
siben168 commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-712363719
> > Facing similar issue on Ubuntu 20.04 LTS via WSL 2 on Docker for Windows with WSL 2 Integration
>
> and.... fixed itself after a few hours.. of idling
That is amazing, i followed you and it worked after one hour waiting for some web packages installations. I've also used WSL2.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] PhucNgo1711 edited a comment on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
PhucNgo1711 edited a comment on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-673135532
I'm having this issue as well. This is my log. I also nuked the volumes, reran compose up, and pulled the lastest from master.
EDIT: Also got this issue when I followed [this](https://github.com/apache/incubator-superset/blob/master/CONTRIBUTING.md#flask-server)
```
superset_app | INFO:werkzeug:172.18.0.1 - - [12/Aug/2020 22:09:09] "GET / HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | 127.0.0.1 - - [12/Aug/2020 22:09:20] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [12/Aug/2020 22:09:20] "GET /health HTTP/1.1" 200 -
```
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] retbrown commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
retbrown commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-659471654
Try leaving it to run for about 5 - 10 minutes. I had the same issue but leaving it webpack started printing messages and eventually I was able to load it when webpack finished but took about 5 minutes locally
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] PhucNgo1711 edited a comment on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
PhucNgo1711 edited a comment on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-673135532
I'm having this issue as well. This is my log. I also nuked the volumes, reran compose up, and pulled the lastest from master.
```
superset_app | INFO:werkzeug:172.18.0.1 - - [12/Aug/2020 22:09:09] "GET / HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | 127.0.0.1 - - [12/Aug/2020 22:09:20] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [12/Aug/2020 22:09:20] "GET /health HTTP/1.1" 200 -
```
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] mistercrunch commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
mistercrunch commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-653685518
@craig-rueda , who has most context on our docker / docker-compose
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] nattapon4erudite edited a comment on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
nattapon4erudite edited a comment on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-704192198
Wait around 5 minutes until it stops printing on the screen, then you're all set. But it may use large amount of ram so you might increase docker ram to 16GB like others said.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] smirs commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
smirs commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-632378949
Solution: Isntalling `node.js` and `vpm`.
Action item: in the installation guide page, it needs to be added to install these packages. Specially because it doesn't directly get displayed in logs when trying to follow the current version of documentation here: https://superset.incubator.apache.org/installation.html#start-with-docker
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] rafaelugolini commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
rafaelugolini commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-714932365
I had the same issue, took around 7m for webpack to finish
```
superset_node | <s> [webpack.Progress] 100%
superset_node | No type errors found
superset_node | Version: typescript 3.8.3
superset_node | Time: 412075ms
superset_node |
superset_node | 8278 modules
```
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] cocodrino commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
cocodrino commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-639709882
@smirs Hi, sorry how did you install node and vpm?..I'm having the same problem, I notice that there are several containers
in my case I'm getting several logs indicating an issue with some npm dependencies
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] jvanulden commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
jvanulden commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-725784415
> It would be good to have official docker images from the project that don't require you to compile. Any newcomer who wants to try superset has to do all this compilation process to run the project.
>
> For anyone who wants to give it a try, here is a link to unofficial docker images:
>
> * https://github.com/amancevice/docker-superset
> * https://hub.docker.com/r/amancevice/superset/
I concur. This should be table stakes IMO.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] zhenbo removed a comment on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
zhenbo removed a comment on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-681059161
Same here
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] siben168 commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
siben168 commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-712343848
I've got exactly same blank page. From my case, i've also seen following errors from stage superset_init:
`superset_init | urllib.error.URLError: <urlopen error [Errno 99] Cannot assign requested address>`
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] imnot70 commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
imnot70 commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-691773942
same problem +1 again
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] kaovilai commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
kaovilai commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-709356240
>
>
> Facing similar issue on Ubuntu 20.04 LTS via WSL 2 on Docker for Windows with WSL 2 Integration
and.... fixed itself after a few hours.. of idling
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] korridor commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
korridor commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-730034744
@nytai Thanks now it's working! I was using the `master` instead of the `master-dev` tag for some reason.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] zhenbo commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
zhenbo commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-700162387
Thanks for the updates. I will bump up docker to 16GB and wait.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] PhucNgo1711 commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
PhucNgo1711 commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-673135532
I'm having this issue as well. This is my log.
```
superset_app | INFO:werkzeug:172.18.0.1 - - [12/Aug/2020 22:09:09] "GET / HTTP/1.1" 302 -
superset_app | 172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | INFO:werkzeug:172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /superset/welcome HTTP/1.1" 200 -
superset_app | 172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | INFO:werkzeug:172.18.0.1 - - [12/Aug/2020 22:09:09] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app | 127.0.0.1 - - [12/Aug/2020 22:09:20] "GET /health HTTP/1.1" 200 -
superset_app | INFO:werkzeug:127.0.0.1 - - [12/Aug/2020 22:09:20] "GET /health HTTP/1.1" 200 -
```
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] craig-rueda commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
craig-rueda commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-659477844
Thanks for reaching out, guys. We're aware of this lagginess when it comes
to the node container and are actively looking at it. Thanks again, and
stay tuned for updates!
-Craig
On Thu, Jul 16, 2020 at 8:03 AM Robert Brown <no...@github.com>
wrote:
> Try leaving it to run for about 5 - 10 minutes. I had the same issue but
> leaving it webpack started printing messages and eventually I was able to
> load it when webpack finished but took about 5 minutes locally
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/incubator-superset/issues/9880#issuecomment-659471654>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AATZTWYWTHUEZJRPHMEVG5DR34JD7ANCNFSM4NHHRZUA>
> .
>
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] nattapon4erudite edited a comment on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
nattapon4erudite edited a comment on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-704192198
Wait around 5 minutes until you see this in terminal.
```
superset_init | ######################################################################
superset_init |
superset_init | Init Step 4/4 [Complete] -- Loading examples
superset_init |
superset_init | ######################################################################
```
Then you're all set. But it may use large amount of ram so you might increase docker ram to 16GB like others said.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] chandresh-pancholi commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
chandresh-pancholi commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-653404112
Facing same issue with 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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] craig-rueda commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
craig-rueda commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-683323775
@thanwin - looks to me like you need to bump your Docker memory limits in order to allow for the `npm` build to run correctly. I see that all of the Flask-served requests are returning `200`, whereas the static assets aren't built.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] licx commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
licx commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-699713593
same problem
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] rafaelugolini commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
rafaelugolini commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-717042213
It would be good to have official docker images from the project that don't require you to compile. Any newcomer who wants to try superset has to do all this compilation process to run the project.
For anyone who wants to give it a try, here is a link to unofficial docker images:
- https://github.com/amancevice/docker-superset
- https://hub.docker.com/r/amancevice/superset/
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] licx commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
licx commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-699717213
I solved it by:
1) Bumping Docker memory to 16GB (not 100% sure if helped since I already had 8gb there)
2) Running `docker-compose up` and wait 10 minutes until Webpack kicked off the build
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] opzetto commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
opzetto commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-691636631
> I have experienced similar issue when trying to setup superset for the first time. Hopefully this could be resolved so we can lower the barrier for people who is excited about superset's potential
May I ask how did you solve the problem?
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [incubator-superset] jinhuang11 commented on issue #9880: Installing Superset via Docker-compose Up
Posted by GitBox <gi...@apache.org>.
jinhuang11 commented on issue #9880:
URL: https://github.com/apache/incubator-superset/issues/9880#issuecomment-700160952
Worked for me now after reinstalling Docker, increasing Docker memory to 16GB, running "docker-compose up" and waiting for about 15 minutes after superset-frontend node_module build complete.
----------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org