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 = 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. From: [email protected] [mailto:[email protected]] On Behalf Of William Muriithi Sent: Monday, December 31, 2012 6:26 PM To: [email protected] Subject: [Spacewalk-list] OSAD clients offline as of unknown >I was wondering if anyone could give me a hand on this. All my clients are >listed as OSA Status: offline as of unknown. They ping fine (OSA Status shows >Last pinged: 12/28/12 2:41:48 PM EST for example). > > Client: > $ sudo service osad status > osad (pid 31798) is running... > > Server: > $ sudo service osa-dispatcher status > osa-dispatcher (pid 19217) is running... > > $ sudo less /var/log/rhn/osa-dispatcher.log > 2012/12/21 16:03:58 -04:00 5269 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.setup_connection('Connected to jabber server', > 'servername.fqdn.com<http://servername.fqdn.com>') > 2012/12/21 16:03:58 -04:00 5269 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.register('ERROR', 'Invalid password') Please check you have the proper password on the osad configuration file. Jabber don't seem to like the current one > 2012/12/21 16:07:34 -04:00 6719 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.__init__ > 2012/12/21 16:07:34 -04:00 6719 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.setup_connection('Connected to jabber server', > 'servername.fqdn.com<http://servername.fqdn.com>') > 2012/12/21 16:07:34 -04:00 6719 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.register('ERROR', 'Invalid password') > 2012/12/21 16:16:59 -04:00 9748 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.__init__ > 2012/12/21 16:16:59 -04:00 9748 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.setup_connection('Connected to jabber server', > 'servername.fqdn.com<http://servername.fqdn.com>') > 2012/12/21 16:16:59 -04:00 9748 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.register('ERROR', 'Invalid password') > 2012/12/28 14:13:12 -04:00 15804 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.__init__ > 2012/12/28 14:13:12 -04:00 15804 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.setup_connection('Connected to jabber server', > 'servername.fqdn.com<http://servername.fqdn.com>') > 2012/12/28 14:13:12 -04:00 15804 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.register('ERROR', 'Invalid password') > 2012/12/28 14:31:55 -04:00 19215 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.__init__ > 2012/12/28 14:31:55 -04:00 19215 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.setup_connection('Connected to jabber server', > 'servername.fqdn.com<http://servername.fqdn.com>') > 2012/12/28 14:31:56 -04:00 19215 0.0.0.0<http://0.0.0.0>: > osad/osa_dispatcher.fix_connection('Upstream notification server started on > port', 1290) > 2012/12/28 14:31:56 -04:00 19215 0.0.0.0<http://0.0.0.0>: > osad/jabber_lib.process_forever > > I found this online and already tried it, no luck: > service jabberd stop > service osa-dispatcher stop > rm -f /var/lib/jabberd/db/* > service jabberd start > sleep 10 > service osa-dispatcher start > > sudo netstat -an | grep 5222 on the server shows ESTABLISHED connections from > clients. I also have the ports in my iptables script needed for > this(5222,5269 I think it was) but to troubleshoot this I created a rule on > the server to allow all traffic to one of my clients for troubleshooting. > > $IPTbls -A INPUT -i $PUBLIC -p all -s $IPADDRESS -j ACCEPT > $IPTbls -A OUTPUT -o $PUBLIC -p all -d $IPADDRESS -j ACCEPT > > Any advice is much appreciated. Thanks! > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <https://www.redhat.com/archives/spacewalk-list/attachments/20121231/86c06f1c/attachment.html> > > ------------------------------ > > _______________________________________________ > Spacewalk-list mailing list > [email protected]<mailto:[email protected]> > https://www.redhat.com/mailman/listinfo/spacewalk-list > > End of Spacewalk-list Digest, Vol 55, Issue 58 > **********************************************
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
