SOLVED: Music playlists do not work [Solved]

[anonymoustumbleweed]

Hi, anytime I upgrade jellyfin above version 10.9.1, all my music/songs and playlist will stop working. A busy cursor appears for hours and the only thing that populates inside the music folder is the playlist covers; however, if I attempt to click on a playlist, the busy cursor reappears. If I revert back to jellyfin 10.9.1, music and playlists work again. 

My music folder contains all mp3 songs and a folder labled playlists full of m3u playlists. Jellyfin 10.9.1 and prior would scan and populate just fine until now. I have had the Jellyfin server for more than 5 years with no issues until now. Please help!

***Update, pastebin link: https://pastebin.com/k1Cp4krR
I restarted Jellyfin and attempted to click on my visible music playlists with cover art and view the song tab. Again, the busy cursor was only showing. I then copied the code after restart but some lines were cutoff from the beginning start code. Here are the 3 lines of code after restart not in pastebin:
[2024-10-05 10:57:01.412 -07:00] [INF] [13] Emby.Server.Implementations.Session.SessionManager: Sending shutdown notifications
[2024-10-05 10:57:01.420 -07:00] [INF] [13] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "172.18.0.1" closed
[2024-10-05 10:57:01.425 -07:00] [INF] [13] Jellyfin.Networking.PortForwardingHost: Stopping NAT discovery

***Update: Solved. The solution was a complete reinstall of jellyfin and not using the old database. 

[TheDreadPirate]

Can you share your full jellyfin log via pastebin? There were a lot of playlist changes and fixes since 10.9.1.

[anonymoustumbleweed]

Can you share your full jellyfin log via pastebin?  There were a lot of playlist changes and fixes since 10.9.1.

I added the logfiles via pastebin to my original post. Thanks so much for inquiring about my issue.

[TheDreadPirate]

This looks like a docker container. Did any of the upgrades since 10.9.1 get interrupted? As in you started the container, the UI didn't come up, so you killed the container and restarted it. Because it looks like the database is corrupt.

[anonymoustumbleweed]

This looks like a docker container.  Did any of the upgrades since 10.9.1 get interrupted?  As in you started the container, the UI didn't come up, so you killed the container and restarted it.  Because it looks like the database is corrupt.

Yes, it is in a docker container. I think you might be on to something. Damn, I was planning to open up a new jellyfin docker instance on another computer to see if this gets resolved. Let me do that now. Thanks for the response!