DK5.8.0 appimgage: Migration error database

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

DK5.8.0 appimgage: Migration error database

cool.chris65

Hi,

 

I'm sing DK 5.8.0 as appimage. Older Version (without databaseconverting) working fine, but since a database converting is implemented, I can't use newer DK 5.8.0 appimages because of a converting error:

 

---- 8-< ----

$ ./digikam-5.8.0-20171207T053823-x86-64.appimage debug
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...done.
Starting program: /tmp/.mount_ykIRBx/usr/bin/digikam  
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe70cc700 (LWP 13430)]
[New Thread 0x7fffe54af700 (LWP 13431)]
[New Thread 0x7fffe4cae700 (LWP 13432)]
[New Thread 0x7fffd6e50700 (LWP 13433)]
[Thread 0x7fffd6e50700 (LWP 13433) exited]
[New Thread 0x7fffd6e50700 (LWP 13434)]
[Thread 0x7fffd6e50700 (LWP 13434) exited]
digikam.coredb: Core database: cannot process schema initialization
[Thread 0x7fffe70cc700 (LWP 13430) exited]
[Thread 0x7fffe4cae700 (LWP 13432) exited]
QThreadStorage: Thread 0x7ffff7dd3540 exited after QThreadStorage 11 destroyed
[Thread 0x7fffe54af700 (LWP 13431) exited]
[Inferior 1 (process 13424) exited normally]

---- 8-< ----

 

Greetz,

Christoph

Reply | Threaded
Open this post in threaded view
|

Re: DK5.8.0 appimgage: Migration error database

cool.chris65

Hi,

 

I'm sorry, in my post is just one line of de cli-output, here is the complete one:

 

---- 8-< ----

 

./digikam-5.8.0-20171207T053823-x86-64.appimage debug
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...done.
Starting program: /tmp/.mount_6B4Pqy/usr/bin/digikam  
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe70cc700 (LWP 13809)]
[New Thread 0x7fffe54af700 (LWP 13810)]
[New Thread 0x7fffe4cae700 (LWP 13811)]
[New Thread 0x7fffd6e50700 (LWP 13812)]
[Thread 0x7fffd6e50700 (LWP 13812) exited]
[New Thread 0x7fffd6e50700 (LWP 13813)]
[Thread 0x7fffd6e50700 (LWP 13813) exited]
digikam.coredb: Core database: cannot process schema initialization
[Thread 0x7fffe70cc700 (LWP 13809) exited]
[Thread 0x7fffe4cae700 (LWP 13811) exited]
QThreadStorage: Thread 0x7ffff7dd3540 exited after QThreadStorage 11 destroyed
[Thread 0x7fffe54af700 (LWP 13810) exited]
[Inferior 1 (process 13804) exited normally]
(gdb) q

---- 8-< ----

 

And I forgot to tell you my DB-config: DK is using an external mysql-server on my NAS, and the older versions works very well in this environment ;-)

 

Greetz,

 

Christoph

 

 

Am Sonntag, 10. Dezember 2017, 12:41:43 CET schrieb [hidden email]:

> Hi,

>

> I'm sing DK 5.8.0 as appimage. Older Version (without

> databaseconverting) working fine, but since a database converting is

> implemented, I can't use newer DK 5.8.0 appimages because of a

> converting error:

>

> ---- 8-< ----

> $ ./digikam-5.8.0-20171207T053823-x86-64.appimage debug

> ---- 8-< ----

>

> Greetz,

> Christoph

 

 

Reply | Threaded
Open this post in threaded view
|

Re: DK5.8.0 appimgage: Migration error database

Maik Qualmann
I do not see any error message in their output. Can you post the error message
please. MySQL or MariaDB server?

Maik

Am Sonntag, 10. Dezember 2017, 12:48:46 CET schrieb [hidden email]:

> Hi,
>
> I'm sorry, in my post is just one line of de cli-output, here is the
> complete one:
>
> ---- 8-< ----
>
> ./digikam-5.8.0-20171207T053823-x86-64.appimage debug
> ---- 8-< ----
>
> And I forgot to tell you my DB-config: DK is using an external mysql-server
> on my NAS, and the older versions works very well in this environment ;-)
>
> Greetz,
>
> Christoph
>
> Am Sonntag, 10. Dezember 2017, 12:41:43 CET schrieb [hidden email]:
> > Hi,
> >
> > I'm sing DK 5.8.0 as appimage. Older Version (without
> > databaseconverting) working fine, but since a database converting is
> > implemented, I can't use newer DK 5.8.0 appimages because of a
> > converting error:
> >
> > ---- 8-< ----
> > $ ./digikam-5.8.0-20171207T053823-x86-64.appimage debug
> > ---- 8-< ----
> >
> > Greetz,
> > Christoph
Reply | Threaded
Open this post in threaded view
|

Re: DK5.8.0 appimgage: Migration error database

Maik Qualmann
Ok, found this in your log:

digikam.coredb: Core database: cannot process schema initialization

Maik

Am Sonntag, 10. Dezember 2017, 13:07:27 CET schrieb Maik Qualmann:

> I do not see any error message in their output. Can you post the error
> message please. MySQL or MariaDB server?
>
> Maik
>
> Am Sonntag, 10. Dezember 2017, 12:48:46 CET schrieb [hidden email]:
> > Hi,
> >
> > I'm sorry, in my post is just one line of de cli-output, here is the
> > complete one:
> >
> > ---- 8-< ----
> >
> > ./digikam-5.8.0-20171207T053823-x86-64.appimage debug
> > ---- 8-< ----
> >
> > And I forgot to tell you my DB-config: DK is using an external
> > mysql-server
> > on my NAS, and the older versions works very well in this environment ;-)
> >
> > Greetz,
> >
> > Christoph
> >
> > Am Sonntag, 10. Dezember 2017, 12:41:43 CET schrieb [hidden email]:
> > > Hi,
> > >
> > > I'm sing DK 5.8.0 as appimage. Older Version (without
> > > databaseconverting) working fine, but since a database converting is
> > > implemented, I can't use newer DK 5.8.0 appimages because of a
> > > converting error:
> > >
> > > ---- 8-< ----
> > > $ ./digikam-5.8.0-20171207T053823-x86-64.appimage debug
> > > ---- 8-< ----
> > >
> > > Greetz,
> > > Christoph
Reply | Threaded
Open this post in threaded view
|

Re: DK5.8.0 appimgage: Migration error database

Maik Qualmann
Updating my old test DB from V7 to V8 to V9 works well with the current
AppImage.

Maik

Am Sonntag, 10. Dezember 2017, 13:26:10 CET schrieben Sie:

> Ok, found this in your log:
>
> digikam.coredb: Core database: cannot process schema initialization
>
> Maik
>
> Am Sonntag, 10. Dezember 2017, 13:07:27 CET schrieb Maik Qualmann:
> > I do not see any error message in their output. Can you post the error
> > message please. MySQL or MariaDB server?
> >
> > Maik
> >
> > Am Sonntag, 10. Dezember 2017, 12:48:46 CET schrieb [hidden email]:
> > > Hi,
> > >
> > > I'm sorry, in my post is just one line of de cli-output, here is the
> > > complete one:
> > >
> > > ---- 8-< ----
> > >
> > > ./digikam-5.8.0-20171207T053823-x86-64.appimage debug
> > > ---- 8-< ----
> > >
> > > And I forgot to tell you my DB-config: DK is using an external
> > > mysql-server
> > > on my NAS, and the older versions works very well in this environment
> > > ;-)
> > >
> > > Greetz,
> > >
> > > Christoph
> > >
> > > Am Sonntag, 10. Dezember 2017, 12:41:43 CET schrieb [hidden email]:
> > > > Hi,
> > > >
> > > > I'm sing DK 5.8.0 as appimage. Older Version (without
> > > > databaseconverting) working fine, but since a database converting is
> > > > implemented, I can't use newer DK 5.8.0 appimages because of a
> > > > converting error:
> > > >
> > > > ---- 8-< ----
> > > > $ ./digikam-5.8.0-20171207T053823-x86-64.appimage debug
> > > > ---- 8-< ----
> > > >
> > > > Greetz,
> > > > Christoph
Reply | Threaded
Open this post in threaded view
|

Re: DK5.8.0 appimgage: Migration error database

cool.chris65

Hi,

 

I tried it again:

 

- if I use a local mariadb-server on the same machine as my digikam, I can start digikam successfull, and (in this case) it creates the db-stuctures.

 

- if I choose a mariadb-server on a different machine but same network I allway get an error that here was a problem to create the db-stuctures

 

Merry Christmas everyone

Greetz, Christoph

 

Am Sonntag, 10. Dezember 2017, 14:27:47 CET schrieb Maik Qualmann:

> Updating my old test DB from V7 to V8 to V9 works well with the current

> AppImage.

>

> Maik

>

> Am Sonntag, 10. Dezember 2017, 13:26:10 CET schrieben Sie:

> > Ok, found this in your log:

> >

> > digikam.coredb: Core database: cannot process schema initialization

> >

> > Maik

> >

> > Am Sonntag, 10. Dezember 2017, 13:07:27 CET schrieb Maik Qualmann:

> > > I do not see any error message in their output. Can you post the error

> > > message please. MySQL or MariaDB server?

> > >

> > > Maik

> > >

> > > Am Sonntag, 10. Dezember 2017, 12:48:46 CET schrieb [hidden email]:

> > > > Hi,

> > > >

> > > > I'm sorry, in my post is just one line of de cli-output, here is the

> > > > complete one:

> > > >

> > > > ---- 8-< ----

> > > >

> > > > ./digikam-5.8.0-20171207T053823-x86-64.appimage debug

> > > > ---- 8-< ----

> > > >

> > > > And I forgot to tell you my DB-config: DK is using an external

> > > > mysql-server

> > > > on my NAS, and the older versions works very well in this environment

> > > > ;-)

> > > >

> > > > Greetz,

> > > >

> > > > Christoph

> > > >

> > > > Am Sonntag, 10. Dezember 2017, 12:41:43 CET schrieb [hidden email]:

> > > > > Hi,

> > > > >

> > > > > I'm sing DK 5.8.0 as appimage. Older Version (without

> > > > > databaseconverting) working fine, but since a database converting is

> > > > > implemented, I can't use newer DK 5.8.0 appimages because of a

> > > > > converting error:

> > > > >

> > > > > ---- 8-< ----

> > > > > $ ./digikam-5.8.0-20171207T053823-x86-64.appimage debug

> > > > > ---- 8-< ----

> > > > >

> > > > > Greetz,

> > > > > Christoph

 

 

Reply | Threaded
Open this post in threaded view
|

Re: DK5.8.0 appimgage: Migration error database

cool.chris65

Hi,

 

this is the way I did it now:

 

- first I created a new database with digikam on an mariaDB-server on my local workstation

- I made a dump from my database (after stopping DK):

mysqldump -u root -p digikam > digikam_sich.sql
-I imported this database into my sql-server on an other machine:

mysql -u root -p < digikam_sich.sql
- I started DK again and changed the credentials to my server; DK ask me for my pics path, but after a short while all my scanned pics where back with all my entries.

 

Important: to get all datas succesfully into a new database by scanning you have to write the metadata also into the pics by default!

 

Greetz an have a merry christmas

Christoph

 

Am Sonntag, 24. Dezember 2017, 14:08:41 CET schrieb [hidden email]:

> Hi,

>

> I tried it again:

>

> - if I use a local mariadb-server on the same machine as my digikam, I can

> start digikam successfull, and (in this case) it creates the db-stuctures.

>

> - if I choose a mariadb-server on a different machine but same network I

> allway get an error that here was a problem to create the db-stuctures

>

> Merry Christmas everyone

> Greetz, Christoph

>

> Am Sonntag, 10. Dezember 2017, 14:27:47 CET schrieb Maik Qualmann:

> > Updating my old test DB from V7 to V8 to V9 works well with the current

> > AppImage.

> >

> > Maik

> >

> > Am Sonntag, 10. Dezember 2017, 13:26:10 CET schrieben Sie:

> > > Ok, found this in your log:

> > >

> > > digikam.coredb: Core database: cannot process schema initialization

> > >

> > > Maik

> > >

> > > Am Sonntag, 10. Dezember 2017, 13:07:27 CET schrieb Maik Qualmann:

> > > > I do not see any error message in their output. Can you post the error

> > > > message please. MySQL or MariaDB server?

> > > >

> > > > Maik

> > > >

> > > > Am Sonntag, 10. Dezember 2017, 12:48:46 CET schrieb [hidden email]:

> > > > > Hi,

> > > > >

> > > > > I'm sorry, in my post is just one line of de cli-output, here is the

> > > > > complete one:

> > > > >

> > > > > ---- 8-< ----

> > > > >

> > > > > ./digikam-5.8.0-20171207T053823-x86-64.appimage debug

> > > > > ---- 8-< ----

> > > > >

> > > > > And I forgot to tell you my DB-config: DK is using an external

> > > > > mysql-server

> > > > > on my NAS, and the older versions works very well in this

> > > > > environment

> > > > > ;-)

> > > > >

> > > > > Greetz,

> > > > >

> > > > > Christoph

> > > > >

> > > > > Am Sonntag, 10. Dezember 2017, 12:41:43 CET schrieb

>

> [hidden email]:

> > > > > > Hi,

> > > > > >

> > > > > > I'm sing DK 5.8.0 as appimage. Older Version (without

> > > > > > databaseconverting) working fine, but since a database converting

> > > > > > is

> > > > > > implemented, I can't use newer DK 5.8.0 appimages because of a

> > > > > > converting error:

> > > > > >

> > > > > > ---- 8-< ----

> > > > > > $ ./digikam-5.8.0-20171207T053823-x86-64.appimage debug

> > > > > > ---- 8-< ----

> > > > > >

> > > > > > Greetz,

> > > > > > Christoph