thegraphnetwork / EpiGraphHub

Software platform to Gather, transmform, harmonize and store epidemiological data for analytical purposes.
https://epigraphhub.org
GNU General Public License v3.0
8 stars 10 forks source link

fix(cron): Fix cron scripts #103

Closed xmnlab closed 2 years ago

xmnlab commented 2 years ago

@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
fccoelho commented 2 years ago

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

eduardocorrearaujo commented 2 years ago

@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 commented 2 years ago

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 commented 2 years ago

@eduardocorrearaujo thank you so much!

xmnlab commented 2 years ago

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
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:38:35,883:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:38:35,999:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:38:42,048:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:38:42,063:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:38:47,857:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:38:47,869:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:38:53,430:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:38:53,437:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:38:58,786:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:38:58,795:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:39:05,367:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:39:05,375:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:39:13,002:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:39:13,010:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:39:23,857:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:39:23,864:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:39:40,441:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:39:40,448:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:40:09,056:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:40:09,063:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:41:03,240:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:41:03,247:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:42:06,065:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:42:06,073:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery-beat_1  | [II] activate epigraphhub (celery)
epigraphhub-celery-beat_1  | logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:43:08,703:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery-beat_1  | 2022-06-01 15:43:08,711:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | 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
epigraphhub-celery-beat_1  | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery-beat_1  | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:38:35,200:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:38:35,321:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:38:41,635:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:38:41,642:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:38:47,350:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:38:47,357:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:38:52,531:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:38:52,539:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:38:58,179:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:38:58,189:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:39:04,652:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:39:04,659:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:39:11,977:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:39:11,984:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:39:22,211:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:39:22,222:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:39:37,815:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:39:37,822:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:40:05,954:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:40:05,958:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:40:59,469:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:40:59,473:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:42:01,794:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:42:01,799:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-celery_1       | [II] activate epigraphhub (celery)
epigraphhub-celery_1       | logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:43:04,163:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-celery_1       | 2022-06-01 15:43:04,167:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | 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
epigraphhub-celery_1       | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-celery_1       | /opt/entrypoint.sh: line 16: Loaded: command not found
epigraphhub-db_1           | The files belonging to this database system will be owned by user "postgres".
epigraphhub-db_1           | This user must also own the server process.
epigraphhub-db_1           | 
epigraphhub-db_1           | The database cluster will be initialized with locale "en_US.utf8".
epigraphhub-db_1           | The default database encoding has accordingly been set to "UTF8".
epigraphhub-db_1           | The default text search configuration will be set to "english".
epigraphhub-db_1           | 
epigraphhub-db_1           | Data page checksums are disabled.
epigraphhub-db_1           | 
epigraphhub-db_1           | fixing permissions on existing directory /var/lib/postgresql/data ... ok
epigraphhub-db_1           | creating subdirectories ... ok
epigraphhub-db_1           | selecting dynamic shared memory implementation ... posix
epigraphhub-db_1           | selecting default max_connections ... 100
epigraphhub-db_1           | selecting default shared_buffers ... 128MB
epigraphhub-db_1           | selecting default time zone ... Etc/UTC
epigraphhub-db_1           | creating configuration files ... ok
epigraphhub-db_1           | running bootstrap script ... ok
epigraphhub-db_1           | performing post-bootstrap initialization ... ok
epigraphhub-db_1           | syncing data to disk ... ok
epigraphhub-db_1           | 
epigraphhub-db_1           | 
epigraphhub-db_1           | Success. You can now start the database server using:
epigraphhub-db_1           | 
epigraphhub-db_1           |     pg_ctl -D /var/lib/postgresql/data -l logfile start
epigraphhub-db_1           | 
epigraphhub-db_1           | initdb: warning: enabling "trust" authentication for local connections
epigraphhub-db_1           | You can change this by editing pg_hba.conf or using the option -A, or
epigraphhub-db_1           | --auth-local and --auth-host, the next time you run initdb.
epigraphhub-db_1           | 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
epigraphhub-db_1           | 2022-06-01 15:38:23.049 UTC [48] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
epigraphhub-db_1           | 2022-06-01 15:38:23.065 UTC [49] LOG:  database system was shut down at 2022-06-01 15:38:22 UTC
epigraphhub-db_1           | 2022-06-01 15:38:23.073 UTC [48] LOG:  database system is ready to accept connections
epigraphhub-db_1           |  done
epigraphhub-db_1           | server started
epigraphhub-db_1           | 
epigraphhub-db_1           | /usr/local/bin/docker-entrypoint.sh: sourcing /docker-entrypoint-initdb.d/10_postgis.sh
epigraphhub-db_1           | CREATE DATABASE
epigraphhub-db_1           | Loading PostGIS extensions into template_postgis
epigraphhub-db_1           | CREATE EXTENSION
epigraphhub-db_1           | CREATE EXTENSION
epigraphhub-db_1           | You are now connected to database "template_postgis" as user "postgres".
epigraphhub-db_1           | CREATE EXTENSION
epigraphhub-db_1           | CREATE EXTENSION
epigraphhub-db_1           | Loading PostGIS extensions into postgres
epigraphhub-db_1           | CREATE EXTENSION
epigraphhub-db_1           | CREATE EXTENSION
epigraphhub-db_1           | You are now connected to database "postgres" as user "postgres".
epigraphhub-db_1           | CREATE EXTENSION
epigraphhub-db_1           | CREATE EXTENSION
epigraphhub-db_1           | 
epigraphhub-db_1           | 2022-06-01 15:38:29.620 UTC [48] LOG:  received fast shutdown request
epigraphhub-db_1           | waiting for server to shut down....2022-06-01 15:38:29.621 UTC [48] LOG:  aborting any active transactions
epigraphhub-db_1           | 2022-06-01 15:38:29.623 UTC [48] LOG:  background worker "logical replication launcher" (PID 55) exited with exit code 1
epigraphhub-db_1           | 2022-06-01 15:38:29.643 UTC [50] LOG:  shutting down
epigraphhub-db_1           | 2022-06-01 15:38:29.957 UTC [48] LOG:  database system is shut down
epigraphhub-db_1           |  done
epigraphhub-db_1           | server stopped
epigraphhub-db_1           | 
epigraphhub-db_1           | PostgreSQL init process complete; ready for start up.
epigraphhub-db_1           | 
epigraphhub-db_1           | 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
epigraphhub-db_1           | 2022-06-01 15:38:30.062 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 25432
epigraphhub-db_1           | 2022-06-01 15:38:30.062 UTC [1] LOG:  listening on IPv6 address "::", port 25432
epigraphhub-db_1           | 2022-06-01 15:38:30.074 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.25432"
epigraphhub-db_1           | 2022-06-01 15:38:30.078 UTC [77] LOG:  database system was shut down at 2022-06-01 15:38:29 UTC
epigraphhub-db_1           | 2022-06-01 15:38:30.084 UTC [1] LOG:  database system is ready to accept connections
epigraphhub-flower_1       | [I 220601 15:38:21 command:135] Visit me at http://localhost:8888
epigraphhub-flower_1       | [I 220601 15:38:21 command:142] Broker: redis://redis:6379/0
epigraphhub-flower_1       | [I 220601 15:38:21 command:143] Registered tasks: 
epigraphhub-flower_1       |     ['celery.accumulate',
epigraphhub-flower_1       |      'celery.backend_cleanup',
epigraphhub-flower_1       |      'celery.chain',
epigraphhub-flower_1       |      'celery.chord',
epigraphhub-flower_1       |      'celery.chord_unlock',
epigraphhub-flower_1       |      'celery.chunks',
epigraphhub-flower_1       |      'celery.group',
epigraphhub-flower_1       |      'celery.map',
epigraphhub-flower_1       |      'celery.starmap']
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:38:36,636:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:38:36,665:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:38:42,910:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:38:42,919:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:38:48,665:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:38:48,684:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:38:54,826:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:38:54,843:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:39:00,494:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:39:00,510:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:39:06,840:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:39:06,846:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:39:14,124:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:39:14,129:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:39:24,878:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:39:24,884:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:39:41,452:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-redis_1        | 1:C 01 Jun 2022 15:38:17.533 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
epigraphhub-redis_1        | 1:C 01 Jun 2022 15:38:17.533 # Redis version=7.0.0, bits=64, commit=00000000, modified=0, pid=1, just started
epigraphhub-redis_1        | 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
epigraphhub-redis_1        | 1:M 01 Jun 2022 15:38:17.533 * monotonic clock: POSIX clock_gettime
epigraphhub-redis_1        | 1:M 01 Jun 2022 15:38:17.534 * Running mode=standalone, port=6379.
epigraphhub-redis_1        | 1:M 01 Jun 2022 15:38:17.534 # Server initialized
epigraphhub-redis_1        | 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.
epigraphhub-redis_1        | 1:M 01 Jun 2022 15:38:17.534 * The AOF directory appendonlydir doesn't exist
epigraphhub-redis_1        | 1:M 01 Jun 2022 15:38:17.534 * Ready to accept connections
epigraphhub-superset_1     | 2022-06-01 15:39:41,458:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:40:10,350:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:40:10,356:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:41:04,836:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:41:04,841:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:42:07,870:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:42:07,876:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
epigraphhub-superset_1     | [II] activate epigraphhub
epigraphhub-superset_1     | + export FLASK_APP=superset
epigraphhub-superset_1     | + FLASK_APP=superset
epigraphhub-superset_1     | + superset db upgrade
epigraphhub-superset_1     | logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:43:10,832:INFO:superset.utils.logging_configurator:logging was configured successfully
epigraphhub-superset_1     | 2022-06-01 15:43:10,838:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | 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
epigraphhub-superset_1     | (Background on this error at: http://sqlalche.me/e/13/e3q8)
epigraphhub-superset_1     | /opt/entrypoint.sh: line 27: Loaded: command not found
xmnlab commented 2 years ago

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

xmnlab commented 2 years ago

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

xmnlab commented 2 years ago

thanks for the review @fccoelho