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 2021/10/01 16:55:18 UTC

[GitHub] [superset] JimCallahanOrlando commented on issue #16922: Windows 10 WSL2 Ubuntu 20.04 LTS $ docker-compose-non-dev.yml up (failed)

JimCallahanOrlando commented on issue #16922:
URL: https://github.com/apache/superset/issues/16922#issuecomment-932392352


   Here is a more complete command log:
   
   $ docker-compose -f docker-compose-non-dev.yml up
   [+] Running 7/7
    ⠿ Network superset_default        Created                                                                                                             1.1s
    ⠿ Container superset_cache        Created                                                                                                             2.5s
    ⠿ Container superset_db           Created                                                                                                             2.4s
    ⠿ Container superset_app          Created                                                                                                             2.6s
    ⠿ Container superset_worker       Created                                                                                                             2.7s
    ⠿ Container superset_worker_beat  Created                                                                                                             2.7s
    ⠿ Container superset_init         Created                                                                                                             2.6s
   Attaching to superset_app, superset_cache, superset_db, superset_init, superset_worker, superset_worker_beat
   superset_db           |
   superset_db           | PostgreSQL Database directory appears to contain a database; Skipping initialization
   superset_db           |
   superset_cache        | 1:C 01 Oct 2021 16:40:50.554 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
   superset_cache        | 1:C 01 Oct 2021 16:40:50.555 # Redis version=6.2.5, bits=64, commit=00000000, modified=0, pid=1, just started
   superset_cache        | 1:C 01 Oct 2021 16:40:50.555 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
   superset_cache        | 1:M 01 Oct 2021 16:40:50.556 * monotonic clock: POSIX clock_gettime
   superset_cache        | 1:M 01 Oct 2021 16:40:50.560 * Running mode=standalone, port=6379.
   superset_cache        | 1:M 01 Oct 2021 16:40:50.560 # Server initialized
   superset_cache        | 1:M 01 Oct 2021 16:40:50.560 # 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 01 Oct 2021 16:40:50.583 * Loading RDB produced by version 6.2.5
   superset_cache        | 1:M 01 Oct 2021 16:40:50.584 * RDB age 72121 seconds
   superset_cache        | 1:M 01 Oct 2021 16:40:50.584 * RDB memory usage when created 8.99 Mb
   superset_cache        | 1:M 01 Oct 2021 16:40:51.826 * DB loaded from disk: 1.243 seconds
   superset_cache        | 1:M 01 Oct 2021 16:40:51.826 * Ready to accept connections
   superset_db           | 2021-10-01 16:40:51.951 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
   superset_db           | 2021-10-01 16:40:51.951 UTC [1] LOG:  listening on IPv6 address "::", port 5432
   superset_db           | 2021-10-01 16:40:52.305 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
   superset_db           | 2021-10-01 16:40:53.076 UTC [27] LOG:  database system was shut down at 2021-09-30 20:38:50 UTC
   superset_db           | 2021-10-01 16:40:53.740 UTC [1] LOG:  database system is ready to accept connections
   superset_init         | Skipping local overrides
   superset_init         |
   superset_init         | ######################################################################
   superset_init         |
   superset_init         |
   superset_init         | Init Step 1/4 [Starting] -- Applying DB migrations
   superset_init         |
   superset_init         |
   superset_init         | ######################################################################
   superset_init         |
   superset_worker_beat  | Skipping local overrides
   superset_worker_beat  | Starting Celery beat...
   superset_worker       | Skipping local overrides
   superset_worker       | Starting Celery worker...
   superset_app          | Skipping local overrides
   superset_app          | Starting web app...
   superset_app          | [2021-10-01 16:41:04 +0000] [8] [INFO] Starting gunicorn 20.0.4
   superset_app          | [2021-10-01 16:41:04 +0000] [8] [INFO] Listening at: http://0.0.0.0:8088 (8)
   superset_app          | [2021-10-01 16:41:04 +0000] [8] [INFO] Using worker: gthread
   superset_app          | [2021-10-01 16:41:04 +0000] [11] [INFO] Booting worker with pid: 11
   superset_app          | logging was configured successfully
   superset_app          | 2021-10-01 16:41:10,802:INFO:superset.utils.logging_configurator:logging was configured successfully
   superset_app          | 2021-10-01 16:41:10,813:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
   superset_worker_beat  | logging was configured successfully
   superset_worker_beat  | 2021-10-01 16:41:10,813:INFO:superset.utils.logging_configurator:logging was configured successfully
   superset_worker       | logging was configured successfully
   superset_worker       | 2021-10-01 16:41:10,839:INFO:superset.utils.logging_configurator:logging was configured successfully
   superset_worker_beat  | 2021-10-01 16:41:10,842:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
   superset_worker       | 2021-10-01 16:41:10,849:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
   superset_init         | logging was configured successfully
   superset_init         | 2021-10-01 16:41:12,096:INFO:superset.utils.logging_configurator:logging was configured successfully
   superset_init         | 2021-10-01 16:41:12,104:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
   superset_init         | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:202: 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_worker_beat  | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:202: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
   superset_worker_beat  |   "Flask-Caching: CACHE_TYPE is set to null, "
   superset_worker_beat  | [2021-10-01 16:41:16,721: INFO/MainProcess] beat: Starting...
   superset_worker_beat  | [2021-10-01 16:41:17,307: INFO/MainProcess] Scheduler: Sending due task reports.prune_log (reports.prune_log)
   superset_worker_beat  | [2021-10-01 16:41:17,518: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
   superset_init         | INFO  [alembic.runtime.migration] Running upgrade  -> 4e6a06bad7a8, Init
   superset_worker       | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:202: 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       | /usr/local/lib/python3.7/site-packages/celery/platforms.py:801: RuntimeWarning: You're running the worker with superuser privileges: this is
   superset_worker       | absolutely not recommended!
   superset_worker       |
   superset_worker       | Please specify a different user using the --uid option.
   superset_worker       |
   superset_worker       | User information: uid=0 euid=0 gid=0 egid=0
   superset_worker       |
   superset_worker       |   uid=uid, euid=euid, gid=gid, egid=egid,
   superset_worker       | [2021-10-01 16:41:19,079: INFO/MainProcess] Connected to redis://redis:6379/0
   superset_worker       | [2021-10-01 16:41:19,087: INFO/MainProcess] mingle: searching for neighbors
   superset_worker       | [2021-10-01 16:41:20,107: INFO/MainProcess] mingle: all alone
   superset_worker       | [2021-10-01 16:41:20,132: INFO/MainProcess] celery@c785757d9879 ready.
   superset_worker       | [2021-10-01 16:41:20,138: INFO/MainProcess] Received task: reports.prune_log[8ee96b8a-643e-42c2-ba47-bbed7efb56c6]
   superset_worker       | [2021-10-01 16:41:20,141: INFO/MainProcess] Received task: reports.scheduler[3ad19f0e-23d7-4322-bbcd-8558baa19f9e]
   superset_db           | 2021-10-01 16:41:20.243 UTC [39] ERROR:  relation "report_schedule" does not exist at character 1627
   superset_db           | 2021-10-01 16:41:20.243 UTC [39] STATEMENT:  SELECT report_schedule.created_on AS report_schedule_created_on, report_schedule.changed_on AS report_schedule_changed_on, report_schedule.id AS report_schedule_id, report_schedule.type AS report_schedule_type, report_schedule.name AS report_schedule_name, report_schedule.description AS report_schedule_description, report_schedule.context_markdown AS report_schedule_context_markdown, report_schedule.active AS report_schedule_active, report_schedule.crontab AS report_schedule_crontab, report_schedule.creation_method AS report_schedule_creation_method, report_schedule.timezone AS report_schedule_timezone, report_schedule.report_format AS report_schedule_report_format, report_schedule.sql AS report_schedule_sql, report_schedule.chart_id AS report_schedule_chart_id, report_schedule.dashboard_id AS report_schedule_dashboard_id, report_schedule.database_id AS report_schedule_database_id, report_schedule.last_eval_dttm 
 AS report_schedule_last_eval_dttm, report_schedule.last_state AS report_schedule_last_state, report_schedule.last_value AS report_schedule_last_value, report_schedule.last_value_row_json AS report_schedule_last_value_row_json, report_schedule.validator_type AS report_schedule_validator_type, report_schedule.validator_config_json AS report_schedule_validator_config_json, report_schedule.log_retention AS report_schedule_log_retention, report_schedule.grace_period AS report_schedule_grace_period, report_schedule.working_timeout AS report_schedule_working_timeout, report_schedule.created_by_fk AS report_schedule_created_by_fk, report_schedule.changed_by_fk AS report_schedule_changed_by_fk
   superset_db           |         FROM report_schedule
   superset_db           | 2021-10-01 16:41:20.246 UTC [40] ERROR:  relation "report_schedule" does not exist at character 1627 [REPEATS "report_schedule" does not exist  set of error messages]
   


-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

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