[jitsi-users] show and kill phantoms users after crash


#1

Hi all,
I'm testing jitsi meet, and somes tests crash when I modify configuration,
etc ...

After this normal crashes, when I connected in the same room, I see old
user who is connected yet (it's me, but me before crash :wink: ).

My question is:
- how can I see connected users (with phantom users)
- how can I kill this phantom users (but with simple kick in jitsi meet
does not work)

thanks in advance


#2

A simple kick should do. What problem are you seeing?

路路路

On May 4, 2017, at 11:22, Mickael Hubert <mickael@winlux.fr> wrote:

Hi all,
I'm testing jitsi meet, and somes tests crash when I modify configuration, etc ...

After this normal crashes, when I connected in the same room, I see old user who is connected yet (it's me, but me before crash :wink: ).

My question is:
- how can I see connected users (with phantom users)
- how can I kill this phantom users (but with simple kick in jitsi meet does not work)

--
Sa煤l


#3

When I want kick, there is no action, no message, nothing :wink:

i can see this logs:

Room 7 contains me alone, and me (phantom user)

ay 04 11:58:19 http.server debug Firing event: POST
meet.winlux.fr/http-bind/
May 04 11:58:19 mod_bosh debug Handling new request table: 0x72ab60:
<body rid='790275158' xmlns='http://jabber.org/protocol/httpbind'
sid='2d450cf6-6278-4867-93bd-2e9b5af24244'><iq to='
room7@conference.meet.winlux.fr' type='set' xmlns='jabber:client'
id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'><query xmlns='
http://jabber.org/protocol/muc#admin'><item nick='d7e6131e'
role='none'><reason>You have been
kicked.</reason></item></query></iq></body>

路路路

----------
May 04 11:58:19 mod_bosh debug BOSH body open (sid:
2d450cf6-6278-4867-93bd-2e9b5af24244)
May 04 11:58:19 mod_bosh debug BOSH stanza received: <iq
id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ' type='set' to='
room7@conference.meet.winlux.fr'>

May 04 11:58:19 bosh2d450cf6-6278-4867-93bd-2e9b5af24244 debug
Received[c2s]: <iq id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'
type='set' to='room7@conference.meet.winlux.fr'>
May 04 11:58:19 datamanager debug Removing empty state datastore for
user room7@conference.meet.winlux.fr
May 04 11:58:19 datamanager debug Removing empty config datastore for
user room7@conference.meet.winlux.fr
May 04 11:58:19 mod_bosh debug We have an open request, so sending on
that
May 04 11:58:19 mod_bosh debug Request destroyed: table: 0xaf93c0
May 04 11:58:19 mod_bosh debug Session
2d450cf6-6278-4867-93bd-2e9b5af24244 has 1 out of 1 requests open
May 04 11:58:19 mod_bosh debug and there are 0 things in the
send_buffer:
May 04 11:58:19 mod_bosh debug Have nothing to say, so leaving
request unanswered for now
May 04 11:58:19 jcpcd1ba0 debug Received[component]: <iq
id='rf8dg-95271' type='get' to='meet.winlux.fr' from='focus.meet.winlux.fr'>
May 04 11:58:19 jcpc9c590 debug Received[component]: <iq
id='gIW27-17760' type='get' to='meet.winlux.fr' from='
jitsi-videobridge.meet.winlux.fr'>

2017-05-04 11:53 GMT+02:00 Sa煤l Ibarra Corretg茅 <scorretge@atlassian.com>:

> On May 4, 2017, at 11:22, Mickael Hubert <mickael@winlux.fr> wrote:
>
> Hi all,
> I'm testing jitsi meet, and somes tests crash when I modify
configuration, etc ...
>
> After this normal crashes, when I connected in the same room, I see old
user who is connected yet (it's me, but me before crash :wink: ).
>
> My question is:
> - how can I see connected users (with phantom users)
> - how can I kill this phantom users (but with simple kick in jitsi meet
does not work)
>

A simple kick should do. What problem are you seeing?

--
Sa煤l

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#4

FYI, even if all jitsi components restart, phantoms users stay here

路路路

2017-05-04 12:01 GMT+02:00 Mickael Hubert <mickael@winlux.fr>:

When I want kick, there is no action, no message, nothing :wink:

i can see this logs:

Room 7 contains me alone, and me (phantom user)

ay 04 11:58:19 http.server debug Firing event: POST
meet.winlux.fr/http-bind/
May 04 11:58:19 mod_bosh debug Handling new request table: 0x72ab60:
<body rid='790275158' xmlns='http://jabber.org/protocol/httpbind'
sid='2d450cf6-6278-4867-93bd-2e9b5af24244'><iq to='room7@conference.meet.
winlux.fr' type='set' xmlns='jabber:client' id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'><query
xmlns='http://jabber.org/protocol/muc#admin'><item nick='d7e6131e'
role='none'><reason>You have been kicked.</reason></item></
></iq></body>
----------
May 04 11:58:19 mod_bosh debug BOSH body open (sid:
2d450cf6-6278-4867-93bd-2e9b5af24244)
May 04 11:58:19 mod_bosh debug BOSH stanza received: <iq
id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ' type='set' to='
room7@conference.meet.winlux.fr'>

May 04 11:58:19 bosh2d450cf6-6278-4867-93bd-2e9b5af24244 debug
Received[c2s]: <iq id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'
type='set' to='room7@conference.meet.winlux.fr'>
May 04 11:58:19 datamanager debug Removing empty state datastore for
user room7@conference.meet.winlux.fr
May 04 11:58:19 datamanager debug Removing empty config datastore
for user room7@conference.meet.winlux.fr
May 04 11:58:19 mod_bosh debug We have an open request, so sending
on that
May 04 11:58:19 mod_bosh debug Request destroyed: table: 0xaf93c0
May 04 11:58:19 mod_bosh debug Session 2d450cf6-6278-4867-93bd-2e9b5af24244
has 1 out of 1 requests open
May 04 11:58:19 mod_bosh debug and there are 0 things in the
send_buffer:
May 04 11:58:19 mod_bosh debug Have nothing to say, so leaving
request unanswered for now
May 04 11:58:19 jcpcd1ba0 debug Received[component]: <iq
id='rf8dg-95271' type='get' to='meet.winlux.fr' from='focus.meet.winlux.fr
'>
May 04 11:58:19 jcpc9c590 debug Received[component]: <iq
id='gIW27-17760' type='get' to='meet.winlux.fr' from='
jitsi-videobridge.meet.winlux.fr'>

2017-05-04 11:53 GMT+02:00 Sa煤l Ibarra Corretg茅 <scorretge@atlassian.com>:

> On May 4, 2017, at 11:22, Mickael Hubert <mickael@winlux.fr> wrote:
>
> Hi all,
> I'm testing jitsi meet, and somes tests crash when I modify
configuration, etc ...
>
> After this normal crashes, when I connected in the same room, I see old
user who is connected yet (it's me, but me before crash :wink: ).
>
> My question is:
> - how can I see connected users (with phantom users)
> - how can I kill this phantom users (but with simple kick in jitsi meet
does not work)
>

A simple kick should do. What problem are you seeing?

--
Sa煤l

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#5

Hi,

Are you using latest prosody? The kick was broken at some point but we
reported it and it was fixed, but this was few months ago and I'm
talking about prosody-trunk.
In latest prosody there is a storage about state of rooms which is
kept between restarts I think to remove it you need:
Component "conference.yourserver.com" "muc"
聽聽聽聽storage = "null"

Hope this helps.
Regards
damencho

路路路

On Thu, May 4, 2017 at 7:48 AM, Mickael Hubert <mickael@winlux.fr> wrote:

FYI, even if all jitsi components restart, phantoms users stay here

2017-05-04 12:01 GMT+02:00 Mickael Hubert <mickael@winlux.fr>:

When I want kick, there is no action, no message, nothing :wink:

i can see this logs:

Room 7 contains me alone, and me (phantom user)

ay 04 11:58:19 http.server debug Firing event: POST
meet.winlux.fr/http-bind/
May 04 11:58:19 mod_bosh debug Handling new request table: 0x72ab60:
<body rid='790275158' xmlns='http://jabber.org/protocol/httpbind'
sid='2d450cf6-6278-4867-93bd-2e9b5af24244'><iq
to='room7@conference.meet.winlux.fr' type='set' xmlns='jabber:client'
id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'><query
xmlns='http://jabber.org/protocol/muc#admin'><item nick='d7e6131e'
role='none'><reason>You have been
kicked.</reason></item></query></iq></body>
----------
May 04 11:58:19 mod_bosh debug BOSH body open (sid:
2d450cf6-6278-4867-93bd-2e9b5af24244)
May 04 11:58:19 mod_bosh debug BOSH stanza received: <iq
id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ' type='set'
to='room7@conference.meet.winlux.fr'>

May 04 11:58:19 bosh2d450cf6-6278-4867-93bd-2e9b5af24244 debug
Received[c2s]: <iq id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'
type='set' to='room7@conference.meet.winlux.fr'>
May 04 11:58:19 datamanager debug Removing empty state datastore for
user room7@conference.meet.winlux.fr
May 04 11:58:19 datamanager debug Removing empty config datastore
for user room7@conference.meet.winlux.fr
May 04 11:58:19 mod_bosh debug We have an open request, so sending
on that
May 04 11:58:19 mod_bosh debug Request destroyed: table: 0xaf93c0
May 04 11:58:19 mod_bosh debug Session
2d450cf6-6278-4867-93bd-2e9b5af24244 has 1 out of 1 requests open
May 04 11:58:19 mod_bosh debug and there are 0 things in the
send_buffer:
May 04 11:58:19 mod_bosh debug Have nothing to say, so leaving
request unanswered for now
May 04 11:58:19 jcpcd1ba0 debug Received[component]: <iq
id='rf8dg-95271' type='get' to='meet.winlux.fr' from='focus.meet.winlux.fr'>
May 04 11:58:19 jcpc9c590 debug Received[component]: <iq
id='gIW27-17760' type='get' to='meet.winlux.fr'
from='jitsi-videobridge.meet.winlux.fr'>

2017-05-04 11:53 GMT+02:00 Sa煤l Ibarra Corretg茅 <scorretge@atlassian.com>:

> On May 4, 2017, at 11:22, Mickael Hubert <mickael@winlux.fr> wrote:
>
> Hi all,
> I'm testing jitsi meet, and somes tests crash when I modify
> configuration, etc ...
>
> After this normal crashes, when I connected in the same room, I see old
> user who is connected yet (it's me, but me before crash :wink: ).
>
> My question is:
> - how can I see connected users (with phantom users)
> - how can I kill this phantom users (but with simple kick in jitsi meet
> does not work)
>

A simple kick should do. What problem are you seeing?

--
Sa煤l

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#6

Thanks a lot Damian :wink:
it works

路路路

2017-05-04 15:06 GMT+02:00 Damian Minkov <damencho@jitsi.org>:

Hi,

Are you using latest prosody? The kick was broken at some point but we
reported it and it was fixed, but this was few months ago and I'm
talking about prosody-trunk.
In latest prosody there is a storage about state of rooms which is
kept between restarts I think to remove it you need:
Component "conference.yourserver.com" "muc"
聽聽聽聽storage = "null"

Hope this helps.
Regards
damencho

On Thu, May 4, 2017 at 7:48 AM, Mickael Hubert <mickael@winlux.fr> wrote:
> FYI, even if all jitsi components restart, phantoms users stay here
>
> 2017-05-04 12:01 GMT+02:00 Mickael Hubert <mickael@winlux.fr>:
>>
>> When I want kick, there is no action, no message, nothing :wink:
>>
>> i can see this logs:
>>
>> Room 7 contains me alone, and me (phantom user)
>>
>> ay 04 11:58:19 http.server debug Firing event: POST
>> meet.winlux.fr/http-bind/
>> May 04 11:58:19 mod_bosh debug Handling new request table:
0x72ab60:
>> <body rid='790275158' xmlns='http://jabber.org/protocol/httpbind'
>> sid='2d450cf6-6278-4867-93bd-2e9b5af24244'><iq
>> to='room7@conference.meet.winlux.fr' type='set' xmlns='jabber:client'
>> id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'><query
>> xmlns='http://jabber.org/protocol/muc#admin'><item nick='d7e6131e'
>> role='none'><reason>You have been
>> kicked.</reason></item></query></iq></body>
>> ----------
>> May 04 11:58:19 mod_bosh debug BOSH body open (sid:
>> 2d450cf6-6278-4867-93bd-2e9b5af24244)
>> May 04 11:58:19 mod_bosh debug BOSH stanza received: <iq
>> id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ' type='set'
>> to='room7@conference.meet.winlux.fr'>
>>
>> May 04 11:58:19 bosh2d450cf6-6278-4867-93bd-2e9b5af24244 debug
>> Received[c2s]: <iq id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'
>> type='set' to='room7@conference.meet.winlux.fr'>
>> May 04 11:58:19 datamanager debug Removing empty state datastore
for
>> user room7@conference.meet.winlux.fr
>> May 04 11:58:19 datamanager debug Removing empty config datastore
>> for user room7@conference.meet.winlux.fr
>> May 04 11:58:19 mod_bosh debug We have an open request, so sending
>> on that
>> May 04 11:58:19 mod_bosh debug Request destroyed: table: 0xaf93c0
>> May 04 11:58:19 mod_bosh debug Session
>> 2d450cf6-6278-4867-93bd-2e9b5af24244 has 1 out of 1 requests open
>> May 04 11:58:19 mod_bosh debug and there are 0 things in the
>> send_buffer:
>> May 04 11:58:19 mod_bosh debug Have nothing to say, so leaving
>> request unanswered for now
>> May 04 11:58:19 jcpcd1ba0 debug Received[component]: <iq
>> id='rf8dg-95271' type='get' to='meet.winlux.fr' from='
focus.meet.winlux.fr'>
>> May 04 11:58:19 jcpc9c590 debug Received[component]: <iq
>> id='gIW27-17760' type='get' to='meet.winlux.fr'
>> from='jitsi-videobridge.meet.winlux.fr'>
>>
>>
>> 2017-05-04 11:53 GMT+02:00 Sa煤l Ibarra Corretg茅 <
scorretge@atlassian.com>:
>>>
>>>
>>> > On May 4, 2017, at 11:22, Mickael Hubert <mickael@winlux.fr> wrote:
>>> >
>>> > Hi all,
>>> > I'm testing jitsi meet, and somes tests crash when I modify
>>> > configuration, etc ...
>>> >
>>> > After this normal crashes, when I connected in the same room, I see
old
>>> > user who is connected yet (it's me, but me before crash :wink: ).
>>> >
>>> > My question is:
>>> > - how can I see connected users (with phantom users)
>>> > - how can I kill this phantom users (but with simple kick in jitsi
meet
>>> > does not work)
>>> >
>>>
>>> A simple kick should do. What problem are you seeing?
>>>
>>> --
>>> Sa煤l
>>>
>>>
>>> _______________________________________________
>>> users mailing list
>>> users@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/users
>>
>>
>
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#7

Hi,

Are you using latest prosody? The kick was broken at some point but we
reported it and it was fixed, but this was few months ago and I'm
talking about prosody-trunk.
In latest prosody there is a storage about state of rooms which is
kept between restarts I think to remove it you need:
Component "conference.yourserver.com" "muc"
聽聽聽storage = 鈥渘ull"

Do you think we should add this to our default config files? Looks like a useful thing to have.

路路路

On May 4, 2017, at 15:06, Damian Minkov <damencho@jitsi.org> wrote:

Hope this helps.
Regards
damencho

On Thu, May 4, 2017 at 7:48 AM, Mickael Hubert <mickael@winlux.fr> wrote:

FYI, even if all jitsi components restart, phantoms users stay here

2017-05-04 12:01 GMT+02:00 Mickael Hubert <mickael@winlux.fr>:

When I want kick, there is no action, no message, nothing :wink:

i can see this logs:

Room 7 contains me alone, and me (phantom user)

ay 04 11:58:19 http.server debug Firing event: POST
meet.winlux.fr/http-bind/
May 04 11:58:19 mod_bosh debug Handling new request table: 0x72ab60:
<body rid='790275158' xmlns='http://jabber.org/protocol/httpbind'
sid='2d450cf6-6278-4867-93bd-2e9b5af24244'><iq
to='room7@conference.meet.winlux.fr' type='set' xmlns='jabber:client'
id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'><query
xmlns='http://jabber.org/protocol/muc#admin'><item nick='d7e6131e'
role='none'><reason>You have been
kicked.</reason></item></query></iq></body>
----------
May 04 11:58:19 mod_bosh debug BOSH body open (sid:
2d450cf6-6278-4867-93bd-2e9b5af24244)
May 04 11:58:19 mod_bosh debug BOSH stanza received: <iq
id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ' type='set'
to='room7@conference.meet.winlux.fr'>

May 04 11:58:19 bosh2d450cf6-6278-4867-93bd-2e9b5af24244 debug
Received[c2s]: <iq id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'
type='set' to='room7@conference.meet.winlux.fr'>
May 04 11:58:19 datamanager debug Removing empty state datastore for
user room7@conference.meet.winlux.fr
May 04 11:58:19 datamanager debug Removing empty config datastore
for user room7@conference.meet.winlux.fr
May 04 11:58:19 mod_bosh debug We have an open request, so sending
on that
May 04 11:58:19 mod_bosh debug Request destroyed: table: 0xaf93c0
May 04 11:58:19 mod_bosh debug Session
2d450cf6-6278-4867-93bd-2e9b5af24244 has 1 out of 1 requests open
May 04 11:58:19 mod_bosh debug and there are 0 things in the
send_buffer:
May 04 11:58:19 mod_bosh debug Have nothing to say, so leaving
request unanswered for now
May 04 11:58:19 jcpcd1ba0 debug Received[component]: <iq
id='rf8dg-95271' type='get' to='meet.winlux.fr' from='focus.meet.winlux.fr'>
May 04 11:58:19 jcpc9c590 debug Received[component]: <iq
id='gIW27-17760' type='get' to='meet.winlux.fr'
from='jitsi-videobridge.meet.winlux.fr'>

2017-05-04 11:53 GMT+02:00 Sa煤l Ibarra Corretg茅 <scorretge@atlassian.com>:

On May 4, 2017, at 11:22, Mickael Hubert <mickael@winlux.fr> wrote:

Hi all,
I'm testing jitsi meet, and somes tests crash when I modify
configuration, etc ...

After this normal crashes, when I connected in the same room, I see old
user who is connected yet (it's me, but me before crash :wink: ).

My question is:
- how can I see connected users (with phantom users)
- how can I kill this phantom users (but with simple kick in jitsi meet
does not work)

A simple kick should do. What problem are you seeing?

--
Sa煤l

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

--
Sa煤l


#8

Yep, we don't care to store anything in the room between restarts. I
will add it to the default config.

路路路

On Thu, May 4, 2017 at 8:46 AM, Sa煤l Ibarra Corretg茅 <scorretge@atlassian.com> wrote:

On May 4, 2017, at 15:06, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

Are you using latest prosody? The kick was broken at some point but we
reported it and it was fixed, but this was few months ago and I'm
talking about prosody-trunk.
In latest prosody there is a storage about state of rooms which is
kept between restarts I think to remove it you need:
Component "conference.yourserver.com" "muc"
聽聽聽storage = 鈥渘ull"

Do you think we should add this to our default config files? Looks like a useful thing to have.

Hope this helps.
Regards
damencho

On Thu, May 4, 2017 at 7:48 AM, Mickael Hubert <mickael@winlux.fr> wrote:

FYI, even if all jitsi components restart, phantoms users stay here

2017-05-04 12:01 GMT+02:00 Mickael Hubert <mickael@winlux.fr>:

When I want kick, there is no action, no message, nothing :wink:

i can see this logs:

Room 7 contains me alone, and me (phantom user)

ay 04 11:58:19 http.server debug Firing event: POST
meet.winlux.fr/http-bind/
May 04 11:58:19 mod_bosh debug Handling new request table: 0x72ab60:
<body rid='790275158' xmlns='http://jabber.org/protocol/httpbind'
sid='2d450cf6-6278-4867-93bd-2e9b5af24244'><iq
to='room7@conference.meet.winlux.fr' type='set' xmlns='jabber:client'
id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'><query
xmlns='http://jabber.org/protocol/muc#admin'><item nick='d7e6131e'
role='none'><reason>You have been
kicked.</reason></item></query></iq></body>
----------
May 04 11:58:19 mod_bosh debug BOSH body open (sid:
2d450cf6-6278-4867-93bd-2e9b5af24244)
May 04 11:58:19 mod_bosh debug BOSH stanza received: <iq
id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ' type='set'
to='room7@conference.meet.winlux.fr'>

May 04 11:58:19 bosh2d450cf6-6278-4867-93bd-2e9b5af24244 debug
Received[c2s]: <iq id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'
type='set' to='room7@conference.meet.winlux.fr'>
May 04 11:58:19 datamanager debug Removing empty state datastore for
user room7@conference.meet.winlux.fr
May 04 11:58:19 datamanager debug Removing empty config datastore
for user room7@conference.meet.winlux.fr
May 04 11:58:19 mod_bosh debug We have an open request, so sending
on that
May 04 11:58:19 mod_bosh debug Request destroyed: table: 0xaf93c0
May 04 11:58:19 mod_bosh debug Session
2d450cf6-6278-4867-93bd-2e9b5af24244 has 1 out of 1 requests open
May 04 11:58:19 mod_bosh debug and there are 0 things in the
send_buffer:
May 04 11:58:19 mod_bosh debug Have nothing to say, so leaving
request unanswered for now
May 04 11:58:19 jcpcd1ba0 debug Received[component]: <iq
id='rf8dg-95271' type='get' to='meet.winlux.fr' from='focus.meet.winlux.fr'>
May 04 11:58:19 jcpc9c590 debug Received[component]: <iq
id='gIW27-17760' type='get' to='meet.winlux.fr'
from='jitsi-videobridge.meet.winlux.fr'>

2017-05-04 11:53 GMT+02:00 Sa煤l Ibarra Corretg茅 <scorretge@atlassian.com>:

On May 4, 2017, at 11:22, Mickael Hubert <mickael@winlux.fr> wrote:

Hi all,
I'm testing jitsi meet, and somes tests crash when I modify
configuration, etc ...

After this normal crashes, when I connected in the same room, I see old
user who is connected yet (it's me, but me before crash :wink: ).

My question is:
- how can I see connected users (with phantom users)
- how can I kill this phantom users (but with simple kick in jitsi meet
does not work)

A simple kick should do. What problem are you seeing?

--
Sa煤l

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

--
Sa煤l

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#9

for me it's mandatory, yes.

my exemple:

Component "conference.meet.winlux.fr" "muc"
聽聽聽聽modules_enabled = { "token_verification" }
聽聽聽聽restrict_room_creation = true
聽聽聽聽storage = "null"
聽聽聽聽ssl = {
聽聽聽聽聽聽聽聽certificate = "/var/lib/prosody/conference.meet.winlux.fr.crt";
聽聽聽聽聽聽聽聽key = "/var/lib/prosody/conference.meet.winlux.fr.key";
聽聽聽聽}

路路路

2017-05-04 15:46 GMT+02:00 Sa煤l Ibarra Corretg茅 <scorretge@atlassian.com>:

> On May 4, 2017, at 15:06, Damian Minkov <damencho@jitsi.org> wrote:
>
> Hi,
>
> Are you using latest prosody? The kick was broken at some point but we
> reported it and it was fixed, but this was few months ago and I'm
> talking about prosody-trunk.
> In latest prosody there is a storage about state of rooms which is
> kept between restarts I think to remove it you need:
> Component "conference.yourserver.com" "muc"
> storage = 鈥渘ull"
>

Do you think we should add this to our default config files? Looks like a
useful thing to have.

> Hope this helps.
> Regards
> damencho
>
>
> On Thu, May 4, 2017 at 7:48 AM, Mickael Hubert <mickael@winlux.fr> > wrote:
>> FYI, even if all jitsi components restart, phantoms users stay here
>>
>> 2017-05-04 12:01 GMT+02:00 Mickael Hubert <mickael@winlux.fr>:
>>>
>>> When I want kick, there is no action, no message, nothing :wink:
>>>
>>> i can see this logs:
>>>
>>> Room 7 contains me alone, and me (phantom user)
>>>
>>> ay 04 11:58:19 http.server debug Firing event: POST
>>> meet.winlux.fr/http-bind/
>>> May 04 11:58:19 mod_bosh debug Handling new request table:
0x72ab60:
>>> <body rid='790275158' xmlns='http://jabber.org/protocol/httpbind'
>>> sid='2d450cf6-6278-4867-93bd-2e9b5af24244'><iq
>>> to='room7@conference.meet.winlux.fr' type='set' xmlns='jabber:client'
>>> id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'><query
>>> xmlns='http://jabber.org/protocol/muc#admin'><item nick='d7e6131e'
>>> role='none'><reason>You have been
>>> kicked.</reason></item></query></iq></body>
>>> ----------
>>> May 04 11:58:19 mod_bosh debug BOSH body open (sid:
>>> 2d450cf6-6278-4867-93bd-2e9b5af24244)
>>> May 04 11:58:19 mod_bosh debug BOSH stanza received: <iq
>>> id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ' type='set'
>>> to='room7@conference.meet.winlux.fr'>
>>>
>>> May 04 11:58:19 bosh2d450cf6-6278-4867-93bd-2e9b5af24244 debug
>>> Received[c2s]: <iq id='55ca6c9d-0f8e-424d-b029-899d3d04fb04:sendIQ'
>>> type='set' to='room7@conference.meet.winlux.fr'>
>>> May 04 11:58:19 datamanager debug Removing empty state datastore
for
>>> user room7@conference.meet.winlux.fr
>>> May 04 11:58:19 datamanager debug Removing empty config datastore
>>> for user room7@conference.meet.winlux.fr
>>> May 04 11:58:19 mod_bosh debug We have an open request, so
sending
>>> on that
>>> May 04 11:58:19 mod_bosh debug Request destroyed: table: 0xaf93c0
>>> May 04 11:58:19 mod_bosh debug Session
>>> 2d450cf6-6278-4867-93bd-2e9b5af24244 has 1 out of 1 requests open
>>> May 04 11:58:19 mod_bosh debug and there are 0 things in the
>>> send_buffer:
>>> May 04 11:58:19 mod_bosh debug Have nothing to say, so leaving
>>> request unanswered for now
>>> May 04 11:58:19 jcpcd1ba0 debug Received[component]: <iq
>>> id='rf8dg-95271' type='get' to='meet.winlux.fr' from='
focus.meet.winlux.fr'>
>>> May 04 11:58:19 jcpc9c590 debug Received[component]: <iq
>>> id='gIW27-17760' type='get' to='meet.winlux.fr'
>>> from='jitsi-videobridge.meet.winlux.fr'>
>>>
>>>
>>> 2017-05-04 11:53 GMT+02:00 Sa煤l Ibarra Corretg茅 <
scorretge@atlassian.com>:
>>>>
>>>>
>>>>> On May 4, 2017, at 11:22, Mickael Hubert <mickael@winlux.fr> wrote:
>>>>>
>>>>> Hi all,
>>>>> I'm testing jitsi meet, and somes tests crash when I modify
>>>>> configuration, etc ...
>>>>>
>>>>> After this normal crashes, when I connected in the same room, I see
old
>>>>> user who is connected yet (it's me, but me before crash :wink: ).
>>>>>
>>>>> My question is:
>>>>> - how can I see connected users (with phantom users)
>>>>> - how can I kill this phantom users (but with simple kick in jitsi
meet
>>>>> does not work)
>>>>>
>>>>
>>>> A simple kick should do. What problem are you seeing?
>>>>
>>>> --
>>>> Sa煤l
>>>>
>>>>
>>>> _______________________________________________
>>>> users mailing list
>>>> users@jitsi.org
>>>> Unsubscribe instructions and other list options:
>>>> http://lists.jitsi.org/mailman/listinfo/users
>>>
>>>
>>
>>
>> _______________________________________________
>> users mailing list
>> users@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/users
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

--
Sa煤l

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users