Open
Description
When a wrong path to the sqlite database is set in the litestream.yml file and litestream can't find the database, the log message is only emitted if the log level is set to debug. Absolutely no log is emitted if the log level is set to info
or higher.
For a disaster recovery tool, I find it strange that litestream basically fails silently and doesn't assume, that if the config tells it to replicate a database that isn't existing, that the configuration is wrong.
At least, I would expect the time=2025-06-17T10:55:22.400Z level=DEBUG msg="sync: no database found" db=/data/data.db
would be in the WARN or ERROR log. Right now, if the logging is set to the default, there is zero indication that anything in the config is wrong.
Metadata
Metadata
Assignees
Labels
No labels