3 hours ago, SBH said:

scanning don't found anything.

I think, I got it.

 

I need folders. Currently all data in one folder.

 

No action required from your side.

I have to check this first 

 

 

It works now. Minimum one folder is required in the root

Edited January 28, 20233 yr by SBH
Solved

3 hours ago, SBH said:

I need folders

 

For the case that someone need to do the same.

 

With following command you will get an order for each .epub element.

Please make Sure that the folder is correct.

When you have other Elements, you have to change .epub to your element type 

 

find /mnt/user/ebooks/Books -name "*.epub" -exec sh -c 'mkdir "${1%.*}" && mv "$1" "${1%.*}"' _ {} \;
 

So i installed Kavita last night and let it scan my ebooks/comics/etc.

 

I'm getting this error:

There was an issue writing to the DB for Series API.Entities.Series An error occurred while saving the entity changes.

See the inner exception for details.

 

Not sure how to get to the inner exception. but i have included pics. and this is from the docker log..

Quote

[Kavita] [2023-04-02 18:08:07.395 -06:00  71] [Error] Microsoft.EntityFrameworkCore.Database.Command Failed executing DbCommand (2ms) [Parameters=[@p0='?' (Size = 9), @p1='?' (Size = 9)], CommandType='"Text"', CommandTimeout='30']
INSERT INTO "Genre" ("NormalizedTitle", "Title")
VALUES (@p0, @p1);
SELECT "Id"
FROM "Genre"
WHERE changes() = 1 AND "rowid" = last_insert_rowid();
[Kavita] [2023-04-02 18:08:07.405 -06:00  71] [Error] Microsoft.EntityFrameworkCore.Update An exception occurred in the database while saving changes for context type 'API.Data.DataContext'.
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
 ---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: Genre.NormalizedTitle'.
   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.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
 ---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: Genre.NormalizedTitle'.
   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.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
[Kavita] [2023-04-02 18:08:07.410 -06:00  71] [Fatal] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] There was an issue writing to the database for series Age of Heroes
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
 ---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: Genre.NormalizedTitle'.
   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.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
   at API.Data.UnitOfWork.CommitAsync() in /home/runner/work/Kavita/Kavita/API/Data/UnitOfWork.cs:line 81
   at API.Services.Tasks.Scanner.ProcessSeries.ProcessSeriesAsync(IList`1 parsedInfos, Library library, Boolean forceUpdate) in /home/runner/work/Kavita/Kavita/API/Services/Tasks/Scanner/ProcessSeries.cs:line 206
[Kavita] [2023-04-02 18:08:07.413 -06:00  71] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Beginning series update on 201507 Avengers in Gearing Up
[Kavita] [2023-04-02 18:08:07.461 -06:00  71] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Processing series 201507 Avengers in Gearing Up
[Kavita] [2023-04-02 18:08:07.461 -06:00  71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Updating 1 volumes on 201507 Avengers in Gearing Up
[Kavita] [2023-04-02 18:08:07.462 -06:00  71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Looking up volume for 0
[Kavita] [2023-04-02 18:08:07.462 -06:00  71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Parsing 201507 Avengers in Gearing Up - Volume 0
[Kavita] [2023-04-02 18:08:07.462 -06:00  71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Adding new chapter, 201507 Avengers in Gearing Up - Vol 0 Ch 1
[Kavita] [2023-04-02 18:08:07.574 -06:00  14] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Finished series update on Secret in 6506 ms
[Kavita] [2023-04-02 18:08:07.574 -06:00  14] [Debug] API.Services.MetadataService [MetadataService] Processing cover image generation for series: Secret
[Kavita] [2023-04-02 18:08:07.577 -06:00  14] [Debug] API.Services.MetadataService [MetadataService] Generating cover image for /library/[Comics]/[New]/[From DC++]/Marvel (2019)/0/Nueva carpeta/Comics/2012/4/Abril 2012 1ª quincena/Secret 001 (2012) (Digital) (Fawkes-Empire).cbr
[Kavita] [2023-04-02 18:08:07.589 -06:00  71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Updated 201507 Avengers in Gearing Up volumes from count of 0 to 1
[Kavita] [2023-04-02 18:08:07.590 -06:00  71] [Debug] API.Services.Tasks.Scanner.ProcessSeries Updating 201507 Avengers in Gearing Up FolderPath to /library/[Comics]/[New]/[From DC++]

(process:8): VIPS-WARNING **: 18:08:07.643: unknown JFIF resolution unit

(process:8): VIPS-WARNING **: 18:08:07.659: unknown JFIF resolution unit

(process:8): VIPS-WARNING **: 18:08:07.668: unknown JFIF resolution unit
[Kavita] [2023-04-02 18:08:07.712 -06:00  14] [Debug] API.Services.MetadataService [MetadataService] Generating cover image for /library/[Comics]/[New]/[From DC++]/Marvel (2019)/0/Nueva carpeta/Comics/2012/6/Junio 1 semana 2012/Secret 002 (2012) (Digital) (Fawkes-Empire).cbr
[Kavita] [2023-04-02 18:08:07.812 -06:00  55] [Information] Serilog.AspNetCore.RequestLoggingMiddleware HTTP GET /api/series/6733 responded 200 in 12.5737 ms
[Kavita] [2023-04-02 18:08:07.839 -06:00  14] [Debug] API.Services.MetadataService [MetadataService] Generating cover image for /library/[Comics]/[New]/[From DC++]/Marvel (2019)/0/Nueva carpeta/Comics/2013/8/Agosto 2013/Secret 003 (2013) (Digital) (Fawkes-Empire).cbr
[Kavita] [2023-04-02 18:08:13.611 -06:00  14] [Information] API.Services.MetadataService [MetadataService] Updated covers for Secret in 6036 milliseconds
[Kavita] [2023-04-02 18:08:13.611 -06:00  14] [Debug] API.Services.MetadataService Dispatching 5 update events
[Kavita] [2023-04-02 18:08:13.612 -06:00  14] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Beginning series update on X-Men Series
[Kavita] [2023-04-02 18:08:13.665 -06:00  14] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Processing series X-Men Series
[Kavita] [2023-04-02 18:08:13.665 -06:00  14] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Updating 1 volumes on X-Men Series
[Kavita] [2023-04-02 18:08:13.665 -06:00  14] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Looking up volume for 0
[Kavita] [2023-04-02 18:08:13.666 -06:00  14] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Parsing X-Men Series - Volume 0
[Kavita] [2023-04-02 18:08:13.666 -06:00  14] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Adding new chapter, X-Men Series - Vol 0 Ch 1
[Kavita] [2023-04-02 18:08:13.706 -06:00  14] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Adding new chapter, X-Men Series - Vol 0 Ch 2
[Kavita] [2023-04-02 18:08:13.795 -06:00  55] [Information] API.Services.Tasks.Metadata.WordCountAnalyzerService [WordCountAnalyzerService] Updated metadata for Secret in 180 milliseconds
[Kavita] [2023-04-02 18:08:14.134 -06:00  14] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Updated X-Men Series volumes from count of 0 to 1
[Kavita] [2023-04-02 18:08:14.134 -06:00  14] [Debug] API.Services.Tasks.Scanner.ProcessSeries Updating X-Men Series FolderPath to /library/[Comics]/[New]/[From DC++]
[Kavita] [2023-04-02 18:08:17.540 -06:00  71] [Error] Microsoft.EntityFrameworkCore.Database.Command Failed executing DbCommand (2ms) [Parameters=[@p0='?' (Size = 9), @p1='?' (Size = 9)], CommandType='"Text"', CommandTimeout='30']
INSERT INTO "Genre" ("NormalizedTitle", "Title")
VALUES (@p0, @p1);
SELECT "Id"
FROM "Genre"
WHERE changes() = 1 AND "rowid" = last_insert_rowid();
[Kavita] [2023-04-02 18:08:17.550 -06:00  71] [Error] Microsoft.EntityFrameworkCore.Update An exception occurred in the database while saving changes for context type 'API.Data.DataContext'.
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
 ---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: Genre.NormalizedTitle'.
   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.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
 ---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: Genre.NormalizedTitle'.
   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.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
[Kavita] [2023-04-02 18:08:17.555 -06:00  71] [Fatal] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] There was an issue writing to the database for series 201507 Avengers in Gearing Up
Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
 ---> Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 19: 'UNIQUE constraint failed: Genre.NormalizedTitle'.
   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.ExecuteReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.ExecuteAsync(IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
   at API.Data.UnitOfWork.CommitAsync() in /home/runner/work/Kavita/Kavita/API/Data/UnitOfWork.cs:line 81
   at API.Services.Tasks.Scanner.ProcessSeries.ProcessSeriesAsync(IList`1 parsedInfos, Library library, Boolean forceUpdate) in /home/runner/work/Kavita/Kavita/API/Services/Tasks/Scanner/ProcessSeries.cs:line 206
[Kavita] [2023-04-02 18:08:17.559 -06:00  71] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Beginning series update on 1978-12 Flintstones
[Kavita] [2023-04-02 18:08:17.622 -06:00  71] [Information] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Processing series 1978-12 Flintstones
[Kavita] [2023-04-02 18:08:17.623 -06:00  71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Updating 1 volumes on 1978-12 Flintstones
[Kavita] [2023-04-02 18:08:17.623 -06:00  71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Looking up volume for 1
[Kavita] [2023-04-02 18:08:17.624 -06:00  71] [Debug] API.Services.Tasks.Scanner.ProcessSeries [ScannerService] Parsing 1978-12 Flintstones - Volume 1

 

and I dunno what to do or how to fix it?

No support issue, just some feedback. I gave it a try and it's a nice app, easy to install but I went back to Ubooquity because I prefer the app using the folder names and structuring accordingly. This app doesn't organize as well or as easily.

Hi, I just installed this app/container and my mapped folder is not displaying any content. I am mapping it to a SMB share. Also, whenever I restart the container, everything resets. I have to set everything up again. Thanks for your help.

Hi All,

 

I hope you can help me,

 

I have been running Kavita on my server now through docker on unraid for a little over a  year.  It seems that every time an update comes out for it it wipes out the wh ole server. Users, directories to books, comics, and I  have to go in and re setup things again.  Is this a normal problem or is there a way to fix this?  This just happened with the latest release and the previous one. 

 

Any help is appreciated very much.

 

Thanks,

 

Drezin

I installed and used Kavita for a month now.

 

Every time I have to add a book, It is a pain-in-the-*

I am never really sure if scanning the library will add it because it most probably will not. If you have a large library and you are not sitting there scanning the library manually you may not realize all the books that are not added to library. There is no log or no error message that popup up to say "Hey, we found this file but cannot add it for reason xyz", or "Hey, we added these titles to library but could not match metadata, match by ISBN# or something".

 

Then I have to fiddle around with creating folders for each book, even then it does not pick up files on the first go and doesn't even say the reason. I haven't been able to pick up .mobi files yet.

I am not sure what the folder structure is because it is not mentioned in the docs.

 

If I have omitted something feel free to help me out here.

I want to genuinely use this as a daily driver, but can't because of the issues I have faced.

 

 

TL;DR - UI is intuitive, good and responsive overall, Adding books can be a pain on another level. Unless there is a way to automate the File download and folder organizing like *arr/plex pairing, I don't see myself switching.

 

Cheers!

Edited June 7, 20233 yr by Shomil Saini

46 minutes ago, Shomil Saini said:

I installed and used Kavita for a month now.

 

Every time I have to add a book, It is a pain-in-the-*

I am never really sure if scanning the library will add it because it most probably will not. If you have a large library and you are not sitting there scanning the library manually you may not realize all the books that are not added to library. There is no log or no error message that popup up to say "Hey, we found this file but cannot add it for reason xyz", or "Hey, we added these titles to library but could not match metadata, match by ISBN# or something".

 

Then I have to fiddle around with creating folders for each book, even then it does not pick up files on the first go and doesn't even say the reason. I haven't been able to pick up .mobi files yet.

I am not sure what the folder structure is because it is not mentioned in the docs.

 

If I have omitted something feel free to help me out here.

I want to genuinely use this as a daily driver, but can't because of the issues I have faced.

 

 

TL;DR - UI is intuitive, good and responsive overall, Adding books can be a pain on another level. Unless there is a way to automate the File download and folder organizing like *arr/plex pairing, I don't see myself switching.

v.0.7.3 may be able to address this. At the time of writing, it was released about 6 hours ago. You can see the change here under "Media Errors" https://github.com/Kareadita/Kavita/releases/tag/v0.7.3
 

Kavita does not support .mobi files, you'd have to convert them to EPUB. You can see the supported file formats here: https://wiki.kavitareader.com/en

45 minutes ago, Shivam Amin said:

v.0.7.3 may be able to address this. At the time of writing, it was released about 6 hours ago. You can see the change here under "Media Errors" https://github.com/Kareadita/Kavita/releases/tag/v0.7.3
 

Kavita does not support .mobi files, you'd have to convert them to EPUB. You can see the supported file formats here: https://wiki.kavitareader.com/en

Thanks for your helpful comment and pointing out the supported formats.

I am already updated to v0.7.3.

If you happen to know about folder structure and how to manage multiple editions of books and multiple file formats please let me know.

 

Cheers!

Hey I'm attempting was setting email and I overshoot past the config file into the templates so I got distracted on that it's the one time I'm thankful for ADHD. I browse through them and saw they're heavy on the trackers and CDNs. And on an inbox there's no reverse proxy to block the scripts with CSPs…plus, I'd kind of like to design my own from scratch.

 

Do you know by chance how these work? Are they parsed (the placeholders) before sending the email, or is there anything noteworthy about them? And, are the placeholders expected to be just markup or some kind of script or syntax?

 

Thanks!

On 6/7/2023 at 2:28 PM, Shomil Saini said:

Thanks for your helpful comment and pointing out the supported formats.

I am already updated to v0.7.3.

If you happen to know about folder structure and how to manage multiple editions of books and multiple file formats please let me know.

 

Cheers!

I'm not sure about editions, but file/folder structure is defined here (With more specific structure based on type): https://wiki.kavitareader.com/en/guides/managing-your-files
You should also read this: https://wiki.kavitareader.com/en/guides/managing-your-files/scanner

On 6/15/2023 at 5:45 PM, Shivam Amin said:

I'm not sure about editions, but file/folder structure is defined here (With more specific structure based on type): https://wiki.kavitareader.com/en/guides/managing-your-files
You should also read this: https://wiki.kavitareader.com/en/guides/managing-your-files/scanner

Thanks for the links, I did some reading and fiddling with my setup and to be honest it is still messier than other *arrs suite I am used to.

• It does not manage revisions of books i.e. 2022 edition vs 2023 edition of the same book in a single folder.
• There is no consistent file naming structure I can adhere to for mixed file types i.e. some as pdf or epub.

It just might not be for my use case, but I just want to throw some books at it and let it organize like plex does for my media. 🤷🏽‍♂️ I might give it another go in a few months.

 

Cheers!

On 5/7/2023 at 11:17 PM, Drezin said:

Hi All,

 

I hope you can help me,

 

I have been running Kavita on my server now through docker on unraid for a little over a  year.  It seems that every time an update comes out for it it wipes out the wh ole server. Users, directories to books, comics, and I  have to go in and re setup things again.  Is this a normal problem or is there a way to fix this?  This just happened with the latest release and the previous one. 

 

Any help is appreciated very much.

 

Thanks,

 

Drezin

 

I'm experiencing this too. Anyone know of a fix for this?

Really unhappy to set up the library folders and users every time an update shows ... will try the linuxserver kavita to check if it´s happening there too

On 5/8/2023 at 1:17 PM, Drezin said:

Hi All,

 

I hope you can help me,

 

I have been running Kavita on my server now through docker on unraid for a little over a  year.  It seems that every time an update comes out for it it wipes out the wh ole server. Users, directories to books, comics, and I  have to go in and re setup things again.  Is this a normal problem or is there a way to fix this?  This just happened with the latest release and the previous one. 

 

Any help is appreciated very much.

 

Thanks,

 

Drezin

 

 

I had the same issue with it wiping my library/user settings with every update

 

Make sure you set a "Data Directory" in the container settings

I set mine to /mnt/user/appdata/Kavita/

 

My guess is if you don't set the data directory then it stores the files in the docker image that gets wiped when you update

Edited September 16, 20232 yr by deltoran

Really unhappy to set up the library folders and users every time an update shows ... will try the linuxserver kavita to check if it´s happening there too

 

no problems with the linuxserver repro - so to me this seems to bad setup on the repro manger.

This just happened again with me; Docker update losing settings.

I double-checked the container and my Data Directory, "Container Path: /config" was set to "/kavita/config". I changed this to "/config" and it restored my settings. Maybe this location changed?

Hi! I have issues logging in on any of my users.

I can reset password succesfully but when logging in, i get a red error message in the lower right but no text in it.

When looking at the logs, the user logs in succesfully but they are stuck at the log in screen.

However, when going to the /libraries subdomain, i dó get access.

So seems the login page doesn't forward correctly and the password wasn't the initial issue at all?

 

Is this a known bug or do i have a local issue?

Thanks for the help in advance!

 

I am receiving the following error in the logs when trying to use Komf with Kavita:

 

 

22:09:33.602 [RxCachedThreadScheduler-1] ERROR org.snd.mediaserver.kavita.KavitaEventListener -- kotlin.Unit
javax.net.ssl.SSLException: Unsupported or unrecognized SSL message

 

 

Any idea what might be causing this?

Figured out my SSL error.  Just user error.  I had put HTTPS for my Ka it’s URL in the docker setup.  Changing to HTTP fixed it.  
 

However, I am now trying to get it to scrap metadata for individual comics with Comicinfo.  It gives me an error that the file types are unsupported though.  My comics are cbr or cbz format so it shouldn’t be an issue.

On 4/2/2023 at 8:09 PM, DevXen said:

So i installed Kavita last night and let it scan my ebooks/comics/etc.

 

I'm getting this error:

There was an issue writing to the DB for Series API.Entities.Series An error occurred while saving the entity changes.

See the inner exception for details.

 

Not sure how to get to the inner exception. but i have included pics. and this is from the docker log..

 

and I dunno what to do or how to fix it?

I am receiving the same error.  I searched and found this: https://github.com/Kareadita/Kavita/issues/2248  However, the problem doesnt' seem resolved on our build? (v0.7.13) Was your issue on PDF's? Did you find a fix?

Edited February 7, 20242 yr by goldbondx

NAG screen in Kavita - Package version in APP store and source repository out of date

 

I have been using Kavita successfully on V0.7.08, when the application started to display a NAG screen saying that the version I am using (sourced from: jvmilazz0/kavita repository) is seriously out of date and that the current version V0.7.14.0 should be sourced. The NAG screen also mentioned that official Kavita repository has moved to jvmilazz0/kavita:latest

 

I managed to upgrade by changing the respository on the Update Container page to jvmilazz0/kavita:latest and restarting the application.

 

My question is: Can the Package setup in the apps store be updated to reflect the repository, so that updating of docker packages works seamlessly and it the application needs to be re-installed it does not revert to a lower version.  V0.7.14.0 - has made database changes and introduced new features a structures.

 

Thank you John

The Unraid app XML was updated when this change occurred, but if you were using the app before then you either have to manually change the image repo yourself or reinstall the app, seems like a limitation of how Unraid handles apps that it can't automatically switch this for you. But yeah manually switching it would be the best method for it as you've done here

Freshly installed Kavita on my trial unRaid, but I have no access to the admin setting dashboard.

Edit: after some test it work on Chrome and on Mobile (Firefox) but not on my Firefox Desktop 🤷‍♂️

Edited April 6, 20242 yr by Exxaxion

I am currently getting the nag screen to update to jvmilazz0/kavita:latest.  I changed this in the Update Container screen, let it do its thing, and I'm still getting the error.  I then removed the image and reinstalled - still get the nag screen.  When I updated it myself, I used :latest.  When I reinstalled it, :latest was left off.  I added it back in after I still got the nag screen.

 

If I Okay through the nag screen, it loads into Kavita but nothing works (and nothing shows up).  I can still browse and access the books through my devices.

 

 

 

I normally don't even log into Kavita, so I didn't see any warnings for updates as they were happening.  Any ideas on what I could do to fix it?