| Summary: | "An error occurred during the internal server start" | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | coolmule0 |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.10.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.0.0 | |
| Sentry Crash Report: | |||
| Attachments: | ib_logfile0.zip | ||
|
Description
coolmule0
2023-03-19 13:17:42 UTC
I think we won't be able to do much here if the database is broken and MariaDB can't initialize it anymore. Start digiKam in the terminal and post the output. Set before the Qt debug variable: export QT_LOGGING_RULES="digikam*=true" Maik (In reply to Maik Qualmann from comment #1) > Start digiKam in the terminal and post the output. Set before the Qt debug variable: digikam.widgets: Use installed icons digikam.general: AlbumWatch is disabled digikam.general: Database Parameters: Type: "QMYSQL" DB Core Name: "digikam" DB Thumbs Name: "digikam" DB Face Name: "digikam" DB Similarity Name: "digikam" Connect Options: "UNIX_SOCKET=/home/[user]/.local/share/digikam/db_misc/mysql.socket" Host Name: "" Host port: -1 Internal Server: true Internal Server Path: "/home/[user]/.pictures" Internal Server Admin Cmd: "mysqladmin" Internal Server Serv Cmd: "mysqld" Internal Server Init Cmd: "mysql_install_db" Username: "root" Password: "" digikam.databaseserver: Database Parameters: Type: "QMYSQL" DB Core Name: "digikam" DB Thumbs Name: "digikam" DB Face Name: "digikam" DB Similarity Name: "digikam" Connect Options: "UNIX_SOCKET=/home/[user]/.local/share/digikam/db_misc/mysql.socket" Host Name: "" Host port: -1 Internal Server: true Internal Server Path: "/home/[user]/.pictures" Internal Server Admin Cmd: "mysqladmin" Internal Server Serv Cmd: "mysqld" Internal Server Init Cmd: "mysql_install_db" Username: "root" Password: "" digikam.databaseserver: Internal Server data path: "/home/[user]/.pictures/.mysql.digikam/db_data" digikam.databaseserver: The mysql configuration was already up-to-date: "/home/[user]/.local/share/digikam/mysql.conf" digikam.databaseserver: Database server: "mysqld" ("--defaults-file=/home/[user]/.local/share/digikam/mysql.conf", "--datadir=/home/[user]/.pictures/.mysql.digikam/db_data", "--socket=/home/[user]/.local/share/digikam/db_misc/mysql.socket") digikam.databaseserver: "Database process exited unexpectedly during initial connection." digikam.databaseserver: Executable: "mysqld" digikam.databaseserver: Arguments: "--defaults-file=/home/[user]/.local/share/digikam/mysql.conf, --datadir=/home/[user]/.pictures/.mysql.digikam/db_data, --socket=/home/[user]/.local/share/digikam/db_misc/mysql.socket" digikam.databaseserver: Stdout: "" digikam.databaseserver: Stderr: "" digikam.databaseserver: Exit code: 1 digikam.databaseserver: Process error: "Unknown error" digikam.databaseserver: Cannot start internal database server Is there something in the MySQL Error file: /home/[user]/.pictures/.mysql.digikam/db_data,/mysql.err Maik Maik, Perhaps it's the same regression problem than QtMysql module under MacOS. Typically, recompiling the qt driver with a lower version of mariadb connector (10.x -> 5.x)... Gilles (In reply to Maik Qualmann from comment #3) > Is there something in the MySQL Error file: > /home/[user]/.pictures/.mysql.digikam/db_data,/mysql.err 2023-03-19 16:29:55 0 [Note] Starting MariaDB 10.11.2-MariaDB-log source revision cafba8761af55ae16cc69c9b53a341340a845b36 as process 41445 2023-03-19 16:29:55 0 [Warning] option 'innodb-log-buffer-size': unsigned value 1048576 adjusted to 2097152 2023-03-19 16:29:55 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 2023-03-19 16:29:55 0 [Note] InnoDB: Number of transaction pools: 1 2023-03-19 16:29:55 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2023-03-19 16:29:55 0 [Note] InnoDB: Using liburing 2023-03-19 16:29:55 0 [Note] InnoDB: Initializing buffer pool, total size = 80.000MiB, chunk size = 1.250MiB 2023-03-19 16:29:55 0 [Note] InnoDB: Completed initialization of buffer pool 2023-03-19 16:29:55 0 [Note] InnoDB: Buffered log writes (block size=512 bytes) 2023-03-19 16:29:55 0 [ERROR] InnoDB: Missing FILE_CHECKPOINT(2046798782) at 2046798782 2023-03-19 16:29:55 0 [ERROR] InnoDB: Log scan aborted at LSN 2046798782 2023-03-19 16:29:55 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2023-03-19 16:29:55 0 [Note] InnoDB: Starting shutdown... 2023-03-19 16:29:55 0 [ERROR] Plugin 'InnoDB' init function returned error. 2023-03-19 16:29:55 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2023-03-19 16:29:55 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2023-03-19 16:29:55 0 [ERROR] Aborting Check if there is an "ib_logfile0" in the directory. If present, rename it and create an empty "ib_logfile0" file. Maik There was a `ib_logfile0`. Removing the existing and creating altered the `mysql.err` file: 2023-03-19 20:46:35 0 [Note] Starting MariaDB 10.11.2-MariaDB-log source revision cafba8761af55ae16cc69c9b53a341340a845b36 as process 91099 2023-03-19 20:46:35 0 [Warning] option 'innodb-log-buffer-size': unsigned value 1048576 adjusted to 2097152 2023-03-19 20:46:35 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 2023-03-19 20:46:35 0 [Note] InnoDB: Number of transaction pools: 1 2023-03-19 20:46:35 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2023-03-19 20:46:35 0 [Note] InnoDB: Using liburing 2023-03-19 20:46:35 0 [Note] InnoDB: Initializing buffer pool, total size = 80.000MiB, chunk size = 1.250MiB 2023-03-19 20:46:35 0 [Note] InnoDB: Completed initialization of buffer pool 2023-03-19 20:46:35 0 [ERROR] InnoDB: File ./ib_logfile0 is too small 2023-03-19 20:46:35 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2023-03-19 20:46:35 0 [Note] InnoDB: Starting shutdown... 2023-03-19 20:46:35 0 [ERROR] Plugin 'InnoDB' init function returned error. 2023-03-19 20:46:35 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2023-03-19 20:46:35 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2023-03-19 20:46:35 0 [ERROR] Aborting Created attachment 157433 [details]
ib_logfile0.zip
Try this ib_logfile0, it needs to be unpacked.
Maik
I used the attached logfile. I needed to re-specify my library locations. But upon doing that, Digikam boots up as expected. It has all the database information still intact. The one thing it is lacking is face tag icons, but everything else appears as it should. Thank you for the assistance Maik Perfect, i close this file now... |