Conference end when second participant connect

Hello,
I installed jitsi on june 2021, on ubuntu 18, all worked fine from the first try.
Today, I needed to prepare a conference that will be held tomorrow, but, participants were not able to see each other. After a search here, it was apparenlty related to google Plan B, I don’t know what it is. But, refering to the topic, an upgrade of jitsi could resolve the problem.

I started first tu upgrade prosody, from 0.10 to 0.11 nightly build 143 (2022-01-24). Some errors occurs, and I spent hours to get it starting without any error. After that, I was going to upgrade jitsi meet, but surpriiiise!!, it was already on latest stable:

  • jitsi-meet 2.0.7001-1
  • jitsi-meet-prosody 1.0.5913-1
  • jitsi-meet-web 1.0.5913-1
  • jitsi-meet-web-config 1.0.5913-1
  • jitsi-videobridge2 2.1.634-gff8609ad-1

How it could be without any command from me??? I don’ know.

After that, I tried to see if everything is working well, but, another problem appears, when second participant connects, they both are disconnected, and logs on browser displays this:

For first participant:

Logger.js:154 2022-03-30T20:43:23.407Z [modules/e2ee/OlmAdapter.js] <cs._bootstrapOlm>: Failed to initialize Olm TypeError: Cannot read properties of undefined (reading ‘apply’)
at o.stackRestore (olm.js:68:288)
at ze.create (olm.js:92:197)
at cs._bootstrapOlm (OlmAdapter.js:223:30)

2022-03-30T20:43:23.423Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: Cannot read properties of undefined (reading ‘apply’) Script: null Line: null Column: null StackTrace: TypeError: Cannot read properties of undefined (reading ‘apply’)
at o.stackRestore (https://meeting.domain.com/libs/app.bundle.min.js?v=5913:138:950597)
at ze.create (https://meeting.domain.com/libs/app.bundle.min.js?v=5913:138:960649)
at cs._bootstrapOlm (https meeting domain./libs/lib-jitsi-meet.min.js?v=5913:2:235580)

olm.js:68 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘apply’)
at o.stackRestore (olm.js:68:288)
at ze.create (olm.js:92:197)
at cs._bootstrapOlm (OlmAdapter.js:223:30)

And when second participant connects:

Logger.js:154 2022-03-30T20:45:54.317Z [conference.js] <yoe._onConferenceFailed>: CONFERENCE FAILED: conference.videobridgeNotAvailable

and some warnings, maybe can help:

wasm streaming compile failed: TypeError: Failed to execute ‘compile’ on ‘WebAssembly’: Incorrect response MIME type. Expected ‘application/wasm’.
2022-03-30T20:47:21.100Z [modules/xmpp/XmppConnection.js] <Os._maybeEnableStreamResume>: Stream resume enabled, but WebSockets are not enabled
2022-03-30T20:47:57.780Z [modules/xmpp/strophe.util.js] <Object.ct.Strophe.log>: Strophe: Disconnect was called because: undefined

I tried to reboot server, and services, no changes.

Any idea?

Check jvb logs. Apparently, there is no jvb connected. Have you tried restarting jitsi-videobridge2 service? There were cases where this would happen on clean install. It is fixed in latest versions which are still not in stable.

Hi, if you mean restarting by
service jitsi-videobridge2 restart
then yes, I tried, but still get the error.

And for logs, i used:

journalctl -u jitsi-videobridge2.service

and all i get is:
Stopping jvb…
Stopped jvb…
Starting jvb…
Started jvb…
These are logs when I restarted it. There are nothing else.

Check /var/logs/jitsi/jvb.log

Oh ! Here it is:

JVB 2022-03-30 22:23:48.194 INFO: [23] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-03-30 22:23:48.249 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000011S. Sticky failure: false
JVB 2022-03-30 22:23:58.250 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000013S. Sticky failure: false
JVB 2022-03-30 22:24:08.250 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000009S. Sticky failure: false
JVB 2022-03-30 22:24:18.249 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000014S. Sticky failure: false
JVB 2022-03-30 22:24:28.250 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000018S. Sticky failure: false
JVB 2022-03-30 22:24:38.249 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000009S. Sticky failure: false
JVB 2022-03-30 22:24:48.194 INFO: [23] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-03-30 22:24:48.249 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000017S. Sticky failure: false
JVB 2022-03-30 22:24:58.249 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000009S. Sticky failure: false
JVB 2022-03-30 22:25:08.249 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000011S. Sticky failure: false
JVB 2022-03-30 22:25:18.250 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000017S. Sticky failure: false
JVB 2022-03-30 22:25:28.249 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000013S. Sticky failure: false
JVB 2022-03-30 22:25:38.250 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000009S. Sticky failure: false
JVB 2022-03-30 22:25:48.194 INFO: [23] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-03-30 22:25:48.250 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.00001S. Sticky failure: false
JVB 2022-03-30 22:25:58.250 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000016S. Sticky failure: false
JVB 2022-03-30 22:26:08.249 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000011S. Sticky failure: false
JVB 2022-03-30 22:26:18.249 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000008S. Sticky failure: false
JVB 2022-03-30 22:26:28.250 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000011S. Sticky failure: false
JVB 2022-03-30 22:26:38.250 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000017S. Sticky failure: false
JVB 2022-03-30 22:26:48.194 INFO: [23] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-03-30 22:26:48.250 INFO: [24] HealthChecker.run#171: Performed a successful health check in PT0.000014S. Sticky failure: false

What about jicofo logs, do you see any errors in jvb log on restart?

For jicofo logs, I selected these lines, I think these are the most relevant:

Jicofo 2022-03-30 22:40:53.556 WARNING: [170] BridgeSelector.selectBridge#181: There are no operational bridges.
Jicofo 2022-03-30 22:40:53.556 SEVERE: [170] [room=bneder@conference.meeting.imedramdani.com meeting_id=a3eec2df-0b65-4fd0-8094-f07b620f407f participant=8b646a37] ParticipantInviteRunnable.doRun#187: Can not invite participant, no bridge available: 8b646a37
Jicofo 2022-03-30 22:40:53.557 WARNING: [173] BridgeSelector.selectBridge#181: There are no operational bridges.
Jicofo 2022-03-30 22:40:53.557 SEVERE: [173] [room=bneder@conference.meeting.imedramdani.com meeting_id=a3eec2df-0b65-4fd0-8094-f07b620f407f participant=b2540922] ParticipantInviteRunnable.doRun#187: Can not invite participant, no bridge available: b2540922

Here are logs on JVB restart:

JVB 2022-03-30 22:39:28.913 INFO: [20] [hostname=localhost id=shard] MucClient.initializeConnectAndJoin#273: Initializing a new MucClient for [ org.jitsi.xmpp.mucclient.MucClientConfiguration id=shard domain=auth.meeting.imedramdani.com hostname=localhost port=null username=jvb mucs=[JvbBrewery@internal.auth.meeting.imedramdani.com] mucNickname=407b416a-285f-4302-bd45-42f9207e93e5 disableCertificateVerification=false]
JVB 2022-03-30 22:39:28.994 INFO: [1] LastNReducer.#65: LastNReducer with reductionScale: 0.75 recoverScale: 1.25 impactTime: PT1M minLastN: 1 maxEnforcedLastN: 40
JVB 2022-03-30 22:39:28.998 INFO: [1] TaskPools.#81: TaskPools detected 4 processors, creating the CPU pool with that many threads
JVB 2022-03-30 22:39:29.033 INFO: [1] UlimitCheck.printUlimits#115: Running with open files limit 65000 (hard 65000), thread limit 65000 (hard 65000).
JVB 2022-03-30 22:39:29.036 INFO: [1] VideobridgeExpireThread.start#88: Starting with 60 second interval.
JVB 2022-03-30 22:39:29.093 INFO: [1] HealthChecker.start#118: Started with interval=10000, timeout=PT30S, maxDuration=PT3S, stickyFailures=false.
JVB 2022-03-30 22:39:29.135 INFO: [1] MainKt.main#121: Not starting CallstatsService, disabled in configuration.
JVB 2022-03-30 22:39:29.139 INFO: [1] MainKt.main#130: Starting public http server
JVB 2022-03-30 22:39:29.268 INFO: [1] ColibriWebSocketService.#40: Base URL: wss://meeting.imedramdani.com:443/colibri-ws/default-id Relay URL: wss://meeting.imedramdani.com:443/colibri-relay-ws/default-id
JVB 2022-03-30 22:39:29.307 INFO: [1] org.eclipse.jetty.util.log.Log.initialized: Logging initialized @2733ms to org.eclipse.jetty.util.log.JavaUtilLog
JVB 2022-03-30 22:39:29.486 INFO: [1] ColibriWebSocketService.registerServlet#79: Registering servlet with baseUrl = wss://meeting.imedramdani.com:443/colibri-ws/default-id, relayUrl = wss://meeting.imedramdani.com:443/colibri-relay-ws/default-id
JVB 2022-03-30 22:39:29.522 INFO: [20] [hostname=localhost id=shard] MucClient.initializeConnectAndJoin#332: Dispatching a thread to connect and login.
JVB 2022-03-30 22:39:29.525 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 11.0.11+9-Ubuntu-0ubuntu2.18.04
JVB 2022-03-30 22:39:29.662 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@2d8f2f3a{/,null,AVAILABLE}
JVB 2022-03-30 22:39:29.694 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@552518c3{HTTP/1.1, (http/1.1)}{0.0.0.0:9090}
JVB 2022-03-30 22:39:29.695 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @3121ms
JVB 2022-03-30 22:39:29.699 INFO: [1] MainKt.main#148: Starting private http server
JVB 2022-03-30 22:39:29.852 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 11.0.11+9-Ubuntu-0ubuntu2.18.04
JVB 2022-03-30 22:39:29.900 INFO: [20] [hostname=localhost id=shard] MucClient$2.connected#305: Connected.
JVB 2022-03-30 22:39:29.901 INFO: [20] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#628: Logging in.
JVB 2022-03-30 22:39:29.978 INFO: [20] [hostname=localhost id=shard] MucClient$2.authenticated#311: Authenticated, b=false
JVB 2022-03-30 22:39:30.481 WARNING: [1] org.glassfish.jersey.server.wadl.WadlFeature.configure: JAXBContext implementation could not be found. WADL feature is disabled.
JVB 2022-03-30 22:39:30.622 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Health registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Health will be ignored.
JVB 2022-03-30 22:39:30.623 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Version registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Version will be ignored.
JVB 2022-03-30 22:39:31.155 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@5b275811{/,null,AVAILABLE}
JVB 2022-03-30 22:39:31.157 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@4943defe{HTTP/1.1, (http/1.1)}{127.0.0.1:8080}
JVB 2022-03-30 22:39:31.158 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @4584ms
JVB 2022-03-30 22:39:35.038 WARNING: [20] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#653: Failed to join the MUCs.
org.jivesoftware.smack.SmackException$NoResponseException: No response received within reply timeout. Timeout was 5000ms (~5s). StanzaCollector has been cancelled. Waited for response using: AndFilter: (StanzaTypeFilter: Presence, OrFilter: (AndFilter: (FromMatchesFilter (ignoreResourcepart): jvbbrewery@internal.auth.meeting.imedramdani.com, MUCUserStatusCodeFilter: status=110), AndFilter: (FromMatchesFilter (full): jvbbrewery@internal.auth.meeting.imedramdani.com/407b416a-285f-4302-bd45-42f9207e93e5, StanzaIdFilter: id=W7XQ2-2, PresenceTypeFilter: type=error))).
at org.jivesoftware.smack.SmackException$NoResponseException.newWith(SmackException.java:124)
at org.jivesoftware.smack.SmackException$NoResponseException.newWith(SmackException.java:104)
at org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:281)
at org.jivesoftware.smackx.muc.MultiUserChat.enter(MultiUserChat.java:405)
at org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:543)
at org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:518)
at org.jitsi.xmpp.mucclient.MucClient$MucWrapper.join(MucClient.java:739)
at org.jitsi.xmpp.mucclient.MucClient$MucWrapper.access$200(MucClient.java:666)
at org.jitsi.xmpp.mucclient.MucClient.joinMucs(MucClient.java:352)
at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$7(MucClient.java:649)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)

This is your problem. Now check prosody logs

Here:

Mar 30 22:47:39 c2s564df9365310 error Traceback[c2s]: /usr/lib/prosody/util/cache.lua:66: table index is nil
stack traceback:
/usr/lib/prosody/util/cache.lua:66: in function ‘set’
/usr/lib/prosody/modules/muc/mod_muc.lua:177: in function ‘track_room’
/usr/lib/prosody/modules/muc/mod_muc.lua:205: in function </usr/lib/prosody/modules/muc/mod_muc.lua:192>
(…tail calls…)
/usr/lib/prosody/modules/muc/mod_muc.lua:434: in function ‘?’
/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
(…tail calls…)
/usr/lib/prosody/core/stanza_router.lua:180: in function ‘core_post_stanza’
/usr/lib/prosody/core/stanza_router.lua:127: in function ‘core_process_stanza’
/usr/lib/prosody/modules/mod_c2s.lua:287: in function ‘func’
/usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125>
Mar 30 22:47:44 c2s564df9365310 error Traceback[c2s]: /usr/lib/prosody/util/cache.lua:66: table index is nil
stack traceback:
/usr/lib/prosody/util/cache.lua:66: in function ‘set’
/usr/lib/prosody/modules/muc/mod_muc.lua:177: in function ‘track_room’
/usr/lib/prosody/modules/muc/mod_muc.lua:205: in function </usr/lib/prosody/modules/muc/mod_muc.lua:192>
(…tail calls…)
/usr/lib/prosody/modules/muc/mod_muc.lua:434: in function ‘?’
/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
(…tail calls…)
/usr/lib/prosody/core/stanza_router.lua:180: in function ‘core_post_stanza’
/usr/lib/prosody/core/stanza_router.lua:127: in function ‘core_process_stanza’
/usr/lib/prosody/modules/mod_c2s.lua:287: in function ‘func’
/usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125>

Probably you fiirst had prosody 0.10 installed then you install jitsi-meet and then you upgrade prosody to 0.11 without adjusting your prosody config.
Make sure all occurrences in prosody config of storage has a value memory.
Like in the template: jitsi-meet/prosody.cfg.lua-jvb.example at 781bb5bd1853ae95dea548364a7e3a7e0710ef1c · jitsi/jitsi-meet · GitHub

Then restart prosody, jvb and then jicofo and you should be good to go.

When I upgraded from 0.10 to 0.11 I changed only one occurrence, I thought it was all.
But now, I removed and purged jitsi and prosody, I reinstalled prosody directly on 0.11, then I installed jitsi meet, it works fine now, I did not have to change any config file since the prosody 0.11 config was already configured by default, all storage occurrences was already set to “memory”.

I read in another topic that you advise to increase the c2s rate limit, from 10kb/s to 512kb/s, do I have to do it?

If you have any problems … or high traffic, many participants. Defaults should be fine.

1 Like

Thanks for your assistance.