[ejabberd] possible bug in max_user_sessions?

Jan Koum jan.koum at gmail.com
Fri Jan 1 04:57:38 MSK 2010


hi guys,

just another update on this issue -- it looks like doing 'ejabberdctl
ban_account' doesn't work either on these "stuck" login sessions:

$ ejabberdctl connected_users | grep jkb
jkb at s.example.net/xxx

$ ejabberdctl ban_account jkb s.example.net testing

$ ejabberdctl connected_users | grep jkb
jkb at s.example.net/xxx

oh, and happy new years!

-- yan


On Tue, Dec 29, 2009 at 1:19 AM, Jan Koum <jan.koum at gmail.com> wrote:

> hi there,
>
> in our ejabberd.cfg we have:
>
> {access, max_user_sessions, [{1, all}]}.
>
> in the past max_user_sessions worked perfectly -- when xmpp user connects
> for the 2nd time, 1st connection gets booted right away.
>
> however, today i discovered an interesting bug where "
> jkb at s.example.net/MBP" got stuck and i was able to connect from two other
> devices.
>
> $ ejabberd/sbin/ejabberdctl connected_users | grep jkb
> jkb at s.example.net/Adium
> jkb at s.example.net/MBP
> jkb at s.example.net/mini
>
> using "ejabberdctl kick_session" i was able to kick the 2nd and 3rd
> connection (/Adium and /mini ones), but 1st connection just wouldn't go
> away.
>
> how could this be?  aside from restarting the server -- any other
> solutions?
>
> thanks,
>
> -- yan
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jabber.ru/pipermail/ejabberd/attachments/20091231/d74a306b/attachment.html>


More information about the ejabberd mailing list