| Summary: | Database process exited unexpectedly during initial connection. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | battyanyi.dani |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | Flags: | battyanyi.dani:
Backport+
|
| Version: | 8.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 8.2.0 | |
| Sentry Crash Report: | |||
|
Description
battyanyi.dani
2022-06-08 13:57:00 UTC
digiKam-8.0.0 from git/master is alpha status. Only use it if you know what you are doing and not in a productive environment. It is currently not tested with MariaDB-10.8.x. Maik You know that MariaDB-10.8.3 is alpha and not intended to be used in production environment? The digiKam log looks like a crash in MariaDB. Please send a complete log to see the database creation. Maik (In reply to Maik Qualmann from comment #2) > You know that MariaDB-10.8.3 is alpha and not intended to be used in > production environment? The digiKam log looks like a crash in MariaDB. > Please send a complete log to see the database creation. > > Maik (In reply to Maik Qualmann from comment #1) > digiKam-8.0.0 from git/master is alpha status. Only use it if you know what > you are doing and not in a productive environment. It is currently not > tested with MariaDB-10.8.x. > > Maik I've tried it after the stable release version didn't work to check if the alpha version works better. Switched back to 7.6.0 when it failed as well. (In reply to Maik Qualmann from comment #2) > You know that MariaDB-10.8.3 is alpha and not intended to be used in > production environment? The digiKam log looks like a crash in MariaDB. > Please send a complete log to see the database creation. > > Maik Do you mean the mariadb log? If so, where can I find it? I've been playing around with it for a little bit, and as it turns out if i delete/rename all of these: ~/.local/share/digikam/db_misc/mysql.socket ~/Pictures/.mysql.digikam/ ~/.local/share/digikam/mysql.conf ~/.config/digikamrc, it succeeds in creating the database, but crashes when clicking "configure digikam" . [warn] epoll_wait: Bad file descriptor pa_write() failed while trying to wake up the mainloop: Bad file descriptor pa_write() failed while trying to wake up the mainloop: Bad file descriptor Invalid write to eventfd: Bad file descriptor [warn] epoll_wait: Bad file descriptor [warn] epoll_wait: Bad file descriptor [warn] epoll_wait: Bad file descriptor [warn] epoll_wait: Bad file descriptor Code should not be reached at ../pulseaudio/src/pulsecore/fdsem.c:188, function pa_fdsem_post(). Aborting. [warn] epoll_wait: Bad file descriptor Thread 36 "digikam" received signal SIGABRT, Aborted. [Switching to Thread 0x7fff6d7fa640 (LWP 1312231)] 0x00007ffff4a8e36c in ?? () from /usr/lib/libc.so.6 After that, on the second start digikam works fine, but on the third start it runs into the database problem. If the program exits correctly it fails to load the database after restarting it. (In reply to battyanyi.dani from comment #5) > I've been playing around with it for a little bit, and as it turns out if i > delete/rename all of these: > > ~/.local/share/digikam/db_misc/mysql.socket > ~/Pictures/.mysql.digikam/ > ~/.local/share/digikam/mysql.conf > ~/.config/digikamrc, > > it succeeds in creating the database, but crashes when clicking "configure > digikam" . > > [warn] epoll_wait: Bad file descriptor > pa_write() failed while trying to wake up the mainloop: Bad file descriptor > pa_write() failed while trying to wake up the mainloop: Bad file descriptor > Invalid write to eventfd: Bad file descriptor > [warn] epoll_wait: Bad file descriptor > [warn] epoll_wait: Bad file descriptor > [warn] epoll_wait: Bad file descriptor > [warn] epoll_wait: Bad file descriptor > Code should not be reached at ../pulseaudio/src/pulsecore/fdsem.c:188, > function pa_fdsem_post(). Aborting. > [warn] epoll_wait: Bad file descriptor > > Thread 36 "digikam" received signal SIGABRT, Aborted. > [Switching to Thread 0x7fff6d7fa640 (LWP 1312231)] > 0x00007ffff4a8e36c in ?? () from /usr/lib/libc.so.6 > > After that, on the second start digikam works fine, but on the third start > it runs into the database problem. If the program exits correctly it fails > to load the database after restarting it. "After that, on the second start digikam works fine, but on the third start it runs into the database problem. If the program exits correctly it fails to load the database after restarting it." This last part is resolved by not deleting the "~/.local/share/digikam/db_misc/mysql.socket" file, only the rest of the ones above. Currently testing whether this resolves the issue completely. Here on openSUSE Tumbleweed with MariaDB-10.7.3 and digiKam-8.0.0 there are no problems with the database. Maik (In reply to Maik Qualmann from comment #7) > Here on openSUSE Tumbleweed with MariaDB-10.7.3 and digiKam-8.0.0 there are > no problems with the database. > > Maik I ended up resolving the issue by downgrading mariadb to version 10.7.4. It has been working ever since. Thank you for your help :). (In reply to Maik Qualmann from comment #2) > You know that MariaDB-10.8.3 is alpha and not intended to be used in > production environment? The digiKam log looks like a crash in MariaDB. > Please send a complete log to see the database creation. > > Maik No, mariadb 10.8.3 is a stable release. https://mariadb.org/mariadb/all-releases/ I also found a bug report for Akonadi on Archlinux. Is there any knowledge as to what the cause is? It looks like the database needs to be upgraded. digiKam, has detected from the MySQL error log whether an upgrade needs to be performed. We will probably have to set up a manual method for the user to initiate the upgrade. This issue relates to an internal MariaDB database managed by digiKam. Maik Ok, I see this option "mariadb-upgrade --check-if-upgrade-is-needed". We can do something with that if it's the cause. Maik (In reply to Maik Qualmann from comment #10) > I also found a bug report for Akonadi on Archlinux. Is there any knowledge > as to what the cause is? It looks like the database needs to be upgraded. > digiKam, has detected from the MySQL error log whether an upgrade needs to > be performed. We will probably have to set up a manual method for the user > to initiate the upgrade. The akonadi issue is caused by a missing ib_logfile0 file, which is mandatory in mariadb 10.8. No idea if this issue is related. See https://bugs.kde.org/show_bug.cgi?id=454948#c16 Hmm, we remove exactly this log file before we start the server... Maik Git commit 8d16ea2e3fddbfa9a1615d506c342070502d1ce9 by Maik Qualmann. Committed on 15/06/2022 at 18:26. Pushed by mqualmann into branch 'master'. do not remove the MySQL log files M +2 -2 core/libs/database/server/databaseserver.cpp https://invent.kde.org/graphics/digikam/commit/8d16ea2e3fddbfa9a1615d506c342070502d1ce9 Arch users please test digikam 7.6.0-5 @battyanyi.dani@gmail.com digiKam 8.0.0 is released. This file still valid ? Gilles Caulier @ battyanyi.dani@gmail.com, What's about this file using current 8.2.0 AppImage Linux bundle ? It's reproducible ? https://files.kde.org/digikam/ Thanks in advance Gilles Caulier Fixed with Bug 475874 Maik |