You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While using a different database filename than sqlite.db, PG2 fails to start. In my case I renamed the database to media.db in the settings, saved it and restarted the server. Everything works fine, while the old file sqlite.db was available.
After removing the file sqlite.db from the folder, the server fails to start, even while the config.json contains the right filename and this file exists.
It is possible to work-around this issue by just creating an empty sqlite.db in the database-folder. It will not be written while running PG2, but enables it to start up.
Environment (please complete the following information):
OS: Armbian V24.8
Used app version:
V2.0.3-edge compiled from source
The text was updated successfully, but these errors were encountered:
Describe the bug
While using a different database filename than
sqlite.db
, PG2 fails to start. In my case I renamed the database tomedia.db
in the settings, saved it and restarted the server. Everything works fine, while the old filesqlite.db
was available.After removing the file
sqlite.db
from the folder, the server fails to start, even while theconfig.json
contains the right filename and this file exists.It is possible to work-around this issue by just creating an empty
sqlite.db
in the database-folder. It will not be written while running PG2, but enables it to start up.Environment (please complete the following information):
Used app version:
The text was updated successfully, but these errors were encountered: