[digiKam-users] error start of internal server

[Maik Qualmann]

 The problem is that digiKam deleted the MySQL log file. By the way,
Akonadi has the same problem. We already fixed deleting MySQL log file for
digiKam-7.7.0. MariaDB will not start without an old log file, it is used
to analyze errors. For me it's a MariaDB bug, MariaDB should start without
log file. What to do if the log files have already been deleted?
- Import log files from a backup.
- Try to use log files from a new database.
- Start with a new database and use digiKam-7.7.0.

Maik

Am Mo., 20. Juni 2022 um 11:45 Uhr schrieb Remco Viëtor <
remco.vietor at wanadoo.fr>:

> On lundi 20 juin 2022 11:39:19 CEST Dr. Martin Senftleben wrote:
> > Hi,
> >
> > I was using digikam since version 2 or so and was mostly happy with it.
> > For some years I was also on this list, until I left it to reduce the
> > number of mails I am receiving and because I didn't have any problems.
> > This has changed. Already the before last version had trouble with the
> > database, which, however, I could solve with the help of some info
> > provided on the Internet.
> > This time it's another problem, which I cannot solve. I need to
> > translate from German, hence the wording might not be the same as you
> > might expect, but I hope you get the meaning. When starting digikam, I
> > get the following:
> >
> > "Error when starting the internal server
> >
> > The database process was stopped unexpectedly while establishing a
> > connection.
> > Program: mysqld
> > Arguments:
> > --defaults-file=~/.local/share/digikam/mysql.conf,
> > --datadir=~/digikam/.mysql.digikam/db_data,
> > --socket=~/.local/share/digikam/db_misc/mysql.socket
> > Process error: timed out"
> >
> > The error occurs almost immediately after starting digikam. I checked
> > and found that in ~/.local/share/digikam/db_misc/ there is no file
> > called "mysql.socket". This probably explains the error. The question
> > is: why is there none?
> > The other mentioned files exist, and it worked all before the last
> > update with those files. I have version 7.6.0-4 of digikam, running
> > Manjaro Linux (64 bit) with all system files up to date.
> >
> > I apologize in advance if that has been discussed before. I didn't find
> > anything in the archive or elsewhere on the internet.
> >
> > Regards
> >
> > Martin
>
> Perhaps have a look at :
> https://discuss.pixls.us/t/digikam-problems-with-the-mysql/31196/
>
> and:
> https://bbs.archlinux.org/viewtopic.php?id=277078
>
> In short, Digikam (and some others) don't work with Mariabd version
> 10.8.x,
> which seems to be a development version (so not recommended for production
> use, you see why...)
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20220620/1c628a02/attachment.htm>