-
Notifications
You must be signed in to change notification settings - Fork 46
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
Classify background jobs don't seem to be doing anything and queue stays filled up. Manual recognize:classify works. #1030
Comments
Hello 👋 Thank you for taking the time to open this issue with recognize. I know it's frustrating when software I look forward to working with you on this issue |
Hello @Fosnine This is a known issue and should be fixed with the upcoming server release |
I have the same issue with Nextcloud version 27.1.6 and Recognize version 5.0.3, a lot of pictures in my case 133228. So the issue is still there. It was not fixed in 27.1.4. Nextcloud is installed with snap in a VM with 16 GB RAM, OS Ubuntu, kernel, Linux 5.11.0-49-generic x86_64 CPU: Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz (8 cores) The pictures are mounted from a second internal drive NVMe 4 TB with NTFS and external drive plugin.
I already reset faces ones and re-run the classify job, but it takes a few days to proces all my pictures which are added in the queue. The issue is the background jobs don't pick up the new faces. Clustering face detections for user x It started fine for a few hours and after that just dropped the queue.
|
Which version of recognize are you using?
5.0.3
Enabled Modes
Object recognition, Face recognition, Video recognition
TensorFlow mode
Normal mode
Downstream App
Memories App
Which Nextcloud version do you have installed?
NextCloudPi 27.0.1
Which Operating system do you have installed?
Debian 11.8
Which database are you running Nextcloud on?
MySQL 10.5.21
Which Docker container are you using to run Nextcloud? (if applicable)
No response
How much RAM does your server have?
6GiB
What processor Architecture does your CPU have?
x86_64
Describe the Bug
When I run recognize:classify manually, everything seems to work correctly and tags show up. I don't have any people even after running cluster manually with the command but that seems to be correct since recognize says:
'Face clustering: 79 faces left to cluster, Last clustering run: 1 hour ago, Scheduled background jobs: 0,
A minimum of 120 faces per user is necessary for clustering to kick in;
Files stay queued after adding them for 2+ days but I don't get any errors. background jobs are scheduled but the amount of queued files isn't going down. When a picture is added, it immediately shows up in the queue.
GUI shows:
'Face recognition: 72 Queued files, Last classification: 1 hour ago, Scheduled background jobs: 1, Last background job execution: 3 minutes ago'
'Object recognition: 72 Queued files, Last classification: 1 hour ago, Scheduled background jobs: 1, Last background job execution: 8 minutes ago'
'Landmark recognition: 27 Queued files, Last classification: never, Scheduled background jobs: 2, Last background job execution: 8 minutes ago'
'Video recognition: 0 Queued files, Last classification: 1 hour ago, Scheduled background jobs: 0,'
The last classification time is when I ran recognize:classify again.
Cron seems to be working correctly since it doesn't show any errors when run manually and debug logs show that other jobs get finished in 0 seconds:
e.g.
[cron] Debug: Finished OCA\Notifications\BackgroundJob\SendNotificationMails job with ID 18 in 0 seconds
at 2023-11-12T16:45:01+00:00
screenshots of oc_jobs table:
Expected Behavior
I expect the background jobs to classify when cron runs.
To Reproduce
Debug log
There are no errors that lead me to believe anything wrong is happening. The only related lines in the logs are the following:
[cron] Debug: Skipping OCA\Recognize\BackgroundJobs\ClassifyLandmarksJob job with ID 4901 because another job with the same class is already running
at 2023-11-12T16:40:02+00:00
[cron] Debug: Skipping OCA\Recognize\BackgroundJobs\ClassifyFacesJob job with ID 4684 because another job with the same class is already running
at 2023-11-12T16:40:02+00:00
[cron] Debug: Skipping OCA\Recognize\BackgroundJobs\ClassifyImagenetJob job with ID 4683 because another job with the same class is already running
at 2023-11-12T16:40:02+00:00
[cron] Debug: Skipping OCA\Recognize\BackgroundJobs\ClassifyLandmarksJob job with ID 4678 because another job with the same class is already running
at 2023-11-12T16:40:02+00:00
The text was updated successfully, but these errors were encountered: