-
-
Notifications
You must be signed in to change notification settings - Fork 317
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
can't scan #738
Comments
downgraded torchvision on the running "backend"
full error of output
|
i starrted a new db coz off "api_longrunningjob_pkey" Key (id)=(16) already exists error and did a
persiists but scan managed to reach 100% this time but the job is still unfinished the "recycle" has not changed in to a "check mark" icon last lines from
last rqworker.log lines says
last ownphotos.log lines looks normal
|
It could be that this line here changed: https://github.com/LibrePhotos/librephotos-docker/blob/00d97785992b8417d82489614d187e38b481288c/backend/base/Dockerfile#L61 We need a custom pytorch dependency, because raspberry pis do not support the whole arm instruction set. We solved this issue by using this 3rd party pytorch dependency: https://github.com/KumaTea/pytorch-aarch64 |
I changed a couple of things in the base image and in the entrypoint file. It would be great, if you could test, if it works again. |
Was using 2022w50 backend image so far. Just updated to latest and I'll wait for my cron to initiate a scan in the morning I'll report back tomorow Thanks |
From guicron_django.log looks like workers are exiting again due to torchvision
From the admin page of the web ui I also see that the scan stuck at 95% The rqworker.log
My docker-compose.yml
|
The warning is normal and also happens on the normal setup. It looks like it's a timeout issue, similar to how #744 (comment) described it. Would be great, if you could open a separate issue for it. |
running on raspberry pi 400
been using an older image for a long time
maybe a torchvision update broke something for arm devices?
sudo docker exec --user root backend python3 manage.py scan
throws error
The text was updated successfully, but these errors were encountered: