OSAD clients not taking actions immediately after a migration or upgrade in SUSE Manager

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

Environment

SUSE Manager 3

Situation

Tasks sent via OSAD (either patching or custom scripts) used to be executed immediately. After a migration from SUSE Manager 2.1 to 3.0 or 3.1 (which is done into a new machine), or also as a result of an upgrade from 3.0 to 3.1 (which is done in the same machine), task are not run as fast as they used to. Typically it could take those tasks up to the 4 hours timeout of OSAD to be finally executed.

Resolution

In the SUSE Manager Server, the jabberd DB should be recreated:

# spacewalk-service stop
# rm -Rf /var/lib/jabberd/db/*
# spacewalk-service start

The same applies for the proxies:

# spacewalk-proxy stop
# rm -Rf /var/lib/jabberd/db/*
# spacewalk-proxy start

In the clients, the osad-auth.conf file should be deleted:

# rcosad stop
# rm -f /etc/sysconfig/rhn/osad-auth.conf
# rcosad start

Obviously this step can be automated through SUSE Manager, specially in the case of having several clients. The task will be eventually run after a maximum of 4 hours. It can also be forced by running the following in the client:

# rhn_check

However, this requires logging into every client.

Cause

Corruption in jabberd DB

Additional Information

More information in the SUSE Manager WIKI:
https://wiki.microfocus.com/index.php/SUSE_Manager/Osad_and_jabberd_troubleshooting

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.