Hello together,
got new problem’s with komga …
it runs a long time without big errors (often a reboot solved little ones) but now it doesn’t works anymore an stopped with an error
root@pinas:~# systemctl status komga.service
● komga.service - Komga (DietPi)
Loaded: loaded (/etc/systemd/system/komga.service; disabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/komga.service.d
└─dietpi-services_edit.conf
Active: failed (Result: exit-code) since Sat 2023-03-25 12:31:13 CET; 2min 20s ago
Process: 22016 ExecStart=/usr/bin/java -Xmx379m -jar komga.jar (code=exited, status=1/FAILURE)
Main PID: 22016 (code=exited, status=1/FAILURE)
CPU: 36.529s
Mar 25 12:31:13 pinas Komga[22016]: ... 124 common frames omitted
Mar 25 12:31:13 pinas Komga[22016]: Caused by: java.lang.Exception: No native library found for os.name=Linux, os.arch=aarch64, paths=[/org/sqlite/native/Linux/aarch64:/usr/java/packages/lib:/usr/lib/arm-linux-gnueabihf/jni:/lib/arm-linux-gnueabihf:/usr/lib/arm-linux-gnueabihf:/usr/lib/jni:/lib:/usr/lib]
Mar 25 12:31:13 pinas Komga[22016]: at org.sqlite.SQLiteJDBCLoader.loadSQLiteNativeLibrary(SQLiteJDBCLoader.java:375) ~[sqlite-jdbc-3.40.1.0.jar!/:na]
Mar 25 12:31:13 pinas Komga[22016]: at org.sqlite.SQLiteJDBCLoader.initialize(SQLiteJDBCLoader.java:68) ~[sqlite-jdbc-3.40.1.0.jar!/:na]
Mar 25 12:31:13 pinas Komga[22016]: at org.sqlite.core.NativeDB.load(NativeDB.java:67) ~[sqlite-jdbc-3.40.1.0.jar!/:na]
Mar 25 12:31:13 pinas Komga[22016]: at org.sqlite.SQLiteConnection.open(SQLiteConnection.java:278) ~[sqlite-jdbc-3.40.1.0.jar!/:na]
Mar 25 12:31:13 pinas Komga[22016]: ... 136 common frames omitted
Mar 25 12:31:13 pinas systemd[1]: komga.service: Main process exited, code=exited, status=1/FAILURE
Mar 25 12:31:13 pinas systemd[1]: komga.service: Failed with result 'exit-code'.
Mar 25 12:31:13 pinas systemd[1]: komga.service: Consumed 36.529s CPU time.
I’ve also increased the memory (normally it runs with 1024M) … same error
There is something wrong with the embedded library:
Mar 25 14:14:32 pinas Komga[1108]: OpenJDK Client VM warning: You have loaded library /tmp/sqlite-3.40.1.0-d7f867f1-22a8-470e-96bc-6cd28c8a0d73-libsqlitejdbc.so which might have disabled stack guard. The VM will try to fix the stack guard now.
Mar 25 14:14:32 pinas Komga[1108]: It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
Mar 25 14:14:32 pinas Komga[1108]: Failed to load native library:sqlite-3.40.1.0-d7f867f1-22a8-470e-96bc-6cd28c8a0d73-libsqlitejdbc.so. osinfo: Linux/aarch64
Mar 25 14:14:32 pinas Komga[1108]: java.lang.UnsatisfiedLinkError: /tmp/sqlite-3.40.1.0-d7f867f1-22a8-470e-96bc-6cd28c8a0d73-libsqlitejdbc.so: /tmp/sqlite-3.40.1.0-d7f867f1-22a8-470e-96bc-6cd28c8a0d73-libsqlitejdbc.so: wrong ELF class: ELFCLASS64 (Possible cause: can't load AARCH64 .so on a ARM platform)
Ah, now I see the problem: You enabled 64-bit kernel mode on a Raspbian userland. Strangely we had another case of this, so probably it is actually a bug in the RPi bootloader loading the 64-bit kernel in some circumstances even that it is not configured to do so. Is there a line arm_64bit=1 in your /boot/config.txt? If so, remove it, reboot and reinstall Komga:
The vcgencmd output indeed indicates that arm_64bit=1 was set by default and hence setting it to 0 explicitly needed. I wonder whether this is a bug or an explicit/intended change on e.g. RPi 4, which would be very troublesome.
But year, to maintain SD card exchangeability it makes sense to simply set it explicitly in all cases. In the meantime, I posted on the RPi forum as well, asking to revert it as it breaks relying on uname -m and as it doesn’t make any sense to run a 32-bit OS with 64-bit kernel. Let’s see whether/what the reaction is.
