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

Uwe Haider uwe.haider at gmx.net
Mon May 22 13:16:10 BST 2017 

My NAS is connected via nfs. DigikamDB is mysql. If I remember correctly, only Sqlite can't be used over nfs - right or wrong?

Am 22. Mai 2017 14:00:05 MESZ schrieb digikam-users-request at kde.org:
>Send Digikam-users mailing list submissions to
>	digikam-users at kde.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://mail.kde.org/mailman/listinfo/digikam-users
>or, via email, send a message with subject or body 'help' to
>	digikam-users-request at kde.org
>
>You can reach the person managing the list at
>	digikam-users-owner at kde.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Digikam-users digest..."
>
>
>Today's Topics:
>
>   1. Re: file not found.... -> no start! (Remco Viëtor)
>   2. Re: Adjusting file last modified date (Andrey Goreev)
>   3. Re: file not found.... -> no start! (Uwe Haider) (Uwe Haider)
>   4. Re: file not found.... -> no start! (Gilles Caulier)
>   5. Re: How do I save "DateTime imported" value in Digikam?
>      (Jens Benecke)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Sun, 21 May 2017 15:50:00 +0200
>From: Remco Viëtor <remco.vietor at wanadoo.fr>
>To: digiKam - Home Manage your photographs as a professional with the
>	power of open source <digikam-users at kde.org>
>Subject: Re: file not found.... -> no start!
>Message-ID: <5388231.gBvAhygMuy at manticore>
>Content-Type: text/plain; charset="UTF-8"
>
>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
>
>
>------------------------------
>
>Message: 2
>Date: Sun, 21 May 2017 08:18:20 -0600
>From: Andrey Goreev <aegoreev at gmail.com>
>To: digiKam - Home Manage your photographs as a professional with the
>	power of open source <digikam-users at kde.org>
>Subject: Re: Adjusting file last modified date
>Message-ID: <5921a1b0.cd20240a.85d95.ba95 at mx.google.com>
>Content-Type: text/plain; charset="utf-8"
>
>I am pretty sure that FileModifyDate is the system's "date modified".
>Windows would have "date created" in addition to it but linux does not
>store "date created". In the example I sent I copy values from
>QuickTime Date Created of mp4 file to system's file date modified (I do
>that because digikam uses date modified (file system) as date created
>(content) for video files. Works for me)
>
>
>Sent from my Samsung Galaxy smartphone.
>-------- Original message --------From: Remco Viëtor
><remco.vietor at wanadoo.fr> Date: 2017-05-21  7:43 AM  (GMT-07:00) To:
>digiKam - Home Manage your photographs as a professional with the power
>of open source <digikam-users at kde.org> Subject: Re: Adjusting file last
>modified date 
>On dimanche 21 mai 2017 15:15:10 CEST Andrey Goreev wrote:
>> In the meantime, exiftool can do that easily.
>> exiftool -api quicktimeutc=1 "-FileModifyDate<QuickTime:CreateDate"
>> -overwrite_original FILE  Change QuickTime:CreateDate to whatever tag
>you
>> want to copy the info from or to a certain value (date). 
>
>But make sure you know which tag you need to overwrite...
>In this case, the OP wanted to change the date the file was last
>/modified/.
>Your exemple would change the date the file content was /created/, not
>the same 
>thing. I'd even think you wouldn't want to touch that particular item
>at all, 
>except when you know the date is wrong and you know the correct
>creation date.
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL:
><http://mail.kde.org/pipermail/digikam-users/attachments/20170521/83b60105/attachment-0001.html>
>
>------------------------------
>
>Message: 3
>Date: Sun, 21 May 2017 16:50:41 +0200
>From: Uwe Haider <uwe.haider at gmx.net>
>To: digikam-users at kde.org
>Subject: Re: file not found.... -> no start! (Uwe Haider)
>Message-ID: <5fc36302-8182-512f-7242-c4f175b4eacd at gmx.net>
>Content-Type: text/plain; charset=utf-8
>
>Thanks Andrey,
>
>I've tested it with vim and it works for my user. Writing is possible
>to
>the NAS.
>
>uhai
>
>-- 
>Uwe Haider
>uwe.haider at gmx.net
>
>
>
>------------------------------
>
>Message: 4
>Date: Sun, 21 May 2017 19:35:58 +0200
>From: Gilles Caulier <caulier.gilles at gmail.com>
>To: digiKam - Home Manage your photographs as a professional with the
>	power of open source <digikam-users at kde.org>
>Subject: Re: file not found.... -> no start!
>Message-ID:
>	<CAHFG6sG2NfMH-FFH3oxW1A8Zw2FEqq_RTFtqVh6UtOFjq4e=iA at mail.gmail.com>
>Content-Type: text/plain; charset="UTF-8"
>
>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
>
>
>------------------------------
>
>Message: 5
>Date: Sun, 21 May 2017 23:03:16 +0200
>From: Jens Benecke <jens-digikam at spamfreemail.de>
>To: digiKam - Home Manage your photographs as a professional with the
>	power of open source <digikam-users at kde.org>
>Subject: Re: How do I save "DateTime imported" value in Digikam?
>Message-ID: <F8CB82BD-576F-4CA8-A0A6-8E4D5C78A0EC at spamfreemail.de>
>Content-Type: text/plain; charset=utf-8
>
>Hello,
>
>wow, this has started quite a discussion. :)
>
>I have now decided to use DateTimeDigitized to store the import date in
>iphoto2xmp.
>It comes closest in meaning and has no other value for digital camera
>pictures anyway, and for my scanned images the date is equal to the
>imported date. This way iPhoto can still use the date.
>
>Thanks for all shared thoughts and considerations!
>
>Regards
>
>-- 
>Jens Benecke - jens at spamfreemail.de
>Keine Lust auf Müll in ihrem Postfach? www.spamfreemail.de
>
>
>
>> Am 19.05.2017 um 08:37 schrieb Gilles Caulier
><caulier.gilles at gmail.com>:
>> 
>> no DK do not touch unknown or un-managed tags.
>> 
>> But don't forget Exiv2 is used at end in background. Something
>> unwanted can be done in this area, but as i know nothing is removed
>> intentionally by Exiv2 at metadata rewriting stage.
>> 
>> Gilles Caulier
>> 
>> 2017-05-19 8:29 GMT+02:00 Mica Semrick <mica at silentumbrella.com>:
>>> I would consider it very bad behavior to remove or ovverwritw ever
>element
>>> in the XMP file. I certainly hope digikam does not have this
>behavior.
>>> 
>>> -m
>>> 
>>> 
>>> On May 18, 2017 11:16:56 PM PDT, "jdd at dodin.org" <jdd at dodin.org>
>wrote:
>>>> 
>>>> Le 19/05/2017 à 07:48, Remco Viëtor a écrit :
>>>> 
>>>>> about. But such unknown tags may get lost on rewriting the file.
>>>>> 
>>>> 
>>>> 
>>>> really? this is pretty odd.
>>>> 
>>>> some tag may be replaced though (editor's name, for example)
>>>> 
>>>> jdd
>
>
>
>------------------------------
>
>Subject: Digest Footer
>
>_______________________________________________
>Digikam-users mailing list
>Digikam-users at kde.org
>https://mail.kde.org/mailman/listinfo/digikam-users
>
>
>------------------------------
>
>End of Digikam-users Digest, Vol 144, Issue 40
>**********************************************

-- 
Diese Nachricht wurde mobil versendet.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170522/ede53276/attachment.html>

More information about the Digikam-users mailing list