Upgrade from 13.2 -> 14.0 failure

[rsteckler]

From my log file:

2024-08-18T07:15:16.073111276-07:00 2024-08-18 14:15:16.073014665  [2024-08-18 14:15:16] frigate.app                    INFO    : Starting Frigate (0.14.0-da913d8)
2024-08-18T07:15:16.077905326-07:00 2024-08-18 14:15:16.077742231  [2024-08-18 14:15:16] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-08-18T07:15:16.080640135-07:00 2024-08-18 14:15:16.080476775  [2024-08-18 14:15:16] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-08-18T07:15:16.205876908-07:00 2024-08-18 14:15:16.205760711  [2024-08-18 14:15:16] frigate.util.config            INFO    : frigate config does not need migration...
2024-08-18T07:15:16.300689859-07:00 2024-08-18 14:15:16.300565159  '/config/database.db' and '/config/database.db' are the same file
2024-08-18T07:15:16.300736737-07:00 2024-08-18 14:15:16.300707140  [2024-08-18 14:15:16] frigate.app                    INFO    : Making backup of DB before migrations...
2024-08-18T07:15:17.609320900-07:00 2024-08-18 14:15:17.609174601  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-08-18T07:15:17.612218781-07:00 s6-rc: info: service legacy-services: stopping
2024-08-18T07:15:17.614040559-07:00 s6-rc: info: service legacy-services successfully stopped
2024-08-18T07:15:17.614130852-07:00 s6-rc: info: service go2rtc-healthcheck: stopping
2024-08-18T07:15:17.614300904-07:00 s6-rc: info: service certsync: stopping

Are there additional log details I can pull to find out why it's exiting during the database migration?

[NickM-27]

the db must be called frigate.db

[rsteckler]

Working great now, thank you for the [insanely fast] support.
Is the database custom path in the config deprecated? Or is it just required to be named frigate.db during the migration?

[NickM-27]

The name of the file itself just needs to be frigate.db