[digiKam-users] (no subject)

[Gilles Caulier]

Look this entry :

https://github.com/Sonarr/Sonarr/issues/1886

"
sqlite databases need to live on a SMB/CIFS/NFS path.
> It shouldn't, like never. Even other synchronization modes aren't reliable over networks, it's horrible for performance too.
"

Gilles Caulier

Le mer. 31 mars 2021 à 22:34, Andrew Goodbody <ajg02 at elfringham.co.uk> a écrit :
>
> Worse than a bad idea, it is specifically warned against. Accessing
> SQLite databases over a network connection is very prone to corrupting
> the database.
>
> If you must have a remote database then use MySQL.
>
> Andrew
>
> On 31/03/2021 14:09, Gilles Caulier wrote:
> > Did you host the SQlite database file on the remote CIFS files system ?
> >
> > If yes, it's a bad idea...
> >
> > Gilles Caulier
> >
> > Le mer. 31 mars 2021 à 15:05, Sweetth Devil <sweetthdevil at gmail.com> a écrit :
> >>
> >> Hello all,
> >> I used Digikam but moved my collection of pictures and my database to my newly installed home server. My computer is running Archlinux and so is my server.
> >>
> >> The database was SQLite.
> >>
> >> The Collection & database get mounted using CIFS on a samba share using the following mount parameters:
> >>
> >> //192.168.1.90/arch_home_server /mnt/share cifs username=sweetth,password=******,rw,user,noauto,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
> >>
> >>
> >> After a lot of frustration I deleted all traces of DigiKam from my install including config files (inc. digikamrc) and database.
> >>
> >> But DigiKam is still complaining of database rights. If I start DigiKam without the Samba share mounted it starts without any issue.
> >>
> >> See below DigiKam debug info:
> >>
> >> Type "apropos word" to search for commands related to "word"...
> >> Reading symbols from digikam...
> >> (No debugging symbols found in digikam)
> >> (gdb) catch throw
> >> Catchpoint 1 (throw)
> >> (gdb) run
> >> Starting program: /usr/bin/digikam
> >> [Thread debugging using libthread_db enabled]
> >> Using host libthread_db library "/usr/lib/libthread_db.so.1".
> >> [New Thread 0x7fffdbbb7640 (LWP 4065)]
> >> [New Thread 0x7fffd9ecd640 (LWP 4066)]
> >> [New Thread 0x7fffd96cc640 (LWP 4067)]
> >> [New Thread 0x7fffd8ecb640 (LWP 4068)]
> >> [New Thread 0x7fffcbfff640 (LWP 4069)]
> >> [New Thread 0x7fffca6f9640 (LWP 4070)]
> >> QCommandLineParser: already having an option named "h"
> >> QCommandLineParser: already having an option named "help-all"
> >> QCommandLineParser: already having an option named "v"
> >> [New Thread 0x7fffc94e8640 (LWP 4071)]
> >> [New Thread 0x7fffc8ce7640 (LWP 4072)]
> >> [New Thread 0x7fffb3fff640 (LWP 4073)]
> >> [Thread 0x7fffb3fff640 (LWP 4073) exited]
> >> digikam.dbengine: Detected locked database file. There is an active transaction. Waited but giving up now.
> >> digikam.coredb: Core database: cannot process schema initialization
> >> [New Thread 0x7fffb3fff640 (LWP 4075)]
> >> [New Thread 0x7fffb3709640 (LWP 4076)]
> >> [New Thread 0x7fffb2f08640 (LWP 4077)]
> >> [New Thread 0x7fffb2707640 (LWP 4078)]
> >> [Thread 0x7fffb3709640 (LWP 4076) exited]
> >> [Thread 0x7fffb3fff640 (LWP 4075) exited]
> >> [Thread 0x7fffb2707640 (LWP 4078) exited]
> >> [Thread 0x7fffb2f08640 (LWP 4077) exited]
> >>
> >> Thread 9 "digikam" received signal SIG32, Real-time event 32.
> >> [Switching to Thread 0x7fffc8ce7640 (LWP 4072)]
> >> 0x00007ffff51f9bf3 in pselect () from /usr/lib/libc.so.6
> >> (gdb) quit
> >> A debugging session is active.
> >>
> >>          Inferior 1 [process 4061] will be killed.
> >>
> >>
> >> Should more information are required, please let me know.
> >> Looking forward to your replies.
> >>
>