Problems with osa-dispatcher/osad/push infrastructure in a multi-node active-passive / highly-available Satellite setup

Solution Verified - Updated -

Issue

  • When starting the osa-dispatcher service, the follow error is returned:
[root@satnode2 ~]# /etc/init.d/osa-dispatcher restart
Shutting down osa-dispatcher:                              [FAILED]
Starting osa-dispatcher: RHN 26931 2012/10/26 11:22:35 -04:00: ('Traceback caught:',)
RHN 26931 2012/10/26 11:22:35 -04:00: ('Traceback (most recent call last):\n  File "/usr/share/rhn/osad/jabber_lib.py", line 621, in connect\n    self.verify_peer(ssl)\n  File "/usr/share/rhn/osad/jabber_lib.py", line 701, in verify_peer\n    raise SSLVerifyError("Mismatch: peer name: %s; common name: %s" %\nSSLVerifyError: Mismatch: peer name: satnode2.example.com; common name: satnode1.example.com.\n',)
  • Another problem is that osad clients are not picking up scheduled actions. The client side osad log had the following errors:
2012-04-29 08:14:11 jabber_lib.check_cert: Loading cert <X509Name object '/C=US/ST=California/L=Los Angeles/O=Example Inc./OU=IT/CN=satellite.example.com'>
2012-04-29 08:14:11 jabber_lib.connect: 
2012-04-29 08:14:11 jabber_lib.connect: Attempting to connect
2012-04-29 08:14:11 jabber_lib.print_message: socket error
2012-04-29 08:14:11 jabber_lib.print_message: Could not connect to jabber server satellite.example.com
2012-04-29 08:14:11 jabber_lib.setup_connection: Could not connect to any jabber server
2012-04-29 08:14:11 jabber_lib.main: Unable to connect to jabber servers, sleeping 113 seconds

Environment

  • Multiple Red Hat Network Satellite hosts in an active-passive / highly-available setup

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.