Nextcloud scan scans entire server / scan stuck at 75 photos

[sysoppl]

This project seems to be dead, but latest PRs showed that there is some development going, so I'm creating this issue.

Using latest @zainlol docker image on fresh ubuntu 20.04 server, when I logged in and selected nextcloud folder to scan, after a while it showed photos from outside selected folder (generally it probably scan entire nextcloud server).

Also, cpu usage drop after a while, and scan was stuck at 75 photos. None of photos in selected folder was shown.

[derneuere]

Hey @sysoppl

I could reproduce your error, but it did not even want to scan one picture. Can you send me your logs?

[sysoppl]

So this time my Chrome shows blank page (even in incognito) with same error as in here, but Firefox works normally. This time CPU usage drops when there was 89 scanned photos. I also tried to open one or two photos, with no success (infinity loading).

Here are the logs. I removed some IPs and changed nextcloud folder paths (selected folder is marked by "THIS_FOLDER_WAS_SELECTED"). command_migrate.log docker-compose.txt gunicorn_django.log gunicorn_image_similarity.log image_similarity.log ownphotos.log rqworker.log show_migrate.log command_makemigrations.log

It even shows 320 photos (there is ~70-100 in selected directory)

As always, fresh ubuntu 20.04 server

---

After restarting everything cpu usage is still idle, and scan seems to be still in progress Photos however appear after a while

I can also open photos now

[derneuere]

@sysoppl I think I fixed the issues. The first issue was that the nextcloud job looked at the local scan path at not at the nextcloud scan path. The second issue was that delayed rq jobs silently crash. If a job instead is started immediately then it works.

I pushed a new image. Please try it out and tell me if it fixed your issues.

[sysoppl]

It is fixed, thank you so much for your effort!