Send Message Example for OpenFire
1,198 views
Skip to first unread message
mIKE
Jan 20, 2012, 9:49:30 AM1/20/12
to SleekXMPP Discussion
I am trying to:
1) connect to openfire server
2) join chat room
3) post message
4) disconnect
I am using the send_client.py example from the github site and I can't
seem to even get a message to send without attempting the chat room
join. Also, I have uncommented the suggested line regarding openfire
(xmpp.ssl_version = ssl.PROTOCOL_SSLv3)
Here is my output:
DEBUG SEND: <message to="tcarey" type="chat"><body>yesh</body></
message>
DEBUG SEND: </stream:stream>
DEBUG End of stream recieved
DEBUG Could not acquire lock
DEBUG ==== TRANSITION connected -> disconnected
DEBUG Quitting Scheduler thread
Please if anyone has been able to get this work fill me in on how you
did it. Thank you!
1) connect to openfire server
2) join chat room
3) post message
4) disconnect
I am using the send_client.py example from the github site and I can't
seem to even get a message to send without attempting the chat room
join. Also, I have uncommented the suggested line regarding openfire
(xmpp.ssl_version = ssl.PROTOCOL_SSLv3)
Here is my output:
DEBUG SEND: <message to="tcarey" type="chat"><body>yesh</body></
message>
DEBUG SEND: </stream:stream>
DEBUG End of stream recieved
DEBUG Could not acquire lock
DEBUG ==== TRANSITION connected -> disconnected
DEBUG Quitting Scheduler thread
Please if anyone has been able to get this work fill me in on how you
did it. Thank you!
mIKE
Jan 20, 2012, 3:21:32 PM1/20/12
to SleekXMPP Discussion
I ended up getting this working:
import sys
import sleekxmpp
import ssl
sys.setdefaultencoding('utf8')
class SendToMUC(sleekxmpp.ClientXMPP):
def __init__(self, CHAT_USER, CHAT_PASSWORD, CHAT_ROOM,
CHAT_NICKNAME):
sleekxmpp.ClientXMPP.__init__(self, CHAT_USER, CHAT_PASSWORD)
self.room = CHAT_ROOM
self.nick = CHAT_NICKNAME
self.add_event_handler("session_start", self.start)
def start(self, event):
self.plugin['xep_0045'].joinMUC(self.CHAT_ROOM,
self.CHAT_NICKNAME)
self.send_message(mto=self.CHAT_ROOM, mbody="Sorry about
spamming the chat...again.", mtype='groupchat')
self.disconnect()
if __name__ == '__main__':
CHAT_USER='<username>@<server_or_ip>'
CHAT_PASSWORD='<password>'
CHAT_ROOM='<chat_room_name>@<full_domain_name>'
CHAT_NICKNAME='<name_you_wish_to_post_chat_as>'
xmpp = SendToMUC(CHAT_USER, CHAT_PASSWORD, CHAT_ROOM,
CHAT_NICKNAME)
xmpp.register_plugin('xep_0030') # Service Discovery
xmpp.register_plugin('xep_0045') # Multi-User Chat
xmpp.register_plugin('xep_0199') # XMPP Ping
xmpp.ssl_version = ssl.PROTOCOL_SSLv3
# Connect to the XMPP server and start processing XMPP stanzas.
if xmpp.connect():
xmpp.process()
print("Done")
else:
print("Unable to connect.")
import sys
import sleekxmpp
import ssl
sys.setdefaultencoding('utf8')
class SendToMUC(sleekxmpp.ClientXMPP):
def __init__(self, CHAT_USER, CHAT_PASSWORD, CHAT_ROOM,
CHAT_NICKNAME):
sleekxmpp.ClientXMPP.__init__(self, CHAT_USER, CHAT_PASSWORD)
self.room = CHAT_ROOM
self.nick = CHAT_NICKNAME
self.add_event_handler("session_start", self.start)
def start(self, event):
self.plugin['xep_0045'].joinMUC(self.CHAT_ROOM,
self.CHAT_NICKNAME)
self.send_message(mto=self.CHAT_ROOM, mbody="Sorry about
spamming the chat...again.", mtype='groupchat')
self.disconnect()
if __name__ == '__main__':
CHAT_USER='<username>@<server_or_ip>'
CHAT_PASSWORD='<password>'
CHAT_ROOM='<chat_room_name>@<full_domain_name>'
CHAT_NICKNAME='<name_you_wish_to_post_chat_as>'
xmpp = SendToMUC(CHAT_USER, CHAT_PASSWORD, CHAT_ROOM,
CHAT_NICKNAME)
xmpp.register_plugin('xep_0030') # Service Discovery
xmpp.register_plugin('xep_0045') # Multi-User Chat
xmpp.register_plugin('xep_0199') # XMPP Ping
xmpp.ssl_version = ssl.PROTOCOL_SSLv3
# Connect to the XMPP server and start processing XMPP stanzas.
if xmpp.connect():
xmpp.process()
print("Done")
else:
print("Unable to connect.")
mIKE
Jan 21, 2012, 4:07:04 PM1/21/12
to SleekXMPP Discussion
Once I got this working on my development machine (Ubuntu) I tried it
on my production server (CentoOS) and I'm getting authentication
errors. Could this be an issue with the OS or potentially some out of
date dependencies?
DEBUG setting jid to mtru...@10.0.1.9
DEBUG Loaded Plugin (RFC-6120) STARTTLS Stream Feature
DEBUG Loaded Plugin (RFC-6120) Resource Binding Stream Feature
DEBUG Loaded Plugin (RFC-3920) Start Session Stream Feature
DEBUG Loaded Plugin (RFC-6120) SASL Stream Feature
DEBUG Loaded Plugin (XEP-0030) Service Discovery
DEBUG Loaded Plugin (XEP-0045) Multi User Chat
DEBUG Loaded Plugin (XEP-0199) XMPP Ping
DEBUG Connecting to 10.0.1.9:5222
DEBUG ==== TRANSITION disconnected -> connected
DEBUG Starting HANDLER THREAD
DEBUG Loading event runner
DEBUG SEND (IMMED): <stream:stream to='10.0.1.9'
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
version='1.0'>
Done
DEBUG RECV: <stream:features><starttls
xmlns="urn:ietf:params:xml:ns:xmpp-tls" /><mechanisms
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>DIGEST-MD5</
mechanism><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</
mechanism><mechanism>CRAM-MD5</mechanism></mechanisms><compression
xmlns="http://jabber.org/features/compress"><method>zlib</method></
compression><auth xmlns="http://jabber.org/features/iq-auth" /></
stream:features>
DEBUG SEND (IMMED): <starttls xmlns="urn:ietf:params:xml:ns:xmpp-
tls" />
DEBUG RECV: <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls" />
DEBUG Starting TLS
INFO Negotiating TLS
INFO Using SSL version: 1
DEBUG SEND (IMMED): <stream:stream to='10.0.1.9'
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
version='1.0'>
DEBUG RECV: <stream:features><mechanisms
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>DIGEST-MD5</
mechanism><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</
mechanism><mechanism>CRAM-MD5</mechanism></mechanisms><compression
xmlns="http://jabber.org/features/compress"><method>zlib</method></
compression><auth xmlns="http://jabber.org/features/iq-auth" /></
stream:features>
DEBUG SEND (IMMED): <auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl"
mechanism="DIGEST-MD5" />
DEBUG RECV: <challenge xmlns="urn:ietf:params:xml:ns:xmpp-
sasl">cmVhbG09ImNoaS1pbnR3ZWItMDEiLG5vbmNlPSJiQlQvaVhKWGpnM2ljeFdSSE5QUkQ1SmRIOTFPRFM4cVVteWlud1hGIixxb3A9ImF1dGgiLGNoYXJzZXQ9dXRmLTgsYWxnb3JpdGhtPW1kNS1zZXNz</
challenge>
DEBUG SEND (IMMED): <response xmlns="urn:ietf:params:xml:ns:xmpp-
sasl">dXNlcm5hbWU9Im10cnVtYmVsbCIsbm9uY2U9ImJCVC9pWEpYamczaWN4V1JITlBSRDVKZEg5MU9EUzhxVW15aW53WEYiLHJlYWxtPSJjaGktaW50d2ViLTAxIixxb3A9YXV0aCxjbm9uY2U9IjAwNDIzNDk2MjQ5NTIxIixuYz0wMDAwMDAwMSxkaWdlc3QtdXJpPSJ4bXBwLzEwLjAuMS45IixyZXNwb25zZT04Y2M4NTc3NDVhN2VhNjU5NmZlMTM3ZmMwYzFjOWZkMg==</
response>
DEBUG RECV: <failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-
authorized /></failure>
INFO Authentication failed: not-authorized
ERROR Connection error.
on my production server (CentoOS) and I'm getting authentication
errors. Could this be an issue with the OS or potentially some out of
date dependencies?
DEBUG setting jid to mtru...@10.0.1.9
DEBUG Loaded Plugin (RFC-6120) STARTTLS Stream Feature
DEBUG Loaded Plugin (RFC-6120) Resource Binding Stream Feature
DEBUG Loaded Plugin (RFC-3920) Start Session Stream Feature
DEBUG Loaded Plugin (RFC-6120) SASL Stream Feature
DEBUG Loaded Plugin (XEP-0030) Service Discovery
DEBUG Loaded Plugin (XEP-0045) Multi User Chat
DEBUG Loaded Plugin (XEP-0199) XMPP Ping
DEBUG Connecting to 10.0.1.9:5222
DEBUG ==== TRANSITION disconnected -> connected
DEBUG Starting HANDLER THREAD
DEBUG Loading event runner
DEBUG SEND (IMMED): <stream:stream to='10.0.1.9'
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
version='1.0'>
Done
DEBUG RECV: <stream:features><starttls
xmlns="urn:ietf:params:xml:ns:xmpp-tls" /><mechanisms
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>DIGEST-MD5</
mechanism><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</
mechanism><mechanism>CRAM-MD5</mechanism></mechanisms><compression
xmlns="http://jabber.org/features/compress"><method>zlib</method></
compression><auth xmlns="http://jabber.org/features/iq-auth" /></
stream:features>
DEBUG SEND (IMMED): <starttls xmlns="urn:ietf:params:xml:ns:xmpp-
tls" />
DEBUG RECV: <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls" />
DEBUG Starting TLS
INFO Negotiating TLS
INFO Using SSL version: 1
DEBUG SEND (IMMED): <stream:stream to='10.0.1.9'
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
version='1.0'>
DEBUG RECV: <stream:features><mechanisms
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>DIGEST-MD5</
mechanism><mechanism>PLAIN</mechanism><mechanism>ANONYMOUS</
mechanism><mechanism>CRAM-MD5</mechanism></mechanisms><compression
xmlns="http://jabber.org/features/compress"><method>zlib</method></
compression><auth xmlns="http://jabber.org/features/iq-auth" /></
stream:features>
DEBUG SEND (IMMED): <auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl"
mechanism="DIGEST-MD5" />
DEBUG RECV: <challenge xmlns="urn:ietf:params:xml:ns:xmpp-
sasl">cmVhbG09ImNoaS1pbnR3ZWItMDEiLG5vbmNlPSJiQlQvaVhKWGpnM2ljeFdSSE5QUkQ1SmRIOTFPRFM4cVVteWlud1hGIixxb3A9ImF1dGgiLGNoYXJzZXQ9dXRmLTgsYWxnb3JpdGhtPW1kNS1zZXNz</
challenge>
DEBUG SEND (IMMED): <response xmlns="urn:ietf:params:xml:ns:xmpp-
sasl">dXNlcm5hbWU9Im10cnVtYmVsbCIsbm9uY2U9ImJCVC9pWEpYamczaWN4V1JITlBSRDVKZEg5MU9EUzhxVW15aW53WEYiLHJlYWxtPSJjaGktaW50d2ViLTAxIixxb3A9YXV0aCxjbm9uY2U9IjAwNDIzNDk2MjQ5NTIxIixuYz0wMDAwMDAwMSxkaWdlc3QtdXJpPSJ4bXBwLzEwLjAuMS45IixyZXNwb25zZT04Y2M4NTc3NDVhN2VhNjU5NmZlMTM3ZmMwYzFjOWZkMg==</
response>
DEBUG RECV: <failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-
authorized /></failure>
INFO Authentication failed: not-authorized
ERROR Connection error.
mIKE
Jan 22, 2012, 10:57:08 AM1/22/12
to SleekXMPP Discussion
When this works on my dev machine the log looks much different than
the failed authorization machine. All of the plugins are NOT loaded
and xmls recv output looks different. Does anyone have acceptable
dependency versions? Could this be a network issue? I worked hard to
get this working properly and to have it working in one environment
and not another is very frustrating. Any help would be much
appreciated.
Here is my successful output:
WARNING server property deprecated. Use boundjid.host
DEBUG No appropriate SRV record found. Using JID server name.
DEBUG SEND: <stream:stream to='10.0.1.9' xmlns:stream='http://
streams"><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls" /
mechanism><mechanism>ANONYMOUS</mechanism><mechanism>CRAM-MD5</
mechanism></mechanisms><compression xmlns="http://jabber.org/features/
compress"><method>zlib</method></compression><auth xmlns="http://
jabber.org/features/iq-auth" /></features>
DEBUG SEND: <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls" />
streams"><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-
sasl"><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</
mechanism><mechanism>ANONYMOUS</mechanism><mechanism>CRAM-MD5</
mechanism></mechanisms><compression xmlns="http://jabber.org/features/
compress"><method>zlib</method></compression><auth xmlns="http://
jabber.org/features/iq-auth" /></features>
DEBUG Starting SASL Auth
DEBUG SEND: <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl'
mechanism='PLAIN'>AG10cnVtYmVsbABvcHRpb25zY2l0eQ==</auth>
DEBUG RECV: <success xmlns="urn:ietf:params:xml:ns:xmpp-sasl" />
DEBUG SEND: <stream:stream to='10.0.1.9' xmlns:stream='http://
streams"><compression xmlns="http://jabber.org/features/
compress"><method>zlib</method></compression><bind
xmlns="urn:ietf:params:xml:ns:xmpp-bind" /><session
xmlns="urn:ietf:params:xml:ns:xmpp-session" /></features>
DEBUG Requesting resource:
DEBUG SEND: <iq type="set" id="1"><bind
xmlns="urn:ietf:params:xml:ns:xmpp-bind" /></iq>
DEBUG RECV: <iq to="chi-intweb-01/7c6646e5" type="result"
id="1"><bind xmlns="urn:ietf:params:xml:ns:xmpp-
bind"><jid>mtrumbell@chi-intweb-01/7c6646e5</jid></bind></iq>
DEBUG setting jid to mtrumbell@chi-intweb-01/7c6646e5
INFO Node set to: None
DEBUG SEND: <iq type="set" id="2"><session
xmlns="urn:ietf:params:xml:ns:xmpp-session" /></iq>
DEBUG RECV: <iq to="mtrumbell@chi-intweb-01/7c6646e5" type="result"
id="2"><session xmlns="urn:ietf:params:xml:ns:xmpp-session" /></iq>
DEBUG Established Session
DEBUG SEND: <presence to="sup...@optionscity.chi-intweb-01/
SupportServices" from="mtrumbell@chi-intweb-01/7c6646e5"><x
xmlns="http://jabber.org/protocol/muc"><history maxchars="0" /></x></
presence>
DEBUG SEND: <message to="sup...@optionscity.chi-intweb-01"
type="groupchat"><body>test</body></message>
DEBUG SEND: </stream:stream>
DEBUG RECV: <presence to="mtrumbell@chi-intweb-01/7c6646e5"
from="sup...@optionscity.chi-intweb-01/rfasouliotis"><show>away</
show><status>I'm not here right now</status><query
xmlns="jabber:iq:last" seconds="128083" /><c xmlns="http://jabber.org/
protocol/caps" node="http://pidgin.im/" ver="AcN1/PEN8nq7AHD
+9jpxMV4U6YM=" ext="voice-v1 camera-v1 video-v1" hash="sha-1" /><x
xmlns="http://jabber.org/protocol/muc#user"><item affiliation="owner"
role="moderator" /></x></presence>
DEBUG RECV: <presence to="mtrumbell@chi-intweb-01/7c6646e5"
from="sup...@optionscity.chi-intweb-01/SupportServices"><x
xmlns="http://jabber.org/protocol/muc#user"><item affiliation="member"
jid="mtrumbell@chi-intweb-01/7c6646e5" role="participant" /></x></
presence>
DEBUG RECV: <message to="mtrumbell@chi-intweb-01/7c6646e5"
type="groupchat" from="sup...@optionscity.chi-intweb-01/
SupportServices"><body>test</body></message>
> sasl">cmVhbG09ImNoaS1pbnR3ZWItMDEiLG5vbmNlPSJiQlQvaVhKWGpnM2ljeFdSSE5QUkQ1S mRIOTFPRFM4cVVteWlud1hGIixxb3A9ImF1dGgiLGNoYXJzZXQ9dXRmLTgsYWxnb3JpdGhtPW1k NS1zZXNz</
the failed authorization machine. All of the plugins are NOT loaded
and xmls recv output looks different. Does anyone have acceptable
dependency versions? Could this be a network issue? I worked hard to
get this working properly and to have it working in one environment
and not another is very frustrating. Any help would be much
appreciated.
Here is my successful output:
DEBUG Loaded Plugin (XEP-0030) Service Discovery
DEBUG Loaded Plugin (XEP-0045) Multi User Chat
DEBUG Loaded Plugin (XEP-0199) XMPP Ping
DEBUG Since no address is supplied,attempting SRV lookup.
DEBUG Loaded Plugin (XEP-0045) Multi User Chat
DEBUG Loaded Plugin (XEP-0199) XMPP Ping
WARNING server property deprecated. Use boundjid.host
DEBUG No appropriate SRV record found. Using JID server name.
DEBUG Connecting to 10.0.1.9:5222
DEBUG ==== TRANSITION disconnected -> connected
DEBUG Starting HANDLER THREAD
DEBUG Loading event runner
Done
DEBUG ==== TRANSITION disconnected -> connected
DEBUG Starting HANDLER THREAD
DEBUG Loading event runner
DEBUG SEND: <stream:stream to='10.0.1.9' xmlns:stream='http://
etherx.jabber.org/streams' xmlns='jabber:client' version='1.0'>
DEBUG RECV: <features xmlns="http://etherx.jabber.org/
streams"><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls" /
><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-
sasl"><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</
mechanism><mechanism>ANONYMOUS</mechanism><mechanism>CRAM-MD5</
mechanism></mechanisms><compression xmlns="http://jabber.org/features/
compress"><method>zlib</method></compression><auth xmlns="http://
jabber.org/features/iq-auth" /></features>
DEBUG SEND: <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls" />
DEBUG RECV: <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls" />
DEBUG Starting TLS
INFO Negotiating TLS
INFO Using SSL version: 1
DEBUG SEND: <stream:stream to='10.0.1.9' xmlns:stream='http://
DEBUG Starting TLS
INFO Negotiating TLS
INFO Using SSL version: 1
etherx.jabber.org/streams' xmlns='jabber:client' version='1.0'>
DEBUG RECV: <features xmlns="http://etherx.jabber.org/
streams"><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-
sasl"><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</
mechanism><mechanism>ANONYMOUS</mechanism><mechanism>CRAM-MD5</
mechanism></mechanisms><compression xmlns="http://jabber.org/features/
compress"><method>zlib</method></compression><auth xmlns="http://
jabber.org/features/iq-auth" /></features>
DEBUG Starting SASL Auth
DEBUG SEND: <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl'
mechanism='PLAIN'>AG10cnVtYmVsbABvcHRpb25zY2l0eQ==</auth>
DEBUG RECV: <success xmlns="urn:ietf:params:xml:ns:xmpp-sasl" />
DEBUG SEND: <stream:stream to='10.0.1.9' xmlns:stream='http://
etherx.jabber.org/streams' xmlns='jabber:client' version='1.0'>
DEBUG RECV: <features xmlns="http://etherx.jabber.org/
streams"><compression xmlns="http://jabber.org/features/
compress"><method>zlib</method></compression><bind
xmlns="urn:ietf:params:xml:ns:xmpp-bind" /><session
xmlns="urn:ietf:params:xml:ns:xmpp-session" /></features>
DEBUG Requesting resource:
DEBUG SEND: <iq type="set" id="1"><bind
xmlns="urn:ietf:params:xml:ns:xmpp-bind" /></iq>
DEBUG RECV: <iq to="chi-intweb-01/7c6646e5" type="result"
id="1"><bind xmlns="urn:ietf:params:xml:ns:xmpp-
bind"><jid>mtrumbell@chi-intweb-01/7c6646e5</jid></bind></iq>
DEBUG setting jid to mtrumbell@chi-intweb-01/7c6646e5
INFO Node set to: None
DEBUG SEND: <iq type="set" id="2"><session
xmlns="urn:ietf:params:xml:ns:xmpp-session" /></iq>
DEBUG RECV: <iq to="mtrumbell@chi-intweb-01/7c6646e5" type="result"
id="2"><session xmlns="urn:ietf:params:xml:ns:xmpp-session" /></iq>
DEBUG Established Session
DEBUG SEND: <presence to="sup...@optionscity.chi-intweb-01/
SupportServices" from="mtrumbell@chi-intweb-01/7c6646e5"><x
xmlns="http://jabber.org/protocol/muc"><history maxchars="0" /></x></
presence>
DEBUG SEND: <message to="sup...@optionscity.chi-intweb-01"
type="groupchat"><body>test</body></message>
DEBUG SEND: </stream:stream>
DEBUG RECV: <presence to="mtrumbell@chi-intweb-01/7c6646e5"
from="sup...@optionscity.chi-intweb-01/rfasouliotis"><show>away</
show><status>I'm not here right now</status><query
xmlns="jabber:iq:last" seconds="128083" /><c xmlns="http://jabber.org/
protocol/caps" node="http://pidgin.im/" ver="AcN1/PEN8nq7AHD
+9jpxMV4U6YM=" ext="voice-v1 camera-v1 video-v1" hash="sha-1" /><x
xmlns="http://jabber.org/protocol/muc#user"><item affiliation="owner"
role="moderator" /></x></presence>
DEBUG RECV: <presence to="mtrumbell@chi-intweb-01/7c6646e5"
from="sup...@optionscity.chi-intweb-01/SupportServices"><x
xmlns="http://jabber.org/protocol/muc#user"><item affiliation="member"
jid="mtrumbell@chi-intweb-01/7c6646e5" role="participant" /></x></
presence>
DEBUG RECV: <message to="mtrumbell@chi-intweb-01/7c6646e5"
type="groupchat" from="sup...@optionscity.chi-intweb-01/
SupportServices"><body>test</body></message>
DEBUG End of stream recieved
DEBUG Could not acquire lock
DEBUG ==== TRANSITION connected -> disconnected
DEBUG Quitting Scheduler thread
DEBUG Could not acquire lock
DEBUG ==== TRANSITION connected -> disconnected
DEBUG Quitting Scheduler thread
On Jan 21, 3:07 pm, mIKE <mich...@trumbell.net> wrote:
> Once I got this working on my development machine (Ubuntu) I tried it
> on my production server (CentoOS) and I'm getting authentication
> errors. Could this be an issue with the OS or potentially some out of
> date dependencies?
>
> DEBUG setting jid to mtrumb...@10.0.1.9
> Once I got this working on my development machine (Ubuntu) I tried it
> on my production server (CentoOS) and I'm getting authentication
> errors. Could this be an issue with the OS or potentially some out of
> date dependencies?
>
> challenge>
> DEBUG SEND (IMMED): <response xmlns="urn:ietf:params:xml:ns:xmpp-
> sasl">dXNlcm5hbWU9Im10cnVtYmVsbCIsbm9uY2U9ImJCVC9pWEpYamczaWN4V1JITlBSRDVKZ Eg5MU9EUzhxVW15aW53WEYiLHJlYWxtPSJjaGktaW50d2ViLTAxIixxb3A9YXV0aCxjbm9uY2U9 IjAwNDIzNDk2MjQ5NTIxIixuYz0wMDAwMDAwMSxkaWdlc3QtdXJpPSJ4bXBwLzEwLjAuMS45Iix yZXNwb25zZT04Y2M4NTc3NDVhN2VhNjU5NmZlMTM3ZmMwYzFjOWZkMg==</
> DEBUG SEND (IMMED): <response xmlns="urn:ietf:params:xml:ns:xmpp-
Lance Stout
Jan 22, 2012, 12:08:24 PM1/22/12
to sleekxmpp-...@googlegroups.com
Which Python versions are you using, and what was the failed output?
A dependency issue would be surprising since we only depend on the
standard lib, but I suppose it could happen.
mIKE
Jan 22, 2012, 12:30:04 PM1/22/12
to SleekXMPP Discussion
Thanks for getting back to me, Lance. I just realized the 2 python
versions are different.
Working version: 2.6.6 (r266:84292, Sep 15 2010, 16:22:56)
Non-working version: 2.6 (r26:66714, May 17 2011, 15:33:27)
The failed output is:
DEBUG setting jid to ta...@10.0.1.9
sasl">cmVhbG09ImNoaS1pbnR3ZWItMDEiLG5vbmNlPSJIQlZCQUtMR0RTSTVsSTQ5MDF3UkFHV3NMa2hvck5tUnlmWi9GT3VCIixxb3A9ImF1dGgiLGNoYXJzZXQ9dXRmLTgsYWxnb3JpdGhtPW1kNS1zZXNz</
DEBUG Waiting for </stream:stream> from server
ERROR no element found: line 1, column 846
Traceback (most recent call last):
File "build/bdist.linux-x86_64/egg/sleekxmpp/xmlstream/
xmlstream.py", line 1150, in _process
if not self.__read_xml():
File "build/bdist.linux-x86_64/egg/sleekxmpp/xmlstream/
xmlstream.py", line 1186, in __read_xml
for event, xml in ET.iterparse(self.filesocket, (b'end',
b'start')):
File "<string>", line 68, in __iter__
SyntaxError: no element found: line 1, column 846
DEBUG State was not ready
DEBUG Quitting Scheduler thread
On Jan 22, 11:08 am, Lance Stout <lancest...@gmail.com> wrote:
> Which Python versions are you using, and what was the failed output?
>
> A dependency issue would be surprising since we only depend on the
> standard lib, but I suppose it could happen.
>
> > DEBUG SEND: <presence to="supp...@optionscity.chi-intweb-01/
> ...
>
> read more »
>
> smime.p7s
> 8KViewDownload
versions are different.
Working version: 2.6.6 (r266:84292, Sep 15 2010, 16:22:56)
Non-working version: 2.6 (r26:66714, May 17 2011, 15:33:27)
The failed output is:
DEBUG setting jid to ta...@10.0.1.9
DEBUG Loaded Plugin (RFC-6120) STARTTLS Stream Feature
DEBUG Loaded Plugin (RFC-6120) Resource Binding Stream Feature
DEBUG Loaded Plugin (RFC-3920) Start Session Stream Feature
DEBUG Loaded Plugin (RFC-6120) SASL Stream Feature
DEBUG Loaded Plugin (XEP-0030) Service Discovery
DEBUG Loaded Plugin (XEP-0045) Multi User Chat
DEBUG Loaded Plugin (XEP-0199) XMPP Ping
DEBUG Connecting to 10.0.1.9:5222
DEBUG ==== TRANSITION disconnected -> connected
DEBUG Starting HANDLER THREAD
DEBUG Loading event runner
Done
DEBUG Loaded Plugin (RFC-6120) Resource Binding Stream Feature
DEBUG Loaded Plugin (RFC-3920) Start Session Stream Feature
DEBUG Loaded Plugin (RFC-6120) SASL Stream Feature
DEBUG Loaded Plugin (XEP-0030) Service Discovery
DEBUG Loaded Plugin (XEP-0045) Multi User Chat
DEBUG Loaded Plugin (XEP-0199) XMPP Ping
DEBUG Connecting to 10.0.1.9:5222
DEBUG ==== TRANSITION disconnected -> connected
DEBUG Starting HANDLER THREAD
DEBUG Loading event runner
challenge>
DEBUG SEND (IMMED): <response xmlns="urn:ietf:params:xml:ns:xmpp-
sasl">dXNlcm5hbWU9InRhc3QiLG5vbmNlPSJIQlZCQUtMR0RTSTVsSTQ5MDF3UkFHV3NMa2hvck5tUnlmWi9GT3VCIixyZWFsbT0iY2hpLWludHdlYi0wMSIscW9wPWF1dGgsY25vbmNlPSIzNTk0MjQyNjgzNTgiLG5jPTAwMDAwMDAxLGRpZ2VzdC11cmk9InhtcHAvMTAuMC4xLjkiLHJlc3BvbnNlPTg0YWVhODUxZDVkODI5OWJhNTM5MGZkYjQwYTNmNzc5</
DEBUG SEND (IMMED): <response xmlns="urn:ietf:params:xml:ns:xmpp-
response>
DEBUG RECV: <failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-
authorized /></failure>
INFO Authentication failed: not-authorized
DEBUG SEND (IMMED): </stream:stream>
DEBUG RECV: <failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-
authorized /></failure>
INFO Authentication failed: not-authorized
DEBUG Waiting for </stream:stream> from server
DEBUG ==== TRANSITION connected -> disconnected
ERROR Error reading from XML stream.
ERROR no element found: line 1, column 846
Traceback (most recent call last):
File "build/bdist.linux-x86_64/egg/sleekxmpp/xmlstream/
xmlstream.py", line 1150, in _process
if not self.__read_xml():
File "build/bdist.linux-x86_64/egg/sleekxmpp/xmlstream/
xmlstream.py", line 1186, in __read_xml
for event, xml in ET.iterparse(self.filesocket, (b'end',
b'start')):
File "<string>", line 68, in __iter__
SyntaxError: no element found: line 1, column 846
DEBUG State was not ready
DEBUG Quitting Scheduler thread
On Jan 22, 11:08 am, Lance Stout <lancest...@gmail.com> wrote:
> Which Python versions are you using, and what was the failed output?
>
> A dependency issue would be surprising since we only depend on the
> standard lib, but I suppose it could happen.
>
> On Jan 22, 2012, at 7:57 AM, mIKE <mich...@trumbell.net> wrote:
>
>
>
>
>
>
>
> > When this works on my dev machine the log looks much different than
> > the failed authorization machine. All of the plugins are NOT loaded
> > and xmls recv output looks different. Does anyone have acceptable
> > dependency versions? Could this be a network issue? I worked hard to
> > get this working properly and to have it working in one environment
> > and not another is very frustrating. Any help would be much
> > appreciated.
>
> > Here is my successful output:
>
> > DEBUG setting jid to mtrumb...@10.0.1.9
>
>
>
>
>
>
>
> > When this works on my dev machine the log looks much different than
> > the failed authorization machine. All of the plugins are NOT loaded
> > and xmls recv output looks different. Does anyone have acceptable
> > dependency versions? Could this be a network issue? I worked hard to
> > get this working properly and to have it working in one environment
> > and not another is very frustrating. Any help would be much
> > appreciated.
>
> > Here is my successful output:
>
> > SupportServices" from="mtrumbell@chi-intweb-01/7c6646e5"><x
> > xmlns="http://jabber.org/protocol/muc"><history maxchars="0" /></x></
> > presence>
> > DEBUG SEND: <message to="supp...@optionscity.chi-intweb-01"
> > xmlns="http://jabber.org/protocol/muc"><history maxchars="0" /></x></
> > presence>
> > type="groupchat"><body>test</body></message>
> > DEBUG SEND: </stream:stream>
> > DEBUG RECV: <presence to="mtrumbell@chi-intweb-01/7c6646e5"
> > from="supp...@optionscity.chi-intweb-01/rfasouliotis"><show>away</
> > DEBUG SEND: </stream:stream>
> > DEBUG RECV: <presence to="mtrumbell@chi-intweb-01/7c6646e5"
> > show><status>I'm not here right now</status><query
> > xmlns="jabber:iq:last" seconds="128083" /><c xmlns="http://jabber.org/
> > protocol/caps" node="http://pidgin.im/" ver="AcN1/PEN8nq7AHD
> > +9jpxMV4U6YM=" ext="voice-v1 camera-v1 video-v1" hash="sha-1" /><x
> > xmlns="http://jabber.org/protocol/muc#user"><item affiliation="owner"
> > role="moderator" /></x></presence>
> > DEBUG RECV: <presence to="mtrumbell@chi-intweb-01/7c6646e5"
> > from="supp...@optionscity.chi-intweb-01/SupportServices"><x
> > xmlns="jabber:iq:last" seconds="128083" /><c xmlns="http://jabber.org/
> > protocol/caps" node="http://pidgin.im/" ver="AcN1/PEN8nq7AHD
> > +9jpxMV4U6YM=" ext="voice-v1 camera-v1 video-v1" hash="sha-1" /><x
> > xmlns="http://jabber.org/protocol/muc#user"><item affiliation="owner"
> > role="moderator" /></x></presence>
> > DEBUG RECV: <presence to="mtrumbell@chi-intweb-01/7c6646e5"
> > xmlns="http://jabber.org/protocol/muc#user"><item affiliation="member"
> > jid="mtrumbell@chi-intweb-01/7c6646e5" role="participant" /></x></
> > presence>
> > DEBUG RECV: <message to="mtrumbell@chi-intweb-01/7c6646e5"
> > type="groupchat" from="supp...@optionscity.chi-intweb-01/
> > jid="mtrumbell@chi-intweb-01/7c6646e5" role="participant" /></x></
> > presence>
> > DEBUG RECV: <message to="mtrumbell@chi-intweb-01/7c6646e5"
>
> read more »
>
> smime.p7s
> 8KViewDownload
Lance Stout
Jan 22, 2012, 12:37:27 PM1/22/12
to sleekxmpp-...@googlegroups.com
Ok, it looks like the DIGEST-MD5 isnt working properly, and your
working version skips it for PLAIN.
working version skips it for PLAIN.
If you're ok with using plain, you can force using it by passing
use_mech="PLAIN" in the ClientXMPP constructor, and that should take
care of the problem.
I will have to do some debugging to see why your client is picking
different SASL mechs.
mIKE
Jan 22, 2012, 1:06:21 PM1/22/12
to SleekXMPP Discussion
Thanks, Lance. Can you post a snippet on how to apply
use_mech="PLAIN" in the ClientXMPP constructor?
Thanks again.
On Jan 22, 11:37 am, Lance Stout <lancest...@gmail.com> wrote:
> Ok, it looks like the DIGEST-MD5 isnt working properly, and your
> working version skips it for PLAIN.
>
> If you're ok with using plain, you can force using it by passing
> use_mech="PLAIN" in the ClientXMPP constructor, and that should take
> care of the problem.
>
> I will have to do some debugging to see why your client is picking
> different SASL mechs.
>
> > sasl">cmVhbG09ImNoaS1pbnR3ZWItMDEiLG5vbmNlPSJIQlZCQUtMR0RTSTVsSTQ5MDF3UkFHV 3NMa2hvck5tUnlmWi9GT3VCIixxb3A9ImF1dGgiLGNoYXJzZXQ9dXRmLTgsYWxnb3JpdGhtPW1k NS1zZXNz</
use_mech="PLAIN" in the ClientXMPP constructor?
Thanks again.
On Jan 22, 11:37 am, Lance Stout <lancest...@gmail.com> wrote:
> Ok, it looks like the DIGEST-MD5 isnt working properly, and your
> working version skips it for PLAIN.
>
> If you're ok with using plain, you can force using it by passing
> use_mech="PLAIN" in the ClientXMPP constructor, and that should take
> care of the problem.
>
> I will have to do some debugging to see why your client is picking
> different SASL mechs.
>
> On Jan 22, 2012, at 9:30 AM, mIKE <mich...@trumbell.net> wrote:
>
>
>
>
>
>
>
> > Thanks for getting back to me, Lance. I just realized the 2 python
> > versions are different.
>
> > Working version: 2.6.6 (r266:84292, Sep 15 2010, 16:22:56)
> > Non-working version: 2.6 (r26:66714, May 17 2011, 15:33:27)
>
> > The failed output is:
> > DEBUG setting jid to t...@10.0.1.9
>
>
>
>
>
>
>
> > Thanks for getting back to me, Lance. I just realized the 2 python
> > versions are different.
>
> > Working version: 2.6.6 (r266:84292, Sep 15 2010, 16:22:56)
> > Non-working version: 2.6 (r26:66714, May 17 2011, 15:33:27)
>
> > The failed output is:
> > challenge>
> > DEBUG SEND (IMMED): <response xmlns="urn:ietf:params:xml:ns:xmpp-
> > sasl">dXNlcm5hbWU9InRhc3QiLG5vbmNlPSJIQlZCQUtMR0RTSTVsSTQ5MDF3UkFHV3NMa2hvc k5tUnlmWi9GT3VCIixyZWFsbT0iY2hpLWludHdlYi0wMSIscW9wPWF1dGgsY25vbmNlPSIzNTk0 MjQyNjgzNTgiLG5jPTAwMDAwMDAxLGRpZ2VzdC11cmk9InhtcHAvMTAuMC4xLjkiLHJlc3BvbnN lPTg0YWVhODUxZDVkODI5OWJhNTM5MGZkYjQwYTNmNzc5</
> > DEBUG SEND (IMMED): <response xmlns="urn:ietf:params:xml:ns:xmpp-
Lance Stout
Jan 22, 2012, 1:14:06 PM1/22/12
to sleekxmpp-...@googlegroups.com
ClientXMPP('som...@example.com', 'password', use_mech="PLAIN")
Or, if using a custom class:
super(MyClass, self).__init__('som...@example.com', 'password',
use_mech="PLAIN")
mIKE
Jan 22, 2012, 1:26:26 PM1/22/12
to SleekXMPP Discussion
I get this:
(Pdb) ClientXMPP('my_...@10.0.1.9', 'my_pass', use_mech="PLAIN")
*** TypeError: __init__() got an unexpected keyword argument
'use_mech'
On Jan 22, 12:14 pm, Lance Stout <lancest...@gmail.com> wrote:
> ClientXMPP('some...@example.com', 'password', use_mech="PLAIN")
> use_mech="PLAIN")
(Pdb) ClientXMPP('my_...@10.0.1.9', 'my_pass', use_mech="PLAIN")
*** TypeError: __init__() got an unexpected keyword argument
'use_mech'
On Jan 22, 12:14 pm, Lance Stout <lancest...@gmail.com> wrote:
> ClientXMPP('some...@example.com', 'password', use_mech="PLAIN")
>
> Or, if using a custom class:
>
> super(MyClass, self).__init__('some...@example.com', 'password',
> Or, if using a custom class:
>
> use_mech="PLAIN")
Lance Stout
Jan 22, 2012, 1:29:26 PM1/22/12
to sleekxmpp-...@googlegroups.com
Gah, that was supposed to be sasl_mech="PLAIN"
mIKE
Jan 22, 2012, 3:38:07 PM1/22/12
to SleekXMPP Discussion
This fixed my ERRORs but the message never reached the group chat. On
the working machine I was unable to sasl_mech="PLAIN" as the version
of sleekxmpp I was using didn't yet support it.
The good news is when I replaced the egg on the machine that was not
working with this older version, my code worked.
Seems like there may be some sasl issues with openfire? Not sure.
Thanks for the help, guys.
-Mike
On Jan 22, 12:29 pm, Lance Stout <lancest...@gmail.com> wrote:
> Gah, that was supposed to be sasl_mech="PLAIN"
>
> > (Pdb) ClientXMPP('my_u...@10.0.1.9', 'my_pass', use_mech="PLAIN")
the working machine I was unable to sasl_mech="PLAIN" as the version
of sleekxmpp I was using didn't yet support it.
The good news is when I replaced the egg on the machine that was not
working with this older version, my code worked.
Seems like there may be some sasl issues with openfire? Not sure.
Thanks for the help, guys.
-Mike
On Jan 22, 12:29 pm, Lance Stout <lancest...@gmail.com> wrote:
> Gah, that was supposed to be sasl_mech="PLAIN"
>
Reply all
Reply to author
Forward
0 new messages