Unexpected info: $gen_event

[lokesh411]

Before creating a ticket, please consider if this should fit the discussion forum better.

Environment

• ejabberd version: 22.05
• Erlang version: 24
• OS: Linux (Debian)
• Installed from: official deb/rpm

Errors from error.log/crash.log

2023-04-28 07:02:31.458674+00:00 [warning] <0.15019.38>@ejabberd_c2s:process_info/2:250 Unexpected info: {'$gen_event',
                     {xmlstreamstart,<<"stream:stream">>,
                         [{<<"xmlns:stream">>,
                           <<"http://etherx.jabber.org/streams">>},
                          {<<"xmlns">>,<<"jabber:client">>},
                          {<<"version">>,<<"1.0">>},
                          {<<"to">>,<<"example.com">>}]}}
2023-04-28 07:02:31.460246+00:00 [warning] <0.15000.38>@ejabberd_c2s:process_info/2:250 Unexpected info: {'$gen_event',
                     {xmlstreamstart,<<"stream:stream">>,
                         [{<<"xmlns:stream">>,
                           <<"http://etherx.jabber.org/streams">>},
                          {<<"xmlns">>,<<"jabber:client">>},
                          {<<"version">>,<<"1.0">>},
                          {<<"to">>,<<"example.com">>}]}}
2023-04-28 07:02:31.460355+00:00 [warning] <0.27781.38>@ejabberd_c2s:process_info/2:250 Unexpected info: {'$gen_event',
                     {xmlstreamstart,<<"stream:stream">>,
                         [{<<"xmlns:stream">>,
                           <<"http://etherx.jabber.org/streams">>},
                          {<<"xmlns">>,<<"jabber:client">>},
                          {<<"version">>,<<"1.0">>},
                          {<<"to">>,<<"example.com">>}]}}

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

[prefiks]

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.

[lokesh411]

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

[lokesh411]

@prefiks anything here?