Despite the downgrade recommendations, I gave this a shot anyways on CentOS 6.3 with Cobbler 2.2. I ran the `spacewalk-hostname-rename <ip>` and got the following: "Changing cobbler settings... FAILED". I manually edited /etc/cobbler/settings to change the hostname parameter, which needs to be changed in multiple places in this file. Then, I commented out the following in /usr/bin/spacewalk-hostname-rename: #echo -n "Changing cobbler settings ..." | tee -a $LOG## --enabled tftp=no means, everything stayes configured from previous configuration#/usr/bin/cobbler-setup --enable-tftp=no >> $LOG 2>&1#print_status $? This portion of the script will always fail as it is ultimately looks for cobbler templates in /usr/share/cobbler/ which does not exist (at least not with cobbler 2.2; perhaps this was the case with cobbler 2.0) The rename script finished successfully and all the spacewalk services start without issues, including cobbler and osa-dispatcher.
Date: Thu, 30 Aug 2012 06:55:34 -0700 From: [email protected] To: [email protected]; [email protected] Subject: Re: [Spacewalk-list] FQDN can't solve 'Unable to connect to jabber servers' The cobbler version is 2.2.3. This spacewalk-hostname-rename issue is not solved yet. I had to give it up finally to save time. After manually replaced all hostname with its FQDN in files under /etc/jabberd, osa-dispatcher starts working. At least the client was upgraded successfully. Thanks! nz From: Jan Hutař <[email protected]> To: [email protected]; [email protected] Cc: [email protected]; Paul Robert Marino <[email protected]>; "[email protected]" <[email protected]> Sent: Thursday, August 30, 2012 12:25:22 AM Subject: Re: [Spacewalk-list] FQDN can't solve 'Unable to connect to jabber servers' On Thu, 23 Aug 2012 12:36:06 -0700 (PDT) [email protected] wrote: > One issue is gone and another issue is coming right away - > this is our life :( :) > > # spacewalk-hostname-rename 192.168.10.99 > ...... > Validating IP ... OK > ============================================= > hostname: spacewalkhost.ourdomain.com > ip: 192.168.10.99 > ============================================= > Stopping rhn-satellite services ... OK > Testing DB connection ... psql:<stdin>:1: ERROR: syntax error > at or near "off" LINE 1: set feed off; > Updating /etc/rhn/rhn.conf ... OK > Actual SSL key pair package: > rhn-org-httpd-ssl-key-pair-spacewalkhost.ourdomain-1.0-1.noarch > Starting generation of new SSL certificate: Generating SSL > certificate: Removing old SSL certificate > (rhn-org-httpd-ssl-key-pair-spacewalkhost.ourdomain-1.0-1.noarch) ... > OK Installing new SSL certificate > (rhn-org-httpd-ssl-key-pair-spacewalkhost.ourdomain-1.0-2.noarch.rpm) ... > OK Deploying jabberd certificate ... OK Regenerating new > bootstrap client-config-overrides.txt ... OK Updating > NOCpulse.ini ... OK Updating monitoring data ... OK Updating > other DB entries ... OK Changing cobbler settings ... FAILED > Fix the problem and run /usr/bin/spacewalk-hostname-rename > again > > # tail /var/log/rhn/rhn_hostname_rename.log: > Changing cobbler settings ... Traceback (most recent call > last): File "/usr/bin/cobbler-setup", line 78, in <module> > main() > File "/usr/bin/cobbler-setup", line 55, in main > answers = dict(loadFile(DEFAULTS)) > File "/usr/bin/cobbler-setup", line 26, in loadFile > return load(open(fl).read()) > IOError: [Errno 2] No such file or directory: > '/usr/share/cobbler/installer_templates/defaults' FAILED This is strange. Which version of cobbler package you have? Regards, Jan > # service cobblerd status > cobblerd is stopped > > # service cobblerd start > Starting cobbler daemon: [ > OK ] > > # service cobblerd status > cobblerd (pid 12373) is running... > > Please help. Thanks. > > > nz > > > > ________________________________ > From: "[email protected]" <[email protected]> > To: "[email protected]" <[email protected]>; Paul Robert Marino > <[email protected]>; "[email protected]" > <[email protected]>; "[email protected]" > <[email protected]> Sent: Thursday, August 23, 2012 > 2:19:06 PM Subject: Re: [Spacewalk-list] FQDN can't solve > 'Unable to connect to jabber servers' > > This issue is fixed by using > > # patch /usr/bin/spacewalk-hostname-rename > /root/spacewalk-hostname-rename_patch > # (the codes in > # https://bugzilla.redhat.com/show_bug.cgi?id=809444) > > > nz > > > > ________________________________ > From: "[email protected]" <[email protected]> > To: Paul Robert Marino <[email protected]>; > "[email protected]" <[email protected]> Sent: > Thursday, August 23, 2012 1:44:56 PM Subject: Re: > [Spacewalk-list] FQDN can't solve 'Unable to connect to jabber > servers' > > Paul, > > I've found the issue and answer in the link you > provided:https://bugzilla.redhat.com/show_bug.cgi?id=809444 I > am studying your answer now. I don't quite understand it. > > > nz > > > > ________________________________ > From: Paul Robert Marino <[email protected]> > To: [email protected]; [email protected] > Sent: Thursday, August 23, 2012 11:03:28 AM > Subject: Re: [Spacewalk-list] FQDN can't solve 'Unable to > connect to jabber servers' > On Thu, Aug 23, 2012 at 10:29 AM, <[email protected]> wrote: > > Hi, I've got a tough issue - Unable to connect to jabber > > servers > > > > # service osa-dispatcher start > > Starting osa-dispatcher: RHN 32080 2012/08/23 09:58:53 > > -04:00: ('Not > able to > > reconnect',) > > RHN 32080 2012/08/23 09:58:53 -04:00: ('Traceback (most > > recent call last):\n File > > "/usr/share/rhn/osad/jabber_lib.py", line 252, in > > setup_connection\n c = self._get_jabber_client(js)\n File > > "/usr/share/rhn/osad/jabber_lib.py", line 309, in > > _get_jabber_client\n c.connect()\n File > > "/usr/share/rhn/osad/jabber_lib.py", line 589, in connect\n > > raise SSLDisabledError\nSSLDisabledError\n',) [ OK ] > > > > I've changed all spacewalk server's hostname with its FQDN > > in all config files I can found: > > > > # grep osa /etc/rhn/rhn.conf > > osa-dispatcher.jabber_server = spacewalkhost.ourdomain.com > > osa-dispatcher.jabber_username = rhn-dispatcher-sat > > osa-dispatcher.jabber_password = rhn-dispatcher-RANDOM_STRING > > osa-dispatcher.osa_ssl_cert = > /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT > > > > # grep spacewalkhost /etc/jabberd/* > > /etc/jabberd/c2s.xml: <id require-starttls="false" > > pemfile="/etc/pki/spacewalk/jabberd/server.pem" realm="" > > register-enable="true">spacewalkhost.ourdomain.com</id> > > /etc/jabberd/server.pem:8ZHSDZRzaSm7bNl2l8om83QrPMG/WDJh40PANPh/b60asdvSb5uwpb6dc4rxxxxx > > /etc/jabberd/sm.xml: <id>spacewalkhost.ourdomain.com</id> > > /etc/jabberd/sm.xml: <id>spacewalkhost.ourdomain.com</id> > > > > # grep > > # spacewalkhost /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT > > Issuer: C=US, ST=..., L=..., O=..., > >OU=spacewalkhost.ourdomain.com, > > CN=spacewalkhost.ourdomain.com > > Subject: C=US, ST=..., L=..., O=..., > >OU=spacewalkhost.ourdomain.com, > > CN=spacewalkhost.ourdomain.com > > > > > > DirName:/C=US/ST=.../L=.../O=.../OU=spacewalkhost.ourdomain.com/CN=spacewalkhost.ourdomain.com > > > > # tail /var/log/rhn/osa-dispatcher.log > > 2012/08/23 10:17:16 -04:00 32080 0.0.0.0: > > osad/jabber_lib.__init__ 2012/08/23 10:17:16 -04:00 32080 > > 0.0.0.0: osad/jabber_lib.connect('Server did not return a > > <features /> stanza, reconnecting',) 2012/08/23 10:17:17 > > -04:00 32080 0.0.0.0: osad/jabber_lib.connect('Server did > > not return a <features /> stanza, reconnecting',) 2012/08/23 > > 10:17:18 -04:00 32080 0.0.0.0: osad/jabber_lib.connect > > ('Server did not return a <features /> stanza, > > reconnecting',) 2012/08/23 10:17:19 -04:00 32080 0.0.0.0: > > osad/jabber_lib.connect('ERROR', 'Not able to reconnect') > > 2012/08/23 10:17:19 -04:00 32080 0.0.0.0: > > osad/jabber_lib.print_message('SSLError',) 2012/08/23 > > 10:17:19 -04:00 32080 0.0.0.0: > > > osad/jabber_lib.print_message('Could not connect to jabber > server', > > 'spacewalkhost.ourdomain.com') > > 2012/08/23 10:17:19 -04:00 32080 0.0.0.0: > > osad/jabber_lib.setup_connection('ERROR', 'Traceback (most > > recent call last):\n File > > "/usr/share/rhn/osad/jabber_lib.py", line 252, in > > setup_connection\n c = self._get_jabber_client(js)\n > > File "/usr/share/rhn/osad/jabber_lib.py", line 309, in > > _get_jabber_client\n c.connect()\n File > > "/usr/share/rhn/osad/jabber_lib.py", line 589, in connect\n > > raise SSLDisabledError\nSSLDisabledError\n') 2012/08/23 > > 10:17:19 -04:00 32080 0.0.0.0: > > osad/jabber_lib.setup_connection('Could not connect to any > > jabber server',) 2012/08/23 10:17:19 -04:00 32080 0.0.0.0: > > osad/jabber_lib.main('Unable to connect to jabber servers, > > sleeping 10 seconds',) > > > > # tail /var/log/messages > > Aug 23 > 10:20:46 spacewalkhost jabberd/c2s[15904]: [7] > [::ffff:192.168.10.99, > > port=48416] connect > > Aug 23 10:20:46 spacewalkhost jabberd/c2s[15904]: [7] > > [::ffff:192.168.10.99, port=48416] disconnect jid=unbound, > > packets: 0 Aug 23 10:20:47 spacewalkhost jabberd/c2s[15904]: > > [7] [::ffff:192.168.10.99, port=48417] connect > > Aug 23 10:20:47 spacewalkhost jabberd/c2s[15904]: [7] > > [::ffff:192.168.10.99, port=48417] disconnect jid=unbound, > > packets: 0 Aug 23 10:20:58 spacewalkhost jabberd/c2s[15904]: > > [7] [::ffff:192.168.10.99, port=48418] connect > > Aug 23 10:20:58 spacewalkhost jabberd/c2s[15904]: [7] > > [::ffff:192.168.10.99, port=48418] disconnect jid=unbound, > > packets: 0 Aug 23 10:20:59 spacewalkhost jabberd/c2s[15904]: > > [7] [::ffff:192.168.10.99, port=48419] connect > > Aug 23 10:20:59 spacewalkhost jabberd/c2s[15904]: [7] > > [::ffff:192.168.10.99, port=48419] > disconnect jid=unbound, packets: 0 > > Aug 23 10:21:00 spacewalkhost jabberd/c2s[15904]: [7] > > [::ffff:192.168.10.99, port=48425] connect > > Aug 23 10:21:00 spacewalkhost jabberd/c2s[15904]: [7] > > [::ffff:192.168.10.99, port=48425] disconnect jid=unbound, > > packets: 0 > > > > Why does the spacewalk server's hostname rather than its > > FQDN display in messages? What do I still miss? Please help > > and thank you in advance! > in answer to the log question Thats because its syslog or > rsyslog writing that log file and thats how its configured by > default > > Also there is more to renaming the host than altering a few > config files there is actually a tool for this > The current version of the tool has a bug with PostgreSQL but > if you download the latest version from the git repo it should > work. see the bug report here > https://bugzilla.redhat.com/show_bug.cgi?id=809444 > > > > > Nick > > > > _______________________________________________ > > 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 -- Jan Hutar Systems Management QA [email protected] Red Hat, Inc. _______________________________________________ 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
