github-actions[bot]
commented
4 months ago Hello :wave:
Thank you for taking the time to open this issue with recognize. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. I try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. (Also see our Code of Conduct. Really.)
I look forward to working with you on this issue Cheers :blue_heart:
marcelklehr
szaimen
RikkiBC
Which version of recognize are you using?
7.0.3
Enabled Modes
Face recognition
TensorFlow mode
WASM mode
Downstream App
Memories App
Which Nextcloud version do you have installed?
29.0.3
Which Operating system do you have installed?
Ubuntu 22.04, running official NextcloudAIO in Docker
Which database are you running Nextcloud on?
PostrgreSQL
Which Docker container are you using to run Nextcloud? (if applicable)
No response
How much RAM does your server have?
10GB
What processor Architecture does your CPU have?
ARM64
Describe the Bug
A month ago, it looks like Recognize stopped working. I only just realised it as it's not often that I check on my recognised faces. In the admin section I saw these messages:
Please Note: It didn't originally say "Face recognition: 0 Queued files", it originally had something like 680~ queued files. It did still say 0 queued jobs though.
It also originally said that the models needed to be downloaded. Using the "
sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ recognize:download-models" command fixed that problem, however there were never any further jobs scheduled, and the error messages about "An error occurred during face recognition, please check the Nextcloud logs" was still there too.Please Also Note: There was another error message there too, originally: "There are queued files in the face recognition queue but no background job is scheduled to process them."
The following was then done in order.
1, attempted manual run of clustering
I tried to cluster faces with "
sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ recognize:cluster-faces", but of course that's not the issue - it just went through each user and let me know that there were no face detections found for them.2, checking Node
I checked Node in a few ways.
sudo docker exec --user www-data -it nextcloud-aio-nextcloud node --version" returned "v20.13.1"./var/www/html/custom_apps/recognize/bin/node". I have not touched this since AIO was first set up, as, originally at least, it was fine.sudo docker exec --user www-data -it nextcloud-aio-nextcloud ls /var/www/html/custom_apps/recognize/bin/node"./var/www/html/custom_apps/recognize/bin/node".sudo docker exec --user www-data -it nextcloud-aio-nextcloud /var/www/html/custom_apps/recognize/bin/node --version".Error relocating /var/www/html/custom_apps/recognize/bin/node: fcntl64: symbol not found"3, manually running recrawl
Perhaps stupidly, I ran "
sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ recognize:recrawl" as, as far as I could tell, it was the only way to get Recognize to schedule a job again. It did... and also set me up for re-crawling aaall my old photos too. Sigh.After running recrawl, the "There are queued files in the face recognition queue but no background job is scheduled to process them." error message disappeared. Likewise, the number of jobs awaiting classification dropped to zero, before (after several minutes) climbing well into the thousands with 5 scheduled jobs.
4, manually stopping background jobs
I stopped the background jobs for now with "
sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ recognize:clear-background-jobs". It's at this point that we get to the screenshot I shared above.5, checking Nextcloud Error Logs
I couldn't see anything in the logs before this point. My logs only went back a week and it looks like the jobs stopped a while ago. But, thanks to Step 3 above, I now had some fresh logs to check.
It's the error "Classifier process output: Error relocating /var/www/html/custom_apps/recognize/bin/node: fcntl64: symbol not found" that really catches my eye.
fcntl64: symbol not foundis the same error I got when trying to check the node version at the end of Step 2 above.It's at this point I'm stuck. I hope I've provided enough info but I really don't know what the issue is or where to go from here. Searching "
fcntl64: symbol not found" online isn't providing much assistance - my Google Fu might be weak right now, but all I'm finding are esoteric pages about stuff which looks unrelated.Please help.
Expected Behavior
Recognize continues working when it hasn't been touched (except maybe by AIO?).
To Reproduce
Not sure what caused this issue in the first place, sorry. I hope I added enough information in the Describe The Bug section, otherwise please ask for more details if needed.
Debug log
No response