Re: Digikam 7.1.0 crashes internal mysqli server on start with MacOs Catalina (Maik Qualmann)

[Dr Janne Ohtonen]

Just in case, I have added read&write permissions to all digicam related folders. That didn’t help.

Here is the debug output from MacOS Terminal

———————————————————— COMMAND LINE OUTPUT ----------------------------------------------------------------------

To update your account to use zsh, please run `chsh -s /bin/zsh`.

For more details, please visit https://support.apple.com/kb/HT208050.

Jannes-MacBook-Pro:~ janneohtonen$     export QT_LOGGING_RULES="digikam*=true"

Jannes-MacBook-Pro:~ janneohtonen$     /opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/digikam

digikam.widgets: Breeze icons resource file found

digikam.widgets: Breeze-dark icons resource file found

QCommandLineParser: already having an option named "h"

QCommandLineParser: already having an option named "help-all"

QCommandLineParser: already having an option named "v"

digikam.general: Switch to widget style:  "Fusion"

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=/Users/janneohtonen/Library/Application Support/digikam/digikam/db_misc/mysql.socket"

   Host Name:                ""

   Host port:                -1

   Internal Server:          true

   Internal Server Path:     "/Users/janneohtonen/Pictures"

   Internal Server Serv Cmd: "/opt/digikam/lib/mariadb/bin/mysqld"

   Internal Server Init Cmd: "/opt/digikam/lib/mariadb/bin/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=/Users/janneohtonen/Library/Application Support/digikam/digikam/db_misc/mysql.socket"

   Host Name:                ""

   Host port:                -1

   Internal Server:          true

   Internal Server Path:     "/Users/janneohtonen/Pictures"

   Internal Server Serv Cmd: "/opt/digikam/lib/mariadb/bin/mysqld"

   Internal Server Init Cmd: "/opt/digikam/lib/mariadb/bin/mysql_install_db"

   Username:                 "root"

   Password:                 ""

digikam.databaseserver: Internal Server data path: "/Users/janneohtonen/Pictures/.mysql.digikam/db_data"

digikam.databaseserver: The mysql configuration was already up-to-date: "/Users/janneohtonen/Library/Application Support/digikam/digikam/mysql.conf"

digikam.databaseserver: Database server: "/opt/digikam/lib/mariadb/bin/mysqld" ("--defaults-file=/Users/janneohtonen/Library/Application Support/digikam/digikam/mysql.conf", "--datadir=/Users/janneohtonen/Pictures/.mysql.digikam/db_data", "--socket=/Users/janneohtonen/Library/Application Support/digikam/digikam/db_misc/mysql.socket")

digikam.databaseserver: "Database process exited unexpectedly during initial connection."

digikam.databaseserver: Executable: "/opt/digikam/lib/mariadb/bin/mysqld"

digikam.databaseserver: Arguments: "--defaults-file=/Users/janneohtonen/Library/Application Support/digikam/digikam/mysql.conf, --datadir=/Users/janneohtonen/Pictures/.mysql.digikam/db_data, --socket=/Users/janneohtonen/Library/Application Support/digikam/digikam/db_misc/mysql.socket"

digikam.databaseserver: Stdout: ""

digikam.databaseserver: Stderr: "201023 10:49:29 [Warning] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --log_slow_queries is not set\n201023 10:49:29 [Note] /opt/digikam/lib/mariadb/bin/mysqld (mysqld 5.5.68-MariaDB) starting as process 35806 ...\n201023 10:49:29 [Warning] Setting lower_case_table_names=2 because file system for /Users/janneohtonen/Pictures/.mysql.digikam/db_data/ is case insensitive\n"

digikam.databaseserver: Exit code: 1

digikam.databaseserver: Process error: "Process operation timed out"

digikam.databaseserver: Cannot start internal database server

———————————————————————————————————

THIS IS THE OUTPUT FROM MYSQL.ERR 

201023 10:49:30 InnoDB: The InnoDB memory heap is disabled

201023 10:49:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins

201023 10:49:30 InnoDB: Compressed tables use zlib 1.2.11

201023 10:49:30 InnoDB: Initializing buffer pool, size = 80.0M

201023 10:49:30 InnoDB: Completed initialization of buffer pool

201023 10:49:30  InnoDB: Log file ./ib_logfile0 did not exist: new to be created

InnoDB: Setting log file ./ib_logfile0 size to 64 MB

InnoDB: Database physically writes the file full: wait...

201023 10:49:30  InnoDB: Log file ./ib_logfile1 did not exist: new to be created

InnoDB: Setting log file ./ib_logfile1 size to 64 MB

InnoDB: Database physically writes the file full: wait...

201023 10:49:30 InnoDB: Cannot initialize created log files because

201023 10:49:30 InnoDB: data files are corrupt, or new data files were

201023 10:49:30 InnoDB: created when the database was started previous

201023 10:49:30 InnoDB: time but the database was not shut down

201023 10:49:30 InnoDB: normally after that.

201023 10:49:30 [ERROR] Plugin 'InnoDB' init function returned error.

201023 10:49:30 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

201023 10:49:30 [ERROR] Unknown/unsupported storage engine: InnoDB

201023 10:49:30 [ERROR] Aborting

201023 10:49:30 [Note] /opt/digikam/lib/mariadb/bin/mysqld: Shutdown complete

———————————————————————————————————

So, the database is broken and I rerun the collection indexing which takes 2 days?

Kind regards,

Janne

On 22. Oct 2020, at 23.47, [hidden email] wrote:

Send Digikam-users mailing list submissions to
[hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.kde.org/mailman/listinfo/digikam-users
or, via email, send a message with subject or body 'help' to
[hidden email]

You can reach the person managing the list at
[hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Digikam-users digest..."


Today's Topics:

  1. Re:  Error message (Familie Reiner Sauer)
  2. Re:  Error message (Maik Qualmann)
  3. Re:  Digikam 7.1.0 crashes internal mysqli server on start
     with MacOs Catalina (Maik Qualmann)


----------------------------------------------------------------------

Message: 1
Date: Thu, 22 Oct 2020 22:04:20 +0200
From: Familie Reiner Sauer <[hidden email]>
To: [hidden email]
Subject: Re: [digiKam-users] Error message
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"

Who can help with advice. I have the same problem.

Thanks in advance

Regards

Reiner L. Sauer

Message: 4
Date: Thu, 22 Oct 2020 14:21:30 +0000 (UTC)
From: Ronald Orenstein <[hidden email]>
To: "[hidden email]" <[hidden email]>
Subject: [digiKam-users] Fw:  Error message
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"

Does anyone have any advice as to what to do about my original problem ( Error message: failed to create tables in database)?
Many thanks - Ron
Ronald Orenstein
1825 Shady Creek Court
Mississauga, ON L5L 3W2
Canada
ronorenstein.blogspot.com
ronorensteinwriter.blogspot.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20201022/36a041ba/attachment-0001.htm>

------------------------------

Message: 2
Date: Thu, 22 Oct 2020 22:40:12 +0200
From: Maik Qualmann <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the
power of open source <[hidden email]>
Subject: Re: [digiKam-users] Error message
Message-ID: <2098145.gm7NTy1ema@linux-tpgn>
Content-Type: text/plain; charset="us-ascii"

Open a terminal and activate the debug output and start digiKam as described
here for MacOS:

https://www.digikam.org/contribute/

Maybe there is more information in the debug output. But I suspect a real
problem that digikam cannot write to the directory. Under Catalina, programs
that are not signed by Apple have been further restricted.

Maik

Am Donnerstag, 22. Oktober 2020, 22:04:20 CEST schrieb Familie Reiner Sauer:

Who can help with advice. I have the same problem.

Thanks in advance

Regards

Reiner L. Sauer

Message: 4
Date: Thu, 22 Oct 2020 14:21:30 +0000 (UTC)
From: Ronald Orenstein <[hidden email]>
To: "[hidden email]" <[hidden email]>
Subject: [digiKam-users] Fw:  Error message
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"

Does anyone have any advice as to what to do about my original problem (
Error message: failed to create tables in database)? Many thanks - Ron
Ronald Orenstein
1825 Shady Creek Court
Mississauga, ON L5L 3W2
Canada
ronorenstein.blogspot.com
ronorensteinwriter.blogspot.com

------------------------------

Message: 3
Date: Thu, 22 Oct 2020 22:46:55 +0200
From: Maik Qualmann <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the
power of open source <[hidden email]>
Subject: Re: [digiKam-users] Digikam 7.1.0 crashes internal mysqli
server on start with MacOs Catalina
Message-ID: <1822175.vXyWbVZuGf@linux-tpgn>
Content-Type: text/plain; charset="UTF-8"

MariaDB cannot start the InnoDB plugin. It looks like it can't create log
files or it can't be accessed. Here, too, I suspect that either digiKam or
MariaDB does not have the required rights to the file system. You can find
many issues related to MariaDB on the web after switching to Catalina.

Open a terminal and activate the debug output and start digiKam as described
here for MacOS:

https://www.digikam.org/contribute/

Maybe there is more information in the debug output.

Maik

Am Donnerstag, 22. Oktober 2020, 11:19:29 CEST schrieb Remco Viëtor:

On mercredi 21 octobre 2020 13:23:17 CEST Dr Janne Ohtonen wrote:

Hi,

Would you have any idea why Digikam 7.1.0 won’t open the internal mysqli
database on my Mac (Catalina)? This has never worked for me.

Do you mean that on previous tries MySQL wouldn't work either, or that it
now refuses to open the database that worked correctly before?

You can find the Apple crash report and screenshots attached.

Currently I can’t use the Digikam with this photo collection at all as it
won’t open. I can’t use any database migration tools either as the
internal
sql server won’t start.

SQLite doesn't work either? Note that internal MySQL is marked as
"experimental" in your screenshot...

Any ideas what’s wrong?

Well, the mysql.err mentions corrupt datafiles. Also, as a possible cause it
mentions the presence of files created during an earlier run that crashed
or was forcibly terminated (user intervention, power failure, ...).

Remco

------------------------------

Subject: Digest Footer

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users


------------------------------

End of Digikam-users Digest, Vol 185, Issue 39
**********************************************