My Favorites

Close

Please to see your favorites.


osad unable to connect to jabber servers

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

Environment

SUSE Manager 1.7

Situation

osad on a SUSE Manager managed client system reports:
Starting osad: 2013-10-29 09:41:40 jabber_lib.main: Unable to connect to jabber servers, sleeping 120 seconds

Resolution

This error can have various reasons, for example:
  • Wrong DNS settings
  • Client is not able to connect to port 5222 on SUSE Manager
  • Client registration not valid even zypper ca output shows channels pointing to SUSE Manager


Wrong DNS settings

Please check the settings in /etc/resolv.conf if the nameserver entry points to a valid IP address. Use tools like host, nslookup or dig to verify DNS resolution of hostnames.


Client not able to connect to port 5222

Check if the server accepts connections on port 5222:

telnet IP-of-SUSE-Manager <port>

for example:

telnet 192.168.20.35 5222

Please adjust the above mentioned IP accordingly.


Outdated registration

Check if the client can retrieve patch information from the server using the zypper patch command. If an error like:

linux:~ # zypper patch
Refreshing service 'spacewalk'.
Problem retrieving the repository index file for service 'spacewalk':
[|] Error communicating with server. The message was:

Error Message:
    Please run rhn_register as root on this client
Error Class Code: 9
Error Class Info: Invalid System Credentials.
Explanation:
     An error has occurred while processing your request. If this problem
     persists please enter a bug report at bugzilla.novell.com.
     If you choose to submit the bug report, please be sure to include
     details of what you were trying to do when this error occurred and
     details on how to reproduce this problem.


Skipping service 'spacewalk' because of the above error.
Loading repository data...
Reading installed packages...
Resolving package dependencies...

appears register the client again, e.g. by re-running the bootstrap script.

Additional Information

To run osad in the foreground please follow these steps:
  • rcosad stop
  • /usr/sbin/osad -N -v -v -v -v

Additionally a TCP trace from the client may reveal more information about connection issues, to accomplish run as root:

tcpdump -i <eth> -s 0 -w filename

e.g.

tcpdump -i eth0 -s 0 -w /tmp/tcpdump.pcap

Finish the tcpdump by pressing CTRL+c, a convenient way to review the data is by loading the file into Wireshark.

osad configuration files:

  • /etc/sysconfig/rhn/osad.conf
  • /etc/sysconfig/rhn/up2date

Log file:

  • /var/log/osad

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.

  • Document ID:7014012
  • Creation Date:29-OCT-13
  • Modified Date:30-OCT-13
    • SUSESUSE Manager

Did this document solve your problem? Provide Feedback