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

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.

Related:

7015878: jabberd initialization fails with “db: couldn’t open environment: Resource temporarily unavailable”

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

Environment

SUSE Manager 3.0

SUSE Manager 2.1

SUSE Manager 1.7

Situation

When jabberd is attempting to start the following error can be seen in /var/log/messages and jabberd fails to load:

Nov 11 10:05:12 suma1 jabberd/sm[7216]: db: couldn’t open environment: Resource temporarily unavailable

Nov 11 10:05:12 suma1 jabberd/sm[7216]: initialisation of storage driver ‘db’ failed

Nov 11 10:05:12 suma1 jabberd/sm[7216]: failed to initialise one or more storage drivers, aborting

Nov 11 10:05:14 suma1 jabberd/c2s[7233]: db: couldn’t open environment: Resource temporarily unavailable

Nov 11 10:05:14 suma1 jabberd/c2s[7233]: failed to initialize auth module ‘db’

Resolution

This issue is caused by a corrupted jabberd database, which can be fixed by doing the following:

rcosa-dispatcher stop

rcjabberd stop

cd /var/lib/jabberd/db

rm *

rcjabberd start

rcosa-dispatcher start

After removing the database jabberd should start without issue.

Cause

jabberd database corruption can occur for many reasons, the most common cause is taskomatic running out of memory (see the following tid: https://www.suse.com/support/kb/doc.php?id=7012598 )

Additional Information

Note: This document is valid for SUSE Manager 1.7, 2.1 and 3.0 _only_!

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/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.

Related: