error window in jellyfin.exe

[ermejor]

  log_20240603-2.zip (Size: 433.14 KB / Downloads: 82)
Since version 10.9.1 and subsequent versions, including 10.9.4, an error window appears randomly in jellyfin.exe, the server stops and I have to restart it to get it working again. The same thing can appear 10 minutes after the server is running or it can appear after 3 hours or 5 hours... it has never taken more than 15 hours to appear. I don't know the reason, but it didn't happen to me in version 10.8.13. The only thing that usually coincides is that it usually happens more easily if the number of users connected to the server is greater. I am sending you the .log file to see if it is due to some problem of mine or something that needs to be addressed in future versions of Jellyfin.

[TheDreadPirate]

Can you share your full jellyfin logs via pastebin?

[ermejor]

It is very long and the browser won't let me paste it, so I sent it as a compressed attachment

[TheDreadPirate]

It looks like you have a device with an expired token somewhere that is trying to continuously authenticate, which is why your log is so large. There is no way to tell which device is causing this.

Code:

[2024-06-03 21:50:09.813 +02:00] [INF] [51] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-06-03 21:50:09.866 +02:00] [INF] [58] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-06-03 21:50:09.867 +02:00] [INF] [58] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."

I am not sure if these invalid token messages are the cause, but eventually I start seeing these messages.

Code:

[2024-06-03 21:51:52.170 +02:00] [ERR] [134] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request. URL "POST" "/Sessions/Playing/Progress".
Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 5: 'database is locked'.

Here is what I recommend. You're going to need to revoke all the active tokens and ask all your users to log back in.

Dashboard > Devices > Delete All

This will revoke all the tokens for all users and devices. Everyone will need to log back in on every device they have. Hopefully the invalid token message stops and this problem goes away as well.

[ermejor]

These messages already appeared in previous versions of the server and they did not cause me any problems. Have you seen the final part of the file I sent you? I think that is where the problem must be because the .log file ends just when the program gives the error.

[TheDreadPirate]

I don't see any other issues in your log.

Regardless, this is something you should deal with. 90% of your log is that message or the database lock message.

A lot of the other mitigations for the database lock message are related to library scans or trickplay generation, but neither of those things are happening when the database lock message appears.

There is an open issue for this message and the devs are still trying to track it down.

https://github.com/jellyfin/jellyfin/issues/11813

[ermejor]

ok. Thank you very much