psi-im / psi

XMPP client
https://psi-im.org/
Other
404 stars 122 forks source link

Since several builds, I have a lag when I check my personal vCard (Self contact vCard) #837

Open Neustradamus opened 5 months ago

Neustradamus commented 5 months ago

Since several builds, I have a lag when I do "Retrieve" on my personal vCard (Self contact vCard). The first may work but if I do a new time "Retrieve", there is no ending.

When I send messages after it, there is a problem:

In more, I see that when we have in Roster, contacts with S2S XMPP server problem (temporary down, dead XMPP services, ...), for example:

<presence type="error" from="acontact@domain.tld" to="myself@adomain.tld/client" xml:lang="en">
<c xmlns="http://jabber.org/protocol/caps" hash="sha-1" node="https://psi-plus.com" ver="XXXXXXXXXXXXXXXXXXXXXXXXX"/>
<x xmlns="vcard-temp:x:update">
<photo/>
</x>
<error type="wait">
<remote-server-timeout xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
<text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en">Connection failed: unknown POSIX error: timeout</text>
</error>
<priority>1</priority>
<show>away</show>
</presence>
<presence type="error" from="acontact@domain.tld" to="myself@adomain.tld/client" xml:lang="en">
<c xmlns="http://jabber.org/protocol/caps" hash="sha-1" node="https://psi-plus.com" ver="XXXXXXXXXXXXXXXXXXXXXXXXX"/>
<x xmlns="vcard-temp:x:update">
<photo/>
</x>
<error type="wait">
<remote-server-timeout xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
<text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en">Stream closed by peer: This host does not serve domain.tld (host-unknown)</text>
</error>
<priority>1</priority>
<show>away</show>
</presence>
<presence type="error" from="acontact@domain.tld" to="myself@adomain.tld/client">
<error type="cancel" by="jabber.org">
<remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
<text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">Server-to-server connection failed: connection timeout</text>
</error>
</presence>
Ri0n commented 5 months ago

Looks like some server bug. Or s2s problem

Neustradamus commented 5 months ago

Currently, I have the lag.

I have found a linked problem, I have left all MUC Rooms but I have from MUC Rooms, for example:

<presence to="me@domain.tld/client" from="ejabberd@conference.process-one.net/user" xml:lang="en" id="XXXXXXXXXXXXXXXXXXXXXX">
<idle xmlns="urn:xmpp:idle:1" since="2024-06-21TXX:XX:XXZ"/>
<c xmlns="http://jabber.org/protocol/caps" ver="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" node="https://gajim.org" hash="sha-1"/>
<x xmlns="vcard-temp:x:update">
<photo/>
</x>
<occupant-id xmlns="urn:xmpp:occupant-id:0" id="XXXXXXXXXXXX"/>
<x xmlns="http://jabber.org/protocol/muc#user">
<item role="participant" affiliation="none"/>
</x>
<show>away</show>
</presence>

@stpeter manages the jabber.org XMPP Public Service.

stpeter commented 5 months ago

This is not the problem that we saw with Psi+ nightly on jabber.org on 2024-06-12 / 2024-06-13. At that time, Neustradamus was sending a very large number of presence stanzas (e.g., 41k stanzas in 5 minutes). After we instituted rate limits, the server was able to recover.

Ri0n commented 5 months ago

I don't really know how to reproduce. I pushed retrieve button dozens of times last days while implementing vcard4. Never seen anything like this with recent builds. So maybe it's some combination of settings and plugins.. @Neustradamus, try to disable all plugins in a new profile and recheck

Neustradamus commented 5 months ago

@Ri0n: I have done it few seconds ago, @stpeter can look logs... Note: In this case, I have left a lot of MUC Rooms.

Neustradamus commented 4 months ago

@stpeter: It is possible to look?