Paweł Chmielowski

That would fix that problem, but that's not correct solution here. I think this is result of buggy client, looks like it start sending message, before it finishes session initialization...

Hm, interesting, would you be able to capture session traffic when this happen, so i could see when we are receiving this? At this point session i think shouldn't be...

That's by design, this field was reused to mark room hibernation time

It just sentinel value for room that are not hibernated. This was done as part of optimization for commands that delete unused rooms, having this as separate column allowed as...

We probably could also exec erl when called with foreground options, i don't think we do any cleanup when erl finishes, and this will allow erlang to inherite ejabberdctl pid.

You could try to whitelist ip addresses in fail2ban to make them never be blocked (mod_fail2ban has access option for that). Now for changing our handling of db error, we...

My guess is that your client is sending presence from unload or some other hook when you close tab (maybe with away status?), and since this is positive priority presence...

Also i just checked with my own websocket using client - offline message are still here after websocket is closed.

Yes

Are your client use anonymous authentication? If so then it's expected that there is no offline storage. If not i think it's really something your client doing, most likely it...