memories
memories copied to clipboard
Index error with 4.8.1
Getting "Exiftool may have crashed" for film and big video file.
Doesn't know yet what will be the consequences.
oh, now it completely crashed:
///
is there a way to edit the memory index path for the time being for all user (using cli, or config, and not the app)
nvm, found it in the db at ec_preference, i changed all of them to: //Photos;//InstantUpload
but while doing occ memories:index --clear
i still get an error and still scan everything
- There's a timeout, which you're hitting in the first post. Should make that configurable.
- The second one seems a bug introduced by #221. I should have paid more attention to this.
- If you want to prevent indexing a directory, the best way is to add a
.nomedia
file in it.
At least the crash should be fixed with v4.8.2
After enabling reverse geocoding, trying to run occ memories:index -f
command, but it is soo slooow (after 16h running it reports 55%, ~50k files) and reports multiple exiftools crashes:
ERROR: Exiftool may have crashed, restarting process [file]
As a result i have now 1131 zombie processes.
Photo dir is outside of /nextcloud dir, but on the same storage (not remote). Memories 4.11.0, Nextcloud Hub 3 (25.0.3)