+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: SQLite Error 8: 'attempt to write a readonly database'. (/t-solved-sqlite-error-8-attempt-to-write-a-readonly-database)
SQLite Error 8: 'attempt to write a readonly database'. - curiouscrumb - 2024-12-27
I am running Jellyfin through dockge on TrueNAS. After months of trouble-free service my jellyfin server started acting up Sometime on dec 24th.
Not sure what changed around that time or if something I was doing caused problems. I've googled around and have read explanations that the title indicates that the database may already be in use, but I only have one instance running on the entire system, and it is installed in a jail.
Here are some log contents from what I'm seeing.
jellyfin logfiles as it happened:
https://pastebin.com/c22FSAnj
I've since updated my NAS to a newer version and tried to re-install jellyfin in a different dockge instance in case that helped. it did not.
In the dockge terminal today:
https://pastebin.com/KcrhnHnx
I do recall seeing Jellyfin saying something about 'migration' on the 24th when I hadn't done anything to trigger such an action as far as I know.
I can access jellyfin config files through the shell, but am unable to start the server or access webui. I've checked that the wizard flag is false in system.xml. Other than nuking jellyfin and reinstalling I am all out of ideas.
RE: SQLite Error 8: 'attempt to write a readonly database'. - TheDreadPirate - 2024-12-27
Code:
System.UnauthorizedAccessException: Access to the path '/config/data/metadata/library/96/966d6e9a18cf6b0b029c36237d1cb513/trickplay' is denied.
---> System.IO.IOException: Permission deniedThe user running Jellyfin doesn't have access to some of the /config directory, which can cause many weird issues. Make sure your user owns everything.
RE: SQLite Error 8: 'attempt to write a readonly database'. - curiouscrumb - 2024-12-27
huh, adding permissions fixed it. I have no idea how I ended up in this state but glad things are back up. thank you for stating the obvious.