file not found.... -> no start!

[Gilles Caulier]

I confirm,

Never place a sqlite database on a network device. sqlite, even if
implementation is better in time, will don't support well the lock
mechanism on network place. Read the entry in this wiki for details :

http://stackoverflow.com/questions/788517/sqlite-over-a-network-share

Gilles Caulier

2017-05-21 15:50 GMT+02:00 Remco Viëtor <remco.vietor at wanadoo.fr>:
> On dimanche 21 mai 2017 14:23:29 CEST Uwe Haider wrote:
>> After moving to a new computer/NAS I have trouble to start digikam. I
>> try to fix it for several weeks now, but no success so far. This is the
>> output of digikam while starting:
>>
>>   [...]
>>
>>   133  digikam.general: Using  8  CPU core to run threads
>>   134 digikam.general: new search text settings:  "" : hasResult =
>> false , validRows =  0
>>   135 QFSFileEngine::open: No file name specified
>>   136 digikam.geoiface: ----
>>   137 digikam.general: Added root album called:  "WD-USB"
>>   138 digikam.general: Added root album called:  "Geschäftsbericht_2011"
>>   139 digikam.general: Added root album called:  "Einweihung HHN"
>>   140 digikam.general: Added root album called:  "Albas Bilder"
>>   141 digikam.general: Added root album called:  "Carla 18"
>>   142 digikam.general: Added root album called:  "Bilder_lokal"
>>   143 digikam.general: Added root album called:  "Bilder"
>>   144 digikam.general: Added root album called:  "Fotos"
>>   145 digikam.general: Added root album called:  "NAS"
>>   146 digikam.general: Did not find album root album in hash
>>   147 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
>> failed: Datei oder Verzeichnis nicht gefunden
>>   148 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
>> failed: Datei oder Verzeichnis nicht gefunden
>>
>> -> last line is repeated until here
>>
>> 3094 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
>> failed: Datei oder Verzeichnis nicht gefunden
>> 3095 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
>> failed: Auf dem Gerät ist kein Speicherplatz mehr verfügbar
>>
>> "Datei oder Verzeichnis nicht gefunden" means "file not found"
>>
>> "Auf dem Gerät ist kein Speicherplatz mehr verfügbar" means "no space
>> left on device".
>>
>> This is, what I have done while moving to the new machine:
>>
>> - moved the mariadb-server to my NAS
>>
>> - moved all files in the NAS-mariadb as separate dumps
>>
>> - changed the album paths in the albumroot-table to the new mount points
>>
>> - I have lost an harddisk (broken, unreadable) and tried to mount the
>> backup instead ( I don't need this files absolut)
>>
>> - changed the configuration in digikam to the NAS-mariadb
>>
>> The main problem seems to be the QInotifyFileSystemWatcherEngine writing
>> a disk full - how can I stop this? I think digikam will be able to check
>> and repare the mariadb if it gets started.
>>
>> Or should I remove the Albumrootpath of the crashed hard disk manually?
>>
>>
>> Any advice is welcome...
>>
>>
>> uhai
> If I understand correctly, you are trying to put the digikam database on a
> network drive. Looking at the Digikam settings dialog, it says explicitly:
> "Note: a remote file system such as NFS, cannot be used here"...
> In addition, MySQL is still marked as experimental, mariadb is a fork of
> MySQL. That's for Digikam version 5.5.0 (as appimage under OpenSuSE 42.2)
>
> Might that be the cause of the problems?
>
> Remco