Is there any way to fix that data corrupt if that is the problem? I haven’t interrupted any processes myself but who knows if the computer did something. This database hasn’t worked and it took Digikam 2.5 days to run through the collection and I don’t want to repeat that.
> On 22. Oct 2020, at 14.00,
[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: Digikam 7.1.0 crashes internal mysqli server on start
> with MacOs Catalina (Remco Viëtor)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 22 Oct 2020 11:19:29 +0200
> From: Remco Viëtor <
[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: <5400852.DvuYhMxLoT@manticore>
> Content-Type: text/plain; charset="UTF-8"
>
> 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 36
> **********************************************
Locked
