OSA Status of clients connected via a Proxy shows offline after a restart of the Satellite services

Solution Unverified - Updated -

Environment

  • Red Hat Satellite and Proxy 5.6

Issue

  • Situation
    • 1 Satellite
    • 2 proxies
    • 3 clients
    • 1 Client connected to proxy A
    • 2 clients connected to proxy B.
  • I scheduled a remote command in the Satellite GUI to the 3 clients. Works fine, actions picked up immediately.
  • I executed rhn-satellite restart. I scheduled a remote command in the Satellite GUI to the 3 clients. Result not OK, the actions are not picked up on any of the clients.
  • I executed rhn-proxy restart (only) on proxy A. I scheduled a remote command in the Satellite GUI to the 3 clients. Result partly OK, the one client connected to proxy A picked up the action immediately, the clients connected to proxy B still are not picking up actions.
  • I executed rhn-proxy restart on proxy B. I scheduled a remote command in the Satellite GUI to the 3 clients. Result OK, actions picked up immediately.

Resolution

  • Please upgrade to Satellite 5.7 which contains updated osa-dispatcher packages that resolves this issue.
  • For more information about the Satellite 5.7 release see the following errata: RHSA-2015:0033

Root Cause

  • Previously, automatic reconnection of the clients depended on jabberd's database however on Red Hat Satellite, the database is discarded upon restart to avoid possible corruption.
  • With the updated osa-dispatcher, clients will now be re-connected according to the state as present in the Satellite database rather than jabberd's database.

Diagnostic Steps

  • Restarting jabberd on the Proxy or osad on the client will resolve the issue, but there is no automatic way to recover. /var/log/messages on the Proxy show that the problem is that the s2s connection between the Proxy and Satellite is terminated:

    Jul 31 15:26:54 proxy jabberd/s2s[31379]: [9] [::ffff:192.168.1.47, port=43823] error: Stream error (s2s shutdown)
Jul 31 15:26:54 proxy jabberd/s2s[31379]: [9] [::ffff:192.168.1.47, port=43823] disconnect, packets: 8
Jul 31 15:26:54 proxy jabberd/s2s[31379]: [8] [192.168.1.47, port=5269] error: Stream error (s2s shutdown)
Jul 31 15:26:54 proxy jabberd/s2s[31379]: [8] [192.168.1.47, port=5269] disconnect, packets: 2

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments