Re: [Spacewalk-list] osa-dispatcher not running or not connecting
On Fri, Jul 08, 2011 at 05:04:06PM +0200, Andre van der Vlies wrote: Problems after 1.2 - 1.4 upgrade... Hi, I decided to make a fresh start, cleaned out all but the oracle stuff... It all seemed to install okay... But now my osa-dispatcher is not running or does not allow connecting to. I've found a 2009 thread with a fix (http://www.mail-archive.com/spacewalk-list@redhat.com/msg02909.html). I didn't help however. I'm not sure what logs to send... My 'osad.log' is filled with: 2011-07-08 16:18:36 jabber_lib.main: Unable to connect to jabber servers, sleeping 92 seconds /var/log/messages: Jul 8 16:56:07 zwalk jabberd/sm[11090]: zwalk.henz.nl ready for sessions Jul 8 16:56:18 zwalk jabberd/c2s[11097]: [7] [94.232.160.136, port=39382] connect Jul 8 16:56:18 zwalk jabberd/c2s[11097]: [7] legacy authentication succeeded: host=, username=rhn-dispatcher-sat, resource=superclient, TLS negotiated Jul 8 16:56:18 zwalk jabberd/c2s[11097]: [7] requesting session: jid=rhn-dispatcher-...@zwalk.henz.nl/superclient Jul 8 16:56:18 zwalk jabberd/sm[11090]: session started: jid=rhn-dispatcher-...@zwalk.henz.nl/superclient [root@zwalk log]# tail -f messages | grep -e jabber -e osad Jul 8 16:57:28 zwalk jabberd/c2s[11097]: [11] [94.232.160.136, port=52536] connect Jul 8 16:57:28 zwalk jabberd/c2s[11097]: [11] legacy authentication succeeded: host=, username=osad-9f31af9ccb, resource=osad, TLS negotiated Jul 8 16:57:28 zwalk jabberd/c2s[11097]: [11] requesting session: jid=osad-9f31af9...@zwalk.henz.nl/osad Jul 8 16:57:28 zwalk jabberd/sm[11090]: session started: jid=osad-9f31af9...@zwalk.henz.nl/osad a telnet to port 5222 works. I' am talking localhost only (yet) Actually, the Unable to connect to jabber servers is printed when exception JabberConnectionError is raised in the osad/jabber_lib code, and that seems to happen when the XMLRPC communication with the server does not go well. So you might want to check /var/log/up2date on the client, or the XMLRPC logs on the server. -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
On Mon, Jul 11, 2011 at 11:36:18AM +0200, Jan Pazdziora wrote: On Fri, Jul 08, 2011 at 05:04:06PM +0200, Andre van der Vlies wrote: Problems after 1.2 - 1.4 upgrade... Hi, I decided to make a fresh start, cleaned out all but the oracle stuff... It all seemed to install okay... But now my osa-dispatcher is not running or does not allow connecting to. [...] Actually, the Unable to connect to jabber servers is printed when exception JabberConnectionError is raised in the osad/jabber_lib code, and that seems to happen when the XMLRPC communication with the server does not go well. So you might want to check /var/log/up2date on the client, or the XMLRPC logs on the server. By the way -- is your osa-dispatcher running or not? -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
On Mon, Jul 11, 2011 at 11:36:18AM +0200, Jan Pazdziora wrote: On Fri, Jul 08, 2011 at 05:04:06PM +0200, Andre van der Vlies wrote: Problems after 1.2 - 1.4 upgrade... Hi, I decided to make a fresh start, cleaned out all but the oracle stuff... It all seemed to install okay... But now my osa-dispatcher is not running or does not allow connecting to. [...] Actually, the Unable to connect to jabber servers is printed when exception JabberConnectionError is raised in the osad/jabber_lib code, and that seems to happen when the XMLRPC communication with the server does not go well. So you might want to check /var/log/up2date on the client, or the XMLRPC logs on the server. By the way -- is your osa-dispatcher running or not? Yes, it is Checking /var/log/up2date (client side) and /var/log/rhn/rhn_server_xmlrpc.log (server side) now... -- Andre van der Vlies an...@vandervlies.xs4all.nl Certifiable Linux/UNIX engineer (CLUE) Homepage: http://vandervlies.xs4all.nl/~andre Books: http://www.lulu.com/andre14 Key fingerprint = 397C 7479 67DB 9306 23DC B423 7B58 CD5A 6EFF 5CF8 -- Programming isn't a craft, it's an art. () ascii ribbon campaign - against html e-mail /\- against proprietary attachments ^[^#] -- ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
Actually, the
Unable to connect to jabber servers
is printed when exception JabberConnectionError is raised in the
osad/jabber_lib code, and that seems to happen when the XMLRPC
communication with the server does not go well.
So you might want to check /var/log/up2date on the client, or the
XMLRPC logs on the server.
The up2date log on the client says:
Traceback (most recent call last):
File /usr/sbin/rhn_check, line 333, in __run_action
(status, message, data) = CheckCli.__do_call(method, params, kwargs)
File /usr/sbin/rhn_check, line 325, in __do_call
method = getMethod.getMethod(method, /usr/share/rhn/, actions)
File /usr/share/rhn/up2date_client/getMethod.py, line 78, in getMethod
actions = __import__(modulename)
File /usr/share/rhn/actions/packages.py, line 268, in ?
yum_base = YumAction()
File /usr/share/rhn/actions/packages.py, line 67, in __init__
self.repos.populateSack(mdtype='all')
File /usr/lib/python2.4/site-packages/yum/repos.py, line 260, in
populateSack
sack.populate(repo, mdtype, callback, cacheonly)
File /usr/lib/python2.4/site-packages/yum/yumRepo.py, line 187, in
populate
xml = repo_get_function()
File /usr/lib/python2.4/site-packages/yum/yumRepo.py, line 1567, in
getOtherXML
return self.retrieveMD('other')
File /usr/lib/python2.4/site-packages/yum/yumRepo.py, line 1498, in
retrieveMD
return self._retrieveMD(mdtype)
File /usr/lib/python2.4/site-packages/yum/yumRepo.py, line 1538, in
_retrieveMD
cache=self.http_caching == 'all')
File /usr/share/yum-plugins/rhnplugin.py, line 333, in _getFile
raise yum.Errors.RepoError, \
yum.Errors.RepoError: failed to retrieve repodata/other.xml.gz from
centos5-addons-x86_64
error was [Errno 14] HTTP Error 404: Not Found
--
Andre van der Vlies an...@vandervlies.xs4all.nl
Certifiable Linux/UNIX engineer (CLUE)
Homepage: http://vandervlies.xs4all.nl/~andre
Books: http://www.lulu.com/andre14
Key fingerprint = 397C 7479 67DB 9306 23DC B423 7B58 CD5A 6EFF 5CF8
--
Programming isn't a craft, it's an art.
() ascii ribbon campaign - against html e-mail
/\- against proprietary attachments
^[^#]
--
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
On Mon, Jul 11, 2011 at 01:38:36PM +0200, Andre van der Vlies wrote:
Actually, the
Unable to connect to jabber servers
is printed when exception JabberConnectionError is raised in the
osad/jabber_lib code, and that seems to happen when the XMLRPC
communication with the server does not go well.
So you might want to check /var/log/up2date on the client, or the
XMLRPC logs on the server.
The up2date log on the client says:
Traceback (most recent call last):
File /usr/sbin/rhn_check, line 333, in __run_action
(status, message, data) = CheckCli.__do_call(method, params, kwargs)
File /usr/sbin/rhn_check, line 325, in __do_call
method = getMethod.getMethod(method, /usr/share/rhn/, actions)
File /usr/share/rhn/up2date_client/getMethod.py, line 78, in getMethod
actions = __import__(modulename)
File /usr/share/rhn/actions/packages.py, line 268, in ?
yum_base = YumAction()
File /usr/share/rhn/actions/packages.py, line 67, in __init__
self.repos.populateSack(mdtype='all')
File /usr/lib/python2.4/site-packages/yum/repos.py, line 260, in
populateSack
sack.populate(repo, mdtype, callback, cacheonly)
File /usr/lib/python2.4/site-packages/yum/yumRepo.py, line 187, in
populate
xml = repo_get_function()
File /usr/lib/python2.4/site-packages/yum/yumRepo.py, line 1567, in
getOtherXML
return self.retrieveMD('other')
File /usr/lib/python2.4/site-packages/yum/yumRepo.py, line 1498, in
retrieveMD
return self._retrieveMD(mdtype)
File /usr/lib/python2.4/site-packages/yum/yumRepo.py, line 1538, in
_retrieveMD
cache=self.http_caching == 'all')
File /usr/share/yum-plugins/rhnplugin.py, line 333, in _getFile
raise yum.Errors.RepoError, \
yum.Errors.RepoError: failed to retrieve repodata/other.xml.gz from
centos5-addons-x86_64
error was [Errno 14] HTTP Error 404: Not Found
So, it looks like your repodata is not being regenerated. Can you
check the status of the centos5-addons-x86_64 channel on the WebUI,
and possibly also the taskomatic logs to see if there is something
wrong there?
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
yum.Errors.RepoError: failed to retrieve repodata/other.xml.gz from centos5-addons-x86_64 error was [Errno 14] HTTP Error 404: Not Found So, it looks like your repodata is not being regenerated. Can you check the status of the centos5-addons-x86_64 channel on the WebUI, and possibly also the taskomatic logs to see if there is something wrong there? I an a bit slow... But this is what I am checking now. The addons repository looks empty... I am running repo_sync.py every day... No error (no packages retreived...) Tyring to find out what has happened... Can I force a single channel??? Will have look in Taskomatic.. -- Andre van der Vlies an...@vandervlies.xs4all.nl Certifiable Linux/UNIX engineer (CLUE) Homepage: http://vandervlies.xs4all.nl/~andre Books: http://www.lulu.com/andre14 Key fingerprint = 397C 7479 67DB 9306 23DC B423 7B58 CD5A 6EFF 5CF8 -- Programming isn't a craft, it's an art. () ascii ribbon campaign - against html e-mail /\- against proprietary attachments ^[^#] -- ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
Joshua Roys wrote: On 10/29/2009 11:43 AM, Michiel van Es wrote: Is it possible to reconfigure the jabber service and start clean? The SYN_RECV packages are not ok.. The strange thing is that I can not even make a normal jabber connection from a client (say pidgin) so I suspect my jabber settings are garbled.. Is it possible if I post some of my configuration here so people can look at it? I don't think it's a jabberd issue ... I feel like this is a general networking issue. I don't think the application would even see a socket in that SYN_RECV state. Here's a test: $ strace nc -l 12345 # tcpdump -vnni lo port 12345 # nmap -v -sS -p 12345 localhost nc doesn't see anything... and the tcpdump shows the kernel sees and replies to the SYN nmap sends: 16:27:56.880966 IP (tos 0x0, ttl 38, id 64160, offset 0, flags [none], proto TCP (6), length 44) 127.0.0.1.42004 127.0.0.1.12345: S, cksum 0xf26f (correct), 1382315266:1382315266(0) win 3072 mss 1460 16:27:56.881000 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44) 127.0.0.1.12345 127.0.0.1.42004: S, cksum 0x0791 (correct), 1846857288:1846857288(0) ack 1382315267 win 32792 mss 16396 (then nmap kills the fake connection with a RST...) So I feel like you should examine the network setup... Is it possible jabber tries to do an ldap lookup? I am trying to install webmin on the same machine and I get this crap in /var/log/messages: Oct 30 13:57:41 devmx01 perl: nss_ldap: failed to bind to LDAP server ldap://10.101.0.95: Can't contact LDAP server Oct 30 13:57:44 devmx01 perl: nss_ldap: failed to bind to LDAP server ldap://10.101.0.95: Can't contact LDAP server Oct 30 13:57:44 devmx01 perl: nss_ldap: reconnecting to LDAP server (sleeping 4 seconds)... Oct 30 13:57:51 devmx01 perl: nss_ldap: failed to bind to LDAP server ldap://10.101.0.95: Can't contact LDAP server Oct 30 13:57:51 devmx01 perl: nss_ldap: reconnecting to LDAP server (sleeping 8 seconds)... Oct 30 13:58:02 devmx01 perl: nss_ldap: failed to bind to LDAP server ldap://10.101.0.95: Can't contact LDAP server Oct 30 13:58:02 devmx01 perl: nss_ldap: reconnecting to LDAP server (sleeping 16 seconds)... Oct 30 13:58:21 devmx01 perl: nss_ldap: failed to bind to LDAP server ldap://10.101.0.95: Can't contact LDAP server Oct 30 13:58:21 devmx01 perl: nss_ldap: reconnecting to LDAP server (sleeping 32 seconds)... Oct 30 13:58:56 devmx01 perl: nss_ldap: failed to bind to LDAP server ldap://10.101.0.95: Can't contact LDAP server Oct 30 13:58:56 devmx01 perl: nss_ldap: reconnecting to LDAP server My /etc/pam.d/jabberd: #%PAM-1.0 auth required pam_nologin.so auth include system-auth accountinclude system-auth sessioninclude system-auth This also stopped my ssh account from loging in.. Another question: Is it possbile to set the rhnsd on 5 minutes instead of 4 hours? In case of a failing jabber server, the clients will pull the requests every 5 minutes? Can this do any harm? That should work - we do something like that here, although we set it to 30 minutes (I think). Edit /etc/sysconfig/rhn/rhnsd - the INTERVAL is in minutes. Also note that rhnsd varies the time a little every 12 intervals to prevent massive concurrent checkins. Hope to help, Michiel Josh ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
FIXED IT! changed the max open files from 1024 to 2024 in the .xml files and moved /var/lib/jabberd/db to /var/lib/jabberd/old-jammer mkdir /var/lib/jabberd/db chown jabber:jabber /var/lib/jabberd/db chmod 777 /var/lib/jabberd/db and restarted jabberd and now I see all connection established :) Works like a charm! :D Michiel van Es wrote: Joshua Roys wrote: On 10/29/2009 11:43 AM, Michiel van Es wrote: Is it possible to reconfigure the jabber service and start clean? The SYN_RECV packages are not ok.. The strange thing is that I can not even make a normal jabber connection from a client (say pidgin) so I suspect my jabber settings are garbled.. Is it possible if I post some of my configuration here so people can look at it? I don't think it's a jabberd issue ... I feel like this is a general networking issue. I don't think the application would even see a socket in that SYN_RECV state. Here's a test: $ strace nc -l 12345 # tcpdump -vnni lo port 12345 # nmap -v -sS -p 12345 localhost nc doesn't see anything... and the tcpdump shows the kernel sees and replies to the SYN nmap sends: 16:27:56.880966 IP (tos 0x0, ttl 38, id 64160, offset 0, flags [none], proto TCP (6), length 44) 127.0.0.1.42004 127.0.0.1.12345: S, cksum 0xf26f (correct), 1382315266:1382315266(0) win 3072 mss 1460 16:27:56.881000 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44) 127.0.0.1.12345 127.0.0.1.42004: S, cksum 0x0791 (correct), 1846857288:1846857288(0) ack 1382315267 win 32792 mss 16396 (then nmap kills the fake connection with a RST...) So I feel like you should examine the network setup... Is it possible jabber tries to do an ldap lookup? I am trying to install webmin on the same machine and I get this crap in /var/log/messages: Oct 30 13:57:41 devmx01 perl: nss_ldap: failed to bind to LDAP server ldap://10.101.0.95: Can't contact LDAP server Oct 30 13:57:44 devmx01 perl: nss_ldap: failed to bind to LDAP server ldap://10.101.0.95: Can't contact LDAP server Oct 30 13:57:44 devmx01 perl: nss_ldap: reconnecting to LDAP server (sleeping 4 seconds)... Oct 30 13:57:51 devmx01 perl: nss_ldap: failed to bind to LDAP server ldap://10.101.0.95: Can't contact LDAP server Oct 30 13:57:51 devmx01 perl: nss_ldap: reconnecting to LDAP server (sleeping 8 seconds)... Oct 30 13:58:02 devmx01 perl: nss_ldap: failed to bind to LDAP server ldap://10.101.0.95: Can't contact LDAP server Oct 30 13:58:02 devmx01 perl: nss_ldap: reconnecting to LDAP server (sleeping 16 seconds)... Oct 30 13:58:21 devmx01 perl: nss_ldap: failed to bind to LDAP server ldap://10.101.0.95: Can't contact LDAP server Oct 30 13:58:21 devmx01 perl: nss_ldap: reconnecting to LDAP server (sleeping 32 seconds)... Oct 30 13:58:56 devmx01 perl: nss_ldap: failed to bind to LDAP server ldap://10.101.0.95: Can't contact LDAP server Oct 30 13:58:56 devmx01 perl: nss_ldap: reconnecting to LDAP server My /etc/pam.d/jabberd: #%PAM-1.0 auth required pam_nologin.so auth include system-auth accountinclude system-auth sessioninclude system-auth This also stopped my ssh account from loging in.. Another question: Is it possbile to set the rhnsd on 5 minutes instead of 4 hours? In case of a failing jabber server, the clients will pull the requests every 5 minutes? Can this do any harm? That should work - we do something like that here, although we set it to 30 minutes (I think). Edit /etc/sysconfig/rhn/rhnsd - the INTERVAL is in minutes. Also note that rhnsd varies the time a little every 12 intervals to prevent massive concurrent checkins. Hope to help, Michiel Josh ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
On 10/30/2009 10:11 AM, Michiel van Es wrote: FIXED IT! changed the max open files from 1024 to 2024 in the .xml files and moved /var/lib/jabberd/db to /var/lib/jabberd/old-jammer mkdir /var/lib/jabberd/db chown jabber:jabber /var/lib/jabberd/db chmod 777 /var/lib/jabberd/db and restarted jabberd and now I see all connection established :) Works like a charm! :D Michiel van Es wrote: Nice! Glad you finally got it. Josh ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
CentOS 5.3 to CentOS 5.4 upgrade and yum_rhn_plugin == WAS: Re: [Spacewalk-list] osa-dispatcher not running or not connecting
Yes :) The next problem I got is to install the correct yum_rhn_plugin working with CentOS 5.4 ;) The problem is that a lot of CentoS 5 machines are now upgrading to CenOS 5.4 with a new yum version not compatible with the yum_rhn_plugin installed by wget -q http://stahnma.fedorapeople.org/spacewalk-tools/spacewalk-client-tools-0.0-1.noarch.rpm The question is now: how can I upgrae my centos 5.3 to 5.4 without the dependency problems (yum_rhn_plugin being to old?) Kind regards, Michiel Joshua Roys wrote: On 10/30/2009 10:11 AM, Michiel van Es wrote: FIXED IT! changed the max open files from 1024 to 2024 in the .xml files and moved /var/lib/jabberd/db to /var/lib/jabberd/old-jammer mkdir /var/lib/jabberd/db chown jabber:jabber /var/lib/jabberd/db chmod 777 /var/lib/jabberd/db and restarted jabberd and now I see all connection established :) Works like a charm! :D Michiel van Es wrote: Nice! Glad you finally got it. Josh ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: CentOS 5.3 to CentOS 5.4 upgrade and yum_rhn_plugin == WAS: Re: [Spacewalk-list] osa-dispatcher not running or not connecting
Michiel van Es wrote: Yes :) The next problem I got is to install the correct yum_rhn_plugin working with CentOS 5.4 ;) The problem is that a lot of CentoS 5 machines are now upgrading to CenOS 5.4 with a new yum version not compatible with the yum_rhn_plugin installed by wget -q http://stahnma.fedorapeople.org/spacewalk-tools/spacewalk-client-tools-0.0-1.noarch.rpm The question is now: how can I upgrae my centos 5.3 to 5.4 without the dependency problems (yum_rhn_plugin being to old?) Kind regards, Michiel The problem is also documented in the wiki: https://fedorahosted.org/spacewalk/wiki/RegisteringClients Where CentOS 5 clients use the old yum_rhn_plugin package, isn't it better to use the rpm's from the spacewalk repo instead of : wget -r http://www-personal.umich.edu/~lrsmith/Spacewalk/rpms/ rpm -Uvh *.rpm or rpm -ivh http://stahnma.fedorapeople.org/spacewalk-tools/spacewalk-client-tools-0.0-1.noarch.rpm yum install rhn-setup Michiel Joshua Roys wrote: On 10/30/2009 10:11 AM, Michiel van Es wrote: FIXED IT! changed the max open files from 1024 to 2024 in the .xml files and moved /var/lib/jabberd/db to /var/lib/jabberd/old-jammer mkdir /var/lib/jabberd/db chown jabber:jabber /var/lib/jabberd/db chmod 777 /var/lib/jabberd/db and restarted jabberd and now I see all connection established :) Works like a charm! :D Michiel van Es wrote: Nice! Glad you finally got it. Josh ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
RE: CentOS 5.3 to CentOS 5.4 upgrade and yum_rhn_plugin == WAS: Re:[Spacewalk-list] osa-dispatcher not running or not connecting
Please see the thread [Spacewalk-list] CentOS 5.4 64 bit and spacewalk client tools, where this has been discussed for a fix. http://article.gmane.org/gmane.linux.redhat.spacewalk.user/2988 Patrick -Original Message- From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Michiel van Es Sent: Friday, October 30, 2009 10:36 AM To: Joshua Roys Cc: spacewalk-list@redhat.com Subject: CentOS 5.3 to CentOS 5.4 upgrade and yum_rhn_plugin == WAS: Re:[Spacewalk-list] osa-dispatcher not running or not connecting Yes :) The next problem I got is to install the correct yum_rhn_plugin working with CentOS 5.4 ;) The problem is that a lot of CentoS 5 machines are now upgrading to CenOS 5.4 with a new yum version not compatible with the yum_rhn_plugin installed by wget -q http://stahnma.fedorapeople.org/spacewalk-tools/spacewalk-clie nt-tools-0.0-1.noarch.rpm The question is now: how can I upgrae my centos 5.3 to 5.4 without the dependency problems (yum_rhn_plugin being to old?) Kind regards, Michiel Joshua Roys wrote: On 10/30/2009 10:11 AM, Michiel van Es wrote: FIXED IT! changed the max open files from 1024 to 2024 in the .xml files and moved /var/lib/jabberd/db to /var/lib/jabberd/old-jammer mkdir /var/lib/jabberd/db chown jabber:jabber /var/lib/jabberd/db chmod 777 /var/lib/jabberd/db and restarted jabberd and now I see all connection established :) Works like a charm! :D Michiel van Es wrote: Nice! Glad you finally got it. Josh ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: CentOS 5.3 to CentOS 5.4 upgrade and yum_rhn_plugin == WAS: Re:[Spacewalk-list] osa-dispatcher not running or not connecting
Hi PAtrick, yes I know, that is my own thread but there is not a solution for all my CentOS 5.3 machines wanting to upgrade to CentOS 5.4 and how I can upgrade my yum_rhn_plugin packages... Or am I missing a post? Michiel Flaherty, Patrick wrote: Please see the thread [Spacewalk-list] CentOS 5.4 64 bit and spacewalk client tools, where this has been discussed for a fix. http://article.gmane.org/gmane.linux.redhat.spacewalk.user/2988 Patrick -Original Message- From: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Michiel van Es Sent: Friday, October 30, 2009 10:36 AM To: Joshua Roys Cc: spacewalk-list@redhat.com Subject: CentOS 5.3 to CentOS 5.4 upgrade and yum_rhn_plugin == WAS: Re:[Spacewalk-list] osa-dispatcher not running or not connecting Yes :) The next problem I got is to install the correct yum_rhn_plugin working with CentOS 5.4 ;) The problem is that a lot of CentoS 5 machines are now upgrading to CenOS 5.4 with a new yum version not compatible with the yum_rhn_plugin installed by wget -q http://stahnma.fedorapeople.org/spacewalk-tools/spacewalk-clie nt-tools-0.0-1.noarch.rpm The question is now: how can I upgrae my centos 5.3 to 5.4 without the dependency problems (yum_rhn_plugin being to old?) Kind regards, Michiel Joshua Roys wrote: On 10/30/2009 10:11 AM, Michiel van Es wrote: FIXED IT! changed the max open files from 1024 to 2024 in the .xml files and moved /var/lib/jabberd/db to /var/lib/jabberd/old-jammer mkdir /var/lib/jabberd/db chown jabber:jabber /var/lib/jabberd/db chmod 777 /var/lib/jabberd/db and restarted jabberd and now I see all connection established :) Works like a charm! :D Michiel van Es wrote: Nice! Glad you finally got it. Josh ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message
Subject: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Michiel van Es michi...@info.nl
To: Joshua Roys joshua.r...@gtri.gatech.edu
Date: 10/27/2009 03:46 PM
Original Message
Subject: Re: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Joshua Roys joshua.r...@gtri.gatech.edu
To: Michiel van Es michi...@info.nl
Date: 10/27/2009 03:18 PM
On 10/27/2009 10:12 AM, Michiel van Es wrote:
[r...@devmx01 sbin]# ./osa-dispatcher -N -
-- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
Update, it takes some time but then I see:
RHN 4848 2009/10/27 15:09:37 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in _get_jabber_client\n
c.connect()\n File /usr/share/rhn/osad/jabber_lib.py, line 577, in
connect\njabber.Client.connect(self)\n File
/usr/lib/python2.4/site-packages/jabber/xmlstream.py, line 512, in
connect\nself.header()\n File /usr/share/rhn/osad/jabber_lib.py,
line 1193, in header\nself.process(jabber.timeout)\n File
/usr/share/rhn/osad/jabber_lib.py, line 1061, in process\ndata =
self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',)
Maybe run a tcpdump and see what is happening?
15:43:56.626250 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto:
TCP (6), length: 60) 10.101.0.26.5222 10.101.0.26.43390: S, cksum
0x3949 (correct), 3212154399:3212154399(0) ack 3212832223 win 32768 mss
16396,sackOK,timestamp 2867760 2866160,nop,wscale 7
0x: 4500 003c 4000 4006 25bf 0a65 001a E..@.@.%..e..
0x0010: 0a65 001a 1466 a97e bf75 961f bf7f eddf .e...f.~.u..
0x0020: a012 8000 3949 0204 400c 0402 080a 9i@.
0x0030: 002b c230 002b bbf0 0103 0307.+.0.+..
15:43:56.626298 IP (tos 0x0, ttl 64, id 23514, offset 0, flags [DF],
proto: TCP (6), length: 64) 10.101.0.26.43390 10.101.0.26.5222: .,
cksum 0x3947 (correct), ack 1 win 257 nop,nop,timestamp 2867760
2867760,nop,nop,sack 1 {0:1}
0x: 4500 0040 5bda 4000 4006 c9e0 0a65 001a e...@[.@@e..
0x0010: 0a65 001a a97e 1466 bf7f ee82 bf75 9620 .e...~.f.u..
0x0020: b010 0101 3947 0101 080a 002b c230 9G...+.0
0x0030: 002b c230 0101 050a bf75 961f bf75 9620 .+.0.u...u..
15:43:56.746125 IP (tos 0x0, ttl 64, id 23515, offset 0, flags [DF],
proto: TCP (6), length: 215) 10.101.0.26.43390 10.101.0.26.5222: P,
cksum 0x15c7 (incorrect (- 0xadc8), 1:164(163) ack 1 win 257
nop,nop,timestamp 2867880 2867760
0x: 4500 00d7 5bdb 4000 4006 c948 0a65 001a e.@.@..H.e..
0x0010: 0a65 001a a97e 1466 bf7f eddf bf75 9620 .e...~.f.u..
0x0020: 8018 0101 15c7 0101 080a 002b c2a8 .+..
0x0030: 002b c230 3c3f 786d 6c20 7665 7273 696f .+.0?xml.versio
0x0040: 6e3d 2731 2e30 2720 656e 636f 6469 6e67 n='1.0'.encoding
0x0050: 3d27 5554 462d 3827 3f3e 3c73 7472 6561 ='UTF-8'?strea
0x0060: 6d3a 7374 7265 616d 2074 6f3d 2764 6576 m:stream.to='dev
0x0070: 6d78 3031 2e62 7572 6f2e 696e 666f 2e6e mx01.buro.info.n
0x0080: 6c27 2078 6d6c 6e73 3d27 6a61 6262 6572 l'.xmlns='jabber
0x0090: 3a63 6c69 656e 7427 2078 6d6c 6e73 3a73 :client'.xmlns:s
0x00a0: 7472 6561 6d3d 2768 7474 703a 2f2f 6574 tream='http://et
0x00b0: 6865 7278 2e6a 6162 6265 722e 6f72 672f herx.jabber.org/
0x00c0: 7374 7265 616d 7327 2076 6572 7369 6f6e streams'.version
0x00d0: 3d27 312e 3027 3e='1.0'
Is it possible that the supplied certificate is not accepted or
something else witj jabber?
Look at my netstat -an ? SYN_RCVD is not good:
r...@devmx01 ~]# netstat -an | grep 5222
tcp0 0 0.0.0.0:52220.0.0.0:*
LISTEN
tcp0 0 10.101.0.26:5222172.22.0.104:39143
SYN_RECV
tcp0 0 10.101.0.26:5222172.23.3.24:59154
SYN_RECV
tcp0 0 10.101.0.26:5222172.22.0.86:35239
SYN_RECV
tcp0 0 10.101.0.26:5222172.22.5.10:51865
SYN_RECV
tcp0 0 10.101.0.26:5222172.23.3.20:39145
SYN_RECV
tcp0 0 10.101.0.26:5222172.22.0.117:48053
SYN_RECV
tcp0 0 10.101.0.26:5222172.23.3.22:56608
SYN_RECV
tcp0 0 10.101.0.26:522210.101.0.170:42861
SYN_RECV
tcp0 0 10.101.0.26:522210.101.0.183:42906
SYN_RECV
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
On 10/29/2009 11:43 AM, Michiel van Es wrote: Is it possible to reconfigure the jabber service and start clean? The SYN_RECV packages are not ok.. The strange thing is that I can not even make a normal jabber connection from a client (say pidgin) so I suspect my jabber settings are garbled.. Is it possible if I post some of my configuration here so people can look at it? I don't think it's a jabberd issue ... I feel like this is a general networking issue. I don't think the application would even see a socket in that SYN_RECV state. Here's a test: $ strace nc -l 12345 # tcpdump -vnni lo port 12345 # nmap -v -sS -p 12345 localhost nc doesn't see anything... and the tcpdump shows the kernel sees and replies to the SYN nmap sends: 16:27:56.880966 IP (tos 0x0, ttl 38, id 64160, offset 0, flags [none], proto TCP (6), length 44) 127.0.0.1.42004 127.0.0.1.12345: S, cksum 0xf26f (correct), 1382315266:1382315266(0) win 3072 mss 1460 16:27:56.881000 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 44) 127.0.0.1.12345 127.0.0.1.42004: S, cksum 0x0791 (correct), 1846857288:1846857288(0) ack 1382315267 win 32792 mss 16396 (then nmap kills the fake connection with a RST...) So I feel like you should examine the network setup... Another question: Is it possbile to set the rhnsd on 5 minutes instead of 4 hours? In case of a failing jabber server, the clients will pull the requests every 5 minutes? Can this do any harm? That should work - we do something like that here, although we set it to 30 minutes (I think). Edit /etc/sysconfig/rhn/rhnsd - the INTERVAL is in minutes. Also note that rhnsd varies the time a little every 12 intervals to prevent massive concurrent checkins. Hope to help, Josh ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
On 10/27/2009 10:46 AM, Michiel van Es wrote: self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',) Maybe run a tcpdump and see what is happening? 15:43:56.626250 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 60) 10.101.0.26.5222 10.101.0.26.43390: S, cksum r...@devmx01 ~]# netstat -an | grep 5222 tcp0 0 0.0.0.0:52220.0.0.0:* LISTEN tcp0 0 10.101.0.26:5222172.22.0.104:39143 SYN_RECV tcp0 0 10.101.0.26:5222172.23.3.24:59154 SYN_RECV Something is Terribly Wrong(tm) with your networking, I think... check `ifconfig -a' and `route' and `iptables -vnL' and anything else you can think of... `ping 10.101.0.26' ? Have you tried restarting (the computer or the network via `service network restart')? `cat /etc/hosts' etc... maybe stop jabberd, isolate the computer (it looks like you have a lot of incoming traffic?), and then try to fix it locally before letting other clients connect? What a confusing problem! Josh ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message
Subject: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Joshua Roys joshua.r...@gtri.gatech.edu
To: Michiel van Es michi...@info.nl
Date: 10/22/2009 04:53 PM
On 10/22/2009 10:33 AM, Michiel van Es wrote:
I use my default ssh terminal from Ubuntu.
Is it better to run:
screen -L router -D etc?
Isn't it possible to startup jabber with verbose logging and send you
the logfiles in stead of the screen debug terminal output?
I would either do a `screen -L' and then run a program, using
ctrl-a,ctrl-c to make new screens (ctrl-a, to see a list of screens),
or edit /etc/init.d/jabberd and find the following in the Start ( )
function (~line 72 for me):
rm -f ${pidPath}/${prog}.pid
args=-c ${confPath}/${prog}.xml
if [ ${prog} == c2s .
and add a -D to the end of the args:
args=-c ${confPath}/${prog}.xml -D
And then probably do something like:
# tail -n0 -f /var/log/messages /tmp/foo
(change /var/log/messages to wherever your jabber logs go)
# service jabberd start
Hi Josh,
I changed the startup in the init file but I can not find anything in
the jabber logfiles.
Only seeing osa-dispatcher complaining:
2009/10/27 14:52:08 +02:00 3868 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 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in _get_jabber_client\n
c.connect()\n File /usr/share/rhn/osad/jabber_lib.py, line 577, in
connect\njabber.Client.connect(self)\n File
/usr/lib/python2.4/site-packages/jabber/xmlstream.py, line 464, in
connect\nelse: self._sock.connect((self._hostIP, self._port))\n
File string, line 1, in connect\nerror: (111, \'Connection
refused\')\n')
2009/10/27 14:52:08 +02:00 3868 0.0.0.0:
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
2009/10/27 14:52:08 +02:00 3868 0.0.0.0: osad/jabber_lib.main('Unable to
connect to jabber servers, sleeping 10 seconds',)
2009/10/27 14:52:18 +02:00 3868 0.0.0.0: osad/jabber_lib.__init__
2009/10/27 14:52:18 +02:00 3868 0.0.0.0:
osad/jabber_lib.print_message('socket error',)
2009/10/27 14:52:18 +02:00 3868 0.0.0.0:
osad/jabber_lib.print_message('Could not connect to jabber server',
'devmx01.buro.info.nl')
2009/10/27 14:52:18 +02:00 3868 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 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in _get_jabber_client\n
c.connect()\n File /usr/share/rhn/osad/jabber_lib.py, line 577, in
connect\njabber.Client.connect(self)\n File
/usr/lib/python2.4/site-packages/jabber/xmlstream.py, line 464, in
connect\nelse: self._sock.connect((self._hostIP, self._port))\n
File string, line 1, in connect\nerror: (111, \'Connection
refused\')\n')
2009/10/27 14:52:18 +02:00 3868 0.0.0.0:
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
2009/10/27 14:52:18 +02:00 3868 0.0.0.0: osad/jabber_lib.main('Unable to
connect to jabber servers, sleeping 10 seconds',)
2009/10/27 14:52:28 +02:00 3868 0.0.0.0: osad/jabber_lib.__init__
Can I do other tests? I don't get why I am not seeing anything going
wrong in the jabber logfiles?
Josh
Michiel
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkrm+5oACgkQSU+5fmlaNkMh2wCgx2iC89sqS6xP8rw9XPGvxzq9
GksAniapf1tOik3sT3gfQ3xGIuQxUjz0
=W8eu
-END PGP SIGNATURE-
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
On 10/27/2009 09:54 AM, Michiel van Es wrote:
File string, line 1, in connect\nerror: (111, \'Connection
refused\')\n')
File string, line 1, in connect\nerror: (111, \'Connection
refused\')\n')
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
Hello,
Now that I'm looking a bit closer, you've been getting 2 different errors:
error: (104, \'Connection reset by peer\')\n
and
error: (111, \'Connection refused\')\n
Right now you're getting connection refused - is port 5222 open and c2s
still running?
Josh
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message
Subject: Re: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Joshua Roys joshua.r...@gtri.gatech.edu
To: Michiel van Es michi...@info.nl
Date: 10/27/2009 03:06 PM
On 10/27/2009 09:54 AM, Michiel van Es wrote:
File string, line 1, in connect\nerror: (111, \'Connection
refused\')\n')
File string, line 1, in connect\nerror: (111, \'Connection
refused\')\n')
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
Hello,
Now that I'm looking a bit closer, you've been getting 2 different errors:
error: (104, \'Connection reset by peer\')\n
and
error: (111, \'Connection refused\')\n
Right now you're getting connection refused - is port 5222 open and c2s
still running?
[r...@devmx01 ~]# nc -vv devmx01.buro.info.nl 5222
Connection to devmx01.buro.info.nl 5222 port [tcp/xmpp-client] succeeded!
[r...@devmx01 ~]# ps aux | grep c2s
jabber3998 0.0 0.1 8928 3912 ?S14:52 0:00
/usr/bin/c2s -c /etc/jabberd/c2s.xml -D
root 4916 0.0 0.0 3912 672 pts/1R+ 15:06 0:00 grep c2s
I think it can connect but something else is wrong:
2009/10/27 15:05:53 +02:00 4848 0.0.0.0:
osad/jabber_lib._get_jabber_client('Connecting to', 'devmx01.buro.info.nl')
2009/10/27 15:05:53 +02:00 4848 0.0.0.0: osad/jabber_lib.__init__
2009/10/27 15:05:53 +02:00 4848 0.0.0.0: osad/jabber_lib.__init__
2009/10/27 15:05:53 +02:00 4848 0.0.0.0:
osad/jabber_lib.check_cert('Loading cert', X509Name object
'/C=NL/ST=Noord Holland/L=Amsterdam/O=Info.nl
HF/OU=devmx01.buro.info.nl/CN=devmx01.buro.info.nl')
2009/10/27 15:05:53 +02:00 4848 0.0.0.0: osad/jabber_lib.connect
2009/10/27 15:05:53 +02:00 4848 0.0.0.0:
osad/jabber_lib.connect('Attempting to connect',)
2009/10/27 15:05:56 +02:00 4848 0.0.0.0: osad/jabber_lib.process(300,)
2009/10/27 15:05:56 +02:00 4848 0.0.0.0: osad/jabber_lib.process('before
select(); timeout', 299.9499320984)
It is seeing the certificate so the port and cert are working but then
something else fails..
The strange thing is that I start osa-dispatcher with -N -vvv but
then I see not that many logging to the std output or my terminal, just:
[r...@devmx01 sbin]# ./osa-dispatcher -N -
- -- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
Josh
Michiel
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkrm/x8ACgkQSU+5fmlaNkO4RwCggtyW9xui5bn9TyVfN6OuLNIT
3c8AoNV/Bgv0qSlaC6QWLa16xGKhz+1S
=4Dbz
-END PGP SIGNATURE-
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message
Subject: Re: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Michiel van Es michi...@info.nl
To: Joshua Roys joshua.r...@gtri.gatech.edu
Date: 10/27/2009 03:09 PM
Original Message
Subject: Re: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Joshua Roys joshua.r...@gtri.gatech.edu
To: Michiel van Es michi...@info.nl
Date: 10/27/2009 03:06 PM
On 10/27/2009 09:54 AM, Michiel van Es wrote:
File string, line 1, in connect\nerror: (111, \'Connection
refused\')\n')
File string, line 1, in connect\nerror: (111, \'Connection
refused\')\n')
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
Hello,
Now that I'm looking a bit closer, you've been getting 2 different errors:
error: (104, \'Connection reset by peer\')\n
and
error: (111, \'Connection refused\')\n
Right now you're getting connection refused - is port 5222 open and c2s
still running?
[r...@devmx01 ~]# nc -vv devmx01.buro.info.nl 5222
Connection to devmx01.buro.info.nl 5222 port [tcp/xmpp-client] succeeded!
[r...@devmx01 ~]# ps aux | grep c2s
jabber3998 0.0 0.1 8928 3912 ?S14:52 0:00
/usr/bin/c2s -c /etc/jabberd/c2s.xml -D
root 4916 0.0 0.0 3912 672 pts/1R+ 15:06 0:00 grep c2s
I think it can connect but something else is wrong:
2009/10/27 15:05:53 +02:00 4848 0.0.0.0:
osad/jabber_lib._get_jabber_client('Connecting to', 'devmx01.buro.info.nl')
2009/10/27 15:05:53 +02:00 4848 0.0.0.0: osad/jabber_lib.__init__
2009/10/27 15:05:53 +02:00 4848 0.0.0.0: osad/jabber_lib.__init__
2009/10/27 15:05:53 +02:00 4848 0.0.0.0:
osad/jabber_lib.check_cert('Loading cert', X509Name object
'/C=NL/ST=Noord Holland/L=Amsterdam/O=Info.nl
HF/OU=devmx01.buro.info.nl/CN=devmx01.buro.info.nl')
2009/10/27 15:05:53 +02:00 4848 0.0.0.0: osad/jabber_lib.connect
2009/10/27 15:05:53 +02:00 4848 0.0.0.0:
osad/jabber_lib.connect('Attempting to connect',)
2009/10/27 15:05:56 +02:00 4848 0.0.0.0: osad/jabber_lib.process(300,)
2009/10/27 15:05:56 +02:00 4848 0.0.0.0: osad/jabber_lib.process('before
select(); timeout', 299.9499320984)
It is seeing the certificate so the port and cert are working but then
something else fails..
The strange thing is that I start osa-dispatcher with -N -vvv but
then I see not that many logging to the std output or my terminal, just:
[r...@devmx01 sbin]# ./osa-dispatcher -N -
-- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
Update, it takes some time but then I see:
RHN 4848 2009/10/27 15:09:37 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in _get_jabber_client\n
c.connect()\n File /usr/share/rhn/osad/jabber_lib.py, line 577, in
connect\njabber.Client.connect(self)\n File
/usr/lib/python2.4/site-packages/jabber/xmlstream.py, line 512, in
connect\nself.header()\n File /usr/share/rhn/osad/jabber_lib.py,
line 1193, in header\nself.process(jabber.timeout)\n File
/usr/share/rhn/osad/jabber_lib.py, line 1061, in process\ndata =
self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',)
And I can not find anything wrong in the jabebr logfiles in
/var/lib/jabberd/logs/*.log ?
Josh
Michiel
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkrm/7YACgkQSU+5fmlaNkNE6wCeIhzfSx5rLc2QFp0iBB18hQS4
PFkAoI5ZU7al+RjU2cNHpJfO1xYHiP3z
=tC2p
-END PGP SIGNATURE-
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
On 10/27/2009 10:12 AM, Michiel van Es wrote:
[r...@devmx01 sbin]# ./osa-dispatcher -N -
-- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
Update, it takes some time but then I see:
RHN 4848 2009/10/27 15:09:37 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in _get_jabber_client\n
c.connect()\n File /usr/share/rhn/osad/jabber_lib.py, line 577, in
connect\njabber.Client.connect(self)\n File
/usr/lib/python2.4/site-packages/jabber/xmlstream.py, line 512, in
connect\nself.header()\n File /usr/share/rhn/osad/jabber_lib.py,
line 1193, in header\nself.process(jabber.timeout)\n File
/usr/share/rhn/osad/jabber_lib.py, line 1061, in process\ndata =
self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',)
Maybe run a tcpdump and see what is happening?
Josh
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message
Subject: Re: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Joshua Roys joshua.r...@gtri.gatech.edu
To: Michiel van Es michi...@info.nl
Date: 10/27/2009 03:18 PM
On 10/27/2009 10:12 AM, Michiel van Es wrote:
[r...@devmx01 sbin]# ./osa-dispatcher -N -
-- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
Update, it takes some time but then I see:
RHN 4848 2009/10/27 15:09:37 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in _get_jabber_client\n
c.connect()\n File /usr/share/rhn/osad/jabber_lib.py, line 577, in
connect\njabber.Client.connect(self)\n File
/usr/lib/python2.4/site-packages/jabber/xmlstream.py, line 512, in
connect\nself.header()\n File /usr/share/rhn/osad/jabber_lib.py,
line 1193, in header\nself.process(jabber.timeout)\n File
/usr/share/rhn/osad/jabber_lib.py, line 1061, in process\ndata =
self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',)
Maybe run a tcpdump and see what is happening?
15:43:56.626250 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto:
TCP (6), length: 60) 10.101.0.26.5222 10.101.0.26.43390: S, cksum
0x3949 (correct), 3212154399:3212154399(0) ack 3212832223 win 32768 mss
16396,sackOK,timestamp 2867760 2866160,nop,wscale 7
0x: 4500 003c 4000 4006 25bf 0a65 001a E..@.@.%..e..
0x0010: 0a65 001a 1466 a97e bf75 961f bf7f eddf .e...f.~.u..
0x0020: a012 8000 3949 0204 400c 0402 080a 9i@.
0x0030: 002b c230 002b bbf0 0103 0307.+.0.+..
15:43:56.626298 IP (tos 0x0, ttl 64, id 23514, offset 0, flags [DF],
proto: TCP (6), length: 64) 10.101.0.26.43390 10.101.0.26.5222: .,
cksum 0x3947 (correct), ack 1 win 257 nop,nop,timestamp 2867760
2867760,nop,nop,sack 1 {0:1}
0x: 4500 0040 5bda 4000 4006 c9e0 0a65 001a e...@[.@@e..
0x0010: 0a65 001a a97e 1466 bf7f ee82 bf75 9620 .e...~.f.u..
0x0020: b010 0101 3947 0101 080a 002b c230 9G...+.0
0x0030: 002b c230 0101 050a bf75 961f bf75 9620 .+.0.u...u..
15:43:56.746125 IP (tos 0x0, ttl 64, id 23515, offset 0, flags [DF],
proto: TCP (6), length: 215) 10.101.0.26.43390 10.101.0.26.5222: P,
cksum 0x15c7 (incorrect (- 0xadc8), 1:164(163) ack 1 win 257
nop,nop,timestamp 2867880 2867760
0x: 4500 00d7 5bdb 4000 4006 c948 0a65 001a e.@.@..H.e..
0x0010: 0a65 001a a97e 1466 bf7f eddf bf75 9620 .e...~.f.u..
0x0020: 8018 0101 15c7 0101 080a 002b c2a8 .+..
0x0030: 002b c230 3c3f 786d 6c20 7665 7273 696f .+.0?xml.versio
0x0040: 6e3d 2731 2e30 2720 656e 636f 6469 6e67 n='1.0'.encoding
0x0050: 3d27 5554 462d 3827 3f3e 3c73 7472 6561 ='UTF-8'?strea
0x0060: 6d3a 7374 7265 616d 2074 6f3d 2764 6576 m:stream.to='dev
0x0070: 6d78 3031 2e62 7572 6f2e 696e 666f 2e6e mx01.buro.info.n
0x0080: 6c27 2078 6d6c 6e73 3d27 6a61 6262 6572 l'.xmlns='jabber
0x0090: 3a63 6c69 656e 7427 2078 6d6c 6e73 3a73 :client'.xmlns:s
0x00a0: 7472 6561 6d3d 2768 7474 703a 2f2f 6574 tream='http://et
0x00b0: 6865 7278 2e6a 6162 6265 722e 6f72 672f herx.jabber.org/
0x00c0: 7374 7265 616d 7327 2076 6572 7369 6f6e streams'.version
0x00d0: 3d27 312e 3027 3e='1.0'
Is it possible that the supplied certificate is not accepted or
something else witj jabber?
Look at my netstat -an ? SYN_RCVD is not good:
r...@devmx01 ~]# netstat -an | grep 5222
tcp0 0 0.0.0.0:52220.0.0.0:*
LISTEN
tcp0 0 10.101.0.26:5222172.22.0.104:39143
SYN_RECV
tcp0 0 10.101.0.26:5222172.23.3.24:59154
SYN_RECV
tcp0 0 10.101.0.26:5222172.22.0.86:35239
SYN_RECV
tcp0 0 10.101.0.26:5222172.22.5.10:51865
SYN_RECV
tcp0 0 10.101.0.26:5222172.23.3.20:39145
SYN_RECV
tcp0 0 10.101.0.26:5222172.22.0.117:48053
SYN_RECV
tcp0 0 10.101.0.26:5222172.23.3.22:56608
SYN_RECV
tcp0 0 10.101.0.26:522210.101.0.170:42861
SYN_RECV
tcp0 0 10.101.0.26:522210.101.0.183:42906
SYN_RECV
tcp0 0 10.101.0.26:5222172.22.0.93:35128
SYN_RECV
tcp0 0 10.101.0.26:5222172.22.5.30:41429
SYN_RECV
tcp0 0 10.101.0.26:5222172.23.1.8:35922
SYN_RECV
tcp0 0 10.101.0.26:5222
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message
Subject: Re: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Michiel van Es michi...@info.nl
To: spacewalk-list@redhat.com spacewalk-list@redhat.com
Date: 10/21/2009 11:19 AM
Original Message
Subject: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Joshua Roys joshua.r...@gtri.gatech.edu
To: spacewalk-list@redhat.com spacewalk-list@redhat.com
Date: 10/20/2009 03:29 PM
Hello,
Hi,
On 10/20/2009 08:52 AM, Michiel van Es wrote:
On 10/20/2009 01:47 AM, Michiel van Es wrote:
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.__init__
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('socket error',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('Could not connect to jabber server',
'devmx01.buro.info.nl')
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.setup_connection('Could not connect to any jabber
server',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.main('Unable to
connect to jabber servers, sleeping 10 seconds',)
2009-10-20 14:46:59 jabber_lib.setup_connection: Connecting to
devmx01.buro.info.nl
2009-10-20 14:46:59 jabber_lib._get_jabber_client:
2009-10-20 14:46:59 jabber_lib._get_jabber_client: Connecting to
devmx01.buro.info.nl
2009-10-20 14:46:59 jabber_lib.__init__:
2009-10-20 14:46:59 jabber_lib.__init__:
2009-10-20 14:46:59 jabber_lib.check_cert: Loading certX509Name object
'/C=NL/ST=Noord Holland/L=Amsterdam/O=Info.nl
HF/OU=devmx01.buro.info.nl/CN=devmx01.buro.info.nl'
2009-10-20 14:46:59 jabber_lib.connect:
2009-10-20 14:47:06 jabber_lib.process: 300
2009-10-20 14:50:36 jabber_lib.process: None
2009-10-20 14:50:58 jabber_lib.print_message: socket error
2009-10-20 14:50:58 jabber_lib.print_message: Could not connect to
jabber server devmx01.buro.info.nl
2009-10-20 14:50:58 jabber_lib.setup_connection: Could not connect to
any jabber server
2009-10-20 14:50:58 jabber_lib.main: Unable to connect to jabber
servers, sleeping 85 seconds
Attached is a patch to hopefully make osa be a little more verbose about
network errors - please apply like so:
# cd /usr/share/rhn/osad
# cp -a jabber_lib.py* /tmp/
(back them up...)
# patch /path/to/osa-print-errors.patch
And then try running osa-dispatcher/osad again. You may have to look in
/var/log/rhn/... to get the tracebacks.
Tue Oct 20 14:44:45 2009 authreg.c:661 auth get
Tue Oct 20 14:44:45 2009 authreg_db.c:105 fetching auth creds for user
'osad-da05225b95' realm ''
Tue Oct 20 14:44:45 2009 authreg_db.c:70 creating new db handle for realm ''
Was there anything after this? It seems to end abruptly.
This is what I got on the osa-dispatcher side:
[r...@devmx01 jabberd]# osa-dispatcher -N -
-- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
RHN 25575 2009/10/21 11:11:04 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in _get_jabber_client\n
c.connect()\n File /usr/share/rhn/osad/jabber_lib.py, line 577, in
connect\njabber.Client.connect(self)\n File
/usr/lib/python2.4/site-packages/jabber/xmlstream.py, line 512, in
connect\nself.header()\n File /usr/share/rhn/osad/jabber_lib.py,
line 1193, in header\nself.process(jabber.timeout)\n File
/usr/share/rhn/osad/jabber_lib.py, line 1061, in process\ndata =
self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',)
-- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
RHN 25575 2009/10/21 11:14:46 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in _get_jabber_client\n
c.connect()\n File /usr/share/rhn/osad/jabber_lib.py, line 577, in
connect\njabber.Client.connect(self)\n File
/usr/lib/python2.4/site-packages/jabber/xmlstream.py, line 512, in
connect\nself.header()\n File /usr/share/rhn/osad/jabber_lib.py,
line 1193, in header\nself.process(jabber.timeout)\n File
/usr/share/rhn/osad/jabber_lib.py, line 1061, in process\ndata =
self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',)
-- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
On the osa client side:
[r...@devgnudb01 osad]# osad -N -vvv
2009-10-21 11:08:36 osad._setup_config: Updating
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
On 10/21/2009 05:19 AM, Michiel van Es wrote: Tue Oct 20 14:44:45 2009 authreg.c:661 auth get Tue Oct 20 14:44:45 2009 authreg_db.c:105 fetching auth creds for user 'osad-da05225b95' realm '' Tue Oct 20 14:44:45 2009 authreg_db.c:70 creating new db handle for realm '' Was there anything after this? It seems to end abruptly. self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',) On the osa client side: [r...@devgnudb01 osad]# osad -N -vvv 2009-10-21 11:08:36 jabber_lib.setup_connection: Connecting to devmx01.buro.info.nl 2009-10-21 11:08:36 jabber_lib._get_jabber_client: 2009-10-21 11:08:36 jabber_lib._get_jabber_client: Connecting to devmx01.buro.info.nl 2009-10-21 11:08:36 jabber_lib.__init__: 2009-10-21 11:08:36 jabber_lib.__init__: 2009-10-21 11:08:36 jabber_lib.check_cert: Loading certX509Name object '/C=NL/ST=Noord Holland/L=Amsterdam/O=Info.nl HF/OU=devmx01.buro.info.nl/CN=devmx01.buro.info.nl' 2009-10-21 11:08:36 jabber_lib.connect: 2009-10-21 11:08:36 jabber_lib.connect: Attempting to connect - -- ?xml version='1.0' encoding='UTF-8'?stream:stream to='devmx01.buro.info.nl' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0' 2009-10-21 11:08:38 jabber_lib.process: 300 2009-10-21 11:08:38 jabber_lib.process: before select(); timeout 300.0 2009-10-21 11:12:08 jabber_lib.process: select() returned 2009-10-21 11:12:08 jabber_lib.connect: Connected 2009-10-21 11:12:08 jabber_lib.process: None 2009-10-21 11:12:08 jabber_lib.process: before select(); timeout None 2009-10-21 11:12:26 jabber_lib.process: select() returned 2009-10-21 11:12:26 jabber_lib.print_message: socket error 2009-10-21 11:12:26 jabber_lib.print_message: Could not connect to jabber server devmx01.buro.info.nl Traceback (most recent call last): File /usr/share/rhn/osad/jabber_lib.py, line 255, in setup_connection c = self._get_jabber_client(js) File /usr/share/rhn/osad/jabber_lib.py, line 312, in _get_jabber_client c.connect() File /usr/share/rhn/osad/jabber_lib.py, line 588, in connect stanza = self.get_one_stanza() File /usr/share/rhn/osad/jabber_lib.py, line 791, in get_one_stanza self.process(timeout=tm) File /usr/share/rhn/osad/jabber_lib.py, line 1060, in process data = self._read(self.BLOCK_SIZE) error: (104, 'Connection reset by peer') Hello, It looks like it's something on the jabber (server) side. Was there anything else after what you previously posted from the c2s -D command? Could you maybe run all the jabberd services in separate terminals (s2s -D, c2s -D, sm -D, router -D)? Josh ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - Original Message Subject: [Spacewalk-list] osa-dispatcher not running or not connecting From: Joshua Roys joshua.r...@gtri.gatech.edu To: spacewalk-list@redhat.com spacewalk-list@redhat.com Date: 10/22/2009 01:30 PM On 10/21/2009 05:19 AM, Michiel van Es wrote: Tue Oct 20 14:44:45 2009 authreg.c:661 auth get Tue Oct 20 14:44:45 2009 authreg_db.c:105 fetching auth creds for user 'osad-da05225b95' realm '' Tue Oct 20 14:44:45 2009 authreg_db.c:70 creating new db handle for realm '' Was there anything after this? It seems to end abruptly. self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',) On the osa client side: snip Hello, Hi It looks like it's something on the jabber (server) side. Was there anything else after what you previously posted from the c2s -D command? Could you maybe run all the jabberd services in separate terminals (s2s -D, c2s -D, sm -D, router -D)? I will try that, I also found that again jabberd service is not correctly halting: [r...@devmx01 ~]# /etc/init.d/jabberd stop Terminating jabberd processes ... Stopping router: [ OK ] Stopping sm: [ OK ] Stopping c2s: [ OK ] Stopping s2s: [FAILED] I will post my findings asap. Josh Michiel ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrgW/8ACgkQSU+5fmlaNkPlgwCgrLMKk2IZdvUNseKj33JgLhln MIsAnjk31+ybwAZFZM/HrGbeRrGYy16z =vvey -END PGP SIGNATURE- ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - Original Message Subject: [Spacewalk-list] osa-dispatcher not running or not connecting From: Joshua Roys joshua.r...@gtri.gatech.edu To: spacewalk-list@redhat.com spacewalk-list@redhat.com Date: 10/22/2009 01:30 PM On 10/21/2009 05:19 AM, Michiel van Es wrote: Tue Oct 20 14:44:45 2009 authreg.c:661 auth get Tue Oct 20 14:44:45 2009 authreg_db.c:105 fetching auth creds for user 'osad-da05225b95' realm '' Tue Oct 20 14:44:45 2009 authreg_db.c:70 creating new db handle for realm '' Was there anything after this? It seems to end abruptly. self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',) On the osa client side: snip Hello, Hi It looks like it's something on the jabber (server) side. Was there anything else after what you previously posted from the c2s -D command? Could you maybe run all the jabberd services in separate terminals (s2s -D, c2s -D, sm -D, router -D)? I had to start them in the opposite order (all modules connect to the router as I am correctly informed?) I see on the router -D: Thu Oct 22 15:24:38 2009 router.c:515 want read Thu Oct 22 15:24:38 2009 router.c:855 read action on fd 6 sx (io.c:191) 6 ready for reading sx (io.c:197) tag 6 event 2 data 0x8daea28 Thu Oct 22 15:24:38 2009 router.c:525 reading from 6 Thu Oct 22 15:24:38 2009 router.c:583 read 256 bytes sx (io.c:216) passed 256 read bytes sx (chain.c:93) calling io read chain sx (sasl_gsasl.c:246) doing sasl decode sx (sasl_gsasl.c:262) 256 bytes decoded from sasl channel sx (io.c:240) decoded read data (256 bytes): route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='devmx01.buro.info.nl' to='s2s'iq xmlns='jabber:client' id='cdtkf3d2' from='devmx01.buro.info.nl' to='s2s' type='get'query xmlns='http://jabber.org/protocol/disco#info'//iq/route sx (io.c:92) completed nad: route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' to='s2s' from='devmx01.buro.info.nl'iq xmlns='jabber:client' type='get' to='s2s' from='devmx01.buro.info.nl' id='cdtkf3d2'query xmlns='http://jabber.org/protocol/disco#info'//iq/route sx (chain.c:119) calling nad read chain sx (io.c:156) tag 6 event 6 data 0x8daf1a8 Thu Oct 22 15:24:38 2009 router.c:379 unicast route from devmx01.buro.info.nl to s2s Thu Oct 22 15:24:38 2009 router.c:424 writing route for 's2s' to 127.0.0.1, port 44982 sx (chain.c:106) calling nad write chain sx (io.c:406) queueing for write: route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' to='s2s' from='devmx01.buro.info.nl'iq xmlns='jabber:client' type='get' to='s2s' from='devmx01.buro.info.nl' id='cdtkf3d2'query xmlns='http://jabber.org/protocol/disco#info'//iq/route sx (io.c:429) tag 8 event 1 data 0x0 Thu Oct 22 15:24:38 2009 router.c:520 want write Thu Oct 22 15:24:38 2009 router.c:869 write action on fd 8 sx (io.c:328) 8 ready for writing sx (io.c:286) encoding 256 bytes for writing: route xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' to='s2s' from='devmx01.buro.info.nl'iq xmlns='jabber:client' type='get' to='s2s' from='devmx01.buro.info.nl' id='cdtkf3d2'query xmlns='http://jabber.org/protocol/disco#info'//iq/route sx (chain.c:79) calling io write chain sx (sasl_gsasl.c:218) doing sasl encode sx (sasl_gsasl.c:234) 256 bytes encoded for sasl channel sx (io.c:349) handing app 256 bytes to write sx (io.c:350) tag 8 event 3 data 0x8db1570 Thu Oct 22 15:24:38 2009 router.c:590 writing to 8 Thu Oct 22 15:24:38 2009 router.c:594 256 bytes written sx (io.c:383) tag 8 event 0 data 0x0 Thu Oct 22 15:24:38 2009 router.c:515 want read sx (io.c:431) tag 8 event 0 data 0x0 Thu Oct 22 15:24:38 2009 router.c:515 want read Thu Oct 22 15:25:38 2009 main.c:446 running time checks Thu Oct 22 15:25:38 2009 main.c:451 next time check at 1256217998 Thu Oct 22 15:26:38 2009 main.c:446 running time checks Thu Oct 22 15:26:38 2009 main.c:451 next time check at 1256218058 Thu Oct 22 15:27:39 2009 main.c:446 running time checks Thu Oct 22 15:27:39 2009 main.c:451 next time check at 1256218119 sm -D: Thu Oct 22 15:24:38 2009 sm.c:53 reading from 5 Thu Oct 22 15:24:38 2009 sm.c:78 read 79 bytes sx (io.c:216) passed 79 read bytes sx (chain.c:93) calling io read chain sx (io.c:240) decoded read data (79 bytes): presence xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='s2s'/ sx (io.c:92) completed nad: presence xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' from='s2s'/ sx (chain.c:119) calling nad read chain sx (io.c:156) tag 5 event 6 data 0x8299b20 Thu Oct 22 15:24:38 2009 sm.c:203 got a packet Thu Oct 22 15:24:38 2009 pkt.c:107 creating new packet Thu Oct 22 15:24:38 2009 mm.c:622 dispatching pkt-router chain Thu Oct 22 15:24:38 2009 mm.c:635 calling module session Thu Oct 22 15:24:38 2009 mm.c:635 calling module disco Thu Oct 22 15:24:38 2009 mod_disco.c:566 presence from component s2s, issuing discovery request Thu Oct 22 15:24:38 2009 pkt.c:107 creating new
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
On 10/22/2009 09:30 AM, Michiel van Es wrote: I had to start them in the opposite order (all modules connect to the router as I am correctly informed?) Yes, sorry. router -D: sm -D: c2s -D: s2s -D: Can you send the whole logs, please? I don't see anything so far. If you're using screen, do a screen -L and then send the screenlog.* files (you can send them straight to me if you want to - they will be decently sized). And maybe try to run osa-dispatcher a few times. osa-dispatcher -N -v (after firing up a push install package): File string, line 1, in connect\nerror: (111, \'Connection refused\')\n',) - -- ?xml version='1.0' encoding='UTF-8'?stream:stream to='devmx01.buro.info.nl' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0' I think the jabber client connection refused is because the jabber server wans't up at that time..(or the router) Yep - looks like it couldn't connect. Josh ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - Original Message Subject: [Spacewalk-list] osa-dispatcher not running or not connecting From: Joshua Roys joshua.r...@gtri.gatech.edu To: Michiel van Es michi...@info.nl Date: 10/22/2009 04:25 PM On 10/22/2009 09:30 AM, Michiel van Es wrote: I had to start them in the opposite order (all modules connect to the router as I am correctly informed?) Yes, sorry. No prob. :) router -D: sm -D: c2s -D: s2s -D: Can you send the whole logs, please? I don't see anything so far. If you're using screen, do a screen -L and then send the screenlog.* files (you can send them straight to me if you want to - they will be decently sized). And maybe try to run osa-dispatcher a few times. I use my default ssh terminal from Ubuntu. Is it better to run: screen -L router -D etc? Isn't it possible to startup jabber with verbose logging and send you the logfiles in stead of the screen debug terminal output? osa-dispatcher -N -v (after firing up a push install package): File string, line 1, in connect\nerror: (111, \'Connection refused\')\n',) - -- ?xml version='1.0' encoding='UTF-8'?stream:stream to='devmx01.buro.info.nl' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0' I think the jabber client connection refused is because the jabber server wans't up at that time..(or the router) Yep - looks like it couldn't connect. Michiel Josh -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrgbSQACgkQSU+5fmlaNkOxdACfYu4L10s+8x22g2YqesAFlg0O EikAnRQ6j1K7lLcqyjKSimrXmJL064Ee =ISft -END PGP SIGNATURE- ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message
Subject: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Joshua Roys joshua.r...@gtri.gatech.edu
To: spacewalk-list@redhat.com spacewalk-list@redhat.com
Date: 10/20/2009 03:29 PM
Hello,
Hi,
On 10/20/2009 08:52 AM, Michiel van Es wrote:
On 10/20/2009 01:47 AM, Michiel van Es wrote:
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.__init__
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('socket error',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('Could not connect to jabber server',
'devmx01.buro.info.nl')
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.main('Unable to
connect to jabber servers, sleeping 10 seconds',)
2009-10-20 14:46:59 jabber_lib.setup_connection: Connecting to
devmx01.buro.info.nl
2009-10-20 14:46:59 jabber_lib._get_jabber_client:
2009-10-20 14:46:59 jabber_lib._get_jabber_client: Connecting to
devmx01.buro.info.nl
2009-10-20 14:46:59 jabber_lib.__init__:
2009-10-20 14:46:59 jabber_lib.__init__:
2009-10-20 14:46:59 jabber_lib.check_cert: Loading certX509Name object
'/C=NL/ST=Noord Holland/L=Amsterdam/O=Info.nl
HF/OU=devmx01.buro.info.nl/CN=devmx01.buro.info.nl'
2009-10-20 14:46:59 jabber_lib.connect:
2009-10-20 14:47:06 jabber_lib.process: 300
2009-10-20 14:50:36 jabber_lib.process: None
2009-10-20 14:50:58 jabber_lib.print_message: socket error
2009-10-20 14:50:58 jabber_lib.print_message: Could not connect to
jabber server devmx01.buro.info.nl
2009-10-20 14:50:58 jabber_lib.setup_connection: Could not connect to
any jabber server
2009-10-20 14:50:58 jabber_lib.main: Unable to connect to jabber
servers, sleeping 85 seconds
Attached is a patch to hopefully make osa be a little more verbose about
network errors - please apply like so:
# cd /usr/share/rhn/osad
# cp -a jabber_lib.py* /tmp/
(back them up...)
# patch /path/to/osa-print-errors.patch
And then try running osa-dispatcher/osad again. You may have to look in
/var/log/rhn/... to get the tracebacks.
Tue Oct 20 14:44:45 2009 authreg.c:661 auth get
Tue Oct 20 14:44:45 2009 authreg_db.c:105 fetching auth creds for user
'osad-da05225b95' realm ''
Tue Oct 20 14:44:45 2009 authreg_db.c:70 creating new db handle for realm ''
Was there anything after this? It seems to end abruptly.
This is what I got on the osa-dispatcher side:
[r...@devmx01 jabberd]# osa-dispatcher -N -
- -- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
RHN 25575 2009/10/21 11:11:04 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in _get_jabber_client\n
c.connect()\n File /usr/share/rhn/osad/jabber_lib.py, line 577, in
connect\njabber.Client.connect(self)\n File
/usr/lib/python2.4/site-packages/jabber/xmlstream.py, line 512, in
connect\nself.header()\n File /usr/share/rhn/osad/jabber_lib.py,
line 1193, in header\nself.process(jabber.timeout)\n File
/usr/share/rhn/osad/jabber_lib.py, line 1061, in process\ndata =
self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',)
- -- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
RHN 25575 2009/10/21 11:14:46 +02:00: ('Traceback (most recent call
last):\n File /usr/share/rhn/osad/jabber_lib.py, line 254, in
setup_connection\nc = self._get_jabber_client(js)\n File
/usr/share/rhn/osad/jabber_lib.py, line 311, in _get_jabber_client\n
c.connect()\n File /usr/share/rhn/osad/jabber_lib.py, line 577, in
connect\njabber.Client.connect(self)\n File
/usr/lib/python2.4/site-packages/jabber/xmlstream.py, line 512, in
connect\nself.header()\n File /usr/share/rhn/osad/jabber_lib.py,
line 1193, in header\nself.process(jabber.timeout)\n File
/usr/share/rhn/osad/jabber_lib.py, line 1061, in process\ndata =
self._read(self.BLOCK_SIZE)\nerror: (104, \'Connection reset by peer\')\n',)
- -- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
On the osa client side:
[r...@devgnudb01 osad]# osad -N -vvv
2009-10-21 11:08:36 osad._setup_config: Updating configuration
2009-10-21 11:08:36 osad._setup_config: Time drift 0
2009-10-21 11:08:36 osad._setup_config: Client name c5a02410c91ae78d
2009-10-21 11:08:36 osad._setup_config: Shared key
64c76d0baf1109ad0653f611f7288947412f7d21
2009-10-21 11:08:36 jabber_lib.setup_connection: Connecting
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
Hello,
On 10/20/2009 01:47 AM, Michiel van Es wrote:
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.__init__
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('socket error',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('Could not connect to jabber server',
'devmx01.buro.info.nl')
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.main('Unable to
connect to jabber servers, sleeping 10 seconds',)
But when I run nc -vv devmx01 5222 it is working
[r...@devmx01 ~]# nc -vv devmx01 5222
Connection to devmx01 5222 port [tcp/xmpp-client] succeeded!
All the logfiles in /var/lib/jabberd/log show no errors.
How can I check what is going wrong?
I think you had a similar problem about a month ago? Has anything
significant changed between then and now? (the thread name is error
jabber after upgrade 0.5 = 0.6) You could grep /var/log/yum.log for
osa and jabber, etc.
I would do something like:
# kill $(pidof c2s)
# c2s -D
and then see what
# service osa-dispatcher stop
# osa-dispatcher -N -
...gives you.
Hope to help,
Josh
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message
Subject: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Joshua Roys joshua.r...@gtri.gatech.edu
To: spacewalk-list@redhat.com spacewalk-list@redhat.com
Date: 10/20/2009 01:51 PM
Hello,
Hi! :)
On 10/20/2009 01:47 AM, Michiel van Es wrote:
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.__init__
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('socket error',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('Could not connect to jabber server',
'devmx01.buro.info.nl')
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.main('Unable to
connect to jabber servers, sleeping 10 seconds',)
But when I run nc -vv devmx01 5222 it is working
[r...@devmx01 ~]# nc -vv devmx01 5222
Connection to devmx01 5222 port [tcp/xmpp-client] succeeded!
All the logfiles in /var/lib/jabberd/log show no errors.
How can I check what is going wrong?
I think you had a similar problem about a month ago? Has anything
significant changed between then and now? (the thread name is error
jabber after upgrade 0.5 = 0.6) You could grep /var/log/yum.log for
osa and jabber, etc.
I would do something like:
# kill $(pidof c2s)
# c2s -D
There is my problem: (a lot of errors)
[r...@devmx01 rhn]# c2s -D
Tue Oct 20 13:58:33 2009 [notice] starting up
Tue Oct 20 13:58:33 2009 [info] process id is 16525, written to
/var/lib/jabberd/pid/c2s.pid
Tue Oct 20 13:58:33 2009 [notice] modules search path: /usr/lib/jabberd/
Tue Oct 20 13:58:33 2009 [info] loading 'db' authreg module
Tue Oct 20 13:58:33 2009 authreg.c:73 preloaded module 'db' (not
initialized yet)
Tue Oct 20 13:58:33 2009 [notice] initialized auth module 'db'
sx (sasl_gsasl.c:860) initialising sasl plugin
sx (sasl_gsasl.c:887) sasl context initialised
sx (env.c:75) plugin initialised (index 0)
Tue Oct 20 13:58:33 2009 bind.c:70 initialising resource bind sx plugin
sx (env.c:75) plugin initialised (index 1)
sx (ssl.c:683) initialising ssl plugin
sx (ssl.c:784) setting ssl context '' verify mode to 00
sx (ssl.c:784) setting ssl context '*' verify mode to 00
sx (ssl.c:805) ssl context '*' initialised; certificate and key loaded
from /etc/pki/spacewalk/jabberd/server.pem
sx (ssl.c:805) ssl context '' initialised; certificate and key loaded
from /etc/pki/spacewalk/jabberd/server.pem
sx (env.c:75) plugin initialised (index 2)
Tue Oct 20 13:58:33 2009 [notice] [devmx01.buro.info.nl] configured;
realm=, registration enabled
Tue Oct 20 13:58:33 2009 [notice] attempting connection to router at
127.0.0.1, port=5347
sx (sx.c:51) allocated new sx for 5
sx (client.c:122) doing client init for sx 5
sx (client.c:138) stream request: ns (null) to (null) from (null)
version 1.0
sx (client.c:168) prepared stream header: ?xml
version='1.0'?stream:stream
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
sx (client.c:175) tag 5 event 1 data 0x0
Tue Oct 20 13:58:33 2009 c2s.c:694 want write
Tue Oct 20 13:58:33 2009 c2s.c:1312 write action on fd 5
sx (io.c:328) 5 ready for writing
sx (io.c:286) encoding 98 bytes for writing: ?xml
version='1.0'?stream:stream
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
sx (chain.c:79) calling io write chain
sx (io.c:349) handing app 98 bytes to write
sx (io.c:350) tag 5 event 3 data 0x9dc61b0
Tue Oct 20 13:58:33 2009 c2s.c:731 writing to 5
Tue Oct 20 13:58:33 2009 c2s.c:735 98 bytes written
sx (client.c:103) 5 state change from 0 to 2
sx (client.c:105) stream header sent, waiting for reply
sx (io.c:383) tag 5 event 0 data 0x0
Tue Oct 20 13:58:33 2009 c2s.c:689 want read
Tue Oct 20 13:58:33 2009 c2s.c:1301 read action on fd 5
sx (io.c:191) 5 ready for reading
sx (io.c:197) tag 5 event 2 data 0x9dc61b0
Tue Oct 20 13:58:33 2009 c2s.c:699 reading from 5
Tue Oct 20 13:58:33 2009 c2s.c:724 read 326 bytes
sx (io.c:216) passed 326 read bytes
sx (chain.c:93) calling io read chain
sx (io.c:240) decoded read data (326 bytes): ?xml
version='1.0'?stream:stream
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
id='edaljssrxx04faixwdlmo8l5r5dagdbvqmgae91b'stream:features
xmlns:stream='http://etherx.jabber.org/streams'mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'mechanismDIGEST-MD5/mechanism/mechanisms/stream:features
sx (client.c:70) stream response: to (null) from (null) version 1.0 id
edaljssrxx04faixwdlmo8l5r5dagdbvqmgae91b
sx (client.c:85) 5 state change from 2 to 3
sx (client.c:86) tag 5 event 4 data 0x0
sx (io.c:92) completed nad: stream:features
xmlns:stream='http://etherx.jabber.org/streams'mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'mechanismDIGEST-MD5/mechanism/mechanisms/stream:features
sx (chain.c:119) calling nad read chain
sx (io.c:156) tag 5 event 6 data 0x9dc6f28
sx (sasl_gsasl.c:960) sending auth request to
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message
Subject: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Joshua Roys joshua.r...@gtri.gatech.edu
To: spacewalk-list@redhat.com spacewalk-list@redhat.com
Date: 10/20/2009 01:51 PM
Hello,
On 10/20/2009 01:47 AM, Michiel van Es wrote:
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.__init__
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('socket error',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('Could not connect to jabber server',
'devmx01.buro.info.nl')
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.main('Unable to
connect to jabber servers, sleeping 10 seconds',)
But when I run nc -vv devmx01 5222 it is working
[r...@devmx01 ~]# nc -vv devmx01 5222
Connection to devmx01 5222 port [tcp/xmpp-client] succeeded!
All the logfiles in /var/lib/jabberd/log show no errors.
How can I check what is going wrong?
I think you had a similar problem about a month ago? Has anything
significant changed between then and now? (the thread name is error
jabber after upgrade 0.5 = 0.6) You could grep /var/log/yum.log for
osa and jabber, etc.
I found:
[r...@devmx01 rhn]# less /var/log/yum.log | grep jabber
Aug 26 00:00:40 Updated: jabberd-2.2.8-2.el5.i386
Aug 26 00:08:28 Updated: jabberd-selinux-1.4.6-1.el5.noarch
Aug 26 00:09:50 Updated: jabberd-selinux-1.4.6-1.el5.noarch
[r...@devmx01 rhn]# less /var/log/yum.log | grep osa
Aug 26 00:09:33 Updated: osa-dispatcher-5.9.21-1.el5.noarch
Aug 26 00:09:35 Updated: osa-dispatcher-selinux-5.9.21-1.el5.noarch
Aug 26 00:09:51 Updated: osa-dispatcher-selinux-5.9.21-1.el5.noarch
I would do something like:
# kill $(pidof c2s)
# c2s -D
and then see what
# service osa-dispatcher stop
# osa-dispatcher -N -
...gives you.
Hope to help,
Josh
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkrdpvUACgkQSU+5fmlaNkP+GACcCLZjrEV+OHQKH5u3LWSOzCcC
uzsAnR9/+xMVBrAPIebABLx0oGUMlsvq
=81I2
-END PGP SIGNATURE-
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- Original Message
Subject: [Spacewalk-list] osa-dispatcher not running or not connecting
From: Joshua Roys joshua.r...@gtri.gatech.edu
To: spacewalk-list@redhat.com spacewalk-list@redhat.com
Date: 10/20/2009 01:51 PM
Hello,
On 10/20/2009 01:47 AM, Michiel van Es wrote:
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.__init__
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('socket error',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('Could not connect to jabber server',
'devmx01.buro.info.nl')
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.main('Unable to
connect to jabber servers, sleeping 10 seconds',)
But when I run nc -vv devmx01 5222 it is working
[r...@devmx01 ~]# nc -vv devmx01 5222
Connection to devmx01 5222 port [tcp/xmpp-client] succeeded!
All the logfiles in /var/lib/jabberd/log show no errors.
How can I check what is going wrong?
I think you had a similar problem about a month ago? Has anything
significant changed between then and now? (the thread name is error
jabber after upgrade 0.5 = 0.6) You could grep /var/log/yum.log for
osa and jabber, etc.
I would do something like:
# kill $(pidof c2s)
# c2s -D
and then see what
# service osa-dispatcher stop
# osa-dispatcher -N -
...gives you.
On the client I get an unable to connect:
2009-10-20 14:46:59 jabber_lib.setup_connection: Connecting to
devmx01.buro.info.nl
2009-10-20 14:46:59 jabber_lib._get_jabber_client:
2009-10-20 14:46:59 jabber_lib._get_jabber_client: Connecting to
devmx01.buro.info.nl
2009-10-20 14:46:59 jabber_lib.__init__:
2009-10-20 14:46:59 jabber_lib.__init__:
2009-10-20 14:46:59 jabber_lib.check_cert: Loading cert X509Name object
'/C=NL/ST=Noord Holland/L=Amsterdam/O=Info.nl
HF/OU=devmx01.buro.info.nl/CN=devmx01.buro.info.nl'
2009-10-20 14:46:59 jabber_lib.connect:
2009-10-20 14:47:06 jabber_lib.process: 300
2009-10-20 14:50:36 jabber_lib.process: None
2009-10-20 14:50:58 jabber_lib.print_message: socket error
2009-10-20 14:50:58 jabber_lib.print_message: Could not connect to
jabber server devmx01.buro.info.nl
2009-10-20 14:50:58 jabber_lib.setup_connection: Could not connect to
any jabber server
2009-10-20 14:50:58 jabber_lib.main: Unable to connect to jabber
servers, sleeping 85 seconds
[r...@devgnudb01 ~]# nc -vv devmx01.buro.info.nl 5222
Connection to devmx01.buro.info.nl 5222 port [tcp/xmpp-client] succeeded!
The osa-dispatcher is only showing:
[r...@devmx01 jabberd]# osa-dispatcher -N -
- -- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
- -- ?xml version='1.0' encoding='UTF-8'?stream:stream
to='devmx01.buro.info.nl' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
c2s -D:
ue Oct 20 14:44:44 2009 c2s.c:735 98 bytes written
sx (client.c:103) 5 state change from 0 to 2
sx (client.c:105) stream header sent, waiting for reply
sx (io.c:383) tag 5 event 0 data 0x0
Tue Oct 20 14:44:44 2009 c2s.c:689 want read
Tue Oct 20 14:44:44 2009 c2s.c:1301 read action on fd 5
sx (io.c:191) 5 ready for reading
sx (io.c:197) tag 5 event 2 data 0x8a3d1b0
Tue Oct 20 14:44:44 2009 c2s.c:699 reading from 5
Tue Oct 20 14:44:44 2009 c2s.c:724 read 326 bytes
sx (io.c:216) passed 326 read bytes
sx (chain.c:93) calling io read chain
sx (io.c:240) decoded read data (326 bytes): ?xml
version='1.0'?stream:stream
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
id='yuivbsh9qr8zocahq8wrjiegzggf2tx1ofx08e9y'stream:features
xmlns:stream='http://etherx.jabber.org/streams'mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'mechanismDIGEST-MD5/mechanism/mechanisms/stream:features
sx (client.c:70) stream response: to (null) from (null) version 1.0 id
yuivbsh9qr8zocahq8wrjiegzggf2tx1ofx08e9y
sx (client.c:85) 5 state change from 2 to 3
sx (client.c:86) tag 5 event 4 data 0x0
sx (io.c:92) completed nad: stream:features
xmlns:stream='http://etherx.jabber.org/streams'mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'mechanismDIGEST-MD5/mechanism/mechanisms/stream:features
sx (chain.c:119) calling nad read chain
sx (io.c:156) tag 5 event 6 data 0x8a3df28
sx (sasl_gsasl.c:960) sending auth request to server, mech 'DIGEST-MD5':
sx (chain.c:106) calling nad write chain
sx (io.c:406) queueing for write: auth
xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5'/
sx (io.c:429) tag 5 event 1 data 0x0
Tue Oct 20 14:44:44 2009 c2s.c:694 want write
Tue Oct 20 14:44:44 2009 c2s.c:1312 write action on fd 5
sx (io.c:328) 5 ready for writing
sx (io.c:286) encoding 71 bytes for writing: auth
xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5'/
sx (chain.c:79) calling io write
Re: [Spacewalk-list] osa-dispatcher not running or not connecting
Hello,
On 10/20/2009 08:52 AM, Michiel van Es wrote:
On 10/20/2009 01:47 AM, Michiel van Es wrote:
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.__init__
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('socket error',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.print_message('Could not connect to jabber server',
'devmx01.buro.info.nl')
2009/10/20 07:43:00 +02:00 3866 0.0.0.0:
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
2009/10/20 07:43:00 +02:00 3866 0.0.0.0: osad/jabber_lib.main('Unable to
connect to jabber servers, sleeping 10 seconds',)
2009-10-20 14:46:59 jabber_lib.setup_connection: Connecting to
devmx01.buro.info.nl
2009-10-20 14:46:59 jabber_lib._get_jabber_client:
2009-10-20 14:46:59 jabber_lib._get_jabber_client: Connecting to
devmx01.buro.info.nl
2009-10-20 14:46:59 jabber_lib.__init__:
2009-10-20 14:46:59 jabber_lib.__init__:
2009-10-20 14:46:59 jabber_lib.check_cert: Loading certX509Name object
'/C=NL/ST=Noord Holland/L=Amsterdam/O=Info.nl
HF/OU=devmx01.buro.info.nl/CN=devmx01.buro.info.nl'
2009-10-20 14:46:59 jabber_lib.connect:
2009-10-20 14:47:06 jabber_lib.process: 300
2009-10-20 14:50:36 jabber_lib.process: None
2009-10-20 14:50:58 jabber_lib.print_message: socket error
2009-10-20 14:50:58 jabber_lib.print_message: Could not connect to
jabber server devmx01.buro.info.nl
2009-10-20 14:50:58 jabber_lib.setup_connection: Could not connect to
any jabber server
2009-10-20 14:50:58 jabber_lib.main: Unable to connect to jabber
servers, sleeping 85 seconds
Attached is a patch to hopefully make osa be a little more verbose about
network errors - please apply like so:
# cd /usr/share/rhn/osad
# cp -a jabber_lib.py* /tmp/
(back them up...)
# patch /path/to/osa-print-errors.patch
And then try running osa-dispatcher/osad again. You may have to look in
/var/log/rhn/... to get the tracebacks.
Tue Oct 20 14:44:45 2009 authreg.c:661 auth get
Tue Oct 20 14:44:45 2009 authreg_db.c:105 fetching auth creds for user
'osad-da05225b95' realm ''
Tue Oct 20 14:44:45 2009 authreg_db.c:70 creating new db handle for realm ''
Was there anything after this? It seems to end abruptly.
Hope to help,
Josh
diff --git a/client/tools/osad/src/jabber_lib.py
b/client/tools/osad/src/jabber_lib.py
index 5c615ae..344a91b 100644
--- a/client/tools/osad/src/jabber_lib.py
+++ b/client/tools/osad/src/jabber_lib.py
@@ -259,12 +259,15 @@ class Runner:
sys.exit(1)
except socket.error, e:
self.print_message(js, socket error)
+log_error(extract_traceback())
continue
except JabberError, e:
self.print_message(js, JabberError)
+log_error(extract_traceback())
continue
except SSLError, e:
self.print_message(js, SSLError)
+log_error(extract_traceback())
continue
else:
# Ran out of Jabber servers to try
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
