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

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Uwe Haider
For jdd the first message again (with the error-messages):

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



--
Uwe Haider
[hidden email]
http://www.familie-haider.de


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

Remco Viëtor
On samedi 27 mai 2017 07:32:05 CEST Uwe Haider wrote:
> For jdd the first message again (with the error-messages):
>
> 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:
> ...

Just a suggestion:
could you please try and reply to an existing message in the original thread,
instead of starting new ones, or replying to the latest digest?
As it is now, your topic is spread out over 3-4 threads. That makes it hard to
follow and hard to find earlier posts.

Remco
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

jdd@dodin.org
In reply to this post by Uwe Haider
Le 27/05/2017 à 07:32, Uwe Haider a écrit :
> For jdd the first message again (with the error-messages):

sorry :-(

>    146 digikam.general: Did not find album root album in hash
>    147 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch

(...)

> - 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.

disk full? the failed one?

>
> Or should I remove the Albumrootpath of the crashed hard disk manually?
>
>
> Any advice is welcome...
>

I don't use mysql because I find backing up is too difficult, when
backing up sqlite is extremely easy (simply copy the file).

But...

I tested a similar thning with my sqlite.

my config is a bit different, but the result may be not so. My main
collection disk is usb. I keep it most all the time on, but it could be
umounted.

I noticed at some moment (where I didn't have time to report bugs) my
collection on this usb disk where seen as local instead of removable;

so I made a backup copy of my base, then umounted the disk and reloaded
digikam (5.6 appimage)

no main  problem, apart of course collection disappearing, but lot of
error messages, of course

but when remounting the disk, digikam where starting but beginning to
scan all the collection anew and may be very long because it found
duplicates (of course). On a network, this very long time may explain
the final crash?

it do not really matters for me because I keep all the infos in the
photo files themselves, but I have lot of separate collection and
recreate then is boring

hope this helps - finally the better you can do IMHO is to keep a data
base backup and try to remove offending collections with phpmyadmin :-(

jdd
Loading...