FocusManager error GRAVE in Jitsi stable 7577

In version 7577, when I try to start a room, I get this error in console:

ago 05, 2022 5:45:10 PM org.jitsi.utils.logging2.LoggerImpl log
INFORMAZIONI: Focus request for room: 5509325956@conference.meet-dev.vianova.it
ago 05, 2022 5:45:10 PM org.jitsi.utils.logging2.LoggerImpl log
INFORMAZIONI: Authentication session created for marco.scammacca_welcomeitalia.it@meet-dev.vianova.it SID: 164a0c52-2c5b-49e7-b0d7-0c62c8542fb2
ago 05, 2022 5:45:10 PM org.jitsi.utils.logging2.LoggerImpl log
INFORMAZIONI: Authenticated jid: marco.scammacca_welcomeitalia.it@meet-dev.vianova.it/18IuQb4S with session: AuthSession[ID=marco.scammacca_welcomeitalia.it@meet-dev.vianova.it, JID=marco.scammacca_welcomeitalia.it@meet-dev.vianova.it/18IuQb4S, SID=164a0c52-2c5b-49e7-b0d7-0c62c8542fb2, MUID=909c6212adae6df459e0f4c93a009f9c, LIFE_TM_SEC=0, R=5509325956@conference.meet-dev.vianova.it]@895521257
ago 05, 2022 5:45:10 PM org.jitsi.utils.logging2.LoggerImpl log
INFORMAZIONI: Jid marco.scammacca_welcomeitalia.it@meet-dev.vianova.it/18IuQb4S authenticated as: marco.scammacca_welcomeitalia.it@meet-dev.vianova.it
ago 05, 2022 5:45:10 PM org.jitsi.utils.logging2.LoggerImpl log
GRAVE: An uncaught exception occurred in thread=Thread[Jicofo Global IO Poolpool-2-thread-22,5,main]
java.lang.NullPointerException
        at java.base/java.util.Objects.requireNonNull(Objects.java:221)
        at org.jitsi.jicofo.conference.JitsiMeetConferenceImpl.<init>(JitsiMeetConferenceImpl.java:250)
        at org.jitsi.jicofo.FocusManager.createConference(FocusManager.java:254)
        at org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:200)
        at org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:162)
        at org.jitsi.jicofo.FocusManager.conferenceRequest(FocusManager.java:141)
        at org.jitsi.jicofo.xmpp.ConferenceIqHandler.handleConferenceIq(ConferenceIqHandler.kt:72)
        at org.jitsi.jicofo.xmpp.ConferenceIqHandler.handleIQRequest$lambda-4(ConferenceIqHandler.kt:156)
        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)

ago 05, 2022 5:45:15 PM org.jitsi.utils.logging2.LoggerImpl log
INFORMAZIONI: Focus request for room: 5509325956@conference.meet-dev.vianova.it
ago 05, 2022 5:45:16 PM org.jitsi.utils.logging2.LoggerImpl log
GRAVE: Error when doing health-check on: Bridge[jid=jvbbrewery@internal.auth.meet-dev.vianova.it/meet-dev.vianova.it, version=2.1.634-gff8609ad, relayId=null, region=null, stress=0,00]
java.lang.NullPointerException
        at java.base/java.util.Objects.requireNonNull(Objects.java:221)
        at org.jitsi.jicofo.bridge.JvbDoctor.getConnection(JvbDoctor.java:77)
        at org.jitsi.jicofo.bridge.JvbDoctor$HealthCheckTask.doHealthCheck(JvbDoctor.java:162)
        at org.jitsi.jicofo.bridge.JvbDoctor$AbstractHealthCheckTask.run(JvbDoctor.java:266)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
        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)

ps. Our setup is docker-free and based on secure-domain and single moderator.

Marco

Do you see a malfunction on the client side?

Yes, the room does not start :sob:

Hi, we solved this problem by understanding that the anomaly was on the Jicofo deployment.

We were copying the libraries and jars to the / usr / share / jicofo folder, so too many resulted.

By deleting all the Jicofo folder and releasing only the clean version, Jicofo starts correctly, port 8888 starts and I no longer have the healt-check error.