Open lokesh411 opened 1 year ago
I think this happens when client sends <stream:stream ..> after session is already estabilished, and server no longer expect something like this to arrive. Looks like some kind of buggy client, rather not something that server can fix.
Understood, I was seeing more of these warning
logs when the clients were reconnecting.
So if the client reconnects, client would be sending <stream:stream ..>
right, Please correct if i am wrong
@prefiks anything here?
Before creating a ticket, please consider if this should fit the discussion forum better.
Environment
24
Errors from error.log/crash.log
Bug description
Hey folks, I could see a lot of logs like these in my ejabberd production server, So i would want to know what does this mean and its impact and solve this if possible. Thanks in advance