-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Tomcat, Fedora 12, ejabberd 2.1.4
All jabber plugins after 1.6 will not connect to my ejabberd server. I've defined 3 ports, one STARTTLS, one TLS, and one with no SSL. I've tried with and without SASL enabled for the plugin on each. No combination works. There's nothing overly exciting with the ejabberd server, it pulls accounts from LDAP and sends premade rosters which is the only thing beyond default.
In all cases, it opens the port and then does nothing:
=INFO REPORT==== 2010-07-23 11:19:56 ===
I(<0.518.0>:ejabberd_listener:232) : (#Port<0.26285>) Accepted connection {{10,0,0,217},59241} -> {{10,0,0,216},5222}
=INFO REPORT==== 2010-07-23 11:19:56 ===
I(<0.5972.0>:ejabberd_net:25) : gethostname
=INFO REPORT==== 2010-07-23 11:19:56 ===
I(<0.5972.0>:ejabberd_c2s:261) : FQDN: "im.get2spec.com"
=INFO REPORT==== 2010-07-23 11:19:56 ===
I(<0.5972.0>:ejabberd_c2s:261) : FQDN: "im.get2spec.com"
I turned the hudson logs up all the way but nothing relevant is printed there.
- is duplicated by
-
-
- Resolved
-
- is related to
-
-
- Open
-
[JENKINS-7060] Hudson not connecting to ejabberd
kev009
created issue -
kutzi
made changes -
| Link |
New:
This issue is duplicated by |
kutzi
made changes -
| Attachment | New: instant-messaging.hpi [ 20233 ] | |
| Attachment | New: jabber.hpi [ 20234 ] |
kutzi
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
kutzi
made changes -
| Link | New: This issue is related to JENKINS-27488 [ JENKINS-27488 ] |
| Workflow | Original: JNJira [ 137157 ] | New: JNJira + In-Review [ 187385 ] |
