This happens to me A LOT. Here's the top reasons I found this fails for me:
First and foremost:
Verify that jabberd + osa-dispatcher are running on the server
and are configured to start on boot.
Verify that osad is running on all the clients and is
configured to start on boot.
If NONE of the clients are getting updates:
Check the osa-dispatcher logs on the server, make sure it can authenticate with
the Jabber server. If it can't you need to reset the auto-generated jabber
auth:
stop osa-dispatcher + jabber
rm -r /var/lib/jabberd/db/*
restart everything - should work now.
Individual clients are not receiving updates:
Stop osad on the client servers
rm the osad auth file (usually /etc/sysconfig/rhn/osad-auth.conf)
Restart osad.
Wait a few minutes, see if your updates come through.
One last reason some clients are not receiving updates:
In my shop we do a lot of VM cloning. When this happens the
freshly cloned VMs have the same auth files as the clone source. We have to
make sure that the local osad-auth file on one or both of the VMs involved are
removed and osad restarted. Otherwise, the osa-dispatcher/jabber setup will
end up seeing the same credentials from two different sources and will only
accept one of them.
From: [email protected]
[mailto:[email protected]] On Behalf Of Nick Kitmitto
Sent: Friday, June 06, 2014 4:24 AM
To: [email protected]
Subject: [Spacewalk-list] OSAD Issues
I'm having issues with a few of my RHEL 6 servers. Some work, some don't, some
reporting to the same proxy work but 3 don't. OSAD is started, when I run osad
-N -v -v -v -v it checks in and gets the tasks I have for it. When I do an
rhn_check it works as well. However, it doesn't actually check in by itself (I
gave it an hour to check in and it didn't). Any idea as to why these 3 servers
aren't checking in automatically when OSAD is running and can communicate with
the proxy server?
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
