[digiKam-users] digikam mariadb configuration fail

[leoutation]

Hi
Today, I installed  digikam on another computer. Sqlite works but not
Mariadb.
Mariadb database/permissions/user  is ok, connection works normally from
digikam.
I could not create schema with db migration from sqlite to mysql or/and
with "mysql server" configuration, it doesn't work.
I got message "the database is not valid. The "DBVersion" setting
doesn't exist. The current database schema version cannot be verified.
Try to start with an empty database"
Other strange point, I configured "local collection" on HD but then, it
is considered as "removable media".
digikam-git r41540
--
Maderios

[Maik Qualmann]

You executed these commands (with customization) as the mysql root user?

mysql -u root -p

CREATE USER 'USERNAME'@'HOSTNAME' IDENTIFIED BY 'password';
GRANT ALL ON *.* TO 'USERNAME'@'HOSTNAME' IDENTIFIED BY 'password';
CREATE DATABASE digikam;
GRANT ALL PRIVILEGES ON digikam.* TO 'USERNAME'@'HOSTNAME';
FLUSH PRIVILEGES;

Am Samstag, 9. Februar 2019, 21:57:38 CET schrieb [hidden email]:

> Hi
> Today, I installed  digikam on another computer. Sqlite works but not
> Mariadb.
> Mariadb database/permissions/user  is ok, connection works normally from
> digikam.
> I could not create schema with db migration from sqlite to mysql or/and
> with "mysql server" configuration, it doesn't work.
> I got message "the database is not valid. The "DBVersion" setting
> doesn't exist. The current database schema version cannot be verified.
> Try to start with an empty database"
> Other strange point, I configured "local collection" on HD but then, it
> is considered as "removable media".
> digikam-git r41540

[leoutation]

On 2/10/19 8:56 AM, Maik Qualmann wrote:
> You executed these commands (with customization) as the mysql root user?
>
> mysql -u root -p
>
> CREATE USER 'USERNAME'@'HOSTNAME' IDENTIFIED BY 'password';
> GRANT ALL ON *.* TO 'USERNAME'@'HOSTNAME' IDENTIFIED BY 'password';
> CREATE DATABASE digikam;
> GRANT ALL PRIVILEGES ON digikam.* TO 'USERNAME'@'HOSTNAME';
> FLUSH PRIVILEGES;

Yes and beside, when i test db connection, digikam says it is ok

>
> Am Samstag, 9. Februar 2019, 21:57:38 CET schrieb [hidden email]:
>> Hi
>> Today, I installed  digikam on another computer. Sqlite works but not
>> Mariadb.
>> Mariadb database/permissions/user  is ok, connection works normally from
>> digikam.
>> I could not create schema with db migration from sqlite to mysql or/and
>> with "mysql server" configuration, it doesn't work.
>> I got message "the database is not valid. The "DBVersion" setting
>> doesn't exist. The current database schema version cannot be verified.
>> Try to start with an empty database"
>> Other strange point, I configured "local collection" on HD but then, it
>> is considered as "removable media".
>> digikam-git r41540
>
>
>
>

--
Maderios

[Gilles Caulier-4]

Run digikam from a console, from the start (it's important). Trace all debug output in a text file until you play with digiKam and face the problem with Mysql/MariaDb.

GilleS Caulier

Le dim. 10 févr. 2019 à 10:44, <[hidden email]> a écrit :

On 2/10/19 8:56 AM, Maik Qualmann wrote:
> You executed these commands (with customization) as the mysql root user?
>
> mysql -u root -p
>
> CREATE USER 'USERNAME'@'HOSTNAME' IDENTIFIED BY 'password';
> GRANT ALL ON *.* TO 'USERNAME'@'HOSTNAME' IDENTIFIED BY 'password';
> CREATE DATABASE digikam;
> GRANT ALL PRIVILEGES ON digikam.* TO 'USERNAME'@'HOSTNAME';
> FLUSH PRIVILEGES;

Yes and beside, when i test db connection, digikam says it is ok

>
> Am Samstag, 9. Februar 2019, 21:57:38 CET schrieb [hidden email]:
>> Hi
>> Today, I installed  digikam on another computer. Sqlite works but not
>> Mariadb.
>> Mariadb database/permissions/user  is ok, connection works normally from
>> digikam.
>> I could not create schema with db migration from sqlite to mysql or/and
>> with "mysql server" configuration, it doesn't work.
>> I got message "the database is not valid. The "DBVersion" setting
>> doesn't exist. The current database schema version cannot be verified.
>> Try to start with an empty database"
>> Other strange point, I configured "local collection" on HD but then, it
>> is considered as "removable media".
>> digikam-git r41540
>
>
>
>


--
Maderios

[leoutation]

On 2/10/19 2:06 PM, Gilles Caulier wrote:
> Run digikam from a console, from the start (it's important). Trace all
> debug output in a text file until you play with digiKam and face the
> problem with Mysql/MariaDb.
>
Console debug here
https://pastebin.com/PPkGKart

--
Maderios

[Gilles Caulier-4]

The "No carrier" messages are really strange.

I suspect something broken in your network configuration or something like that. This can explain all your dysfunctions.

Gilles Caulier

Le dim. 10 févr. 2019 à 16:47, <[hidden email]> a écrit :

On 2/10/19 2:06 PM, Gilles Caulier wrote:
> Run digikam from a console, from the start (it's important). Trace all
> debug output in a text file until you play with digiKam and face the
> problem with Mysql/MariaDb.
>
Console debug here
https://pastebin.com/PPkGKart

--
Maderios

[Gilles Caulier-4]

A mess like this :

https://bbs.archlinux.org/viewtopic.php?id=153519

It's just an example. Network dysfunction can be complex to solve. Remember that connection to Mysql/Mariadb database pass through the network interface...

Gilles Caulier

Le dim. 10 févr. 2019 à 16:51, Gilles Caulier <[hidden email]> a écrit :

The "No carrier" messages are really strange.

I suspect something broken in your network configuration or something like that. This can explain all your dysfunctions.

Gilles Caulier

Le dim. 10 févr. 2019 à 16:47, <[hidden email]> a écrit :

On 2/10/19 2:06 PM, Gilles Caulier wrote:
> Run digikam from a console, from the start (it's important). Trace all
> debug output in a text file until you play with digiKam and face the
> problem with Mysql/MariaDb.
>
Console debug here
https://pastebin.com/PPkGKart

--
Maderios

[leoutation]

On 2/10/19 4:51 PM, Gilles Caulier wrote:
> The "No carrier" messages are really strange.
>
> I suspect something broken in your network configuration or something
> like that. This can explain all your dysfunctions.

On an other PC, digikam-git/external mariadb works fine.
All my files, conf, etc, are local on hard drive, too. Same Arch system
version, same digikam-git version, same images collections.
"No carrier" is displayed the same way, each ten seconds, i don't have
any problem with that...
digikam with no problem console debug:

digikam.general: Stacked View Mode :  1
digikam.dimg: "/home/youseur/images/1perso/1modèles/noir.jpeg"  : JPEG
file identified
digikam.general: Stacked View Mode :  0
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
qt.qpa.xcb: Unhandled client message:  "_E_COMP_FLUSH"
qt.qpa.xcb: Unhandled client message:  "_E_COMP_DUMP"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
qt.qpa.xcb: Unhandled client message:  "_E_COMP_FLUSH"
qt.qpa.xcb: Unhandled client message:  "_E_COMP_DUMP"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"
"No carrier"

>
> Gilles Caulier
>
> Le dim. 10 févr. 2019 à 16:47, <[hidden email]
> <mailto:[hidden email]>> a écrit :
>
>     On 2/10/19 2:06 PM, Gilles Caulier wrote:
>      > Run digikam from a console, from the start (it's important).
>     Trace all
>      > debug output in a text file until you play with digiKam and face the
>      > problem with Mysql/MariaDb.
>      >
>     Console debug here
>     https://pastebin.com/PPkGKart
>
>     --
>     Maderios
>

--
Maderios

[leoutation]

On 2/10/19 4:53 PM, Gilles Caulier wrote:
>     The "No carrier" messages are really strange.
>
>     I suspect something broken in your network configuration or
>     something like that. This can explain all your dysfunctions.
>
I launched Digikam *sqlite* db from console.
"No carrier" message is displayed each 10 secund, it never stops when
digikam is idle.
Just like with mariadb.
Beside, i have no problem with network and mariadb, no dmesg warning.
Last digikam-git r41548 i built today
Arch system

--
Maderios

[Maik Qualmann]

A quick note of when this error message occurs and what conditions cause:

digikam.coredb: Core database: have a structure version  0
digikam.coredb: Core database: version not available! Giving up schema
upgrading.

The "Albums" table already exists in the digiKam database. But either the
"Settings" table does not exist or the entry "DBVersion" is deleted. It would
definitely have to be manually checked or repaired.

Maik

Am Sonntag, 10. Februar 2019, 17:44:03 CET schrieb [hidden email]:

> On 2/10/19 4:51 PM, Gilles Caulier wrote:
> > The "No carrier" messages are really strange.
> >
> > I suspect something broken in your network configuration or something
> > like that. This can explain all your dysfunctions.
>
> On an other PC, digikam-git/external mariadb works fine.
> All my files, conf, etc, are local on hard drive, too. Same Arch system
> version, same digikam-git version, same images collections.
> "No carrier" is displayed the same way, each ten seconds, i don't have
> any problem with that...
> digikam with no problem console debug:
>
> digikam.general: Stacked View Mode :  1
> digikam.dimg: "/home/youseur/images/1perso/1modèles/noir.jpeg"  : JPEG
> file identified
> digikam.general: Stacked View Mode :  0
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> qt.qpa.xcb: Unhandled client message:  "_E_COMP_FLUSH"
> qt.qpa.xcb: Unhandled client message:  "_E_COMP_DUMP"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> qt.qpa.xcb: Unhandled client message:  "_E_COMP_FLUSH"
> qt.qpa.xcb: Unhandled client message:  "_E_COMP_DUMP"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
> "No carrier"
>
> > Gilles Caulier
> >
> > Le dim. 10 févr. 2019 à 16:47, <[hidden email]
> >
> > <mailto:[hidden email]>> a écrit :
> >     On 2/10/19 2:06 PM, Gilles Caulier wrote:
> >      > Run digikam from a console, from the start (it's important).
> >    
> >     Trace all
> >    
> >      > debug output in a text file until you play with digiKam and face
> >      > the
> >      > problem with Mysql/MariaDb.
> >    
> >     Console debug here
> >     https://pastebin.com/PPkGKart

[leoutation]

On 2/11/19 7:49 PM, Maik Qualmann wrote:

> A quick note of when this error message occurs and what conditions cause:
>
> digikam.coredb: Core database: have a structure version  0
> digikam.coredb: Core database: version not available! Giving up schema
> upgrading.
>
> The "Albums" table already exists in the digiKam database. But either the
> "Settings" table does not exist or the entry "DBVersion" is deleted. It would
> definitely have to be manually checked or repaired.
>

Digikam mariadb ext server works after deleting my (old) mariadb
installation, reinstalling and configuring it.
Thanks!

--
Maderios