Auto logout after a while?

22 views
Skip to first unread message

segura...@gmail.com

unread,
Jul 18, 2016, 11:56:55 AM7/18/16
to profanity development
Hey Guys,
Im starting to use profanity. its looks great but after join to a chatroom sucessfully, the chatroom windows it closes and when I try to join to the room again nothing seems happen.
What Im missing?
Marco

Boothj5

unread,
Jul 18, 2016, 4:05:53 PM7/18/16
to profanity development, segura...@gmail.com
If the connection is lost, the room windows should stay open, and after reconnect you should be able to send message as usual. Some commands that might help:

http://www.profanity.im/reference.html#autoping
http://www.profanity.im/reference.html#reconnect

If you can supply some logs I can take a look and see whats happening:

http://www.profanity.im/issues.html#proflogs

Don't forget to remove anything sensitive.

Thanks.

Marco Segura

unread,
Jul 19, 2016, 3:38:20 PM7/19/16
to Boothj5, profanity development
Thanks for your help. I've tried to set this parameters but still I was dropped of the room after a while. Here you can find the log when I was dropped.

19/07/2016 09:02:31: prof: DBG: Autoping: Sending ping request: prof_ping_17
19/07/2016 09:02:31: conn: DBG: SENT: <iq id="prof_ping_17" type="get"><ping xmlns="urn:xmpp:ping"/></iq>
19/07/2016 09:02:33: xmpp: DBG: RECV: <iq id="prof_ping_17" type="result" to="myu...@lol.com/profanity"/>
19/07/2016 09:02:33: prof: DBG: iq stanza handler fired
19/07/2016 09:02:33: prof: DBG: Autoping: Pong handler fired: prof_ping_17.
19/07/2016 09:02:37: prof: DBG: Autoping: Sending ping request: prof_ping_18
19/07/2016 09:02:37: conn: DBG: SENT: <iq id="prof_ping_18" type="get"><ping xmlns="urn:xmpp:ping"/></iq>
19/07/2016 09:02:39: xmpp: DBG: RECV: <iq id="prof_ping_18" type="result" to="myu...@lol.com/profanity"/>
19/07/2016 09:02:39: prof: DBG: iq stanza handler fired
19/07/2016 09:02:39: prof: DBG: Autoping: Pong handler fired: prof_ping_18.
19/07/2016 09:02:43: prof: DBG: Autoping: Sending ping request: prof_ping_19
19/07/2016 09:02:43: conn: DBG: SENT: <iq id="prof_ping_19" type="get"><ping xmlns="urn:xmpp:ping"/></iq>
19/07/2016 09:02:43: xmpp: DBG: RECV: <presence type="unavailable" to="z...@conference.lol.com/myuser" from="myr...@conference.lol.com/otheruser"><x xmlns="http://jabber.org/protocol/muc#user"><item role="none" jid="othe...@lol.com" affiliation="none"/><status code="110"/></x></presence>
19/07/2016 09:02:43: prof: DBG: Presence stanza handler fired
19/07/2016 09:02:43: prof: DBG: Unavailable presence handler fired for myr...@conference.lol.com/otheruser
19/07/2016 09:02:43: prof: DBG: Room self presence received from myr...@conference.lol.com/otheruser
19/07/2016 09:02:43: xmpp: DBG: RECV: <iq id="prof_ping_19" type="result" to="myu...@lol.com/profanity"/>
19/07/2016 09:02:43: prof: DBG: iq stanza handler fired
19/07/2016 09:02:43: prof: DBG: Autoping: Pong handler fired: prof_ping_19.
19/07/2016 09:02:48: prof: DBG: Autoping: Sending ping request: prof_ping_20
19/07/2016 09:02:48: conn: DBG: SENT: <iq id="prof_ping_20" type="get"><ping xmlns="urn:xmpp:ping"/></iq>
19/07/2016 09:02:48: xmpp: DBG: RECV: <iq id="prof_ping_20" type="result" to="myu...@lol.com/profanity"/>
19/07/2016 09:02:48: prof: DBG: iq stanza handler fired
19/07/2016 09:02:48: prof: DBG: Autoping: Pong handler fired: prof_ping_20.

After this there is no way to join again to the room :(

Thanks again,
Marco

Boothj5

unread,
Jul 19, 2016, 3:51:05 PM7/19/16
to profanity development, boo...@gmail.com, segura...@gmail.com
The relevant line in the logs is:


19/07/2016 09:02:43: xmpp: DBG: RECV: <presence type="unavailable" to="z...@conference.lol.com/myuser" from="myr...@conference.lol.com/otheruser"><x xmlns="http://jabber.org/protocol/muc#user"><item role="none" jid="othe...@lol.com" affiliation="none"/><status code="110"/></x></presence>

This means that othe...@lol.com has left the room, the status code 110 means that this is a self presence, i.e. it is you who have left the room.  If your Jabber ID is not othe...@lol.com then this appears to be an issue with the server.

So for some reason the server has informed Profanity that you have left the room, which is why the room window closes.

Do you have any logs from when you are trying to rejoin the room?

Boothj5

unread,
Jul 19, 2016, 6:16:04 PM7/19/16
to profanity development, boo...@gmail.com, segura...@gmail.com
Based on your logs below, profanity sends the join request, but does not hear back from the server.

So it looks like your server is removing you from the room, and then not letting you rejoin.  Have you tried with any other clients?

From your response:

19/07/2016 16:41:53: prof: DBG: Input received: /join myroom
19/07/2016 16:41:53: prof: DBG: Sending room join presence to: myr...@conference.lol.com/mysuser
19/07/2016 16:41:53: conn: DBG: SENT: <presence id="prof_join_30" to="myr...@conference.lol.com/mysuser"><x xmlns="http://jabber.org/protocol/muc"/><c hash="sha-1" xmlns="http://jabber.org/protocol/caps" ver="JHAKN8yAVmq16LX5jTl2HYcJdiY=" node="http://www.profanity.im"/></presence>
19/07/2016 16:41:55: prof: DBG: Autoping: Sending ping request: prof_ping_31
19/07/2016 16:41:55: conn: DBG: SENT: <iq id="prof_ping_31" type="get"><ping xmlns="urn:xmpp:ping"/></iq>
19/07/2016 16:41:55: xmpp: DBG: RECV: <iq id="prof_ping_31" type="result" to="mys...@lol.com/profanity"/>
19/07/2016 16:41:55: prof: DBG: iq stanza handler fired
19/07/2016 16:41:55: prof: DBG: Autoping: Pong handler fired: prof_ping_31.
19/07/2016 16:42:00: prof: DBG: Autoping: Sending ping request: prof_ping_32
19/07/2016 16:42:00: conn: DBG: SENT: <iq id="prof_ping_32" type="get"><ping xmlns="urn:xmpp:ping"/></iq>
19/07/2016 16:42:01: xmpp: DBG: RECV: <iq id="prof_ping_32" type="result" to="mys...@lol.com/profanity"/>
19/07/2016 16:42:01: prof: DBG: iq stanza handler fired
19/07/2016 16:42:01: prof: DBG: Autoping: Pong handler fired: prof_ping_32.
Reply all
Reply to author
Forward
0 new messages