digikam 5.6 mariadb problem
Locked
 
|
Hi
I tried digikam-5.6.0-01-x86-64.appimage with mariadb external server. I can't connect to mariadb. Is it a bug? I can connect normally to mariadb server with DK 5.3 debian package (Debian Buster amd64) Thanks -- Maderios |
Re: digikam 5.6 mariadb problem
|
|
Nothing special have been touch with mysql support as i know. Which
kind of error message do you see on the console ? Gilles Caulier 2017-08-14 13:09 GMT+02:00 maderios <[hidden email]>: > Hi > I tried digikam-5.6.0-01-x86-64.appimage with mariadb external server. > I can't connect to mariadb. Is it a bug? > I can connect normally to mariadb server with DK 5.3 debian package > (Debian Buster amd64) > Thanks > -- > Maderios |
Re: digikam 5.6 mariadb problem
|
|
Also check with current 5.7.0 pre version appimage :
https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier 2017-08-14 13:28 GMT+02:00 Gilles Caulier <[hidden email]>: > Nothing special have been touch with mysql support as i know. Which > kind of error message do you see on the console ? > > Gilles Caulier > > 2017-08-14 13:09 GMT+02:00 maderios <[hidden email]>: >> Hi >> I tried digikam-5.6.0-01-x86-64.appimage with mariadb external server. >> I can't connect to mariadb. Is it a bug? >> I can connect normally to mariadb server with DK 5.3 debian package >> (Debian Buster amd64) >> Thanks >> -- >> Maderios |
Re: digikam 5.6 mariadb problem
|
|
perhaps it's relevant of this entry in bugzilla :
https://bugs.kde.org/show_bug.cgi?id=382482 Gilles Caulier 2017-08-14 13:34 GMT+02:00 Gilles Caulier <[hidden email]>: > Also check with current 5.7.0 pre version appimage : > > https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM > > Gilles Caulier > > 2017-08-14 13:28 GMT+02:00 Gilles Caulier <[hidden email]>: >> Nothing special have been touch with mysql support as i know. Which >> kind of error message do you see on the console ? >> >> Gilles Caulier >> >> 2017-08-14 13:09 GMT+02:00 maderios <[hidden email]>: >>> Hi >>> I tried digikam-5.6.0-01-x86-64.appimage with mariadb external server. >>> I can't connect to mariadb. Is it a bug? >>> I can connect normally to mariadb server with DK 5.3 debian package >>> (Debian Buster amd64) >>> Thanks >>> -- >>> Maderios |
|
|
In reply to this post by Gilles Caulier-4
On 08/14/2017 01:28 PM, Gilles Caulier wrote:
> Nothing special have been touch with mysql support as i know. Which > kind of error message do you see on the console ? I choosed 'Internal Server' option but Internal Server is seen as 'false' digikam.database: Testing DB connection ( "ConnectionTest" ) with these settings: digikam.database: Database Parameters: Type: "QMYSQL" DB Core Name: "dkmoi" DB Thumbs Name: "dkmoi" DB Face Name: "dkmoi" Connect Options: "" Host Name: "localhost" Host port: 3306 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "dkmoi" Password: "XXXXXXXXXXXXX" QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. > > Gilles Caulier > > 2017-08-14 13:09 GMT+02:00 maderios <[hidden email]>: >> Hi >> I tried digikam-5.6.0-01-x86-64.appimage with mariadb external server. >> I can't connect to mariadb. Is it a bug? >> I can connect normally to mariadb server with DK 5.3 debian package >> (Debian Buster amd64) >> Thanks >> -- >> Maderios -- Maderios |
Re: digikam 5.6 mariadb problem
|
|
I tested here with Mariadb, internal and external, and all work fine :
mysql Ver 15.1 Distrib 10.1.24-MariaDB, for Linux (x86_64) using readline 5.1 Gilles Caulier 2017-08-14 14:05 GMT+02:00 maderios <[hidden email]>: > On 08/14/2017 01:28 PM, Gilles Caulier wrote: >> >> Nothing special have been touch with mysql support as i know. Which >> kind of error message do you see on the console ? > > I choosed 'Internal Server' option but Internal Server is seen as 'false' > > digikam.database: Testing DB connection ( "ConnectionTest" ) with these > settings: > digikam.database: Database Parameters: > Type: "QMYSQL" > DB Core Name: "dkmoi" > DB Thumbs Name: "dkmoi" > DB Face Name: "dkmoi" > Connect Options: "" > Host Name: "localhost" > Host port: 3306 > Internal Server: false > Internal Server Path: "" > Internal Server Serv Cmd: "" > Internal Server Init Cmd: "" > Username: "dkmoi" > Password: "XXXXXXXXXXXXX" > > QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in > use, all queries will cease to work. > > > >> >> Gilles Caulier >> >> 2017-08-14 13:09 GMT+02:00 maderios <[hidden email]>: >>> >>> Hi >>> I tried digikam-5.6.0-01-x86-64.appimage with mariadb external server. >>> I can't connect to mariadb. Is it a bug? >>> I can connect normally to mariadb server with DK 5.3 debian package >>> (Debian Buster amd64) >>> Thanks >>> -- >>> Maderios > > > > -- > Maderios |
Re: digikam 5.6 mariadb problem
|
|
Sorry, i precise : i tested with native version compiled by myself
under Linux, not with the AppImage. Gilles Caulier 2017-08-14 14:15 GMT+02:00 Gilles Caulier <[hidden email]>: > I tested here with Mariadb, internal and external, and all work fine : > > mysql Ver 15.1 Distrib 10.1.24-MariaDB, for Linux (x86_64) using readline 5.1 > > Gilles Caulier > > > 2017-08-14 14:05 GMT+02:00 maderios <[hidden email]>: >> On 08/14/2017 01:28 PM, Gilles Caulier wrote: >>> >>> Nothing special have been touch with mysql support as i know. Which >>> kind of error message do you see on the console ? >> >> I choosed 'Internal Server' option but Internal Server is seen as 'false' >> >> digikam.database: Testing DB connection ( "ConnectionTest" ) with these >> settings: >> digikam.database: Database Parameters: >> Type: "QMYSQL" >> DB Core Name: "dkmoi" >> DB Thumbs Name: "dkmoi" >> DB Face Name: "dkmoi" >> Connect Options: "" >> Host Name: "localhost" >> Host port: 3306 >> Internal Server: false >> Internal Server Path: "" >> Internal Server Serv Cmd: "" >> Internal Server Init Cmd: "" >> Username: "dkmoi" >> Password: "XXXXXXXXXXXXX" >> >> QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in >> use, all queries will cease to work. >> >> >> >>> >>> Gilles Caulier >>> >>> 2017-08-14 13:09 GMT+02:00 maderios <[hidden email]>: >>>> >>>> Hi >>>> I tried digikam-5.6.0-01-x86-64.appimage with mariadb external server. >>>> I can't connect to mariadb. Is it a bug? >>>> I can connect normally to mariadb server with DK 5.3 debian package >>>> (Debian Buster amd64) >>>> Thanks >>>> -- >>>> Maderios >> >> >> >> -- >> Maderios |
Re: digikam 5.6 mariadb problem
|
|
I can reproduce the problem here, but in fact it's not a problem :
My settings : Type: "QMYSQL" DB Core Name: "digikam" DB Thumbs Name: "digikam" DB Face Name: "digikam" Connect Options: "" Host Name: "192.168.1.20" Host port: 3306 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "digikam" Password: "XXXXXXXX" I replaced host name from "localhost" with real IP on the network and all work fine with AppImage Please check. Gilles Caulier 2017-08-14 14:16 GMT+02:00 Gilles Caulier <[hidden email]>: > Sorry, i precise : i tested with native version compiled by myself > under Linux, not with the AppImage. > > Gilles Caulier > > 2017-08-14 14:15 GMT+02:00 Gilles Caulier <[hidden email]>: >> I tested here with Mariadb, internal and external, and all work fine : >> >> mysql Ver 15.1 Distrib 10.1.24-MariaDB, for Linux (x86_64) using readline 5.1 >> >> Gilles Caulier >> >> >> 2017-08-14 14:05 GMT+02:00 maderios <[hidden email]>: >>> On 08/14/2017 01:28 PM, Gilles Caulier wrote: >>>> >>>> Nothing special have been touch with mysql support as i know. Which >>>> kind of error message do you see on the console ? >>> >>> I choosed 'Internal Server' option but Internal Server is seen as 'false' >>> >>> digikam.database: Testing DB connection ( "ConnectionTest" ) with these >>> settings: >>> digikam.database: Database Parameters: >>> Type: "QMYSQL" >>> DB Core Name: "dkmoi" >>> DB Thumbs Name: "dkmoi" >>> DB Face Name: "dkmoi" >>> Connect Options: "" >>> Host Name: "localhost" >>> Host port: 3306 >>> Internal Server: false >>> Internal Server Path: "" >>> Internal Server Serv Cmd: "" >>> Internal Server Init Cmd: "" >>> Username: "dkmoi" >>> Password: "XXXXXXXXXXXXX" >>> >>> QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in >>> use, all queries will cease to work. >>> >>> >>> >>>> >>>> Gilles Caulier >>>> >>>> 2017-08-14 13:09 GMT+02:00 maderios <[hidden email]>: >>>>> >>>>> Hi >>>>> I tried digikam-5.6.0-01-x86-64.appimage with mariadb external server. >>>>> I can't connect to mariadb. Is it a bug? >>>>> I can connect normally to mariadb server with DK 5.3 debian package >>>>> (Debian Buster amd64) >>>>> Thanks >>>>> -- >>>>> Maderios >>> >>> >>> >>> -- >>> Maderios |
|
|
The problem is probably with the configuraiton of the mysql server:
If the option "bind-address" is set to anything else than localhost/127.0.0.1 or 0.0.0.0 (any address) then you can only connact with that specific address. If you didn't modify this yourself, maybe you a mysql/mariadb update changed the default. Or I am wrong and this isn't the problem after all :) On 14/08/17 14:26, Gilles Caulier wrote: > I can reproduce the problem here, but in fact it's not a problem : > > My settings : > > Type: "QMYSQL" > DB Core Name: "digikam" > DB Thumbs Name: "digikam" > DB Face Name: "digikam" > Connect Options: "" > Host Name: "192.168.1.20" > Host port: 3306 > Internal Server: false > Internal Server Path: "" > Internal Server Serv Cmd: "" > Internal Server Init Cmd: "" > Username: "digikam" > Password: "XXXXXXXX" > > I replaced host name from "localhost" with real IP on the network and > all work fine with AppImage > > Please check. > > Gilles Caulier > > 2017-08-14 14:16 GMT+02:00 Gilles Caulier <[hidden email]>: >> Sorry, i precise : i tested with native version compiled by myself >> under Linux, not with the AppImage. >> >> Gilles Caulier >> >> 2017-08-14 14:15 GMT+02:00 Gilles Caulier <[hidden email]>: >>> I tested here with Mariadb, internal and external, and all work fine : >>> >>> mysql Ver 15.1 Distrib 10.1.24-MariaDB, for Linux (x86_64) using readline 5.1 >>> >>> Gilles Caulier >>> >>> >>> 2017-08-14 14:05 GMT+02:00 maderios <[hidden email]>: >>>> On 08/14/2017 01:28 PM, Gilles Caulier wrote: >>>>> Nothing special have been touch with mysql support as i know. Which >>>>> kind of error message do you see on the console ? >>>> I choosed 'Internal Server' option but Internal Server is seen as 'false' >>>> >>>> digikam.database: Testing DB connection ( "ConnectionTest" ) with these >>>> settings: >>>> digikam.database: Database Parameters: >>>> Type: "QMYSQL" >>>> DB Core Name: "dkmoi" >>>> DB Thumbs Name: "dkmoi" >>>> DB Face Name: "dkmoi" >>>> Connect Options: "" >>>> Host Name: "localhost" >>>> Host port: 3306 >>>> Internal Server: false >>>> Internal Server Path: "" >>>> Internal Server Serv Cmd: "" >>>> Internal Server Init Cmd: "" >>>> Username: "dkmoi" >>>> Password: "XXXXXXXXXXXXX" >>>> >>>> QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in >>>> use, all queries will cease to work. >>>> >>>> >>>> >>>>> Gilles Caulier >>>>> >>>>> 2017-08-14 13:09 GMT+02:00 maderios <[hidden email]>: >>>>>> Hi >>>>>> I tried digikam-5.6.0-01-x86-64.appimage with mariadb external server. >>>>>> I can't connect to mariadb. Is it a bug? >>>>>> I can connect normally to mariadb server with DK 5.3 debian package >>>>>> (Debian Buster amd64) >>>>>> Thanks >>>>>> -- >>>>>> Maderios >>>> >>>> >>>> -- >>>> Maderios |
|
|
On 08/14/2017 02:45 PM, Simon Frei wrote:
> The problem is probably with the configuraiton of the mysql server: > If the option "bind-address" is set to anything else than > localhost/127.0.0.1 or 0.0.0.0 (any address) then you can only connact > with that specific address. If you didn't modify this yourself, maybe > you a mysql/mariadb update changed the default. Or I am wrong and this > isn't the problem after all :) > I found in /etc/mysql/mariadb.conf.d/50-server.cnf bind-address = 127.0.0.1 I changed dk settings hostname 'localhost' --> '127.0.0.1' I can connect now :) Thanks Gilles & Simon -- Maderios |
Re: [solved] Re: digikam 5.6 mariadb problem
|
|
On 14/08/17 15:36, maderios wrote:
> On 08/14/2017 02:45 PM, Simon Frei wrote: >> The problem is probably with the configuraiton of the mysql server: >> If the option "bind-address" is set to anything else than >> localhost/127.0.0.1 or 0.0.0.0 (any address) then you can only connact >> with that specific address. If you didn't modify this yourself, maybe >> you a mysql/mariadb update changed the default. Or I am wrong and this >> isn't the problem after all :) >> > I found in /etc/mysql/mariadb.conf.d/50-server.cnf > bind-address = 127.0.0.1 > I changed dk settings hostname 'localhost' --> '127.0.0.1' > I can connect now :) > > Thanks Gilles & Simon > > I was puzzled that it makes a difference whether you use 'localhost' or '127.0.0.1', I always assumed the former is just an alias for the latter. A bit more googling brought up the following SO Q&A: https://stackoverflow.com/questions/3715925/localhost-vs-127-0-0-1 The problem is that if you use 'localhost', mysql tries to connect via a unix domain socket and ignores the port (which in your case was the non-standard 3306). With '127.0.0.1' it connects via tcp/ip and uses the given port. |
|
|
On 08/14/2017 03:49 PM, Simon Frei wrote:
> On 14/08/17 15:36, maderios wrote: >> On 08/14/2017 02:45 PM, Simon Frei wrote: >>> The problem is probably with the configuraiton of the mysql server: >>> If the option "bind-address" is set to anything else than >>> localhost/127.0.0.1 or 0.0.0.0 (any address) then you can only connact >>> with that specific address. If you didn't modify this yourself, maybe >>> you a mysql/mariadb update changed the default. Or I am wrong and this >>> isn't the problem after all :) >>> >> I found in /etc/mysql/mariadb.conf.d/50-server.cnf >> bind-address = 127.0.0.1 >> I changed dk settings hostname 'localhost' --> '127.0.0.1' >> I can connect now :) >> >> Thanks Gilles & Simon >> >> > Glad the problem is solved. > > I was puzzled that it makes a difference whether you use 'localhost' or > '127.0.0.1', I always assumed the former is just an alias for the > latter. A bit more googling brought up the following SO Q&A: > https://stackoverflow.com/questions/3715925/localhost-vs-127-0-0-1 > The problem is that if you use 'localhost', mysql tries to connect via a > unix domain socket and ignores the port (which in your case was the > non-standard 3306). With '127.0.0.1' it connects via tcp/ip and uses the > given port. > I think the problem comes from appimage. I never had such problem when -- Maderios |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |