Thanks Jérémie,
I ran toolforge jobs flush, which stopped all jobs apparently, and removed everything from my list of jobs. I ran toolforge jobs load to reload my list of jobs.
So it seems things are back to normal now, but I have a few questions : * How is it possible that there was 2 instances of the same cron job ? Is it because one was stuck more than a week and a second one was started at this time ? * How can I really stop a job (I see only toolforge commands for restarting) when it gets stuck ? * How can I stop jobs when there are several instances of the same cron job ?
Nicolas
On Sun, Dec 7, 2025 at 3:50 PM Jérémie Roquet jroquet@arkanosis.net wrote:
Hi Nicolas,
Le dim. 7 déc. 2025 à 15:30, Nicolas Vervelle nvervelle@gmail.com a écrit :
My resource consumption reported by the quota is way above the
consumption of my currently running job, preventing other jobs from starting. Where does the extra consumption come from ? And how to clean this ?
It seems you currently have 3 jobs running:
- 2 instances of the wpcleaner-fr-list cronjob that requests 2 × 3
GiB of memory,
- 1 instance of webservice which I guess requests the default 0,5 GiB
of memory.
Hence a total of 6,5 GiB requested (but not actually consumed), which means that you cannot request an additional 3 GiB for another job (the quota for requests being 8 GiB).
My suspicions stem for the Grafana monitoring, where three pods are visible, including two for wpcleaner-fr-list:
https://grafana.wmcloud.org/d/TJuKfnt4z/tool-dashboard?orgId=1&var-names...
Best regards,
-- Jérémie