Hi all,

Our Uyuni infra is quite little with 90 registered clients and increasing, however since some days we notice like a starvation of taskomatic which don’t seem

to be able to launch SSHPush tasks and check Uyuni client status. All the registered servers are consequently shown as inactive (“System not checking in with Uyuni”).

Important perhaps to mention that “push via SSH” is the registration method used for all the registered servers ( = no Salt minion installed).

The only one servers not affected by this issue are the Uyuni proxies which are registered with salt-minion.

We can repetitively see in the taskomatik logs this:

2020-11-22 10:21:00,500 [DefaultQuartzScheduler_Worker-88] WARN  com.redhat.rhn.taskomatic.task.SSHPush - Maximum number of workers already put ... skipping.

2020-11-22 10:22:00,327 [DefaultQuartzScheduler_Worker-22] WARN  com.redhat.rhn.taskomatic.task.SSHPush - Maximum number of workers already put ... skipping.

2020-11-22 10:23:00,173 [DefaultQuartzScheduler_Worker-92] WARN  com.redhat.rhn.taskomatic.task.SSHPush - Maximum number of workers already put ... skipping.

No more info in any logs, and repositories sync is still working without issue though. Seems so that the SSHPush tasks queue is blocked at some point ?

A restart of taskomatic temporarily solve the issue.

I have tried to follow this https://www.uyuni-project.org/uyuni-docs/uyuni/large-deployments/tuning.html,

but well, from what mentioned the doc, it should not be necessary in my case (“Tuning is not required on installations of fewer than 1000 clients. Do not perform these instructions on small or medium scale installations.”), and no luck with it anyway.

Any ideas ? Somebody who experienced this same issue ?

Philippe.