Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Linux samos 2.6.28-16-server #55-Ubuntu SMP Tue Oct 20 20:37:10 UTC 2009 x86_64 GNU/Linux
Description
After upgrading Jabber (from 1.6 -> 1.7), Hudson (1.352) doesn't restart.
The reload page is shown to browsers, but reloading doesn't terminate.
There is no error in hudson.log.
I have to kill -9 the JVM because soft ways don't work.
Before upgrade, all other plugins were up to date and running well, especially instant-messaging.
Régis
Attachments
Activity
Régis Desgroppes
added a comment - No, that's an external server (.1e100.net belongs to Google)
$ ping gmail.com
Régis Desgroppes
added a comment - No, that's an external server (.1e100.net belongs to Google)
$ ping gmail.com Hmm, not much ideas left how to help you.
- have you tried to disable SASL authentication in the global config page?
- SYN_SENT seems to incidcate that there are connection problems on the TCP level. Maybe you have some network admin at hand who can help you to debug this? This is definitely out of my knowledge field
- maybe you could try to ask at the Smack forum http://www.igniterealtime.org/community/community/developers/smack if someone there knows about problems connecting to GoogleTalk in Smack 3.1
BTW: with Jabber plugin v1.10 Hudson does restart, right? 'Only' Jabber connection doesn't work.
kutzi
added a comment - - edited Hmm, not much ideas left how to help you.
have you tried to disable SASL authentication in the global config page?
SYN_SENT seems to incidcate that there are connection problems on the TCP level. Maybe you have some network admin at hand who can help you to debug this? This is definitely out of my knowledge field
maybe you could try to ask at the Smack forum http://www.igniterealtime.org/community/community/developers/smack if someone there knows about problems connecting to GoogleTalk in Smack 3.1
BTW: with Jabber plugin v1.10 Hudson does restart, right? 'Only' Jabber connection doesn't work. Régis Desgroppes
added a comment - Yes!
So the problem is now solved. All what I've done:
1. upgraded Hudson Jabber notifier plugin to 1.10 (w/ Hudson instant-messaging plugin 1.8)
2. forced server to: talk.google.com [I didn't see this notice in the wiki page before]
3. disabled SASL authentication
I think we can close this issue.
Thanks for all your inputs.
Régis
Régis Desgroppes
added a comment - Yes!
So the problem is now solved. All what I've done:
1. upgraded Hudson Jabber notifier plugin to 1.10 (w/ Hudson instant-messaging plugin 1.8)
2. forced server to: talk.google.com [I didn't see this notice in the wiki page before]
3. disabled SASL authentication
I think we can close this issue.
Thanks for all your inputs.
Régis Régis Desgroppes
added a comment - Fixed since version 1.8, see: http://wiki.jenkins-ci.org/pages/viewpage.action?pageId=753777
Régis Desgroppes
added a comment - Fixed since version 1.8, see: http://wiki.jenkins-ci.org/pages/viewpage.action?pageId=753777 
Thanks for the feedback.
You could additionally do a lsof on ww-in-f125.1e100.net (I suppose that's your Jabber server)
and then check if any of the corresponding ports re protected by some firewall rule.