On the client side: Typically, you should only have to change the following variable in /etc/sysconfig/rhn/osad.conf: osa_ssl_cert = /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
You could grep for 'Subject' in the cert file above and make sure that the hostname matches the serverURL in up2date. For example, grep Subject /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT Subject: C=US, ST=XX, L=Locality, O=Work, OU=Place, CN=spacewalk.example.com I usually don't have to change any variables in /etc/sysconfig/rhn/up2date, but two that I double-check are: sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT serverURL=https://spacewalk.example.com/XMLRPC I ran into this issue because I registered a machine with rhn_ks with the short hostname in --server instead of the FQDN. That caused the serverURL to show up as "serverURL=https://spacewalk/XMLRPC";. The system will register successfully, but OSAD will cry and fail to start, typically with an SSLDisabledError or something to that effect. On the server side: The jabber config files are on the server side. I usually don't touch these files either, because if it breaks, I probably won't know how to fix it. I just check to make sure that the <id> tag also has a matching FQDN hostname as above. The files are /etc/jabberd/c2s.xml and sm.xml. Date: Fri, 12 Oct 2012 09:44:25 -0700 From: [email protected] To: [email protected] Subject: Re: [Spacewalk-list] OSA Status: offline as of unknown Thanks, Giovanni. What are the entries containing hostname in osad.conf, up2date conf file, and jabber config files? Where is the jabber config file? Can you give me some details? Thank you! nz From: Giovanni Torres <[email protected]> To: "[email protected]" <[email protected]> Sent: Friday, October 12, 2012 11:43:59 AM Subject: Re: [Spacewalk-list] OSA Status: offline as of unknown Apparently, jabber is very particular about its ssl configuration. you have to make sure that the hostname in the ssl cert configured in osad.conf matches what is in the up2date conf file. things also need to match up the jabber config files. See here: https://fedorahosted.org/spacewalk/wiki/OsadHowTo If the status says online but unknown, try deleting or renaming the osad-auth.conf file and restart osad on the client. it will regenerate new credentials. Try to "Ping System" again through the Web UI and see if that helps. Date: Fri, 12 Oct 2012 08:26:41 -0700 From: [email protected] To: [email protected] Subject: [Spacewalk-list] OSA Status: offline as of unknown Hi, Why is the System page in Spacewalk server GUI showing 'OSA Status: offline as of unknown' while osad from the client is connected to the server? spwclient# osad status -v 2012-10-12 11:15:58 jabber_lib.__init__: 2012-10-12 11:15:58 jabber_lib.setup_connection: Connected to jabber server spwserver.mydomain.com There is one client shown as 'OSA Status: online as of unknown'. The rest of the clients are all shown as 'OSA Status: offline as of unknown'. I don't see any special for this 'online' client. Thank you! nz _______________________________________________ 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 _______________________________________________ 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
