XMPP Service Operators - 2020-04-28

Would someone with a cisco account mind providing some firmware files for me?

eww

Link Mauve are you still using Prosody with Arch by any chance?

Yes.

Link Mauve, still experiencing those random crashes?

IIRC most random crashes were related to lua-event.

Maranda, the infinite loops we have lately are related to Stream Management, mod_limits, as well as mod_cloud_notify.

Not crashes per se.

Link Mauve: I'm really curious what kind of IQ set it was.

Ge0rG, this kind: https://xmpp.org/extensions/xep-0357.xml#example-12

Link Mauve: ah, right.

I also have accounts with their full JID as the push target

one of them is even logged in

why am I not crashing yet?

if they were crashes it wouldn't be a problem as I set metronomectl to automatically call a restart on defined intervals, but it just hangs there queuing connections. And it all started when I modified the service account to allow it to use the ssh-agent and enabled account lingering

it only registered 20mins ago. It will crash my server any time now!

so I have two culprit being possible, one malloc() with util.signal which should be sorted

and the other being lua-event in some other way

Link Mauve: 12:21:07 Ge0rG> iNPUTmice: when will it do that? 12:21:29 iNPUTmice> i haven’t reproduced but I think if you try to join your own jid as a room

Link Mauve, this issue of yours mostly picked up my curiousity https://issues.prosody.im/1295

Link Mauve: I can confirm that from my logs. Also loaded your module.

But I still need to kill that user somehow

killed the session, removed the cloud_notify property. Server still running. Phew.

Ge0rG, for now I unloaded mod_smacks, but that’s only temporary.

Link Mauve: wasn't it triggered by mod_clown_notify?

I think so, but maybe not only.

Another failure, three days before, was an infinite loop in mod_smacks, triggered by a Gajim user.

And those don’t AFAIK do clown stuff.

yeah, right

Link Mauve, and nm not related to anything it looks to be a deadlock