$ rpm -q osa-dispatcher osa-dispatcher-5.11.10-1.el6.noarch When I added: > osa-dispatcher.jabber_username = pqsql username > osa-dispatcher.jabber_password = pqsql password
It fixed my osad problem on half my clients. The other half was missing server_name osa_ssl_cert = /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT in osad.conf. Adding it brought them online. But according to your last e-mail neither of these should matter right? What would be wrong? Before in psql running: select jabber_id, password from rhnPushDispatcher; returned 0 fields. After adding username and password to osad.conf now it returns 1 row: ([email protected]/superclient | encrypted password) and no more 'Invalid password' in osa-dispatcher.log Is something wrong here? I'm running spacewalk 1.8 upgraded from 1.7. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Milan Zazrivec Sent: Thursday, January 03, 2013 7:36 AM To: [email protected] Subject: Re: [Spacewalk-list] OSAD clients offline as of unknown > 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 _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
