2024-09-12, 02:53 PM
Well, I thought that I found a final answer, but this morning I'm not so sure.
linuxserver/jellyfin has a different /config layout than jellyfin/jellyfin.
The Linuxserver container writes the playback_reporting.db to /config/data/data
The jellyfin official container writes the playback_reporting.db to /config/data
I moved the file to /config/data on the Linuxserver container and it appeared to start working. This morning however, I noticed that the playback_reporting.db had been rewritten to /config/data/data and was now collecting data. I'm not sure what happened, but apparently when the file was able to be rewritten, it started working. I honestly thought we had done that before. Nevertheless, it is working on the Linuxserver container.
I'm leaving on PTO for a week. When I get back I plan to spin up a test instance and see if I can replicate the "fix".
Thanks for all your help!
linuxserver/jellyfin has a different /config layout than jellyfin/jellyfin.
The Linuxserver container writes the playback_reporting.db to /config/data/data
The jellyfin official container writes the playback_reporting.db to /config/data
I moved the file to /config/data on the Linuxserver container and it appeared to start working. This morning however, I noticed that the playback_reporting.db had been rewritten to /config/data/data and was now collecting data. I'm not sure what happened, but apparently when the file was able to be rewritten, it started working. I honestly thought we had done that before. Nevertheless, it is working on the Linuxserver container.
I'm leaving on PTO for a week. When I get back I plan to spin up a test instance and see if I can replicate the "fix".
Thanks for all your help!
(2024-09-11, 08:16 PM)TheDreadPirate Wrote: Spin up a separate container, but try using the official jellyfin/jellyfin image?