2024-09-04, 07:42 AM
Hmm, frustratingly, it seems I now can't log into the server at all. It asks me to "Please sign in", but there shouldn't be any users yet. I would have expected the start wizard.
While looking at what files were different between the backup and new jellyfin folders, I found a few things:
Jellyfin has not recreated many files or folders. Most of these make sense, but the config folder hasn't been recreated, and I'm not sure if that's an issue yet.
There's a migrations.xml in the old config folder of jellyfin. This one hadn't been updated since 2022. Until now, I'd been looking at the migrations.xml in my own config folder for my user, which is more recent. I'm not sure what this means, but renaming this older one doesn't help either (when I put the backup version back in place and run jellyfin again).
I found that the final logs inside
The logs from the two days before that do not.
On that note, the logs seem to have changed their filenames in June, so I have the old logs for June 10, 12, and 13, none of which show the database errors.
Ok, that was a lot of rambling, but it does seem I am somehow kinda' stuck. If I remove the old jellyfin folder, I can't log in. If I uninstall and reinstall the jellyfin server package, nothing changes. If I return the old jellyfin folder, I can log in again, but the errors still occur.
While looking at what files were different between the backup and new jellyfin folders, I found a few things:
Jellyfin has not recreated many files or folders. Most of these make sense, but the config folder hasn't been recreated, and I'm not sure if that's an issue yet.
There's a migrations.xml in the old config folder of jellyfin. This one hadn't been updated since 2022. Until now, I'd been looking at the migrations.xml in my own config folder for my user, which is more recent. I'm not sure what this means, but renaming this older one doesn't help either (when I put the backup version back in place and run jellyfin again).
I found that the final logs inside
/var/lib/jellyfinBKUP/logs
were from November 19th last year, the same time as the last time my (not Jellyfin's) migrations.xml was modified. Not sure why these are here and the newer logs are in var/log/jellyfin
. The final day contains repeated instances of this:Code:
[2023-11-19 20:24:15.389 +11:00] [ERR] [141] Jellyfin.Server.Middleware.ExceptionMiddleware: Error processing request: "Could not load file or assembly 'Microsoft.AspNetCore.WebUtilities, Ve
rsion=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.
". URL "GET" "/system/info/public".
[2023-11-19 20:24:15.389 +11:00] [ERR] [141] Microsoft.AspNetCore.Server.Kestrel: Connection id ""0HMV8QE7CH1JB"", Request id ""0HMV8QE7CH1JB:00000002"": An unhandled exception was thrown by
the application.
System.TypeInitializationException: The type initializer for 'Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.ReasonPhrases' threw an exception.
---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.AspNetCore.WebUtilities, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.
File name: 'Microsoft.AspNetCore.WebUtilities, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.ReasonPhrases..cctor()
--- End of inner exception stack trace ---
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.ReasonPhrases.ToStatusBytes(Int32 statusCode, String reasonPhrase)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1OutputProducer.WriteResponseHeadersInternal(BufferWriter`1& writer, Int32 statusCode, String reasonPhrase, HttpResponseHeaders responseHeaders, Boolean autoChunk)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Http1OutputProducer.WriteResponseHeaders(Int32 statusCode, String reasonPhrase, HttpResponseHeaders responseHeaders, Boolean autoChunk, Boolean appComplete)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProduceStart(Boolean appCompleted)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.InitializeResponseAsync(Int32 firstWriteByteCount)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.Microsoft.AspNetCore.Http.Features.IHttpResponseBodyFeature.StartAsync(CancellationToken cancellationToken)
at Microsoft.AspNetCore.Http.DefaultHttpResponse.StartAsync(CancellationToken cancellationToken)
at Microsoft.AspNetCore.Http.HttpResponseWritingExtensions.WriteAsync(HttpResponse response, String text, Encoding encoding, CancellationToken cancellationToken)
at Microsoft.AspNetCore.Http.HttpResponseWritingExtensions.WriteAsync(HttpResponse response, String text, CancellationToken cancellationToken)
at Jellyfin.Server.Middleware.ExceptionMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.InvokeCore(HttpContext context, PathString matchedPath, PathString remainingPath)
at Jellyfin.Server.Middleware.BaseUrlRedirectionMiddleware.Invoke(HttpContext httpContext, IServerConfigurationManager serverConfigurationManager)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)
On that note, the logs seem to have changed their filenames in June, so I have the old logs for June 10, 12, and 13, none of which show the database errors.
Ok, that was a lot of rambling, but it does seem I am somehow kinda' stuck. If I remove the old jellyfin folder, I can't log in. If I uninstall and reinstall the jellyfin server package, nothing changes. If I return the old jellyfin folder, I can log in again, but the errors still occur.