search

gotson / komga

Media server for comics/mangas/BDs/magazines/eBooks with API, OPDS and Kobo Sync support
https://komga.org
MIT License
4.06k stars 240 forks source link

[Bug] cannot update read progress on FreeBSD #319

Closed garbled1 closed 4 years ago

garbled1 commented 4 years ago

Komga environment

Describe the bug

The application runs fine, I can load new comics in just great, but when I finish reading one, it doesn't save my spot, or allow me to mark anything as read.

Steps to reproduce

  1. Go to any comic
  2. Read it.
  3. Still stays orange.

Expected behavior

Mark comics as read

Actual behavior

Not marked read

Additional context

na

Screenshots

na

Log file

Whenever I trigger a mark of read, I get this in the log. I do have a database. I can login, my comics exist, everything works fine except marking my spot. I simply run the jar, no magical configuration.

2020-09-10 18:52:18.302 INFO 84568 --- [nio-8080-exec-8] o.g.k.domain.service.SeriesLifecycle : House keeping thumbnails for series: 02HAHBAMYTY62 2020-09-10 18:52:33.834 ERROR 84568 --- [nio-8080-exec-9] o.a.c.c.C.[.[.[/].[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.springframework.jdbc.UncategorizedSQLException: jOOQ; uncategorized SQLException for SQL [insert into READ_PROGRESS (BOOK_ID, USER_ID, PAGE, COMPLETED) values (?, ?, ?, ?) on conflict (BOOK_ID, USER_ID) do update set PAGE = ?, COMPLETED= ?, LAST_MODIFIED_DATE = ?]; SQL state [null]; error code [1]; [SQLITE_ERROR] SQL error or missing database (near "on": syntax error); nested exception is org.sqlite.SQLiteException: [SQLITE_ERROR] SQL error or missing database (near "on": syntax error)] with root cause

org.sqlite.SQLiteException: [SQLITE_ERROR] SQL error or missing database (near "on": syntax error) at org.sqlite.core.DB.newSQLException(DB.java:1010) ~[sqlite-jdbc-3.32.3.2.jar!/:na] at org.sqlite.core.DB.newSQLException(DB.java:1022) ~[sqlite-jdbc-3.32.3.2.jar!/:na] at org.sqlite.core.DB.throwex(DB.java:987) ~[sqlite-jdbc-3.32.3.2.jar!/:na] at org.sqlite.core.NativeDB.prepare_utf8(Native Method) ~[sqlite-jdbc-

gotson commented 4 years ago

Can you enable debug logs, and also do the same for logging.level.org.jooq=DEBUG, then send me the complete log file?

garbled1 commented 4 years ago

log.log

gotson commented 4 years ago

right now the only hint i have would be that the database is not writable, maybe a file permission access.

Can you try to add a new user? We can verify that the inserts are working and rule out a database permission.

garbled1 commented 4 years ago

2020-09-11 06:15:03.856 INFO 41874 --- [DefaultMessageListenerContainer-1] o.g.komga.application.tasks.TaskHandler : Task ScanLibrary(libraryId=02HAHBA3ATWAK) executed in 1.59s 2020-09-11 06:16:51.115 INFO 41874 --- [http-nio-8080-exec-5] o.g.k.domain.service.KomgaUserLifecycle : User created: KomgaUser(email='test@test.com', roleAdmin=false, roleFileDownload=true, rolePageStreaming=true, sharedLibrariesIds=[],sharedAllLibraries=true, id=02HXT6GZ3DTKE, createdDate=2020-09-11T06:16:50, lastModifiedDate=2020-09-11T06:16:50)

I assume book data is stored in the database? I don't have to rescan all my books every time I start the server. It appears the db is writable.. Also my initial user is still there... it also let me delete that newuser just fine...

Basically, I more or less followed the link in the guide for installing in a FreeNAS jail. Only difference was I used the latest release instead of whatever version he said, and I did use openjdk 11 as I think you commented. I then mounted 2 nas volumes, one full of pdfs, the other full of hand-made cbz's, and imported them. This was basically yesterday.

The cbz's are just zips of 30 jpgs each. No metadata files or anything in them. I just double-checked, it doesn't mark my PDF's as read either.

gotson commented 4 years ago

Yes, everything is stored in the database.

gotson commented 4 years ago

Could you advise what's your hardware, especially the cpu architecture?

garbled1 commented 4 years ago

FreeBSD 11.3-RELEASE-p11 CPU: AMD Opteron(TM) Processor 6212 (2600.06-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x600f12 Family=0x15 Model=0x1 Stepping=2 Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> Features2=0x1e98220b<SSE3,PCLMULQDQ,MON,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AESNI,XSAVE,OSXSAVE,AVX> AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM> AMD Features2=0x1c9bfff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,XOP,SKINIT,WDT,LWP,FMA4,NodeId,Topology,PCXC,PNXC> SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=65536 TSC: P-state invariant, performance statistics

gotson commented 4 years ago

I think I found the issue. Freenas is built on top of freebsd, and the sqlite library used in Komga seems to have an old version for freebsd, which doesn't support the upsert statement used for read progress update.

I'm trying first to check why the freebsd native binary for sqlite is outdated in that library.

If I can't get a decent answer or fix, I'll need to update the sql code in Komga to use a different query.

garbled1 commented 4 years ago

Any word on this? It makes it really hard to keep up on the comics I'm reading.. :)

richiecoy commented 4 years ago

Finally found this software and it's fantastic...however, I have this same issue. Installed in FreeNAS jail (freebsd) and get the same error when trying to mark something read. Is there a fix for this yet?

gotson commented 4 years ago

@richiecoy can you advise what is your cpu architecture?

gotson commented 4 years ago

:tada: This issue has been resolved in version 0.64.1 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

gotson commented 4 years ago

I have forked the sqlite-jdbc repo, merged 2 PRs that were adding/updating FreeBSD libraries, and published it on jcenter for my own consumption.

This should enhance support for FreeBSD for the following CPU architecture: x86, x64, arm64