https://bugs.kde.org/show_bug.cgi?id=3D377039

            Bug ID: 377039
           Summary: Network Collections cause hang on "Reading Database"
           Product: digikam
           Version: 5.4.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Database-Mysql
          Assignee: digikam-devel@kde.org
          Reporter: photo@fritztech.com
  Target Milestone: ---

OSX 10.12.3 (and previous versions also)
Occurs on Digikam 5.4.0, and 5.3.0, and several previous versions. Installed
via the .pkg files on the digikam site.=20=20
External localhost MySQL (5.7.9) on a SSD, tuned properly for the hardware.=
=20
Network drives on ubuntu via NetATalk.=20
~200,000 images on several network shares.

Digikam appears to hang on "Reading Database" on the splash screen when net=
work
collections are present and the drives are mounted. If you wait long enough=
, it
will usually eventually start up (>30 minutes). Sometimes forcing quit and
trying again results in a start up in only 4 or 5 minutes.=20

If I start digikam with the network drives unmounted, it starts in less tha=
n 20
seconds but then I can't access any of the files on the network collections
only the local ~50k images. The network images remain unavailable even if I
mount the remote drives. .=20

The hang/slow start gets worse as the size of the remote collections gets
larger so I'm guessing digikam is doing something on those drives for each
image file?!? In any case, mysql shows no queries running and the slow query
log shows nothing for digikam.

Once digikam starts, everything works normally.=20

This problem has been getting studly worse as my collections get bigger and=
 as
I add network collections for various reasons.=20

2 issues/questions:=20

1) Why doesn't digikam see that the files are available if the drives are
mounted after digikam starts? Why does this require a restart of digikam (w=
hich
hangs for 30+ minutes). A simple "stat" call will show the image file or
collection root is present and available after startup, but maybe it is har=
der
than that (i.e. scan for changes might need to run?). Am I missing some menu
item to make it see the connected network drives?=20

2) Is there a way to fix the hang/slow start? What can I do to help you fig=
ure
out the issue? As noted, mysql does not appear to be doing anything during =
the
hang, and the collections exist whether the drives are mounted or not so th=
e DB
is the same.

--=20
You are receiving this mail because:
You are watching all bug changes.=