Skip to content

fix(cron): Fix cron scripts#103

Merged
xmnlab merged 14 commits intothegraphnetwork:mainfrom
xmnlab:fix-cron-scripts
Jun 8, 2022
Merged

fix(cron): Fix cron scripts#103
xmnlab merged 14 commits intothegraphnetwork:mainfrom
xmnlab:fix-cron-scripts

Conversation

@xmnlab
Copy link
Copy Markdown
Member

@xmnlab xmnlab commented May 24, 2022

No description provided.

@xmnlab
Copy link
Copy Markdown
Member Author

xmnlab commented May 24, 2022 •
edited
Loading

@eduardocorrearaujo
I run the colombia.sh script and it raised this error:

docker-compose --env-file .env --project-name eph-prod --file docker/compose-base.yaml --file docker/compose-prod.yaml exec -T epigraphhub-superset bash \
        /opt/EpiGraphHub/Data_Collection/CRON_scripts/colombia.sh
[II] conda env activated.
Traceback (most recent call last):
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context
    self.dialect.do_execute(
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 608, in do_execute
    cursor.execute(statement, parameters)
psycopg2.errors.InvalidColumnReference: there is no unique or exclusion constraint matching the ON CONFLICT specification

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "colombia_data.py", line 116, in <module>
    load_into_db(client)
  File "colombia_data.py", line 100, in load_into_db
    upsert(
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/pangres/core.py", line 301, in upsert
    executor.execute(connectable=con, if_row_exists=if_row_exists, chunksize=chunksize)
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/pangres/executor.py", line 87, in execute
    pse.upsert(if_row_exists=if_row_exists, chunksize=chunksize)
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/pangres/engine.py", line 512, in upsert
    upq.execute(db_type=self._db_type, values=chunk, if_row_exists=if_row_exists)
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/pangres/upsert_query.py", line 180, in execute
    return self.connection.execute(query)
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1011, in execute
    return meth(self, multiparams, params)
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection
    return connection._execute_clauseelement(self, multiparams, params)
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1124, in _execute_clauseelement
    ret = self._execute_context(
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1316, in _execute_context
    self._handle_dbapi_exception(
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1510, in _handle_dbapi_exception
    util.raise_(
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_
    raise exception
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context
    self.dialect.do_execute(
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 608, in do_execute
    cursor.execute(statement, parameters)
sqlalchemy.exc.ProgrammingError: (psycopg2.errors.InvalidColumnReference) there is no unique or exclusion constraint matching the ON CONFLICT specification

any idea?

this is the command I ran:

make docker-cron ENV=prod CRON=colombia.sh &> /tmp/services.log

@xmnlab xmnlab requested a review from eduardocorrearaujo May 24, 2022 03:22
@xmnlab xmnlab marked this pull request as ready for review May 24, 2022 03:22
@fccoelho
Copy link
Copy Markdown
Contributor

fccoelho commented May 24, 2022

That's because the argument to ON CONFLICT clause in SQL requires an unique index to define the conflict. So the SQL code needs to be changed.

https://www.postgresql.org/docs/current/sql-insert.html#SQL-ON-CONFLICT

fccoelho
fccoelho reviewed May 24, 2022
View reviewed changes
Comment thread Data_Collection/CRON_scripts/colombia_data.py
logger.info('table casos_positivos_covid updated')


upsert(
Copy link
Copy Markdown
Contributor

@fccoelho fccoelho May 24, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the "on conflict update" is being done by Pangres upsert function, we need to know how it is doing it or switch to doing it ourselves using plain SQL.

@eduardocorrearaujo
Copy link
Copy Markdown
Contributor

eduardocorrearaujo commented May 24, 2022

@eduardocorrearaujo I run the colombia.sh script and it raised this error:

docker-compose --env-file .env --project-name eph-prod --file docker/compose-base.yaml --file docker/compose-prod.yaml exec -T epigraphhub-superset bash \
        /opt/EpiGraphHub/Data_Collection/CRON_scripts/colombia.sh
[II] conda env activated.
Traceback (most recent call last):
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context
    self.dialect.do_execute(
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 608, in do_execute
    cursor.execute(statement, parameters)
psycopg2.errors.InvalidColumnReference: there is no unique or exclusion constraint matching the ON CONFLICT specification

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "colombia_data.py", line 116, in <module>
    load_into_db(client)
  File "colombia_data.py", line 100, in load_into_db
    upsert(
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/pangres/core.py", line 301, in upsert
    executor.execute(connectable=con, if_row_exists=if_row_exists, chunksize=chunksize)
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/pangres/executor.py", line 87, in execute
    pse.upsert(if_row_exists=if_row_exists, chunksize=chunksize)
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/pangres/engine.py", line 512, in upsert
    upq.execute(db_type=self._db_type, values=chunk, if_row_exists=if_row_exists)
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/pangres/upsert_query.py", line 180, in execute
    return self.connection.execute(query)
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1011, in execute
    return meth(self, multiparams, params)
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection
    return connection._execute_clauseelement(self, multiparams, params)
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1124, in _execute_clauseelement
    ret = self._execute_context(
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1316, in _execute_context
    self._handle_dbapi_exception(
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1510, in _handle_dbapi_exception
    util.raise_(
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_
    raise exception
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context
    self.dialect.do_execute(
  File "/opt/conda/envs/epigraphhub/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 608, in do_execute
    cursor.execute(statement, parameters)
sqlalchemy.exc.ProgrammingError: (psycopg2.errors.InvalidColumnReference) there is no unique or exclusion constraint matching the ON CONFLICT specification

any idea?

this is the command I ran:

make docker-cron ENV=prod CRON=colombia.sh &> /tmp/services.log

I will take a look at it, thank you.

@eduardocorrearaujo
Copy link
Copy Markdown
Contributor

eduardocorrearaujo commented May 25, 2022

Hi, @xmnlab and @fccoelho. I think this problem is being caused by a difference in the types of the column in the database and of the new data. I think tomorrow I will be able to take a look on that and solve it.

@xmnlab
Copy link
Copy Markdown
Member Author

xmnlab commented May 25, 2022

@eduardocorrearaujo thank you so much!

@eduardocorrearaujo eduardocorrearaujo mentioned this pull request May 30, 2022
Merged
@xmnlab xmnlab force-pushed the fix-cron-scripts branch from 28e55b2 to 441b81e Compare June 1, 2022 03:32
@xmnlab xmnlab force-pushed the fix-cron-scripts branch from 441b81e to 61991ef Compare June 1, 2022 14:49
@xmnlab
Copy link
Copy Markdown
Member Author

xmnlab commented Jun 1, 2022

log:

docker-compose --env-file .env --project-name eph-dev --file docker/compose-base.yaml --file docker/compose-dev.yaml logs --tail 300 
Attaching to eph-dev_epigraphhub-superset_1, eph-dev_epigraphhub-celery_1, eph-dev_epigraphhub-celery-beat_1, eph-dev_epigraphhub-flower_1, eph-dev_epigraphhub-db_1, eph-dev_epigraphhub-redis_1
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:35,883:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:35,999:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:36,006:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:36,013:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:36,036:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:42,048:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:42,063:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:42,072:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:42,082:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:42,097:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:47,857:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:47,869:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:47,871:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:47,874:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:47,888:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:53,430:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:53,437:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:53,440:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:53,443:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:53,457:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:58,786:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:58,795:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:58,797:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:58,805:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:38:58,821:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:05,367:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:05,375:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:05,377:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:05,381:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:05,395:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:13,002:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:13,010:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:13,012:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:13,016:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:13,031:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:23,857:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:23,864:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:23,867:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:23,870:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:23,885:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:40,441:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:40,448:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:40,450:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:40,454:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:39:40,469:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:40:09,056:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:40:09,063:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:40:09,066:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:40:09,069:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:40:09,083:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:41:03,240:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:41:03,247:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:41:03,250:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:41:03,253:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:41:03,268:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:42:06,065:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:42:06,073:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:42:06,075:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:42:06,078:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:42:06,092:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[36mepigraphhub-celery-beat_1  |�[0m [II] activate epigraphhub (celery)
�[36mepigraphhub-celery-beat_1  |�[0m logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:43:08,703:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:43:08,711:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:43:08,713:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:43:08,717:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36mepigraphhub-celery-beat_1  |�[0m 2022-06-01 15:43:08,732:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36mepigraphhub-celery-beat_1  |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36mepigraphhub-celery-beat_1  |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:35,200:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:35,321:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:35,329:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:35,336:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:35,351:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:41,635:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:41,642:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:41,653:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:41,657:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:41,681:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:47,350:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:47,357:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:47,360:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:47,363:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:47,377:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:52,531:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:52,539:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:52,541:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:52,545:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:52,559:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:58,179:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:58,189:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:58,191:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:58,196:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:38:58,216:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:04,652:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:04,659:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:04,667:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:04,673:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:04,697:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:11,977:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:11,984:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:11,987:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:11,990:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:12,005:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:22,211:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:22,222:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:22,226:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:22,234:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:22,251:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:37,815:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:37,822:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:37,824:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:37,827:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:39:37,841:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:40:05,954:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:40:05,958:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:40:05,960:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:40:05,962:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:40:05,971:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:40:59,469:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:40:59,473:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:40:59,475:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:40:59,477:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:40:59,486:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:42:01,794:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:42:01,799:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:42:01,801:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:42:01,803:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:42:01,812:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[33mepigraphhub-celery_1       |�[0m [II] activate epigraphhub (celery)
�[33mepigraphhub-celery_1       |�[0m logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:43:04,163:INFO:superset.utils.logging_configurator:logging was configured successfully
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:43:04,167:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:43:04,169:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:43:04,171:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[33mepigraphhub-celery_1       |�[0m 2022-06-01 15:43:04,180:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[33mepigraphhub-celery_1       |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[33mepigraphhub-celery_1       |�[0m /opt/entrypoint.sh: line 16: Loaded: command not found
�[32mepigraphhub-db_1           |�[0m The files belonging to this database system will be owned by user "postgres".
�[32mepigraphhub-db_1           |�[0m This user must also own the server process.
�[32mepigraphhub-db_1           |�[0m 
�[32mepigraphhub-db_1           |�[0m The database cluster will be initialized with locale "en_US.utf8".
�[32mepigraphhub-db_1           |�[0m The default database encoding has accordingly been set to "UTF8".
�[32mepigraphhub-db_1           |�[0m The default text search configuration will be set to "english".
�[32mepigraphhub-db_1           |�[0m 
�[32mepigraphhub-db_1           |�[0m Data page checksums are disabled.
�[32mepigraphhub-db_1           |�[0m 
�[32mepigraphhub-db_1           |�[0m fixing permissions on existing directory /var/lib/postgresql/data ... ok
�[32mepigraphhub-db_1           |�[0m creating subdirectories ... ok
�[32mepigraphhub-db_1           |�[0m selecting dynamic shared memory implementation ... posix
�[32mepigraphhub-db_1           |�[0m selecting default max_connections ... 100
�[32mepigraphhub-db_1           |�[0m selecting default shared_buffers ... 128MB
�[32mepigraphhub-db_1           |�[0m selecting default time zone ... Etc/UTC
�[32mepigraphhub-db_1           |�[0m creating configuration files ... ok
�[32mepigraphhub-db_1           |�[0m running bootstrap script ... ok
�[32mepigraphhub-db_1           |�[0m performing post-bootstrap initialization ... ok
�[32mepigraphhub-db_1           |�[0m syncing data to disk ... ok
�[32mepigraphhub-db_1           |�[0m 
�[32mepigraphhub-db_1           |�[0m 
�[32mepigraphhub-db_1           |�[0m Success. You can now start the database server using:
�[32mepigraphhub-db_1           |�[0m 
�[32mepigraphhub-db_1           |�[0m     pg_ctl -D /var/lib/postgresql/data -l logfile start
�[32mepigraphhub-db_1           |�[0m 
�[32mepigraphhub-db_1           |�[0m initdb: warning: enabling "trust" authentication for local connections
�[32mepigraphhub-db_1           |�[0m You can change this by editing pg_hba.conf or using the option -A, or
�[32mepigraphhub-db_1           |�[0m --auth-local and --auth-host, the next time you run initdb.
�[32mepigraphhub-db_1           |�[0m waiting for server to start....2022-06-01 15:38:23.035 UTC [48] LOG:  starting PostgreSQL 14.3 (Debian 14.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:23.049 UTC [48] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:23.065 UTC [49] LOG:  database system was shut down at 2022-06-01 15:38:22 UTC
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:23.073 UTC [48] LOG:  database system is ready to accept connections
�[32mepigraphhub-db_1           |�[0m  done
�[32mepigraphhub-db_1           |�[0m server started
�[32mepigraphhub-db_1           |�[0m 
�[32mepigraphhub-db_1           |�[0m /usr/local/bin/docker-entrypoint.sh: sourcing /docker-entrypoint-initdb.d/10_postgis.sh
�[32mepigraphhub-db_1           |�[0m CREATE DATABASE
�[32mepigraphhub-db_1           |�[0m Loading PostGIS extensions into template_postgis
�[32mepigraphhub-db_1           |�[0m CREATE EXTENSION
�[32mepigraphhub-db_1           |�[0m CREATE EXTENSION
�[32mepigraphhub-db_1           |�[0m You are now connected to database "template_postgis" as user "postgres".
�[32mepigraphhub-db_1           |�[0m CREATE EXTENSION
�[32mepigraphhub-db_1           |�[0m CREATE EXTENSION
�[32mepigraphhub-db_1           |�[0m Loading PostGIS extensions into postgres
�[32mepigraphhub-db_1           |�[0m CREATE EXTENSION
�[32mepigraphhub-db_1           |�[0m CREATE EXTENSION
�[32mepigraphhub-db_1           |�[0m You are now connected to database "postgres" as user "postgres".
�[32mepigraphhub-db_1           |�[0m CREATE EXTENSION
�[32mepigraphhub-db_1           |�[0m CREATE EXTENSION
�[32mepigraphhub-db_1           |�[0m 
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:29.620 UTC [48] LOG:  received fast shutdown request
�[32mepigraphhub-db_1           |�[0m waiting for server to shut down....2022-06-01 15:38:29.621 UTC [48] LOG:  aborting any active transactions
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:29.623 UTC [48] LOG:  background worker "logical replication launcher" (PID 55) exited with exit code 1
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:29.643 UTC [50] LOG:  shutting down
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:29.957 UTC [48] LOG:  database system is shut down
�[32mepigraphhub-db_1           |�[0m  done
�[32mepigraphhub-db_1           |�[0m server stopped
�[32mepigraphhub-db_1           |�[0m 
�[32mepigraphhub-db_1           |�[0m PostgreSQL init process complete; ready for start up.
�[32mepigraphhub-db_1           |�[0m 
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:30.058 UTC [1] LOG:  starting PostgreSQL 14.3 (Debian 14.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:30.062 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 25432
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:30.062 UTC [1] LOG:  listening on IPv6 address "::", port 25432
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:30.074 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.25432"
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:30.078 UTC [77] LOG:  database system was shut down at 2022-06-01 15:38:29 UTC
�[32mepigraphhub-db_1           |�[0m 2022-06-01 15:38:30.084 UTC [1] LOG:  database system is ready to accept connections
�[35mepigraphhub-flower_1       |�[0m [I 220601 15:38:21 command:135] Visit me at http://localhost:8888
�[35mepigraphhub-flower_1       |�[0m [I 220601 15:38:21 command:142] Broker: redis://redis:6379/0
�[35mepigraphhub-flower_1       |�[0m [I 220601 15:38:21 command:143] Registered tasks: 
�[35mepigraphhub-flower_1       |�[0m     ['celery.accumulate',
�[35mepigraphhub-flower_1       |�[0m      'celery.backend_cleanup',
�[35mepigraphhub-flower_1       |�[0m      'celery.chain',
�[35mepigraphhub-flower_1       |�[0m      'celery.chord',
�[35mepigraphhub-flower_1       |�[0m      'celery.chord_unlock',
�[35mepigraphhub-flower_1       |�[0m      'celery.chunks',
�[35mepigraphhub-flower_1       |�[0m      'celery.group',
�[35mepigraphhub-flower_1       |�[0m      'celery.map',
�[35mepigraphhub-flower_1       |�[0m      'celery.starmap']
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:36,636:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:36,665:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:36,670:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:36,676:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:36,688:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:42,910:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:42,919:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:42,922:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:42,926:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:42,941:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:48,665:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:48,684:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:48,686:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:48,690:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:48,715:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:54,826:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:54,843:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:54,845:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:54,850:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:38:54,881:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:00,494:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:00,510:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:00,516:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:00,519:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:00,552:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:06,840:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:06,846:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:06,847:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:06,850:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:06,859:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:14,124:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:14,129:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:14,131:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:14,133:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:14,143:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:24,878:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:24,884:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:24,885:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:24,888:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:24,897:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:41,452:INFO:superset.utils.logging_configurator:logging was configured successfully
�[34mepigraphhub-redis_1        |�[0m 1:C 01 Jun 2022 15:38:17.533 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
�[34mepigraphhub-redis_1        |�[0m 1:C 01 Jun 2022 15:38:17.533 # Redis version=7.0.0, bits=64, commit=00000000, modified=0, pid=1, just started
�[34mepigraphhub-redis_1        |�[0m 1:C 01 Jun 2022 15:38:17.533 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
�[34mepigraphhub-redis_1        |�[0m 1:M 01 Jun 2022 15:38:17.533 * monotonic clock: POSIX clock_gettime
�[34mepigraphhub-redis_1        |�[0m 1:M 01 Jun 2022 15:38:17.534 * Running mode=standalone, port=6379.
�[34mepigraphhub-redis_1        |�[0m 1:M 01 Jun 2022 15:38:17.534 # Server initialized
�[34mepigraphhub-redis_1        |�[0m 1:M 01 Jun 2022 15:38:17.534 # 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.
�[34mepigraphhub-redis_1        |�[0m 1:M 01 Jun 2022 15:38:17.534 * The AOF directory appendonlydir doesn't exist
�[34mepigraphhub-redis_1        |�[0m 1:M 01 Jun 2022 15:38:17.534 * Ready to accept connections
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:41,458:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:41,459:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:41,462:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:39:41,471:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:40:10,350:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:40:10,356:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:40:10,357:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:40:10,359:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:40:10,369:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:41:04,836:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:41:04,841:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:41:04,843:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:41:04,845:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:41:04,855:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:42:07,870:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:42:07,876:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:42:07,877:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:42:07,880:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:42:07,889:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found
�[36;1mepigraphhub-superset_1     |�[0m [II] activate epigraphhub
�[36;1mepigraphhub-superset_1     |�[0m + export FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + FLASK_APP=superset
�[36;1mepigraphhub-superset_1     |�[0m + superset db upgrade
�[36;1mepigraphhub-superset_1     |�[0m logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:43:10,832:INFO:superset.utils.logging_configurator:logging was configured successfully
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:43:10,838:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:43:10,839:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:43:10,842:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
�[36;1mepigraphhub-superset_1     |�[0m 2022-06-01 15:43:10,851:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (sqlite3.OperationalError) unable to open database file
�[36;1mepigraphhub-superset_1     |�[0m (Background on this error at: http://sqlalche.me/e/13/e3q8)
�[36;1mepigraphhub-superset_1     |�[0m /opt/entrypoint.sh: line 27: Loaded: command not found

@xmnlab
Copy link
Copy Markdown
Member Author

xmnlab commented Jun 1, 2022

I managed to replicate this problem changing the local environment variables.
investigating that now

@xmnlab xmnlab mentioned this pull request Jun 3, 2022
Closed
@xmnlab
Copy link
Copy Markdown
Member Author

xmnlab commented Jun 3, 2022

Just missing the CI part. it seems that it is a problem with environment variables. hope to have this merged later today

@xmnlab
Copy link
Copy Markdown
Member Author

xmnlab commented Jun 8, 2022

thanks for the review @fccoelho

@xmnlab xmnlab merged commit c2d3129 into thegraphnetwork:main Jun 8, 2022
@xmnlab xmnlab deleted the fix-cron-scripts branch June 8, 2022 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@fccoelho fccoelho fccoelho approved these changes

@eduardocorrearaujo eduardocorrearaujo Awaiting requested review from eduardocorrearaujo

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@xmnlab @fccoelho @eduardocorrearaujo