Bug 1078649 - jabber_lib.main: Unable to connect to jabber servers
Summary: jabber_lib.main: Unable to connect to jabber servers
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Spacewalk
Classification: Community
Component: Clients
Version: 2.0
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space27
TreeView+ depends on / blocked
 
Reported: 2014-03-20 05:55 UTC by hrcr2012
Modified: 2017-09-28 18:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-04 12:04:42 UTC
Embargoed:


Attachments (Terms of Use)
c2s configuration file (21.81 KB, text/xml)
2014-03-26 11:40 UTC, hrcr2012
no flags Details
s2s configuration file (10.83 KB, text/xml)
2014-03-26 11:41 UTC, hrcr2012
no flags Details
sm configuration file (28.93 KB, text/xml)
2014-03-26 11:42 UTC, hrcr2012
no flags Details
router configuration file (6.58 KB, text/xml)
2014-03-26 11:44 UTC, hrcr2012
no flags Details
osad configuration file on client (1.79 KB, text/plain)
2014-03-26 11:51 UTC, hrcr2012
no flags Details
up2date file on client (2.01 KB, text/plain)
2014-03-26 11:53 UTC, hrcr2012
no flags Details

Description hrcr2012 2014-03-20 05:55:37 UTC
Description of problem:

 
On spacewalk server, jabberd and osa-dispatcher are started , just fine. Following:

[root@spacewalk jabberd]# service postgresql status
postmaster (pid  2383) is running...
[root@spacewalk ~]# service jabberd status
router (pid 2516) is running...
sm (pid 2523) is running...
c2s (pid 2530) is running...
s2s (pid 2538) is running...
[root@spacewalk ~]# service osa-dispatcher status
osa-dispatcher (pid  2607) is running...

On /var/log/rhn/osa-dispatcher.log, filled with :
......
2014/03/19 09:01:55 +08:00 2601 0.0.0.0: osad/jabber_lib.__init__
2014/03/19 09:01:55 +08:00 2601 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', 'spacewalk.cs2c.com.cn')
2014/03/19 09:01:55 +08:00 2601 0.0.0.0: osad/osa_dispatcher.fix_connection('Upstream notification server started on port', 1290)
2014/03/19 09:01:55 +08:00 2601 0.0.0.0: osad/jabber_lib.process_forever
2014/03/20 09:03:46 +08:00 2605 0.0.0.0: osad/jabber_lib.__init__
2014/03/20 09:03:46 +08:00 2605 0.0.0.0: osad/jabber_lib.setup_connection('Connected to jabber server', 'spacewalk.cs2c.com.cn')
2014/03/20 09:03:47 +08:00 2605 0.0.0.0: osad/osa_dispatcher.fix_connection('Upstream notification server started on port', 1290)
2014/03/20 09:03:47 +08:00 2605 0.0.0.0: osad/jabber_lib.process_forever
......

Executing spacewalk-hostname-rename 10.1.81.45 ( 10.1.81.45 is spacewalk server IP.)command, It's OK. Following:

[root@spacewalk jabberd]# spacewalk-hostname-rename 10.1.81.45
Validating IP ... OK
=============================================
hostname: spacewalk.cs2c.com.cn
ip: 10.1.81.45
=============================================
Stopping rhn-satellite services ... OK
Testing DB connection ... OK
Updating /etc/rhn/rhn.conf ... OK
Actual SSL key pair package: rhn-org-httpd-ssl-key-pair-spacewalk.cs2c-1.0-7.noarch
 No need to re-generate SSL certificate.
Regenerating new bootstrap client-config-overrides.txt ... OK
Updating NOCpulse.ini ... OK
Updating monitoring data ... OK
Updating other DB entries ... OK
Changing cobbler settings ... OK
Changing jabberd settings ... OK
Starting rhn-satellite services ... OK

But, Executing service osad start on spacewalk client is failed.
Following:

[root@ns64b05 ~]# service osad start
Starting osad: 
2014-03-20 12:06:27 jabber_lib.main: Unable to connect to jabber servers, sleeping 67 seconds
                                                           [  OK  ]

Version-Release number of selected component (if applicable):
spacewalk 2.0.3

jabberd-2.2.14-5.el6.x86_64
spacewalk-setup-jabberd-2.0.1-1.el6.noarch

osa-dispatcher-selinux-5.11.27-1.el6.noarch
osa-dispatcher-5.11.27-1.el6.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
On spacewalk client executing service osad start is failed with " jabber_lib.main: Unable to connect to jabber servers, sleeping 67 seconds"

Expected results:
On spacewalk client executing service osad start is OK.

Additional info:

Comment 1 hrcr2012 2014-03-20 07:46:28 UTC
How reproducible:

On spacewalk client, executing "service osad start".

Steps to Reproduce:
1.On spacewalk client, executing "service osad start".
2.
3.

Comment 2 hrcr2012 2014-03-21 00:55:33 UTC
How reproducible:

Always

Steps to Reproduce:
1.On spacewalk client, executing "service osad start".
2.
3.

Comment 3 Milan Zázrivec 2014-03-21 09:10:19 UTC
The error you're showing means that either the c2s process (part of
jabberd service) is not running or you did not configure your
clients correctly.

It seems you renamed your Spacewalk server, which means you should also
update /etc/sysconfig/rhn/up2date on your registered clients.

Either way, this is not a bug, just an error message telling osad
cannot connect to the server.

Comment 4 hrcr2012 2014-03-26 11:40:08 UTC
Created attachment 878959 [details]
c2s configuration file

Comment 5 hrcr2012 2014-03-26 11:41:38 UTC
Created attachment 878961 [details]
s2s configuration file

Comment 6 hrcr2012 2014-03-26 11:42:55 UTC
Created attachment 878962 [details]
sm configuration file

Comment 7 hrcr2012 2014-03-26 11:44:59 UTC
Created attachment 878963 [details]
router configuration file

Comment 8 hrcr2012 2014-03-26 11:51:57 UTC
Created attachment 878965 [details]
osad configuration file on client

Comment 9 hrcr2012 2014-03-26 11:53:43 UTC
Created attachment 878966 [details]
up2date file on client

Comment 10 hrcr2012 2014-03-26 12:07:57 UTC
On spacewalk server, /var/log/messages content following as:
......
Mar 26 19:42:53 spacewalk jabberd/router[2497]: starting up
Mar 26 19:42:53 spacewalk jabberd/router[2497]: process id is 2497, written to /var/lib/jabberd/pid/router.pid
Mar 26 19:42:53 spacewalk jabberd/router[2497]: loaded user table (1 users)
Mar 26 19:42:53 spacewalk jabberd/router[2497]: loaded filters (0 rules)
Mar 26 19:42:53 spacewalk jabberd/router[2497]: [::1, port=5347] listening for incoming connections
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: starting up
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: process id is 2504, written to /var/lib/jabberd/pid/sm.pid
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: loading 'db' storage module
Mar 26 19:42:53 spacewalk jabberd/c2s[2511]: starting up
Mar 26 19:42:53 spacewalk jabberd/c2s[2511]: process id is 2511, written to /var/lib/jabberd/pid/c2s.pid
Mar 26 19:42:53 spacewalk jabberd/c2s[2511]: modules search path: /usr/lib64/jabberd
Mar 26 19:42:53 spacewalk jabberd/c2s[2511]: loading 'db' authreg module
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: initialised storage driver 'db'
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: modules search path: /usr/lib64/jabberd
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'status' added to chain 'sess-start' (order 0 index 0 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'status' added to chain 'sess-end' (order 0 index 0 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-last' added to chain 'sess-end' (order 1 index 1 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'validate' added to chain 'in-sess' (order 0 index 2 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'status' added to chain 'in-sess' (order 1 index 0 seq 2)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'privacy' added to chain 'in-sess' (order 2 index 3 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'roster' added to chain 'in-sess' (order 3 index 4 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'vacation' added to chain 'in-sess' (order 4 index 5 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-vcard' added to chain 'in-sess' (order 5 index 6 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-ping' added to chain 'in-sess' (order 6 index 7 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-private' added to chain 'in-sess' (order 7 index 8 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'disco' added to chain 'in-sess' (order 8 index 9 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'amp' added to chain 'in-sess' (order 9 index 10 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'offline' added to chain 'in-sess' (order 10 index 11 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'announce' added to chain 'in-sess' (order 11 index 12 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'presence' added to chain 'in-sess' (order 12 index 13 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'deliver' added to chain 'in-sess' (order 13 index 14 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'session' added to chain 'in-router' (order 0 index 15 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'validate' added to chain 'in-router' (order 1 index 2 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'presence' added to chain 'in-router' (order 2 index 13 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'privacy' added to chain 'in-router' (order 3 index 3 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'privacy' added to chain 'out-router' (order 0 index 3 seq 2)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-last' added to chain 'pkt-sm' (order 0 index 1 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-ping' added to chain 'pkt-sm' (order 1 index 7 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-time' added to chain 'pkt-sm' (order 2 index 16 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-version' added to chain 'pkt-sm' (order 3 index 17 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'amp' added to chain 'pkt-sm' (order 4 index 10 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'disco' added to chain 'pkt-sm' (order 5 index 9 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'announce' added to chain 'pkt-sm' (order 6 index 12 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'help' added to chain 'pkt-sm' (order 7 index 18 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'echo' added to chain 'pkt-sm' (order 8 index 19 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'status' added to chain 'pkt-sm' (order 9 index 0 seq 3)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'presence' added to chain 'pkt-sm' (order 10 index 13 seq 2)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'roster' added to chain 'pkt-user' (order 0 index 4 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'presence' added to chain 'pkt-user' (order 1 index 13 seq 3)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-vcard' added to chain 'pkt-user' (order 2 index 6 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'amp' added to chain 'pkt-user' (order 3 index 10 seq 2)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'deliver' added to chain 'pkt-user' (order 4 index 14 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'vacation' added to chain 'pkt-user' (order 5 index 5 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'offline' added to chain 'pkt-user' (order 6 index 11 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-last' added to chain 'pkt-user' (order 7 index 1 seq 2)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'session' added to chain 'pkt-router' (order 0 index 15 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'disco' added to chain 'pkt-router' (order 1 index 9 seq 2)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'active' added to chain 'user-load' (order 0 index 20 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'roster' added to chain 'user-load' (order 1 index 4 seq 2)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'roster-publish' added to chain 'user-load' (order 2 index 21 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'privacy' added to chain 'user-load' (order 3 index 3 seq 3)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'vacation' added to chain 'user-load' (order 4 index 5 seq 2)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'active' added to chain 'user-create' (order 0 index 20 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'template-roster' added to chain 'user-create' (order 1 index 22 seq 0)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'active' added to chain 'user-delete' (order 0 index 20 seq 2)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'announce' added to chain 'user-delete' (order 1 index 12 seq 2)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'offline' added to chain 'user-delete' (order 2 index 11 seq 2)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'privacy' added to chain 'user-delete' (order 3 index 3 seq 4)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'roster' added to chain 'user-delete' (order 4 index 4 seq 3)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'vacation' added to chain 'user-delete' (order 5 index 5 seq 3)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'status' added to chain 'user-delete' (order 6 index 0 seq 4)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-last' added to chain 'user-delete' (order 7 index 1 seq 3)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-private' added to chain 'user-delete' (order 8 index 8 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-vcard' added to chain 'user-delete' (order 9 index 6 seq 2)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'iq-version' added to chain 'disco-extend' (order 0 index 17 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: module 'help' added to chain 'disco-extend' (order 1 index 18 seq 1)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: version: jabberd sm 2.2.14
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: [spacewalk.cs2c.com.cn] configured
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: [spacewalk.cs2c.com.cn] configured
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: [spacewalk.cs2c.com.cn] configured
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: [spacewalk.cs2c.com.cn] configured
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: [spacewalk.cs2c.com.cn] configured
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: [spacewalk.cs2c.com.cn] configured
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: [spacewalk.cs2c.com.cn] configured
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: [spacewalk.cs2c.com.cn] configured
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: [spacewalk.cs2c.com.cn] configured
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: [localhost.localdomain] configured
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: attempting connection to router at ::1, port=5347
Mar 26 19:42:53 spacewalk jabberd/router[2497]: [::1, port=39251] connect
Mar 26 19:42:53 spacewalk jabberd/router[2497]: [::1, port=39251] authenticated as jabberd@jabberd-router
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: connection to router established
Mar 26 19:42:53 spacewalk jabberd/router[2497]: [sm] online (bound to ::1, port 39251)
Mar 26 19:42:53 spacewalk jabberd/router[2497]: [spacewalk.cs2c.com.cn] online (bound to ::1, port 39251)
Mar 26 19:42:53 spacewalk jabberd/router[2497]: [localhost.localdomain] online (bound to ::1, port 39251)
Mar 26 19:42:53 spacewalk jabberd/sm[2504]: sm ready for sessions
Mar 26 19:42:53 spacewalk jabberd/s2s[2518]: starting up (interval=3, queue=60, keepalive=0, idle=86400)
Mar 26 19:42:53 spacewalk jabberd/s2s[2518]: process id is 2518, written to /var/lib/jabberd/pid/s2s.pid
Mar 26 19:42:53 spacewalk jabberd/s2s[2518]: attempting connection to router at ::1, port=5347
Mar 26 19:42:53 spacewalk jabberd/router[2497]: [::1, port=39252] connect
Mar 26 19:42:53 spacewalk jabberd/router[2497]: [::1, port=39252] authenticated as jabberd@jabberd-router
Mar 26 19:42:53 spacewalk jabberd/s2s[2518]: connection to router established
Mar 26 19:42:53 spacewalk jabberd/router[2497]: [s2s] set as default route
Mar 26 19:42:53 spacewalk jabberd/router[2497]: [s2s] online (bound to ::1, port 39252)
Mar 26 19:42:53 spacewalk jabberd/s2s[2518]: [::, port=5269] listening for connections
Mar 26 19:42:53 spacewalk jabberd/s2s[2518]: ready for connections
Mar 26 19:42:56 spacewalk jabberd/c2s[2511]: initialized auth module 'db'
Mar 26 19:42:56 spacewalk jabberd/c2s[2511]: [spacewalk.cs2c.com.cn] configured; realm=, registration enabled
Mar 26 19:42:56 spacewalk jabberd/c2s[2511]: attempting connection to router at ::1, port=5347
Mar 26 19:42:56 spacewalk jabberd/router[2497]: [::1, port=39254] connect
Mar 26 19:42:56 spacewalk jabberd/router[2497]: [::1, port=39254] authenticated as jabberd@jabberd-router
Mar 26 19:42:56 spacewalk jabberd/c2s[2511]: connection to router established
Mar 26 19:42:56 spacewalk jabberd/router[2497]: [c2s] online (bound to ::1, port 39254)
Mar 26 19:42:56 spacewalk jabberd/c2s[2511]: [::, port=5222] listening for connections
Mar 26 19:42:56 spacewalk jabberd/c2s[2511]: ready for connections
Mar 26 19:42:57 spacewalk jabberd/c2s[2511]: [7] [::ffff:10.1.81.45, port=55911] connect
Mar 26 19:42:57 spacewalk jabberd/c2s[2511]: [7] legacy authentication succeeded: host=, username=rhn-dispatcher-sat, resource=superclient, TLS negotiated
Mar 26 19:42:57 spacewalk jabberd/c2s[2511]: [7] requesting session: jid=rhn-dispatcher-sat.com.cn/superclient
Mar 26 19:42:57 spacewalk jabberd/sm[2504]: session started: jid=rhn-dispatcher-sat.com.cn/superclient
Mar 26 19:42:57 spacewalk wdmd[2679]: wdmd started S0 H1 G179
Mar 26 19:42:57 spacewalk wdmd[2679]: /dev/watchdog armed with fire_timeout 60
Mar 26 19:43:01 spacewalk wrapper[2850]: --> Wrapper Started as Daemon
Mar 26 19:43:01 spacewalk wrapper[2850]: Launching a JVM...

On spacewalk server, /etc/hosts content following as:
127.0.0.1       localhost.localdomain   localhost
::1             localhost.localdomain   localhost
10.1.81.45      spacewalk.cs2c.com.cn   spacewalk

On spacewalk client, /etc/hosts content following as:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1       localhost.localdomain   localhost
::1             localhost.localdomain   localhost
10.1.81.39      ns64b05.cs2c.com.cn     ns64b05

10.1.81.45      spacewalk.cs2c.com.cn   spacewalk

10.1.81.39 is spacewalk client ip.

I still got "jabber_lib.main: Unable to connect to jabber servers, sleeping 67 seconds" after running "service osad start" on spacewalk client.

I don't know if I have configed spacewalk server & client is correctly.

all configuration files are as above comment 4 ~ comment 9.

I sincerely hope to get your advice.

Comment 11 Milan Zázrivec 2014-04-04 12:04:42 UTC
My advice is to check selinux, iptables, dns functionality, etc.

This is not a bug in Spacewalk, the error simply informs the user
that the client is unable to connect to the jabberd server (c2s).
Even more so, when the jabberd service on the Spacewalk server side
seem to be running all right.

Closing, not a bug.

Comment 12 Eric Herget 2017-09-28 18:06:33 UTC
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.


Note You need to log in before you can comment on or make changes to this bug.