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
