Salt SSH clients are not "checking in" in SUSE Manager

This document (000021132) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager 4.3 Server
SUSE Manager 4.2 Server

Situation

Salt SSH clients located in DMZ can be properly operated from SUSE Manager Server webUI. The clients respond correctly to every action scheduled from SUSE Manager Server, however, several hours after the action is completed, clients are reported as "Not checking in" in SUSE Manager Server until another action is scheduled against those clients.

Resolution

Set the value taskomatic.ssh_push_workers = 5 (or higher) into /etc/rhn/rhn.conf
Restart spacewalk-service: spacewalk-service restart

Cause

The taskomatic service is exhausted and maximum number of threads is already occupied. In /var/log/rhn/rhn_taskomatic_daemon.log following messages appear:

2023-06-30 15:32:00,160 [DefaultQuartzScheduler_Worker-17] INFO  com.redhat.rhn.taskomatic.task.ErrataCacheTask - In the queue: 1
2023-06-30 15:32:00,232 [DefaultQuartzScheduler_Worker-9] WARN  com.redhat.rhn.taskomatic.task.SSHPush - Maximum number of workers already put ... skipping.
2023-06-30 15:33:00,182 [DefaultQuartzScheduler_Worker-11] INFO  com.redhat.rhn.taskomatic.task.ErrataCacheTask - In the queue: 1
2023-06-30 15:33:00,242 [DefaultQuartzScheduler_Worker-1] WARN  com.redhat.rhn.taskomatic.task.SSHPush - Maximum number of workers already put ... skipping.
2023-06-30 15:34:00,036 [DefaultQuartzScheduler_Worker-13] WARN  com.redhat.rhn.taskomatic.task.SSHPush - Maximum number of workers already put ... skipping.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.