Punjab - Openfire - Candy

185 views
Skip to first unread message

Matt

unread,
Oct 24, 2012, 1:35:51 PM10/24/12
to punja...@googlegroups.com
Hoping someone can give me some help or point me in the right direction.

Having some issues and I think it may be punjab or candy.

Using Twisted 12.2, Openfire 3.7.0,  Punjab. and Candy as a web based  chat client. Running on CentOS 5.2

Have everything installed, was able to use candy through Openfire's http-bind but since its buggy and drops a lot I was advised to use punjab. Got twisted installed and punjab installed.

On the http://myhost/http-bind/ for punjab I get the XEP-0124 - BOSH when I hit the page with a browser.

When I attempt to log in through candy it stays at connecting. When I look on the openfire server the user has connected. But on the client it stays saying connecting.... 
Openfire log is blank for errors or warnings

Punjab Log below:

Candy Console output below:

Candy htaccess


Christopher Zorn

unread,
Oct 24, 2012, 4:11:48 PM10/24/12
to punja...@googlegroups.com
Looks like after tls it never goes into the auth stages. The reason seems that stream:features is not being sent back to Candy. This could be that punjab expects tls to complete before it gets the auth mechanisms and its just dropping those stanzas. I would have to look further. You can turn off starttls and see if things work to make sure its that.





--
You received this message because you are subscribed to the Google Groups "Punjab" group.
To view this discussion on the web visit https://groups.google.com/d/msg/punjab-xmpp/-/w0UGCad_-tMJ.
To post to this group, send email to punja...@googlegroups.com.
To unsubscribe from this group, send email to punjab-xmpp...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/punjab-xmpp?hl=en.

Matt

unread,
Oct 24, 2012, 8:26:20 PM10/24/12
to punja...@googlegroups.com
Yep, turning off tls in openfire fixed the issue. Think my pyOpenSSL is out of date. Going to try updating it to a newer version and see if that fixes the issue with TLS.

Christopher Zorn

unread,
Oct 25, 2012, 1:35:18 PM10/25/12
to punja...@googlegroups.com
Ok let me know because I think there may be an issue in Punjab where it drops the features if it receives them before it starts tls. 

To view this discussion on the web visit https://groups.google.com/d/msg/punjab-xmpp/-/ycC5jlewBfgJ.

Christian Schneider

unread,
Oct 25, 2013, 6:33:05 AM10/25/13
to punja...@googlegroups.com
Hi there,
is there an update on the punjab tls issue? I am having the same issues, if I disable TLS in Openfire, candy-chat works, otherwise it gets stuck at the "Connecting" screen.

Christopher Zorn

unread,
Oct 25, 2013, 1:01:13 PM10/25/13
to punja...@googlegroups.com
The typical solution to this issue is to make sure you have pyopenssl installed. Also, running punjab in verbose mode should produce an error to aid in figuring out your issue. 


To unsubscribe from this group and stop receiving emails from it, send an email to punjab-xmpp...@googlegroups.com.

To post to this group, send email to punja...@googlegroups.com.
Visit this group at http://groups.google.com/group/punjab-xmpp.
For more options, visit https://groups.google.com/groups/opt_out.

Christian Schneider

unread,
Oct 28, 2013, 5:41:48 AM10/28/13
to punja...@googlegroups.com
Hi Christopher,
pyopenssl is installed in version 0.13.1. I just checked the twisd.log and I get the following error:

        RETURN HTTPB 1382952463.55:
2013-10-28 10:27:43+0100 [HTTPChannel,7,127.0.0.1] <body xmlns='http://jabber.org/protocol/httpbind' type='terminate'/>
2013-10-28 10:27:43+0100 [HTTPChannel,7,127.0.0.1] 3637198252
2013-10-28 10:27:43+0100 [HTTPChannel,7,127.0.0.1] 127.0.0.1 - - [28/Oct/2013:09:27:43 +0000] "POST /http-bind/ HTTP/1.1" 200 68 "http://somese.er.methodpark.d$
2013-10-28 10:29:37+0100 [XmlStream,client] connect ERROR: [Failure instance: Traceback: <class 'OpenSSL.SSL.Error'>: [('SSL routines', 'SSL3_READ_BYTES', 'tls$
        /usr/lib/python2.7/dist-packages/twisted/python/context.py:81:callWithContext
        /usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py:586:_doReadOrWrite
        /usr/lib/python2.7/dist-packages/twisted/internet/tcp.py:199:doRead
        /usr/lib/python2.7/dist-packages/twisted/protocols/tls.py:406:dataReceived
        --- <exception caught here> ---
        /usr/lib/python2.7/dist-packages/twisted/protocols/tls.py:505:_write
        ]

This seems to happen when the I close the browser window with candy-chat trying to connect. The logs before actually do seem to look good, as far as I can tell:

2013-10-28 10:23:34+0100 [HTTPChannel,0,127.0.0.1] HEADERS 1382952214.14:
2013-10-28 10:23:34+0100 [HTTPChannel,0,127.0.0.1] {'content-length': '221', 'accept-language': 'en-US,en;q=0.5', 'accept-encoding': 'gzip, deflate', 'x-forwar$
2013-10-28 10:23:34+0100 [HTTPChannel,0,127.0.0.1] HTTPB POST :
2013-10-28 10:23:34+0100 [HTTPChannel,0,127.0.0.1] <body rid='2415357001' xmlns='http://jabber.org/protocol/httpbind' to='somese.er.methodpark.de' xml:lang='en$
2013-10-28 10:23:34+0100 [HTTPChannel,0,127.0.0.1] Session Created : 3d0edd66ca0fd64308ef5e3a9c04b2a8ef9dbada 1382952214.17
2013-10-28 10:23:34+0100 [HTTPChannel,0,127.0.0.1] ================================== 1382952214.17 connect to somese.er.methodpark.de:5222 ===================$
2013-10-28 10:23:34+0100 [HTTPChannel,0,127.0.0.1] /opt/punjab/punjab/session.py:85: exceptions.UserWarning: Domain argument to XMPPClientConnector should be b$
2013-10-28 10:23:34+0100 [HTTPChannel,0,127.0.0.1] Starting factory <punjab.session.Session object at 0x18d3410>
2013-10-28 10:23:34+0100 [HTTPChannel,0,127.0.0.1] /etc/resolv.conf changed, reparsing
2013-10-28 10:23:34+0100 [HTTPChannel,0,127.0.0.1] Resolver added ('10.10.1.11', 53) to server list
2013-10-28 10:23:34+0100 [HTTPChannel,0,127.0.0.1] DNSDatagramProtocol starting on 56357
2013-10-28 10:23:34+0100 [HTTPChannel,0,127.0.0.1] Starting protocol <twisted.names.dns.DNSDatagramProtocol object at 0x18d8950>
2013-10-28 10:23:34+0100 [-] (UDP Port 56357 Closed)
2013-10-28 10:23:34+0100 [-] Stopping protocol <twisted.names.dns.DNSDatagramProtocol object at 0x18d8950>
2013-10-28 10:23:34+0100 [Uninitialized] SID: 3d0edd66ca0fd64308ef5e3a9c04b2a8ef9dbada => SEND: "<stream:stream xmlns:stream='http://etherx.jabber.org/streams'$
2013-10-28 10:23:34+0100 [XmlStream,client] SID: 3d0edd66ca0fd64308ef5e3a9c04b2a8ef9dbada => RECV: '<?xml version=\'1.0\' encoding=\'UTF-8\'?><stream:stream xm$
2013-10-28 10:23:34+0100 [XmlStream,client] Wait until starttls is completed.
2013-10-28 10:23:34+0100 [XmlStream,client] [<twisted.words.protocols.jabber.xmlstream.TLSInitiatingInitializer object at 0x18e8550>]
2013-10-28 10:23:34+0100 [XmlStream,client] SID: 3d0edd66ca0fd64308ef5e3a9c04b2a8ef9dbada => SEND: "<starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>"
2013-10-28 10:23:34+0100 [XmlStream,client] SID: 3d0edd66ca0fd64308ef5e3a9c04b2a8ef9dbada => RECV: '<proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>'
2013-10-28 10:23:34+0100 [XmlStream,client] SID: 3d0edd66ca0fd64308ef5e3a9c04b2a8ef9dbada => SEND: "<stream:stream xmlns:stream='http://etherx.jabber.org/strea$
2013-10-28 10:24:03+0100 [-] ================================== 3d0edd66ca0fd64308ef5e3a9c04b2a8ef9dbada 1382952243.1 startup timeout =========================$
2013-10-28 10:24:03+0100 [-]

        RETURN HTTPB 1382952243.1:
2013-10-28 10:24:03+0100 [-] <body xmlns='http://jabber.org/protocol/httpbind' inactivity='60' secure='true' authid='48f6f8f' content='text/xml; charset=utf-8'$
2013-10-28 10:24:03+0100 [-] 127.0.0.1 - - [28/Oct/2013:09:24:02 +0000] "POST /http-bind/ HTTP/1.1" 200 226 "http://somese.er.methodpark.de:8080/chat/" "Mozill$
2013-10-28 10:24:03+0100 [HTTPChannel,1,127.0.0.1] HEADERS 1382952243.11:
2013-10-28 10:24:03+0100 [HTTPChannel,1,127.0.0.1] {'content-length': '115', 'accept-language': 'en-US,en;q=0.5', 'accept-encoding': 'gzip, deflate', 'x-forwar$
2013-10-28 10:24:03+0100 [HTTPChannel,1,127.0.0.1] HTTPB POST :
2013-10-28 10:24:03+0100 [HTTPChannel,1,127.0.0.1] <body rid='2415357002' xmlns='http://jabber.org/protocol/httpbind' sid='3d0edd66ca0fd64308ef5e3a9c04b2a8ef9d$
2013-10-28 10:24:03+0100 [HTTPChannel,1,127.0.0.1] 2415357002
2013-10-28 10:24:34+0100 [-] SID: 3d0edd66ca0fd64308ef5e3a9c04b2a8ef9dbada => SEND: ' '
2013-10-28 10:25:03+0100 [-]

        RETURN HTTPB 1382952303.1:
2013-10-28 10:25:03+0100 [-] <body xmlns='http://jabber.org/protocol/httpbind'/>
2013-10-28 10:25:03+0100 [-] 2415357002
2013-10-28 10:25:03+0100 [-] 127.0.0.1 - - [28/Oct/2013:09:25:02 +0000] "POST /http-bind/ HTTP/1.1" 200 51 "http://somese.er.methodpark.de:8080/chat/" "Mozilla$
2013-10-28 10:25:03+0100 [HTTPChannel,2,127.0.0.1] HEADERS 1382952303.11:
2013-10-28 10:25:03+0100 [HTTPChannel,2,127.0.0.1] {'content-length': '115', 'accept-language': 'en-US,en;q=0.5', 'accept-encoding': 'gzip, deflate', 'x-forwar$
2013-10-28 10:25:03+0100 [HTTPChannel,2,127.0.0.1] HTTPB POST :
2013-10-28 10:25:03+0100 [HTTPChannel,2,127.0.0.1] <body rid='2415357003' xmlns='http://jabber.org/protocol/httpbind' sid='3d0edd66ca0fd64308ef5e3a9c04b2a8ef9d$
2013-10-28 10:25:03+0100 [HTTPChannel,2,127.0.0.1] 2415357003
2013-10-28 10:26:03+0100 [-]

        RETURN HTTPB 1382952363.1:
2013-10-28 10:26:03+0100 [-] <body xmlns='http://jabber.org/protocol/httpbind'/>
2013-10-28 10:26:03+0100 [-] 2415357003
2013-10-28 10:26:03+0100 [-] 127.0.0.1 - - [28/Oct/2013:09:26:02 +0000] "POST /http-bind/ HTTP/1.1" 200 51 "http://somese.er.methodpark.de:8080/chat/" "Mozilla$
2013-10-28 10:26:03+0100 [HTTPChannel,3,127.0.0.1] HEADERS 1382952363.11:
2013-10-28 10:26:03+0100 [HTTPChannel,3,127.0.0.1] {'content-length': '115', 'accept-language': 'en-US,en;q=0.5', 'accept-encoding': 'gzip, deflate', 'x-forwar$
2013-10-28 10:26:03+0100 [HTTPChannel,3,127.0.0.1] HTTPB POST :
2013-10-28 10:26:03+0100 [HTTPChannel,3,127.0.0.1] <body rid='2415357004' xmlns='http://jabber.org/protocol/httpbind' sid='3d0edd66ca0fd64308ef5e3a9c04b2a8ef9d$
2013-10-28 10:26:03+0100 [HTTPChannel,3,127.0.0.1] 2415357004
2013-10-28 10:26:34+0100 [-] SID: 3d0edd66ca0fd64308ef5e3a9c04b2a8ef9dbada => SEND: ' '
2013-10-28 10:26:39+0100 [HTTPChannel,4,127.0.0.1] HEADERS 1382952399.84:
2013-10-28 10:26:39+0100 [HTTPChannel,4,127.0.0.1] {'content-length': '132', 'accept-language': 'en-US,en;q=0.5', 'accept-encoding': 'gzip, deflate', 'x-forwar$
2013-10-28 10:26:39+0100 [HTTPChannel,4,127.0.0.1] HTTPB POST :
2013-10-28 10:26:39+0100 [HTTPChannel,4,127.0.0.1] <body rid='2415357005' xmlns='http://jabber.org/protocol/httpbind' sid='3d0edd66ca0fd64308ef5e3a9c04b2a8ef9d$
2013-10-28 10:26:39+0100 [HTTPChannel,4,127.0.0.1] 2415357005
2013-10-28 10:26:39+0100 [HTTPChannel,4,127.0.0.1] SESSION -> Terminate
2013-10-28 10:26:39+0100 [HTTPChannel,4,127.0.0.1]


Any idea what could be going wrong?



2013/10/25 Christopher Zorn <christop...@gmail.com>

--
You received this message because you are subscribed to a topic in the Google Groups "Punjab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/punjab-xmpp/MxxuOIz0M44/unsubscribe.
To unsubscribe from this group and all its topics, send an email to punjab-xmpp...@googlegroups.com.

Christopher Zorn

unread,
Oct 29, 2013, 1:11:44 PM10/29/13
to punja...@googlegroups.com
First error looks like you lost the socket connection for some reason. 

The second one is strange because it does seem you establish a tls connection, idle and then timeout. These logs are cut off so it is hard to see the entire sent and receive values. Those full values may help with understanding the issue.  
Reply all
Reply to author
Forward
0 new messages