Sander, this is excellent inforamtion and advice, thank you.
I've now found the spacewalk rename trac page https://fedorahosted.org/spacewalk/wiki/SpacewalkHostnameRename which is very useful. I'm now having a problem in that when I try to run the spacewalk-hostname-rename script it's complaining that the Oracle instance isn't running/listening. Which is it. [root@spacewalk01 ~]# spacewalk-hostname-rename 80.86.39.112 Validating IP ... OK ============================================= hostname: spacewalk01.sccis.net ip: 80.86.39.112 ============================================= Stopping rhn-satellite services ... OK Testing DB connection ... ERROR: ORA-12541: TNS:no listener SP2-0306: Invalid option. Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM}] [edition=value]] where <logon> ::= <username>[/<password>][@<connect_identifier>] <proxy> ::= <proxyuser>[<username>][/<password>][@<connect_identifier>] SP2-0306: Invalid option. Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM}] [edition=value]] where <logon> ::= <username>[/<password>][@<connect_identifier>] <proxy> ::= <proxyuser>[<username>][/<password>][@<connect_identifier>] SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus FAILED Your database isn't running. Fix the problem and run /usr/bin/spacewalk-hostname-rename again the line that worries me here is the "SP2-0306 invalid option" My Oracle configuration hasn't changed, is there something obvious I'm missing ? thanks, Matt. ________________________________________ From: [email protected] [[email protected]] on behalf of Sander Grendelman [[email protected]] Sent: 24 May 2011 16:14 To: [email protected] Subject: Re: [Spacewalk-list] clients can't register - ssl cert problem > > When I do a rhn_register on a client I get told it's failed and I should look > in the up2date log. > > The up2date log shows a large python backtrace ... > 15. > up2date_client.up2dateErrors.SSLCertificateVerifyFailedError: The SSL > certificate /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT failed verification. > > if I look in /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT on the CLIENT machine > the certificate is exactly the same as the one on the spacewalk machine > > > > [root@spacewalk01 auth]# ls -la /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT > -rw-r--r-- 1 root root 5467 May 24 11:23 > /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT > > [root@vmbuild01 rhn]# ls -la RHN-ORG-TRUSTED-SSL-CERT > -rw-r--r-- 1 root root 5467 May 24 11:29 RHN-ORG-TRUSTED-SSL-CERT * Are the md5sums also the same? * Where did you get this SSL cert from? Did you install the rpm from your SW-server? (/var/www/html/pub/rhn-org-trusted-ssl-cert*noarch.rpm ? > > any suggestions as to what would cause this would be most welcome as I had a > working spacewalk machine and I can't figure out what I've done to break this. You've changed the hostname ;) NB: there's also a special script for hostname changes: [root@mir ~]# rpm -qf $(which spacewalk-hostname-rename) spacewalk-utils-1.2.9-1.el5 [root@mir ~]# Kind regards, Sander. _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
