-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Indexer is stuck at 100.1% #245
Comments
The 18 out of 17 might be just indexing related UI issue.
Can you please provide docker logs for the container?
You can also set the log level to 'silly" in the config.json to force
all.logs.
…-- Sorry for being brief, sent from my phone.
Magneticdud ***@***.***> ezt írta (időpont: 2021. ápr. 1., Cs
19:21):
I created another docker container with a totally different set of images
and while it still shows "18 out of 17", it wasn't stuck and continued to
the next step
[image: image]
<https://user-images.githubusercontent.com/2940598/113330637-41138680-931f-11eb-8803-f70459f18404.png>
I am even more puzzled...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#245 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZKA5VWG54U7RVPPIGHTT3TGSTQZANCNFSM42HIICTQ>
.
|
I have also begun experiencing this recently. I'm running a new index and capturing the logs. Lots of pictures, so it'll take a while. |
I've created a gist of the log I see after triggering an index. It seems to be the ER_TRUNCATED_WRONG_VALUE_FOR_FIELD, which keeps being raised for a particular picture (02478_castleofdecay_1920x1080.jpg) over and over. Maybe that image is what's holding up the indexing? It errors out, but isn't removed from something. |
huh. I added it, hope it fixes your issue. |
I changed tags to |
Pls make sure, that the version you are running was built with d8b3ff0 or later. (It takes about 40 mins to build a release and publish it on docker. ) Also if you send me some logs and corrupted images, I can take a look. |
Ah, might not have that then. Is git revision output in the docker logs or visible in the GUI? |
i set to silly but i didn't notice anything strange
The error about "Senzatitolo10.jpg" is repeated another hundred times, and it's one of the first images to be scanned. The Picasa folder, that's the last one to be scanned, it's in the ignore list, should it be scanned? By the way, I deleted that image and the picasa folder, now it gets stuck in another image
I noticed that all the pictures in that directory have an invalid creation date in the exif set to 00/00/0000 00:00:00, maybe if the date is clearly invalid, it should be ignored and not be written in the database I'll try to fix the exif |
Hi, the first issue is still the ISO is a For the second: the creation date is a negative number (the app does not support b.c. :), so ) is in an "illegal" value. Can you send me a photo that produces this error? |
The ignore lists ignores whole folders, you cannot ignore single photos. (if the ignore does not take effect, there might be some issue with the settings.) |
I found out that any photos imported by the tool that was builtin in windows xp have the exif date set to an invalid value... Why 15 years ago I was lazy and used that tool instead of taking out the compact flash??? This image has a date that is 00/00/0000 00:00:00 if read with exiftool or -0001/11/30 00:00:00 if read with verexif.com |
I made an update 3c70ce4, with that the last photo looks good. |
Hi, looks like all errors are gone, now I get this and it still get stuck:
I tried to reset the database but the result did not change (the entry had a different number appended to the name after the reset) There aren't other images with this name in the directory, or other files with the same md5 hash. The image doesn't appear in the duplicates section (which is VERY useful, thanks! Noticed a lot of duplicates that I never noticed before) Unfortunately this image contains questionable content and can't be shared |
Unfortunately from this I cannot really figure out. You can try switching to sqlite, that usually has less issues. I'm also using that on my rpi4 with a relatively decent performance. |
in this case i got the image from a friend he named all the images the same, then added a single letter at the end like this
then because images were > 26, used accented letters èòà, and maybe I guess it could be imagee.jpg and imageè.jpg are giving the conflict. I'll properly rename them and see if this is the reason edit: after renaming the files and removed the accented letters, the problem is gone |
most likely that comes from the DB collocation and letters with/without accents counts to be the same when checking if the string is unique. |
Had an other look to this photo. That is unfortunate, but there is no way to detect it as it is possible that there is a photo before epoch (1970). I also have some. So I will just support from now on negative timestamps. |
Describe the bug
I am not sure how this happened, the folder indexer processed 885 folders out of 884, so it's "stuck" at 100.1%
Then it is blocked to doing this task (which can never reach 100%)

And it can't do other jobs

I tried to stop the docker and restart it but it restarts the indexing job immediately. In the docker logs I didn't see any messages that could explain the problem.
I tried to reset the database, but then when I run the indexing again, the problem repeats. In the indexing log I see it's indexing some folders that should be ignored (.stfolder, .stversions, Picasa)
Environment:
The text was updated successfully, but these errors were encountered: