-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 20 Jul 2009 21:07:11 -0500 Anoop Bhat <[email protected]> wrote:
> After doing some more research, I found that the spacewalk client is > connecting (or atleast attempting to connect) to the spacewalk server > on port 5222 > > That port on the server is just not open. I'm working on trying to > figure out what that is. > > If possible, can I get a sample c2s.xml from someone running > > jabberd-2.2.5-1.el5 > > I'm sorry but my jabber skills are non existent so I'd appreciate any > help in this matter... > > Here are valid logs from the server side. > > Jul 20 19:11:18 crp-spwk-chi-02 jabberd/c2s[6713]: starting up > Jul 20 19:11:18 crp-spwk-chi-02 jabberd/c2s[6713]: process id is > 6713, written to /var/lib/jabberd/pid/c2s.pid Jul 20 19:11:18 > crp-spwk-chi-02 jabberd/c2s[6713]: modules search > path: /usr/lib64/jabberd Jul 20 19:11:18 crp-spwk-chi-02 > jabberd/c2s[6713]: loading 'pam' authreg module Jul 20 19:11:18 > crp-spwk-chi-02 jabberd/c2s[6713]: initialized auth module 'pam' Jul > 20 19:11:18 crp-spwk-chi-02 jabberd/c2s[6713]: > [localhost.localdomain] configured; realm=, registration disabled Jul > 20 19:11:18 crp-spwk-chi-02 jabberd/c2s[6713]: attempting connection > to router at 127.0.0.1, port=5347 Jul 20 19:11:18 crp-spwk-chi-02 > jabberd/c2s[6713]: error from router: Authentication failed ((null)) > Jul 20 19:11:18 crp-spwk-chi-02 jabberd/c2s[6713]: connection to > router closed Jul 20 19:11:18 crp-spwk-chi-02 jabberd/c2s[6713]: > attempting reconnect (3 left) Jul 20 19:11:20 crp-spwk-chi-02 > jabberd/c2s[6713]: attempting connection to router at 127.0.0.1, > port=5347 Jul 20 19:11:20 crp-spwk-chi-02 jabberd/c2s[6713]: error > from router: Authentication failed ((null)) Jul 20 19:11:20 > crp-spwk-chi-02 jabberd/c2s[6713]: connection to router closed Jul 20 > 19:11:20 crp-spwk-chi-02 jabberd/c2s[6713]: attempting reconnect (2 > left) Jul 20 19:11:22 crp-spwk-chi-02 jabberd/c2s[6713]: attempting > connection to router at 127.0.0.1, port=5347 Jul 20 19:11:22 > crp-spwk-chi-02 jabberd/c2s[6713]: error from router: Authentication > failed ((null)) Jul 20 19:11:22 crp-spwk-chi-02 jabberd/c2s[6713]: > connection to router closed Jul 20 19:11:22 crp-spwk-chi-02 > jabberd/c2s[6713]: attempting reconnect (1 left) Jul 20 19:11:24 > crp-spwk-chi-02 jabberd/c2s[6713]: attempting connection to router at > 127.0.0.1, port=5347 Jul 20 19:11:24 crp-spwk-chi-02 > jabberd/c2s[6713]: error from router: Authentication failed ((null)) > Jul 20 19:11:24 crp-spwk-chi-02 jabberd/c2s[6713]: connection to > router closed Jul 20 19:11:24 crp-spwk-chi-02 jabberd/c2s[6713]: > shutting down > > > Anoop Bhat > Systems Administrator > Trustwave > 70 W. Madison > Chicago, IL, 60602 > O: 312.873.7446 > C: 312.925.3271 > > > > ________________________________ > From: Anoop Bhat <[email protected]> > Reply-To: <[email protected]> > Date: Mon, 20 Jul 2009 16:21:54 -0500 > To: <[email protected]> > Subject: Re: [Spacewalk-list] Osad not connecting to jabberd > > Hi all, > > Anyone having trouble like below? > > Is it my sillyness in how I named the spacewalk server and what the > cert is for? > > Thanks > > Anoop > > Anoop Bhat > Systems Administrator > Trustwave > 70 W. Madison > Chicago, IL, 60602 > O: 312.873.7446 > C: 312.925.3271 > > > > ________________________________ > From: Anoop Bhat <[email protected]> > Reply-To: <[email protected]> > Date: Thu, 16 Jul 2009 17:35:09 -0500 > To: <[email protected]> > Subject: [Spacewalk-list] Osad not connecting to jabberd > > Starting osad: 2009-07-16 17:32:32 osad._setup_config: Updating > configuration 2009-07-16 17:32:33 osad._setup_config: Time drift 1 > 2009-07-16 17:32:33 osad._setup_config: Client name 8730c35077b85944 > 2009-07-16 17:32:33 osad._setup_config: Shared key > c9e26b5ea490d6f3a8cc3d620c97028f67f9dc52 2009-07-16 17:32:33 > jabber_lib.setup_connection: Connecting to spacewalk.trustwave.com > 2009-07-16 17:32:33 jabber_lib._get_jabber_client: 2009-07-16 > 17:32:33 jabber_lib._get_jabber_client: Connecting to > spacewalk.trustwave.com 2009-07-16 17:32:33 jabber_lib.__init__: > 2009-07-16 17:32:33 jabber_lib.__init__: 2009-07-16 17:32:33 > jabber_lib.check_cert: Loading cert <X509Name object > '/C=US/ST=IL/L=Chicago/O=Trustwave Holdings > Inc./OU=crp-spwk-chi-02.trustwave.com/CN=crp-spwk-chi-02.trustwave.com'> > 2009-07-16 17:32:33 jabber_lib.connect: 2009-07-16 17:32:33 > jabber_lib.connect: Attempting to connect 2009-07-16 17:32:33 > jabber_lib.print_message: socket error 2009-07-16 17:32:33 > jabber_lib.print_message: Could not connect to jabber server > spacewalk.trustwave.com 2009-07-16 17:32:33 > jabber_lib.setup_connection: Could not connect to any jabber server > 2009-07-16 17:32:33 jabber_lib.push_to_background: Pushing process > into background > > Client and server are vms on the same network. > > Only thing I can think of is an issue with the name of the server. > > I'm not sure what my /etc/hosts should contain. > > Other than that, spacewalk is working great. Manual check-ins and > timed check-ins are working quite well. > > Just the osad/osa-dispatcher is an issue. > > Thanks! > > Anoop Bhat > Systems Administrator > Trustwave > 70 W. Madison > Chicago, IL, 60602 > O: 312.873.7446 > C: 312.925.3271 > > Yes many people are having jabberd problems, investigating now so we can get it right in 0.6. Suspect it may be a config related problem that's only affecting EL5. Devan - -- Devan Goodwin <[email protected]> Software Engineer Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAkpnB1QACgkQAyHWaPV9my4KPQCeIjCPF9eKdCYfL48UtWHKZH4k 5v0AoMT/AuHXzaV+Aax87N4mshlKlxoD =3mG+ -----END PGP SIGNATURE----- _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
