On Tue, 13 Jan 2015, at 01:20 PM, Peter Saint-Andre - &yet wrote: > I do have access to the logs and will send along what I have.
Thanks Peter, this is exactly what I needed. Fyi, the offending bit: stream4 debug IN: <?xml version="1.0" encoding="UTF-8"?><stream:stream version="1.0" xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client" from="betachat.messagingengine.com" id="317607850.1421109523"><stream:features><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>LOGIN</mechanism></mechanisms></stream:features> stream4 debug Firing event: outgoing stream4 debug Firing event: outgoing-raw stream4 debug OUT: </stream:stream> stream4 debug Firing event: drained socket debug server.lua: clienttable: 0xb651ddc0 SSL connection: 0xb65222a8 stream4 debug Firing event: incoming-raw stream4 debug Firing event: stream-error verse error Error: /opt/xmppoke/bin/xmppoke:3516: undefined-condition verse error Traceback: stack traceback: /opt/xmppoke/bin/xmppoke:3289: in function </opt/xmppoke/bin/xmppoke:3287> [C]: in function 'feed' /opt/xmppoke/bin/xmppoke:3541: in function </opt/xmppoke/bin/xmppoke:3540> /opt/xmppoke/bin/xmppoke:2742: in function 'event' /opt/xmppoke/bin/xmppoke:3434: in function 'readbuffer' /opt/xmppoke/bin/xmppoke:2210: in function </opt/xmppoke/bin/xmppoke:2192> [C]: in function 'loop' /opt/xmppoke/bin/xmppoke:6909: in main chunk [C]: at 0x0804bbf0 The bug on my end is that </stream:stream> got interpreted as an unknown element, and resulted in an undefined-condition error being issued. The bug on your (xmppoke's) end is that it crashed when it recieved an undefined-condition error :) I'll fix mine tonight and test again. Cheers, Rob N.
