search

ChatSecure / ChatSecure-iOS

ChatSecure is a free and open source encrypted chat client for iOS that supports OTR and OMEMO encryption over XMPP.
https://chatsecure.org
Other
3.13k stars 1.03k forks source link

The client says it handled (n) new stanzas, but we only sent (n-m) :) #979

Open jotwewe opened 6 years ago

jotwewe commented 6 years ago

Since there is a Chatsecure user connected to my prosody 0.10 server, prosody issues warnings like this:

The client says it handled 7 new stanzas, but we only sent 6 :)

The "sent" count is one or more less than what the client says to have handled.

Users connected with conversations, swift, psi-plus, dino and sleekxmpp before and I have never seen this warning until the chatsecure user connected.

A typical log of events after I sent a message to this chatsecure user:

Mar 25 21:55:04 host.de:cloud_notify Sending push notification for user@host.de to pubsub.chatsecure.org (some string) Mar 25 21:55:06 c2s562ed7954710 Authenticated as user@host.de Mar 25 21:55:08 c2s562ed7954710 The client says it handled 5 new stanzas, but we only sent 4 :) Mar 25 21:55:09 c2s562ed7954710 Attempting to enable push notifications Mar 25 21:55:09 c2s562ed7954710 Push notifications enabled for user@host.de/chatsecure30149 (pubsub.chatsecure.org<some string) Mar 25 21:55:10 c2s562ed7954710 The client says it handled 7 new stanzas, but we only sent 6 :)

This does not seem to be a problem for prosody, but maybe it points to something important nonetheless...

Loader23 commented 6 years ago

Iam also curious about these entrys :-)

licaon-kter commented 6 years ago

Seeing the same on the latest ejabberd

[warning] <0.1306.0>@mod_stream_mgmt:check_h_attribute:473 jid1@mydomain.tld/chatsecure12345 acknowledged 29 stanzas, but only 28 were sent
[info] <0.1306.0>@ejabberd_c2s:process_terminated:270 (tls|<0.1306.0>) Closing c2s session for jid1@mydomain.tld/chatsecure12345: Stream closed by us: Client acknowledged more stanzas than sent by server (undefined-condition)

[warning] <0.1558.0>@mod_stream_mgmt:check_h_attribute:473 jid1@mydomain.tld/chatsecure12345 acknowledged 31 stanzas, but only 29 were sent
[info] <0.1558.0>@ejabberd_c2s:process_terminated:270 (tls|<0.1558.0>) Closing c2s session for jid1@mydomain.tld/chatsecure12345: Stream closed by us: Client acknowledged more stanzas than sent by server (undefined-condition)

[warning] <0.1576.0>@mod_stream_mgmt:check_h_attribute:473 jid1@mydomain.tld/chatsecure12345 acknowledged 186 stanzas, but only 185 were sent
[info] <0.1576.0>@ejabberd_c2s:process_terminated:270 (tls|<0.1576.0>) Closing c2s session for jid1@mydomain.tld/chatsecure12345: Stream closed by us: Client acknowledged more stanzas than sent by server (undefined-condition)

[warning] <0.2829.0>@mod_stream_mgmt:check_h_attribute:473 jid1@mydomain.tld/chatsecure12345 acknowledged 31 stanzas, but only 30 were sent
[info] <0.2829.0>@ejabberd_c2s:process_terminated:270 (tls|<0.2829.0>) Closing c2s session for jid1@mydomain.tld/chatsecure12345: Stream closed by us: Client acknowledged more stanzas than sent by server (undefined-condition)
weiss commented 6 years ago

The problem has been tracked down and described in an XMPPFramework issue by @GlacierSecurityInc (many thanks!).