Description of problem:
Osad stop working when client is registered for the second time
Version-Release number of selected component (if applicable):
sat530 or sat540
this is not regression
Steps to Reproduce:
1. register client into satellite
2. start osad, make sure it works, it create some log in auth info in /etc/sysconfig/rhn/osad-auth.conf
3. register again the same client into same satellite
4. restart osad or wait
osad is not working
2010-12-20 07:22:54 osad_client._check_signature: Signatures do not match 250d3751e67a9bd1714838487103aff38143bf26 264cbfff622762737a03513ad72d0116dc53ce38
2010-12-20 07:22:54 jabber_lib.main: Sleeping 107 seconds
/etc/init.d/osad restart should regenerated auth info by deleting osad-auth.conf.
osad takes auth info from /etc/sysconfig/rhn/osad-auth.conf
When I delete this file + osad restart then it starts working
or it could write some info message about removing/checking osad-auth.conf in log file
Indeed, we are seeing the same thing at another client site that is using RHN Satellite 5.4.1. Deleting the /etc/sysconfig/rhn/osad-auth.conf file worked.
Problem has been addressed in Spacewalk in bug #590608
This issue is resolved with the release of RHN Satellite 5.5.
As of September 20th 2012, RHN Satellite 5.5 has been generally available.
Release Notes and other 5.5 documentation can be found here:
The associated Errata for the 5.5 release are:
5.5 Satellite GA Errata
5.5 Upgrade Errata
5.5 RHN Proxy GA Errata
5.5 RHN Tools GA Errata
- Engineering Manager, Satellite