[Spacewalk-list] OSAD clients offline as of unknown

Milan Zazrivec mzazrivec at redhat.com
Thu Jan 3 12:35:34 UTC 2013


> In /etc/rhn/rhn.conf I have
> 
> osa-dispatcher.jabber_server = yourspacewalk.example.org
> osa-dispatcher.osa_ssl_cert = /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT
> 
> but not:
> 
> osa-dispatcher.jabber_username =
> osa-dispatcher.jabber_password =

These two directives are not being used since Spacewalk 1.6 -- these two
values are not stored in your database.

> I never removed this so I'm not sure what happened there. So, I added those
> lines,  added my PostgreSQL account and restarted spacewalk.
> 
> Now I have some clients online which is a huge improvement!
> 
> I also have some that are still offline as of unknown and some that are
> just unknown. I assume I was correct to use the PostgreSQL account since a
> few clients are fixed now?
> 
> Now, I think my problem may be related to client config.  In osad.conf
> there is a section I only filled out on some of my clients:
> 
> # Use a different certificate from what up2date is using
> # This should point to the satellite certificate for
> # server_name
> osa_ssl_cert = /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
> 
> Does that have to be filled out? The way I read it is it's only if you want
> to use a certificate different than what's in the up2date config (from my
> bootstrap script) which I don't think I do.

Correct, this should not matter much, as long as the CA certificate in
/etc/sysconfig/rhn/up2date is setup correctly.

-MZ




More information about the Spacewalk-list mailing list