why the deploy process get failed
emon3455
TRIALOP

2 years ago

here is the log details::

                         setting pragmas                                    

                DEBUG    2024-08-03 09:27:17 - DEBUG    -     [service.py:280](service.py:280)

                         service - Database and tables                      

                         already exist                                      

                INFO     2024-08-03 09:27:17 - INFO     -     [service.py:195](service.py:195)

                         service - Alembic already                          

                         initialized                                        

                INFO     2024-08-03 09:27:17 - INFO     -     [service.py:197](service.py:197)

                         service - Running DB migrations in                 

                         /app/.venv/lib/python3.12/site-packa               

                         ges/langflow/alembic                               

                DEBUG    2024-08-03 09:27:17 - DEBUG    -      [manager.py:65](manager.py:65)

                         manager - Create service                           

                         ServiceType.MONITOR_SERVICE                        

                WARNING  2024-08-03 09:27:17 - WARNING  - utils  [utils.py:30](utils.py:30)

                         - Error retrieving messages from                   

                         monitor service: IO Error: Cannot open             

                         database                                           

                         "/app/data/.cache/langflow/monitor.duck            

                         db" in read-only mode: database does               

                         not exist                                          

                WARNING  2024-08-03 09:27:17 - WARNING  - utils [utils.py:166](utils.py:166)

                         - Error retrieving transactions from               

                         monitor service: IO Error: Cannot open             

                         database                                           

                         "/app/data/.cache/langflow/monitor.duc             

                         kdb" in read-only mode: database does              

                         not exist                                          

                DEBUG    2024-08-03 09:27:17 - DEBUG    - utils [utils.py:129](utils.py:129)

                         - Database initialized                             

                DEBUG    2024-08-03 09:27:17 - DEBUG    - utils  [utils.py:65](utils.py:65)

                         - AUTO_LOGIN is set to True. Creating              

                         default superuser.

[08/03/24 09:27:18] DEBUG 2024-08-03 09:27:18 - DEBUG - auth - auth.py:76

                         Resetting superuser password to default            

                         value                                              

                INFO     2024-08-03 09:27:18 - INFO     -      [service.py:77](service.py:77)

                         service - sqlite connect listener,                 

                         setting pragmas                                    

                INFO     2024-08-03 09:27:18 - INFO     - utils [utils.py:116](utils.py:116)

                         - No LLM cache set.                                

                DEBUG    2024-08-03 09:27:18 - DEBUG   langfuse_[plugin.py:43](plugin.py:43)

                         - langfuse_plugin - Updating                       

                         Langfuse instance                                  

                DEBUG    2024-08-03 09:27:18 - DEBUG   langfuse_[plugin.py:22](plugin.py:22)

                         - langfuse_plugin - Creating                       

                         Langfuse instance                                  

                DEBUG    2024-08-03 09:27:18 - DEBUG   langfuse_[plugin.py:35](plugin.py:35)

                         - langfuse_plugin - No

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.

0 Replies

Loading...