Participants randomly disconnects from meetings - 2.0.8044

Install & Config
1

Issue appears randomly and not for all participants in the meeting. We are seeing this more or less every day and are holding to increase the user base until we have identified the issue.

No clear pattern has been identified as of yet. Running 2.0.8044

Any advice where to look next?

jvb log:

JVB 2023-03-13 10:42:28.853 SEVERE: [27] [confId=5232c7cc3ab5f8cb conf_name=meeting@muc.meet.jitsi meeting_id=4600a100 epId=75886d41 stats_id=Nestor-j9X] EndpointMessageTransport.webSocketError#382: Colibri websocket error: null
JVB 2023-03-13 10:43:28.856 INFO: [4847] [confId=5232c7cc3ab5f8cb conf_name=meeting@muc.meet.jitsi meeting_id=4600a100 epId=75886d41 stats_id=Nestor-j9X] AbstractEndpoint.expire#289: Expiring.
JVB 2023-03-13 10:43:28.856 INFO: [4892] [confId=5232c7cc3ab5f8cb conf_name=meeting@muc.meet.jitsi meeting_id=4600a100] Conference.recentSpeakersChanged#467: Recent speakers changed: [90ff3e96, 99211141], dominant speaker changed: true silence:false
JVB 2023-03-13 10:43:28.857 INFO: [4847] [confId=5232c7cc3ab5f8cb conf_name=meeting@muc.meet.jitsi meeting_id=4600a100 epId=75886d41 stats_id=Nestor-j9X] Endpoint.expire#1112: Spent 0 seconds oversending
JVB 2023-03-13 10:43:28.857 INFO: [4847] [confId=5232c7cc3ab5f8cb conf_name=meeting@muc.meet.jitsi meeting_id=4600a100 epId=75886d41 stats_id=Nestor-j9X] Transceiver.teardown#353: Tearing down
JVB 2023-03-13 10:43:28.857 INFO: [4847] [confId=5232c7cc3ab5f8cb conf_name=meeting@muc.meet.jitsi meeting_id=4600a100 epId=75886d41 stats_id=Nestor-j9X] RtpReceiverImpl.tearDown#347: Tearing down
JVB 2023-03-13 10:43:28.857 INFO: [4847] [confId=5232c7cc3ab5f8cb conf_name=meeting@muc.meet.jitsi meeting_id=4600a100 epId=75886d41 stats_id=Nestor-j9X] RtpSenderImpl.tearDown#318: Tearing down
JVB 2023-03-13 10:43:28.857 INFO: [4847] [confId=5232c7cc3ab5f8cb conf_name=meeting@muc.meet.jitsi meeting_id=4600a100 epId=75886d41 stats_id=Nestor-j9X] DtlsTransport.stop#178: Stopping
JVB 2023-03-13 10:43:28.857 INFO: [4847] [confId=5232c7cc3ab5f8cb conf_name=meeting@muc.meet.jitsi meeting_id=4600a100 epId=75886d41 stats_id=Nestor-j9X local_ufrag=24n9n1grd36l02] IceTransport.stop#252: Stopping
JVB 2023-03-13 10:13:31.845 WARNING: [4824] [confId=5232c7cc3ab5f8cb conf_name=meeting@muc.meet.jitsi meeting_id=4600a100 epId=743b20c5 stats_id=Breana-JmQ local_ufrag=5dujn1grd3934f ufrag=5dujn1grd3934f name=stream-743b20c5 componentId=1] MergingDatagramSocket.doRemove#349: Removing the active socket. Won’t be able to send until a new one is elected.

We are also seeing this several times a day:

JVB 2023-03-13 10:02:03.709 WARNING: [4820] [confId=5232c7cc3ab5f8cb conf_name=meeting@muc.meet.jitsi meeting_id=4600a100 epId=743b20c5 stats_id=Breana-JmQ local_ufrag=5dujn1grd3934f ufrag=5dujn1grd3934f name=stream-743b20c5 componentId=1] MergingDatagramSocket.initializeActive#599: Active socket already initialized.

jicofo log:

Jicofo 2023-03-13 10:43:28.855 INFO: [3107] [room=meeting@muc.meet.jitsi meeting_id=4600a100-eae1-4501-8cc1-4ca51856c772] JitsiMeetConferenceImpl.onMemberLeft#811: Member left:75886d41
Jicofo 2023-03-13 10:43:28.855 INFO: [3107] [room=meeting@muc.meet.jitsi meeting_id=4600a100-eae1-4501-8cc1-4ca51856c772] JitsiMeetConferenceImpl.terminateParticipant#853: Terminating 75886d41, reason: gone, send session-terminate: false
Jicofo 2023-03-13 10:43:28.855 INFO: [3107] AbstractOperationSetJingle.terminateSession#509: Terminate session: meeting@muc.meet.jitsi/75886d41, reason: gone, send terminate: false
Jicofo 2023-03-13 10:43:28.855 INFO: [3107] [room=meeting@muc.meet.jitsi meeting_id=4600a100-eae1-4501-8cc1-4ca51856c772] ColibriV2SessionManager.updateParticipant#457: Updating 75886d41 with transport=null, sources={}
Jicofo 2023-03-13 10:43:28.855 INFO: [3107] [room=meeting@muc.meet.jitsi meeting_id=4600a100-eae1-4501-8cc1-4ca51856c772] JitsiMeetConferenceImpl.terminateParticipant#876: Removed participant 75886d41 removed=true
Jicofo 2023-03-13 10:43:28.855 INFO: [3107] [room=meeting@muc.meet.jitsi meeting_id=4600a100-eae1-4501-8cc1-4ca51856c772] ColibriV2SessionManager.removeParticipant#111: Removing 75886d41

2

What are the client logs from the js browser when this happens?

3

Not sure, will try to collect them the following days. Does the devconsole in Edge/Chrome work or do we need another tool do collect more logs from the client?

4

yep, the logs from the developer console.

5

Here are logs from the developer console - looks like websocket breaks?

2023-03-14T09:15:30.024Z [modules/RTC/BridgeChannel.js] <e.onclose>: Channel closed: 1006
r @ Logger.js:154
e.onclose @ BridgeChannel.js:443
Logger.js:154

   2023-03-14T09:15:30.053Z [JitsiMeetJS.ts] <Object.getGlobalOnErrorHandler>:  UnhandledError: Strophe: Websocket closed unexpectedly Script: null Line: null Column: null StackTrace:  Error: Strophe: Websocket closed unexpectedly
at mt.Strophe.log (https://URL/libs/lib-jitsi-meet.min.js?v=6776:2:238302)
at Object.error (https://URL/libs/lib-jitsi-meet.min.js?v=6776:2:758494)
at w.Websocket._onClose (https://URL/libs/lib-jitsi-meet.min.js?v=6776:2:797306)

r @ Logger.js:154
getGlobalOnErrorHandler @ JitsiMeetJS.ts:526
window.onerror @ middleware.ts:85
callErrorHandler @ GlobalOnErrorHandler.js:61
mt.Strophe.log @ strophe.util.js:88
error @ strophe.umd.js:1392
_onClose @ strophe.umd.js:5676
Logger.js:154

   2023-03-14T09:15:30.055Z [modules/xmpp/strophe.util.js] <mt.Strophe.log>:  Strophe: Websocket closed unexpectedly

r @ Logger.js:154
mt.Strophe.log @ strophe.util.js:89
error @ strophe.umd.js:1392
_onClose @ strophe.umd.js:5676
BridgeChannel.js:84

   WebSocket connection to 'wss://URL/colibri-ws/IP-NUMBER/1234567890/33c97f5a?pwd=PASSWORD' failed:

_initWebSocket @ BridgeChannel.js:84
t @ BridgeChannel.js:103
Logger.js:154

   2023-03-14T09:15:31.164Z [modules/RTC/BridgeChannel.js] <e.onclose>:  Channel closed: 1006

r @ Logger.js:154
e.onclose @ BridgeChannel.js:443
strophe.umd.js:5463

   WebSocket connection to 'wss://URL/xmpp-websocket?room=8roagteufedmuj&token=JWTTOKEN&previd=IDNUMBER' failed:

_connect @ strophe.umd.js:5463
connect @ strophe.umd.js:2368
resume @ strophe.stream-management.js:152
_resumeConnection @ ResumeTask.js:144
(anonymous) @ ResumeTask.js:91
Logger.js:154

   2023-03-14T09:15:33.008Z [JitsiMeetJS.ts] <Object.getGlobalOnErrorHandler>:  UnhandledError: Strophe: Websocket error [object Event] Script: null Line: null Column: null StackTrace:  Error: Strophe: Websocket error [object Event]
at mt.Strophe.log (https://URL/libs/lib-jitsi-meet.min.js?v=6776:2:238302)
at Object.error (https://URL/libs/lib-jitsi-meet.min.js?v=6776:2:758494)
at w.Websocket._onError (https://URL/libs/lib-jitsi-meet.min.js?v=6776:2:797967)

r @ Logger.js:154
getGlobalOnErrorHandler @ JitsiMeetJS.ts:526
window.onerror @ middleware.ts:85
callErrorHandler @ GlobalOnErrorHandler.js:61
mt.Strophe.log @ strophe.util.js:88
error @ strophe.umd.js:1392
_onError @ strophe.umd.js:5730
error (async)
_connect @ strophe.umd.js:5465
connect @ strophe.umd.js:2368
resume @ strophe.stream-management.js:152
_resumeConnection @ ResumeTask.js:144
(anonymous) @ ResumeTask.js:91
setTimeout (async)
_scheduleResume @ ResumeTask.js:91
schedule @ ResumeTask.js:64
_tryResumingConnection @ XmppConnection.js:631
_stropheConnectionCb @ XmppConnection.js:301
_changeConnectStatus @ strophe.umd.js:3011
_doDisconnect @ strophe.umd.js:3052
_interceptDoDisconnect @ strophe.stream-management.js:218
_onClose @ strophe.umd.js:5678
Logger.js:154

   2023-03-14T09:15:33.010Z [modules/xmpp/strophe.util.js] <mt.Strophe.log>:  Strophe: Websocket error [object Event]

r @ Logger.js:154
mt.Strophe.log @ strophe.util.js:89
error @ strophe.umd.js:1392
_onError @ strophe.umd.js:5730
error (async)
_connect @ strophe.umd.js:5465
connect @ strophe.umd.js:2368
resume @ strophe.stream-management.js:152
_resumeConnection @ ResumeTask.js:144
(anonymous) @ ResumeTask.js:91
setTimeout (async)
_scheduleResume @ ResumeTask.js:91
schedule @ ResumeTask.js:64
_tryResumingConnection @ XmppConnection.js:631
_stropheConnectionCb @ XmppConnection.js:301
_changeConnectStatus @ strophe.umd.js:3011
_doDisconnect @ strophe.umd.js:3052
_interceptDoDisconnect @ strophe.stream-management.js:218
_onClose @ strophe.umd.js:5678
BridgeChannel.js:84

6

Error 1006 is a server side closing of the socket, so nginx or some other hop on the way closes the connection.

1 Like