Error Message Catalog Error: Table with name transaction does not exist!
Bug Description
2024-07-28 01:06:56 - ERROR - utils - Error retrieving messages from monitor utils.py:27 service: Catalog Error: Table with name messages does not exist! Did you mean "information_schema.tables"? LINE 1: ...ession_id, text, files, timestamp FROM messages ORDER BY timestamp DESC ^ ERROR 2024-07-28 01:06:56 - ERROR - service - Error migrating transactions from service.py:221 monitor service to database: Catalog Error: Table with name transactions does not exist! Did you mean "information_schema.columns"? LINE 1: ...ex_id, inputs, outputs, target_id FROM transactions LIMIT 100
Reproduction
- installed langflow in windows 11
- use python env
- when run langflow run , those two error appear.
Expected behavior
the error appear when running the app, I can open it on the browser,
Who can help?
@italojohnny
Operating System
windows 11
Langflow Version
1.0.13
Python Version
3.11
Screenshot
\Users\usr\langflow\venv\Lib\site-packages\langflow\alembic 2024-07-28 01:06:34.679 | DEBUG | langflow.services.manager:_create_service:65 - Create service ServiceType.MONITOR_SERVICE 2024-07-28 01:06:34.705 | ERROR | langflow.services.database.utils:migrate_messages_from_monitor_service_to_database:27 - Error retrieving messages from monitor service: Catalog Error: Table with name messages does not exist! Did you mean "information_schema.tables"? LINE 1: ...ession_id, text, files, timestamp FROM messages ORDER BY timestamp DESC ^ 2024-07-28 01:06:34.725 | ERROR | langflow.services.database.service:run_migrations:221 - Error migrating transactions from monitor service to database: Catalog Error: Table with name transactions does not exist! Did you mean "information_schema.columns"? LINE 1: ...ex_id, inputs, outputs, target_id FROM transactions LIMIT 100 ^
Flow File
This will delete all data necessary to fix migrations. Are you sure you want to continue? [y/N]: y 2024-07-28 01:06:34.606 | DEBUG | langflow.services.manager:_create_service:65 - Create service ServiceType.CACHE_SERVICE 2024-07-28 01:06:34.607 | DEBUG | langflow.services.manager:_create_service:65 - Create service ServiceType.SETTINGS_SERVICE 2024-07-28 01:06:34.608 | DEBUG | langflow.services.settings.base:set_database_url:182 - No database_url provided, trying LANGFLOW_DATABASE_URL env variable 2024-07-28 01:06:34.608 | DEBUG | langflow.services.settings.base:set_database_url:187 - No database_url env variable, using sqlite database 2024-07-28 01:06:34.609 | DEBUG | langflow.services.settings.base:set_database_url:206 - Saving database to langflow directory: C:\Users\josec\langflow\venv\Lib\site-packages\langflow 2024-07-28 01:06:34.609 | DEBUG | langflow.services.settings.base:set_database_url:230 - Database already exists at C:\Users\josec\langflow\venv\Lib\site-packages\langflow/langflow.db, using it 2024-07-28 01:06:34.609 | DEBUG | langflow.services.settings.base:set_components_path:270 - Setting default components path to components_path 2024-07-28 01:06:34.610 | DEBUG | langflow.services.settings.base:set_components_path:275 - Components path: ['C:\Users\josec\langflow\venv\Lib\site-packages\langflow\components'] 2024-07-28 01:06:34.610 | DEBUG | langflow.services.settings.base:set_user_agent:151 - Setting user agent to langflow 2024-07-28 01:06:34.612 | DEBUG | langflow.services.settings.auth:get_secret_key:98 - No secret key provided, generating a random one 2024-07-28 01:06:34.612 | DEBUG | langflow.services.settings.auth:get_secret_key:102 - Loaded secret key 2024-07-28 01:06:34.612 | DEBUG | langflow.services.settings.auth:validate_superuser:76 - Resetting superuser password to default value 2024-07-28 01:06:34.612 | DEBUG | langflow.services.database.utils:initialize_database:87 - Initializing database 2024-07-28 01:06:34.613 | DEBUG | langflow.services.manager:_create_service:65 - Create service ServiceType.DATABASE_SERVICE 2024-07-28 01:06:34.620 | INFO | langflow.services.database.service:on_connection:77 - sqlite connect listener, setting pragmas 2024-07-28 01:06:34.632 | DEBUG | langflow.services.database.service:create_db_and_tables:280 - Database and tables already exist 2024-07-28 01:06:34.633 | INFO | langflow.services.database.service:run_migrations:195 - Alembic already initialized 2024-07-28 01:06:34.634 | INFO | langflow.services.database.service:run_migrations:197 - Running DB migrations in C:\Users\josec\langflow\venv\Lib\site-packages\langflow\alembic 2024-07-28 01:06:34.679 | DEBUG | langflow.services.manager:_create_service:65 - Create service ServiceType.MONITOR_SERVICE 2024-07-28 01:06:34.705 | ERROR | langflow.services.database.utils:migrate_messages_from_monitor_service_to_database:27 - Error retrieving messages from monitor service: Catalog Error: Table with name messages does not exist! Did you mean "information_schema.tables"? LINE 1: ...ession_id, text, files, timestamp FROM messages ORDER BY timestamp DESC ^ 2024-07-28 01:06:34.725 | ERROR | langflow.services.database.service:run_migrations:221 - Error migrating transactions from monitor service to database: Catalog Error: Table with name transactions does not exist! Did you mean "information_schema.columns"? LINE 1: ...ex_id, inputs, outputs, target_id FROM transactions LIMIT 100 ^ 2024-07-28 01:06:34.746 | DEBUG | langflow.services.database.utils:initialize_database:126 - Database initialized 2024-07-28 01:06:34.747 | DEBUG | langflow.services.utils:setup_superuser:65 - AUTO_LOGIN is set to True. Creating default superuser. 2024-07-28 01:06:34.759 | DEBUG | langflow.services.settings.auth:validate_superuser:76 - Resetting superuser password to default value 2024-07-28 01:06:34.765 | INFO | langflow.services.database.service:on_connection:77 - sqlite connect listener, setting pragmas Migration apikey ┏━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━┓ ┃ Name ┃ Type ┃ Status ┃ ┡━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━┩ │ apikey │ table │ Success │ │ name │ column │ Success │ │ last_used_at │ column │ Success │ │ total_uses │ column │ Success │ │ is_active │ column │ Success │ │ id │ column │ Success │ │ created_at │ column │ Success │ │ api_key │ column │ Success │ │ user_id │ column │ Success │ └──────────────┴────────┴─────────┘
Migration flow
┏━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━┓ ┃ Name ┃ Type ┃ Status ┃ ┡━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━┩ │ flow │ table │ Success │ │ name │ column │ Success │ │ description │ column │ Success │ │ icon │ column │ Success │ │ icon_bg_color │ column │ Success │ │ data │ column │ Success │ │ is_component │ column │ Success │ │ updated_at │ column │ Success │ │ webhook │ column │ Success │ │ endpoint_name │ column │ Success │ │ id │ column │ Success │ │ user_id │ column │ Success │ │ folder_id │ column │ Success │ └───────────────┴────────┴─────────┘
Migration folder
┏━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━┓ ┃ Name ┃ Type ┃ Status ┃ ┡━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━┩ │ folder │ table │ Success │ │ name │ column │ Success │ │ description │ column │ Success │ │ id │ column │ Success │ │ parent_id │ column │ Success │ │ user_id │ column │ Success │ └─────────────┴────────┴─────────┘
Migration message
┏━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━┓ ┃ Name ┃ Type ┃ Status ┃ ┡━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━┩ │ message │ table │ Success │ │ timestamp │ column │ Success │ │ sender │ column │ Success │ │ sender_name │ column │ Success │ │ session_id │ column │ Success │ │ text │ column │ Success │ │ files │ column │ Success │ │ id │ column │ Success │ │ flow_id │ column │ Success │ └─────────────┴────────┴─────────┘
Migration user
┏━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━┓ ┃ Name ┃ Type ┃ Status ┃ ┡━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━┩ │ user │ table │ Success │ │ id │ column │ Success │ │ username │ column │ Success │ │ password │ column │ Success │ │ profile_image │ column │ Success │ │ is_active │ column │ Success │ │ is_superuser │ column │ Success │ │ create_at │ column │ Success │ │ updated_at │ column │ Success │ │ last_login_at │ column │ Success │ │ store_api_key │ column │ Success │ └───────────────┴────────┴─────────┘
Migration variable
┏━━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━┓ ┃ Name ┃ Type ┃ Status ┃ ┡━━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━┩ │ variable │ table │ Success │ │ name │ column │ Success │ │ value │ column │ Success │ │ default_fields │ column │ Success │ │ type │ column │ Success │ │ id │ column │ Success │ │ created_at │ column │ Success │ │ updated_at │ column │ Success │ │ user_id │ column │ Success │ └────────────────┴────────┴─────────┘
Migration transaction
┏━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━┓ ┃ Name ┃ Type ┃ Status ┃ ┡━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━┩ │ transaction │ table │ Success │ │ timestamp │ column │ Success │ │ vertex_id │ column │ Success │ │ target_id │ column │ Success │ │ inputs │ column │ Success │ │ outputs │ column │ Success │ │ status │ column │ Success │ │ error │ column │ Success │ │ flow_id │ column │ Success │ │ id │ column │ Success │ └─────────────┴────────┴─────────┘
(venv) C:\Users\josec\langflow>langflow run ╭───────────────────────────────────────────────────────────────────╮ │ Welcome to ⛓ Langflow │ │ │ │ │ │ Collaborate, and contribute at our GitHub Repo 🌟 │ │ │ │ We collect anonymous usage data to improve Langflow. │ │ You can opt-out by setting DO_NOT_TRACK=true in your environment. │ │ │ │ Access http://127.0.0.1:7860 │ ╰───────────────────────────────────────────────────────────────────╯ Starting Langflow v1.0.13... [07/28/24 01:06:56] ERROR 2024-07-28 01:06:56 - ERROR - utils - Error retrieving messages from monitor utils.py:27 service: Catalog Error: Table with name messages does not exist! Did you mean "information_schema.tables"? LINE 1: ...ession_id, text, files, timestamp FROM messages ORDER BY timestamp DESC ^ ERROR 2024-07-28 01:06:56 - ERROR - service - Error migrating transactions from service.py:221 monitor service to database: Catalog Error: Table with name transactions does not exist! Did you mean "information_schema.columns"? LINE 1: ...ex_id, inputs, outputs, target_id FROM transactions LIMIT 100 ^
Hello @cuba6112! I'm here to assist you with your issue. I can help you solve bugs, answer questions, and become a contributor. While you're waiting for a human maintainer, feel free to ask me anything.
To resolve the errors related to missing tables (messages and transactions), you should ensure that the necessary tables are created in the database. You can use the create_db_and_tables method from the DatabaseService class to achieve this. Here is how you can do it:
-
Ensure Database and Tables Creation: Use the
create_db_and_tablesmethod to check if the required tables exist and create them if they do not.def create_db_and_tables(self): from sqlalchemy import inspect inspector = inspect(self.engine) table_names = inspector.get_table_names() current_tables = ["flow", "user", "apikey", "messages", "transactions"] if table_names and all(table in table_names for table in current_tables): logger.debug("Database and tables already exist") return logger.debug("Creating database and tables") for table in SQLModel.metadata.sorted_tables: try: table.create(self.engine, checkfirst=True) except OperationalError as oe: logger.warning(f"Table {table} already exists, skipping. Exception: {oe}") except Exception as exc: logger.error(f"Error creating table {table}: {exc}") raise RuntimeError(f"Error creating table {table}") from exc # Now check if the required tables exist, if not, something went wrong. inspector = inspect(self.engine) table_names = inspector.get_table_names() for table in current_tables: if table not in table_names: logger.error("Something went wrong creating the database and tables.") logger.error("Please check your database settings.") raise RuntimeError("Something went wrong creating the database and tables.") logger.debug("Database and tables created successfully") -
Call the Method: Ensure you have an instance of
DatabaseServiceand callcreate_db_and_tableson it.database_service = DatabaseService(database_url="your_database_url") database_service.create_db_and_tables() -
Run Migrations: If the tables are still missing, you might need to run the migrations manually. Use the
migrationcommand to apply the migrations.langflow migration --no-testIf you encounter issues, you can try fixing the migrations:
langflow migration --fix
These steps should help resolve the errors related to missing tables and ensure that the necessary tables are created in the database [1][2][3].
To continue talking to Dosu, mention @dosu.
Hey thanks for reporting, is the service gets stopped or is it just a log? Theoretically it should continue. Anyway we need to silence the exception, I will fix it soon
Hi there,
I am able to open the website and work normally. However, it does appear as an error.
Thanks, Jose
On Sun, Jul 28, 2024 at 4:51 AM Nicolò Boschi @.***> wrote:
Hey thanks for reporting, is the service gets stopped or is it just a log? Theoretically it should continue. Anyway we need to silence the exception, I will fix it soon
— Reply to this email directly, view it on GitHub https://github.com/langflow-ai/langflow/issues/3007#issuecomment-2254400716, or unsubscribe https://github.com/notifications/unsubscribe-auth/BE5HODFDWPCRO6SPRBS2TXTZOSWKXAVCNFSM6AAAAABLSPHBLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGQYDANZRGY . You are receiving this because you were mentioned.Message ID: @.***>
I also faced this issue. I am using official docker image 1.0.13 and using a new database.
The new setup faces the same issue.
@artemus717 @weweliang this has been fixed in 1.0.14; will be released soon
[07/31/24 07:26:13] INFO 2024-07-31 07:26:13 - INFO - main - main.py:228
2024-07-31T15:26:13.577157299+08:00 Setting up app with static files
2024-07-31T15:26:13.577162839+08:00 directory None
[07/31/24 07:26:13] INFO 2024-07-31 07:26:13 - INFO - init.py:1762
2024-07-31T15:26:13.833505543+08:00 init - Starting gunicorn
2024-07-31T15:26:13.833509148+08:00 22.0.0
INFO 2024-07-31 07:26:13 - INFO - init.py:1762
2024-07-31T15:26:13.838276181+08:00 init - Listening at:
2024-07-31T15:26:13.838280551+08:00 http://0.0.0.0:7860 (87)
INFO 2024-07-31 07:26:13 - INFO - init.py:1762
2024-07-31T15:26:13.839864248+08:00 init - Using worker:
2024-07-31T15:26:13.839868512+08:00 langflow.server.LangflowUvicornWor
2024-07-31T15:26:13.839871745+08:00 ker
INFO 2024-07-31 07:26:13 - INFO - init.py:1762
2024-07-31T15:26:13.852108342+08:00 init - Booting worker with
2024-07-31T15:26:13.852112108+08:00 pid: 88
INFO 2024-07-31 07:26:13 - INFO - init.py:1762
2024-07-31T15:26:13.930605469+08:00 init - Started server process
2024-07-31T15:26:13.930609588+08:00 [88]
INFO 2024-07-31 07:26:13 - INFO - init.py:1762
2024-07-31T15:26:13.932148505+08:00 init - Waiting for application
2024-07-31T15:26:13.932152586+08:00 startup.
Starting Langflow v1.0.14...
[07/31/24 07:26:14] INFO 2024-07-31 07:26:14 - INFO - service.py:195
2024-07-31T15:26:14.078827845+08:00 service - Alembic already
2024-07-31T15:26:14.078831630+08:00 initialized
INFO 2024-07-31 07:26:14 - INFO - service.py:197
2024-07-31T15:26:14.080624323+08:00 service - Running DB migrations in
2024-07-31T15:26:14.080627875+08:00 /app/.venv/lib/python3.12/site-packa
2024-07-31T15:26:14.080630874+08:00 ges/langflow/alembic
[07/31/24 07:26:17] ERROR 2024-07-31 07:26:17 - ERROR - service.py:211
2024-07-31T15:26:17.663506948+08:00 service - AutogenerateDiffsDetected:
2024-07-31T15:26:17.663511030+08:00 New upgrade operations detected:
2024-07-31T15:26:17.663524822+08:00 [[('modify_type', None, 'apikey',
2024-07-31T15:26:17.663528027+08:00 'last_used_at',
2024-07-31T15:26:17.663531430+08:00 {'existing_nullable': True,
2024-07-31T15:26:17.663534270+08:00 'existing_server_default': False,
2024-07-31T15:26:17.663537106+08:00 'existing_comment': None},
2024-07-31T15:26:17.663540113+08:00 TIMESTAMP(timezone=True),
2024-07-31T15:26:17.663542896+08:00 DateTime())]]
ERROR 2024-07-31 07:26:17 - ERROR - utils utils.py:127
2024-07-31T15:26:17.666652481+08:00 - There's a mismatch between the
2024-07-31T15:26:17.666656094+08:00 models and the database.
2024-07-31T15:26:17.666658895+08:00 New upgrade operations detected:
2024-07-31T15:26:17.666661689+08:00 [[('modify_type', None, 'apikey',
2024-07-31T15:26:17.666664694+08:00 'last_used_at', {'existing_nullable':
2024-07-31T15:26:17.666667661+08:00 True, 'existing_server_default':
2024-07-31T15:26:17.666670411+08:00 False, 'existing_comment': None},
2024-07-31T15:26:17.666673741+08:00 TIMESTAMP(timezone=True),
2024-07-31T15:26:17.666676562+08:00 DateTime())]]
ERROR 2024-07-31 07:26:17 - ERROR - main - main.py:98
2024-07-31T15:26:17.669699827+08:00 There's a mismatch between the models
2024-07-31T15:26:17.669704843+08:00 and the database.
2024-07-31T15:26:17.669708802+08:00 New upgrade operations detected:
2024-07-31T15:26:17.669714646+08:00 [[('modify_type', None, 'apikey',
2024-07-31T15:26:17.669719000+08:00 'last_used_at', {'existing_nullable':
2024-07-31T15:26:17.669723260+08:00 True, 'existing_server_default': False,
2024-07-31T15:26:17.669727390+08:00 'existing_comment': None},
2024-07-31T15:26:17.669731234+08:00 TIMESTAMP(timezone=True), DateTime())]]
ERROR 2024-07-31 07:26:17 - ERROR - init.py:1762
2024-07-31T15:26:17.682049657+08:00 init - Traceback (most recent
2024-07-31T15:26:17.682055211+08:00 call last):
2024-07-31T15:26:17.682059726+08:00 File
2024-07-31T15:26:17.682063755+08:00 "/app/.venv/lib/python3.12/site-pa
2024-07-31T15:26:17.682067848+08:00 ckages/langflow/services/database/
2024-07-31T15:26:17.682071710+08:00 service.py", line 209, in
2024-07-31T15:26:17.682086127+08:00 run_migrations
2024-07-31T15:26:17.682090317+08:00 command.check(alembic_cfg)
2024-07-31T15:26:17.682094311+08:00 File
2024-07-31T15:26:17.682098208+08:00 "/app/.venv/lib/python3.12/site-pa
2024-07-31T15:26:17.682104646+08:00 ckages/alembic/command.py", line
2024-07-31T15:26:17.682108412+08:00 300, in check
2024-07-31T15:26:17.682112230+08:00 raise
2024-07-31T15:26:17.682116199+08:00 util.AutogenerateDiffsDetected(
2024-07-31T15:26:17.682119877+08:00 alembic.util.exc.AutogenerateDiffs
2024-07-31T15:26:17.682123586+08:00 Detected: New upgrade operations
2024-07-31T15:26:17.682133031+08:00
detected: [[('modify_type', None,
2024-07-31T15:26:17.682137012+08:00 'apikey', 'last_used_at',
2024-07-31T15:26:17.682140442+08:00 {'existing_nullable': True,
2024-07-31T15:26:17.682144022+08:00 'existing_server_default': False,
2024-07-31T15:26:17.682147668+08:00 'existing_comment': None},
TIMESTAMP(timezone=True),
2024-07-31T15:26:17.682155397+08:00 DateTime())]]
2024-07-31T15:26:17.682159093+08:00
During handling of the above
2024-07-31T15:26:17.682166135+08:00 exception, another exception
2024-07-31T15:26:17.682169706+08:00 occurred:
2024-07-31T15:26:17.682173225+08:00
2024-07-31T15:26:17.682177578+08:00 Traceback (most recent call last):
2024-07-31T15:26:17.682181313+08:00 File
2024-07-31T15:26:17.682184927+08:00 "/app/.venv/lib/python3.12/site-pa
2024-07-31T15:26:17.682188669+08:00 ckages/starlette/routing.py", line
2024-07-31T15:26:17.682192255+08:00 732, in lifespan
2024-07-31T15:26:17.682195795+08:00 async with
2024-07-31T15:26:17.682199560+08:00 self.lifespan_context(app) as
maybe_state:
File
2024-07-31T15:26:17.682212071+08:00 "/usr/local/lib/python3.12/context
lib.py", line 210, in aenter
2024-07-31T15:26:17.682223044+08:00 return await anext(self.gen)
2024-07-31T15:26:17.682226968+08:00 ^^^^^^^^^^^^^^^^^^^^^
2024-07-31T15:26:17.682231234+08:00 File
2024-07-31T15:26:17.682235679+08:00 "/app/.venv/lib/python3.12/site-pa
ckages/langflow/main.py", line 87,
2024-07-31T15:26:17.682259786+08:00 in lifespan
2024-07-31T15:26:17.682264328+08:00 initialize_services(fix_migrat
2024-07-31T15:26:17.682268865+08:00 ion=fix_migration,
socketio_server=socketio_server)
2024-07-31T15:26:17.682277652+08:00 File
2024-07-31T15:26:17.682299966+08:00 "/app/.venv/lib/python3.12/site-pa
2024-07-31T15:26:17.682304155+08:00 ckages/langflow/services/utils.py"
2024-07-31T15:26:17.682308012+08:00 , line 167, in initialize_services
raise exc
2024-07-31T15:26:17.682316303+08:00 File
2024-07-31T15:26:17.682320554+08:00 "/app/.venv/lib/python3.12/site-pa
2024-07-31T15:26:17.682324463+08:00 ckages/langflow/services/utils.py"
, line 165, in initialize_services
2024-07-31T15:26:17.682333400+08:00 initialize_database(fix_migrat
ion=fix_migration)
2024-07-31T15:26:17.682341981+08:00 File
2024-07-31T15:26:17.682346185+08:00 "/app/.venv/lib/python3.12/site-pa
ckages/langflow/services/database/
2024-07-31T15:26:17.682354546+08:00 utils.py", line 128, in
initialize_database
2024-07-31T15:26:17.682362434+08:00 raise exc
2024-07-31T15:26:17.682366967+08:00 File
2024-07-31T15:26:17.682371555+08:00 "/app/.venv/lib/python3.12/site-pa
2024-07-31T15:26:17.682375510+08:00 ckages/langflow/services/database/
2024-07-31T15:26:17.682379855+08:00 utils.py", line 108, in
2024-07-31T15:26:17.682384241+08:00 initialize_database
database_service.run_migration
2024-07-31T15:26:17.682396118+08:00 s(fix=fix_migration)
2024-07-31T15:26:17.682400604+08:00 File
2024-07-31T15:26:17.682404956+08:00 "/app/.venv/lib/python3.12/site-pa
2024-07-31T15:26:17.682409346+08:00 ckages/langflow/services/database/
service.py", line 213, in
2024-07-31T15:26:17.682418501+08:00 run_migrations
2024-07-31T15:26:17.682422579+08:00 raise RuntimeError(f"There's a
2024-07-31T15:26:17.682426821+08:00 mismatch between the models and
2024-07-31T15:26:17.682430521+08:00 the database.\n{exc}")
2024-07-31T15:26:17.682434419+08:00 RuntimeError: There's a mismatch
2024-07-31T15:26:17.682438155+08:00 between the models and the
2024-07-31T15:26:17.682442220+08:00 database.
2024-07-31T15:26:17.682446049+08:00 New upgrade operations detected:
[[('modify_type', None, 'apikey',
2024-07-31T15:26:17.682461694+08:00 'last_used_at',
2024-07-31T15:26:17.682465683+08:00 {'existing_nullable': True,
2024-07-31T15:26:17.682469560+08:00 'existing_server_default': False,
'existing_comment': None},
2024-07-31T15:26:17.682478717+08:00 TIMESTAMP(timezone=True),
2024-07-31T15:26:17.682482574+08:00 DateTime())]]
ERROR 2024-07-31 07:26:17 - ERROR - __init__.py:1762
2024-07-31T15:26:17.684541158+08:00 init - Application startup
2024-07-31T15:26:17.684544794+08:00 failed. Exiting.
INFO 2024-07-31 07:26:17 - INFO - init.py:1762
2024-07-31T15:26:17.687432869+08:00 init - Worker exiting (pid:
2024-07-31T15:26:17.687436536+08:00 88)
[07/31/24 07:26:17] ERROR 2024-07-31 07:26:17 - ERROR - init.py:1762
2024-07-31T15:26:17.702302074+08:00 init - Worker (pid:88) exited
2024-07-31T15:26:17.702306067+08:00 with code 3
ERROR 2024-07-31 07:26:17 - ERROR - init.py:1762
2024-07-31T15:26:17.704346649+08:00 init - Shutting down: Master
ERROR 2024-07-31 07:26:17 - ERROR - init.py:1762
2024-07-31T15:26:17.705873616+08:00 init - Reason: Worker failed
2024-07-31T15:26:17.705877435+08:00 to boot.
Hi @nicoloboschi this error disapper, but still other error. I upgrade from 0.6.16 to 1.0.14. If there are no plan for 0.6 upgrade to 1.0. I will install a new 1.0.
Thanks