[BUG] Microsoft SQL issues maybe

[johnson7827]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When updating the container I started to get SQL key errors attached below, so I thought it was an issue with the internal database not being able to upgrade correctly. So then I removed the docker container with the image and reinstalled, then looking at the logs it was providing the same error.

Expected Behavior

No response

Steps To Reproduce

1. Using unraid community apps install Kavita application
2. Check logs, application fails to start even from fresh install

Environment

- OS: Unraid
- How docker service was installed: Community Applications

CPU architecture

x86-64

Docker creation

n/a

Container logs

---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'FOREIGN KEY constraint failed'.
   at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
   at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject)
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.Execute(IRelationalConnection connection)
   --- End of inner exception stack trace ---
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.Execute(IRelationalConnection connection)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.Execute(IEnumerable`1 commandBatches, IRelationalConnection connection)
   at Microsoft.EntityFrameworkCore.Storage.RelationalDatabase.SaveChanges(IList`1 entries)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(IList`1 entriesToSave)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(StateManager stateManager, Boolean acceptAllChangesOnSuccess)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.<>c.<SaveChanges>b__114_0(DbContext _, ValueTuple`2 t)
   at Microsoft.EntityFrameworkCore.Storage.NonRetryingExecutionStrategy.Execute[TState,TResult](TState state, Func`3 operation, Func`3 verifySucceeded)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(Boolean acceptAllChangesOnSuccess)
   at Microsoft.EntityFrameworkCore.DbContext.SaveChanges(Boolean acceptAllChangesOnSuccess)
   at API.Data.DataContext.SaveChanges(Boolean acceptAllChangesOnSuccess) in /Users/amelia/Projects/Kavita/API/Data/DataContext.cs:line 561
   at Microsoft.EntityFrameworkCore.DbContext.SaveChanges()
   at API.Data.DataContext.SaveChanges() in /Users/amelia/Projects/Kavita/API/Data/DataContext.cs:line 554
   at API.Startup.Configure(IApplicationBuilder app, IWebHostEnvironment env, IHostApplicationLifetime applicationLifetime, IServiceProvider serviceProvider, IDirectoryService directoryService, IUnitOfWork unitOfWork, IVersionUpdaterService versionService) in /Users/amelia/Projects/Kavita/API/Startup.cs:line 283
   at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args)
   at System.Reflection.MethodBaseInvoker.InvokeWithManyArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[johnson7827]

Okay, so I discovered the issue may be unique to me. Though I haven't solved my own problem I did discover that a secondary install of kavita brings a properly working application. Even though I thought I was doing this by removing the docker image something in my instance is sticking and creating the issue, possibly a bad ebook file, just didn't think a bad ebook file would prevent it from starting when starting at square one.