Upgraded to latest version, now "Something went wrong"

I’ve been running Jitsi Meet for a few years with no problems. Decided to update to the latest version (Ubuntu) and now I get “Something went wrong” immediately on trying to start a conference.

I verified port 10000 is open. Again, nothing changed on the server/firewall. Any advice appreciated.

jicofo.log

Jicofo 2021-05-29 12:29:08.270 INFO: [1] Main.main#49: Starting Jicofo.
Jicofo 2021-05-29 12:29:10.286 INFO: [1] JitsiConfig.<clinit>#47: Initialized newConfig: merge of /etc/jitsi/jicofo/jicofo.conf: 1,system properties,reference.conf @ jar:file:/usr/share/jicofo/jicofo.jar!/reference.conf: 1
Jicofo 2021-05-29 12:29:10.366 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#51: loading config file at path /etc/jitsi/jicofo/sip-communicator.properties
Jicofo 2021-05-29 12:29:10.376 INFO: [1] JitsiConfig.<clinit>#68: Initialized legacyConfig: sip communicator props (no description provided)
Jicofo 2021-05-29 12:29:10.376 INFO: [1] JitsiConfig$Companion.reloadNewConfig#94: Reloading the Typesafe config source (previously reloaded 0 times).
Jicofo 2021-05-29 12:29:14.119 INFO: [1] XmppServices.<init>#40: No dedicated Service XMPP connection configured, re-using the client XMPP connection.
Jicofo 2021-05-29 12:29:14.371 INFO: [1] BridgeSelector.<init>#79: Using org.jitsi.jicofo.bridge.SingleBridgeSelectionStrategy
Jicofo 2021-05-29 12:29:14.535 INFO: [1] [type=bridge brewery=jvbbrewery] BaseBrewery.<init>#101: Initialized with JID=jvbbrewery@internal.auth.meet.aquilatech.com
Jicofo 2021-05-29 12:29:14.720 INFO: [1] JicofoServices.<init>#103: No Jibri detector configured.
Jicofo 2021-05-29 12:29:14.721 INFO: [1] JicofoServices.<init>#109: No SIP Jibri detector configured.
Jicofo 2021-05-29 12:29:16.399 INFO: [1] [type=jigasi brewery=jigasibrewery] BaseBrewery.<init>#101: Initialized with JID=jigasibrewery@internal.auth.meet.aquilatech.com
Jicofo 2021-05-29 12:29:16.585 WARNING: [1] FocusManager.start#134: Jicofo ID is not set correctly set (value=0). Configure a valid value [1-65535] by setting org.jitsi.jicofo.SHORT_ID in sip-communicator.properties or jicofo.octo.id in jicofo.conf. Future versions will require this for Octo.
Jicofo 2021-05-29 12:29:16.706 INFO: [1] JicofoServices.createAuthenticationAuthority#198: Starting authentication service with config=AuthConfig[enabled=true, type=XMPP, loginUrl=aquilatech.com, logoutUrl=null, authenticationLifetime=PT24H, enableAutoLogin=true].
Jicofo 2021-05-29 12:29:16.715 INFO: [1] AbstractAuthAuthority.<init>#112: Authentication lifetime: PT24H
Jicofo 2021-05-29 12:29:16.803 INFO: [1] IqHandler.init#95: Registering IQ handlers with XmppConnection.
Jicofo 2021-05-29 12:29:16.830 INFO: [1] JicofoServices.<init>#161: Starting HTTP server with config: host=null, port=8888, tlsPort=8843, isTls=false, keyStorePath=null.
Jicofo 2021-05-29 12:29:18.080 INFO: [1] org.eclipse.jetty.util.log.Log.initialized: Logging initialized @17288ms to org.eclipse.jetty.util.log.Slf4jLog
Jicofo 2021-05-29 12:29:19.020 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.35.v20201120; built: 2020-11-20T21:17:03.964Z; git: bdc54f03a5e0a7e280fab27f55c3c75ee8da89fb; jvm 1.8.0_292-8u292-b10-0ubuntu1~18.04-b10
Jicofo 2021-05-29 12:29:19.590 INFO: [11] [xmpp_connection=client] XmppProviderImpl.doConnect#200: Connected, JID= null
Jicofo 2021-05-29 12:29:20.252 INFO: [11] [type=bridge brewery=jvbbrewery] BaseBrewery.start#172: Joined the room.
Jicofo 2021-05-29 12:29:20.352 INFO: [11] [type=jigasi brewery=jigasibrewery] BaseBrewery.start#172: Joined the room.
Jicofo 2021-05-29 12:29:20.354 INFO: [11] [xmpp_connection=client] XmppProviderImpl.fireRegistrationStateChanged#325: Set replyTimeout=PT15S
Jicofo 2021-05-29 12:29:21.574 INFO: [25] [type=bridge brewery=jvbbrewery] BaseBrewery.addInstance#338: Added brewery instance: jvbbrewery@internal.auth.meet.aquilatech.com/f368628f-f12c-4267-87b7-c08ba9733d2c
Jicofo 2021-05-29 12:29:21.626 WARNING: [25] Main$1.warn#154: Key 'jicofo.bridge.average-participant-packet-rate-pps' from source 'typesafe config (reloaded 1 times)' is deprecated: use jicofo.bridge.average-participant-stress
Jicofo 2021-05-29 12:29:21.634 INFO: [25] BridgeSelector.addJvbAddress#118: Added new videobridge: Bridge[jid=jvbbrewery@internal.auth.meet.aquilatech.com/f368628f-f12c-4267-87b7-c08ba9733d2c, relayId=null, region=null, stress=0.00]
Jicofo 2021-05-29 12:29:21.649 INFO: [25] JvbDoctor.addBridge#140: Scheduled health-check task for: jvbbrewery@internal.auth.meet.aquilatech.com/f368628f-f12c-4267-87b7-c08ba9733d2c
Jicofo 2021-05-29 12:29:22.711 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.
Jicofo 2021-05-29 12:29:23.706 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@497aec8c{/,null,AVAILABLE}
Jicofo 2021-05-29 12:29:23.773 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@63648ee9{HTTP/1.1, (http/1.1)}{0.0.0.0:8888}
Jicofo 2021-05-29 12:29:23.773 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @22984ms
jicofo.log (END)

jvb.log

JVB 2021-05-29 12:29:10.925 INFO: [1] JitsiConfig.<clinit>#47: Initialized newConfig: merge of /etc/jitsi/videobridge/jvb.conf: 1,application.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/application.conf: 1,system properties,reference.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/ice4j-3.0-25-g5a299cd.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/jitsi-media-transform-1.0-234-gf48db15.jar!/reference.conf: 1
JVB 2021-05-29 12:29:10.968 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#51: loading config file at path /etc/jitsi/videobridge/sip-communicator.properties
JVB 2021-05-29 12:29:10.989 INFO: [1] JitsiConfig.<clinit>#68: Initialized legacyConfig: sip communicator props (no description provided)
JVB 2021-05-29 12:29:11.002 INFO: [1] JitsiConfig$Companion.reloadNewConfig#94: Reloading the Typesafe config source (previously reloaded 0 times).
JVB 2021-05-29 12:29:14.231 INFO: [10] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Using org.ice4j.ice.harvest.MappingCandidateHarvester, face=/10.0.8.15, mask=/108.22.254.9
JVB 2021-05-29 12:29:14.233 INFO: [10] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Initialized mapping harvesters (delay=3061ms).  stunDiscoveryFailed=false
JVB 2021-05-29 12:29:15.574 INFO: [11] [hostname=localhost id=shard] MucClient.initializeConnectAndJoin#227: Initializing a new MucClient for [ org.jitsi.xmpp.mucclient.MucClientConfiguration id=shard domain=auth.meet.aquilatech.com hostname=localhost port=null username=jvb mucs=[JvbBrewery@internal.auth.meet.aquilatech.com] mucNickname=f368628f-f12c-4267-87b7-c08ba9733d2c disableCertificateVerification=false]
JVB 2021-05-29 12:29:15.840 INFO: [1] LastNReducer.<init>#65: LastNReducer with reductionScale: 0.75 recoverScale: 1.25 impactTime: PT1M minLastN: 1 maxEnforcedLastN: 40
JVB 2021-05-29 12:29:15.875 INFO: [1] TaskPools.<clinit>#81: TaskPools detected 2 processors, creating the CPU pool with that many threads
JVB 2021-05-29 12:29:16.079 INFO: [11] [hostname=localhost id=shard] MucClient.initializeConnectAndJoin#302: Dispatching a thread to connect and login.
JVB 2021-05-29 12:29:16.116 INFO: [1] UlimitCheck.printUlimits#115: Running with open files limit 65000 (hard 65000), thread limit 65000 (hard 65000).
JVB 2021-05-29 12:29:16.118 INFO: [1] VideobridgeExpireThread.start#88: Starting with 60 second interval.
JVB 2021-05-29 12:29:16.365 INFO: [1] HealthChecker.start#118: Started with interval=10000, timeout=PT30S, maxDuration=PT3S, stickyFailures=false.
JVB 2021-05-29 12:29:16.480 INFO: [1] MainKt.main#108: Not starting CallstatsService, disabled in configuration.
JVB 2021-05-29 12:29:16.507 INFO: [1] MainKt.main#117: Starting public http server
JVB 2021-05-29 12:29:17.279 INFO: [1] ColibriWebSocketService.<init>#40: Base URL: wss://meet.aquilatech.com:443/colibri-ws/default-id
JVB 2021-05-29 12:29:17.464 INFO: [1] org.eclipse.jetty.util.log.Log.initialized: Logging initialized @14265ms to org.eclipse.jetty.util.log.JavaUtilLog
JVB 2021-05-29 12:29:17.982 INFO: [1] ColibriWebSocketService.registerServlet#65: Registering servlet at /colibri-ws/*, baseUrl = wss://meet.aquilatech.com:443/colibri-ws/default-id
JVB 2021-05-29 12:29:18.006 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.35.v20201120; built: 2020-11-20T21:17:03.964Z; git: bdc54f03a5e0a7e280fab27f55c3c75ee8da89fb; jvm 1.8.0_292-8u292-b10-0ubuntu1~18.04-b10
JVB 2021-05-29 12:29:18.871 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@56928307{/,null,AVAILABLE}
JVB 2021-05-29 12:29:19.137 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@662706a7{HTTP/1.1, (http/1.1)}{0.0.0.0:9090}
JVB 2021-05-29 12:29:19.138 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @15941ms
JVB 2021-05-29 12:29:19.142 INFO: [1] MainKt.main#135: Starting private http server
JVB 2021-05-29 12:29:19.692 INFO: [11] [hostname=localhost id=shard] MucClient$1.connected#259: Connected.
JVB 2021-05-29 12:29:19.692 INFO: [11] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$8#597: Logging in.
JVB 2021-05-29 12:29:19.857 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.35.v20201120; built: 2020-11-20T21:17:03.964Z; git: bdc54f03a5e0a7e280fab27f55c3c75ee8da89fb; jvm 1.8.0_292-8u292-b10-0ubuntu1~18.04-b10
JVB 2021-05-29 12:29:20.191 INFO: [11] [hostname=localhost id=shard] MucClient$1.authenticated#265: Authenticated, b=false
JVB 2021-05-29 12:29:20.312 INFO: [11] [hostname=localhost id=shard] MucClient$MucWrapper.join#723: Joined MUC: jvbbrewery@internal.auth.meet.aquilatech.com
JVB 2021-05-29 12:29:23.051 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 2021-05-29 12:29:23.052 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 2021-05-29 12:29:24.068 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@e04ccf8{/,null,AVAILABLE}
JVB 2021-05-29 12:29:24.074 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@130dca52{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
JVB 2021-05-29 12:29:24.075 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @20878ms
JVB 2021-05-29 12:29:26.349 INFO: [21] HealthChecker.run#171: Performed a successful health check in PT0.001S. Sticky failure: false
JVB 2021-05-29 12:29:36.347 INFO: [21] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false

Can you share your prosody config?

I think this is the file you are looking for? Thanks for taking a look!

meet.aquilatech.com.cfg.lua.txt (3.1 KB)

Try executing prosodyctl mod_roster_command subscribe focus.yourdomain.com focus@auth.yourdomain.com

Maybe restart prosody, wait 10-15 seconds and try again. Is there any difference?

This command returned an error:
prosodyctl mod_roster_command subscribe focus.aquilatech.com focus@auth.aquilatech.com
The host ‘focus.aquilatech.com’ is not configured for this server.

I adjusted it to this, and no error.
prosodyctl mod_roster_command subscribe focus.meet.aquilatech.com focus@auth.aquilatech.com

Restarted prosody, waited and tested but same failure.

May 29 15:55:12 general info    Hello and welcome to Prosody version 0.10.0
May 29 15:55:12 general info    Prosody is using the select backend for connection handling
May 29 15:55:12 portmanager     info    Activated service 'c2s' on [::]:5222, [*]:5222
May 29 15:55:12 portmanager     info    Activated service 'legacy_ssl' on no ports
May 29 15:55:12 portmanager     info    Activated service 's2s' on [::]:5269, [*]:5269
May 29 15:55:12 mod_posix       info    Prosody is about to detach from the console, disabling further console output
May 29 15:55:12 mod_posix       info    Successfully daemonized to PID 18651
May 29 15:55:12 portmanager     info    Activated service 'http' on [::]:5280, [*]:5280
May 29 15:55:12 portmanager     error   Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
May 29 15:55:12 portmanager     error   Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
May 29 15:55:12 portmanager     info    Activated service 'https' on no ports
May 29 15:55:12 portmanager     info    Activated service 'component' on [127.0.0.1]:5347, [::1]:5347
May 29 15:55:12 conference.meet.aquilatech.com:muc_domain_mapper        info    Loading mod_muc_domain_mapper for host meet.aquilatech.com!
May 29 15:55:12 conference.meet.aquilatech.com:muc_domain_mapper        info    Loading mod_muc_domain_mapper for host callcontrol.meet.aquilatech.com!
May 29 15:55:12 conference.meet.aquilatech.com:muc_domain_mapper        info    Loading mod_muc_domain_mapper for host localhost!
May 29 15:55:12 conference.meet.aquilatech.com:muc_domain_mapper        info    Loading mod_muc_domain_mapper for host conference.meet.aquilatech.com!
May 29 15:55:12 conference.meet.aquilatech.com:muc_domain_mapper        info    Loading mod_muc_domain_mapper for host guest.meet.aquilatech.com!
May 29 15:55:12 conference.meet.aquilatech.com:muc_domain_mapper        info    Loading mod_muc_domain_mapper for host auth.meet.aquilatech.com!
May 29 15:55:12 conference.meet.aquilatech.com:muc_domain_mapper        info    Loading mod_muc_domain_mapper for host aquilatech.com!
May 29 15:55:12 conference.meet.aquilatech.com:muc_domain_mapper        info    Loading mod_muc_domain_mapper for host conferenceduration.meet.aquilatech.com!
May 29 15:55:12 conferenceduration.meet.aquilatech.com:conference_duration_component    warn    conference duration will not work with Prosody version 0.10 or less.
May 29 15:55:12 conference.meet.aquilatech.com:muc_domain_mapper        info    Loading mod_muc_domain_mapper for host speakerstats.meet.aquilatech.com!
May 29 15:55:12 speakerstats.meet.aquilatech.com:speakerstats_component warn    speaker stats will not work with Prosody version 0.10 or less.
May 29 15:55:12 conference.meet.aquilatech.com:muc_domain_mapper        info    Loading mod_muc_domain_mapper for host focus.meet.aquilatech.com!
May 29 15:55:12 conference.meet.aquilatech.com:muc_domain_mapper        info    Loading mod_muc_domain_mapper for host internal.auth.meet.aquilatech.com!
May 29 15:55:15 c2s56034c3806c0 info    Client connected
May 29 15:55:15 c2s56034c3806c0 info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
May 29 15:55:15 c2s56034c3806c0 info    Authenticated as jvb@auth.meet.aquilatech.com
May 29 15:55:24 c2s56034c4e54e0 info    Client connected
May 29 15:55:25 c2s56034c4e54e0 info    Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
May 29 15:55:25 c2s56034c4e54e0 info    Authenticated as focus@auth.meet.aquilatech.com
May 29 15:55:25 focus.meet.aquilatech.com:component     warn    Component not connected, bouncing error for: <presence id='a9hC6-4997' to='focus.meet.aquilatech.com' from='focus@auth.meet.aquilatech.com/focus'>
May 29 15:56:22 mod_bosh        info    New BOSH session, assigned it sid 'c299c564-0bbf-4534-a1d6-6d041a9bf00c'
May 29 15:56:22 boshc299c564-0bbf-4534-a1d6-6d041a9bf00c        info    Authenticated as 138e4b89-2bd1-45c2-b9ad-da5eff93de5a@guest.meet.aquilatech.com
May 29 15:56:23 focus.meet.aquilatech.com:component     warn    Component not connected, bouncing error for: <iq id='a03b3b02-f92a-4dd7-8364-aa07e7c811d5:sendIQ' type='set' to='focus.meet.aquilatech.com' from='138e4b89-2bd1-45c2-b9ad-da5eff93de5a@guest.meet.aquilatech.com/7576a6dc-b59f-4dab-b0e0-eeafe7da1a5e'>
May 29 15:56:24 focus.meet.aquilatech.com:component     warn    Component not connected, bouncing error for: <iq id='a1941693-a92f-4450-9440-9b90ba4d68ca:sendIQ' type='set' to='focus.meet.aquilatech.com' from='138e4b89-2bd1-45c2-b9ad-da5eff93de5a@guest.meet.aquilatech.com/7576a6dc-b59f-4dab-b0e0-eeafe7da1a5e'>
May 29 15:56:26 focus.meet.aquilatech.com:component     warn    Component not connected, bouncing error for: <iq id='52bb8560-48c8-4958-b1ff-919a942e2347:sendIQ' type='set' to='focus.meet.aquilatech.com' from='138e4b89-2bd1-45c2-b9ad-da5eff93de5a@guest.meet.aquilatech.com/7576a6dc-b59f-4dab-b0e0-eeafe7da1a5e'>
May 29 15:56:26 boshc299c564-0bbf-4534-a1d6-6d041a9bf00c        info    BOSH client disconnected

one second, I just realized there is another config file in the prosody folder. Posting it in a moment.

I believe this is the correct prosody config.

aquilatech.com.cfg.lua.txt (2.5 KB)

Why do you have two? This one is wrong:Component "focus.meet.aquilatech.com"
this one uses the xmpp component for jicofo, but jicofo no longer supports that.
The previous one was correct … The update if packages is taking care of that … but something in your config is wrong, not sure how that happened, but in the last file there are some mismatches from the default config, so it was edited by hand probably …

The reason is simple confusion about how the config files work on my part.
When I built the server, by step two I added ldap2 authentication. I guess at that time the config files got confused. (but this was running fine for years). Yes it was edited by hand.

I will attempt to clean that up, then re-upgrade jitsi-meet from a working backup.
Perhaps it will then update correctly.

OK, I did it. I managed to fix the prosody configuration and get the server upgraded.
Now, the only remaining problem is that jigasi is now broken, I’m looking at it…

Thanks for your help.

Hi,

could you point me to which exact change / rewriting this is? I’m running in to the same thing and I’d like to find which change I should reflect in my ansible scripts.

edit I’ve tried adding “client_proxy” to the component, and that does resolve the ‘Component not connected’ error in the logfiles, but still does not result in succesful conferences being setup. Also to check I’ve used the mod_roster_command you’ve described. Prosody, jicofo and jvb logs do not seem to log anything relevant to the issue:

Restarting prosody, showing jvb’s and jicofo connecting:

Jun 01 10:15:55 c2s562d6323ca10	info	Client connected
Jun 01 10:15:55 c2s562d6323ca10	info	Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jun 01 10:15:55 c2s562d6323ca10	info	Authenticated as jvb@auth.<meet-hostname>
Jun 01 10:15:57 c2s562d631cbc00	info	Client connected
Jun 01 10:15:57 c2s562d631cbc00	info	Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jun 01 10:15:57 c2s562d631cbc00	info	Authenticated as jvb@auth.<meet-hostname>
Jun 01 10:15:58 c2s562d63162840	info	Client connected
Jun 01 10:15:58 c2s562d63162840	info	Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jun 01 10:15:58 c2s562d63162840	info	Authenticated as jvb@auth.<meet-hostname>
Jun 01 10:16:02 c2s562d63066320	info	Client connected
Jun 01 10:16:02 c2s562d63066320	info	Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Jun 01 10:16:02 c2s562d63066320	info	Authenticated as focus@auth.<meet-hostname>

Attempting to open a new conference:

|Jun 01 10:14:24 mod_bosh|info|New BOSH session, assigned it sid 'd1c76847-070c-48c8-b39f-5b1f5b55982d'|
|---|---|---|
|Jun 01 10:14:24 boshd1c76847-070c-48c8-b39f-5b1f5b55982d|info|Authenticated as rta-rt51pkumo2ua@<meet-hostname>|
|Jun 01 10:14:26 boshd1c76847-070c-48c8-b39f-5b1f5b55982d|info|BOSH client disconnected: session close|

Thanks,
Florian

What are the errors you see in js console?

It comes down to: “Focus error, retry after …” but here is a snippet:

Logger.js:154 2021-06-02T07:23:54.835Z [modules/RTC/RTCUtils.js] onUserMediaSuccess
Logger.js:154 2021-06-02T07:23:54.848Z [conference.js] <Object.startConference>:  Initialized with 2 local tracks
Logger.js:154 2021-06-02T07:23:54.851Z [modules/xmpp/xmpp.js] <P.createRoom>:  JID _srj8zkeatl4uu_d@<meet-host>/-_nukbvi using MUC nickname 09a08342
Logger.js:154 2021-06-02T07:23:54.851Z [modules/xmpp/ChatRoom.js] <new E>:  Joined MUC as goodloansdesertconstantly@conference.<meet-host>/09a08342
Logger.js:154 2021-06-02T07:23:54.852Z [modules/e2eping/e2eping.js] <new u>:  Initializing e2e ping; pingInterval=10000, analyticsInterval=60000.
Logger.js:154 2021-06-02T07:23:54.853Z [modules/connectivity/ParticipantConnectionStatus.js] <new g>:  RtcMuteTimeout set to: 10000
Logger.js:154 2021-06-02T07:23:54.855Z [modules/statistics/AvgRTPStatsReporter.js] <new g>:  Avg RTP stats will be calculated every 15 samples
Logger.js:154 2021-06-02T07:23:54.855Z [JitsiConference.js] <new ae>:  backToP2PDelay: 5
Logger.js:154 2021-06-02T07:23:54.856Z [JitsiConference.js] <new ae>:  End-to-End Encryprtion is supported
Logger.js:154 2021-06-02T07:23:54.888Z [JitsiConference.js] <ae._doReplaceTrack>:  _doReplaceTrack - no JVB JingleSession
Logger.js:154 2021-06-02T07:23:54.889Z [JitsiConference.js] <ae._doReplaceTrack>:  _doReplaceTrack - no P2P JingleSession
Logger.js:154 2021-06-02T07:23:54.892Z [JitsiConference.js] <ae._doReplaceTrack>:  _doReplaceTrack - no JVB JingleSession
Logger.js:154 2021-06-02T07:23:54.892Z [JitsiConference.js] <ae._doReplaceTrack>:  _doReplaceTrack - no P2P JingleSession
Logger.js:154 2021-06-02T07:23:54.894Z [modules/xmpp/moderator.js] <l.setFocusUserJid>:  Focus jid set to:  undefined
Logger.js:154 2021-06-02T07:23:54.895Z [modules/xmpp/moderator.js] <l.createConferenceIq>:  Session ID: null machine UID: 2cbea2f3da1bce386dce63366383b3a8
Logger.js:154 2021-06-02T07:23:54.907Z [features/base/tracks] Replace audio track - unmuted
Logger.js:154 2021-06-02T07:23:54.912Z [features/base/tracks] Replace video track - unmuted
Logger.js:154 2021-06-02T07:23:54.944Z [features/base/redux] <Object.persistState>:  redux state persisted. b4a5207fdeeccef5d3d69330cb0cad3b -> b6586a5c65b6685631fc1394809f185c
Logger.js:154 2021-06-02T07:23:55.001Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>:  UnhandledError: Focus error, retry after 1000 Script: null Line: null Column: null StackTrace:  Error: Focus error, retry after 1000
    at l._allocateConferenceFocusError (https://<meet-host>/libs/lib-jitsi-meet.min.js?v=4985:10:165609)
    at https://<meet-host>/libs/lib-jitsi-meet.min.js?v=4985:10:164660
    at w.Handler.handler (https://<meet-host>/libs/lib-jitsi-meet.min.js?v=4985:1:31531)
    at w.Handler.run (https://<meet-host>/libs/lib-jitsi-meet.min.js?v=4985:1:26830)
    at https://<meet-host>/libs/lib-jitsi-meet.min.js?v=4985:1:35268
    at Object.forEachChild (https://<meet-host>/libs/lib-jitsi-meet.min.js?v=4985:1:18492)
    at w.Connection._dataRecv (https://<meet-host>/libs/lib-jitsi-meet.min.js?v=4985:1:35117)
    at D.Bosh._onRequestStateChange (https://<meet-host>/libs/lib-jitsi-meet.min.js?v=4985:1:55102)
o @ Logger.js:154
getGlobalOnErrorHandler @ JitsiMeetJS.js:545

Thanks,
Florian

Then, are there errors in jicofo logs?

No, jicofo is completely silent. I’ve even checked if the process is running and what is logged when it’s restarted. What I do notice here is an error at startup:

2021-06-02 11:45:21.144 SEVERE: [1] JicofoServices.<init>#95: No bridge detector configured.

There is also a warning about the Jicofo ID not being set and some other warning level items:

2021-06-02 11:47:18.903 WARNING: [1] FocusManager.start#134: Jicofo ID is not set correctly set (value=0). Configure a valid value [1-65535] by setting org.jitsi.jicofo.SHORT_ID in sip-communicator.properties or jicofo.octo.id in jicofo.conf. Future versions will require this for Octo.
2021-06-02 11:47:19.664 WARNING: [1] org.glassfish.jersey.server.wadl.WadlFeature.configure: JAXBContext implementation could not be found. WADL feature is disabled.
2021-06-02 11:47:19.780 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

I do notice that adding the ID in sip-communicator.properties no longer works, it seems we now have some mixed config, with a config file, a sip-communicator.properties, a logging.properties but also a jicofo.conf. I’m pretty sure that is also not a desirable state?

edit simply moving jicofo.conf out of the way did not change behaviour, by the way. Just checking things here.

Thanks for thinking along!
Best,
Florian

This means that there is no brewery room configured. Do you have this in your config: jicofo/postinst at f654702737e62e0a359025440b57975f24e31bfa · jitsi/jicofo · GitHub ?

Yes, that line exists in jicofo/sip-communicator.properties

Hum … its either not reading it or something else is wrong … can you upload your jicofo configs and logs from jicofo.

Hi Damian,

Thanks for bearing with me. Here’s a bunch of stuff in one:

202106021647 jicofo-debugging.txt (8.9 KB)

I also did some sanity checking on the file privileges (can the process read all of this) and that all looks good…