Jibri Removed from Brewery after 1-2hrs of standy

Hi, all - wondering if anyone else has encountered this issue before?

I setup a Jibri instance which is able to connect, authenticate, record and stream without issue. However, after 1-2hrs of standby, the Jibri will just get kicked out of the JibriBrewery as if it was disconnected, but the Jibri is still running fine.

In jicofo logs, we can see when the Jibri joins and then an ~1.5hrs later, is removed:

Jicofo 2022-01-26 01:58:10.864 INFO: [6192] [type=jibri brewery=jibribrewery] BaseBrewery.addInstance#341: Added brewery instance: jibribrewery@internal.auth.jitsi-meet.mydomain.com/689b57ba-7e4b-11ec-8f40-001dd84034f1
Jicofo 2022-01-26 01:58:10.864 INFO: [6192] JibriDetector.onInstanceStatusChanged#95: Creating a new instance for jibribrewery@internal.auth.jitsi-meet.mydomain.com/689b57ba-7e4b-11ec-8f40-001dd84034f1, available = true
Jicofo 2022-01-26 03:29:31.011 INFO: [6218] [type=jibri brewery=jibribrewery] BaseBrewery.removeInstance#353: Removed brewery instance: jibribrewery@internal.auth.jitsi-meet.mydomain.com/689b57ba-7e4b-11ec-8f40-001dd84034f1
Jicofo 2022-01-26 03:29:31.012 INFO: [6218] JibriDetector.notifyInstanceOffline#118: Removing instance jibribrewery@internal.auth.jitsi-meet.mydomain.com/689b57ba-7e4b-11ec-8f40-001dd84034f1

I am not sure what could be causing this given that the Jibri instances work perfectly fine otherwise.

Checking the Jibri logs shows that the Jibri connected to the MUC and is standing by without issue

2022-01-26 01:58:08.716 INFO: [1] MainKt.handleCommandLineArgs#185: Jibri run with args [--config, /etc/jitsi/jibri/config.json]
2022-01-26 01:58:08.833 INFO: [1] MainKt.setupLegacyConfig#210: Checking legacy config file /etc/jitsi/jibri/config.json
2022-01-26 01:58:08.833 INFO: [1] MainKt.setupLegacyConfig#213: Legacy config file /etc/jitsi/jibri/config.json doesn't exist
2022-01-26 01:58:09.147 INFO: [1] MainKt.main#55: Jibri starting up with id 
2022-01-26 01:58:09.626 INFO: [1] JwtInfo$Companion.fromConfig#154: got jwtConfig: {}

2022-01-26 01:58:09.627 INFO: [1] JwtInfo$Companion.fromConfig#164: Unable to create JwtInfo: com.typesafe.config.ConfigException$Missing: reference.conf @ jar:file:/opt/jitsi/jibri/jibri.jar!/reference.conf: 62: No configuration setting found for key 'signing-key-path'
2022-01-26 01:58:09.789 INFO: [1] MainKt.main#125: Using port 3333 for internal HTTP API
2022-01-26 01:58:09.816 FINE: [18] WebhookClient$updateStatus$1.invokeSuspend#107: Updating 0 subscribers of status
2022-01-26 01:58:10.246 INFO: [1] XmppApi.updatePresence#144: Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections
2022-01-26 01:58:10.255 INFO: [1] XmppApi.start#97: Connecting to xmpp environment on jitsi-meet.mydomain.com with config XmppEnvironmentConfig(name=Jibri Sessions, xmppServerHosts=[jitsi-meet.mydomain.com], xmppDomain=jitsi-meet.mydomain.com, baseUrl=null, controlLogin=XmppCredentials(domain=auth.jitsi-meet.mydomain.com, port=null, username=jibri, password=*****), controlMuc=XmppMuc(domain=internal.auth.jitsi-meet.mydomain.com, roomName=JibriBrewery, nickname=689b57ba-7e4b-11ec-8f40-001dd84034f1), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.jitsi-meet.mydomain.com, port=null, username=recorder, password=*****), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true, securityMode=null)
2022-01-26 01:58:10.259 INFO: [1] XmppApi.start#109: The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted
2022-01-26 01:58:10.292 INFO: [1] MainKt.main#151: Using port 2222 for HTTP API
2022-01-26 01:58:10.295 INFO: [29] [hostname=jitsi-meet.mydomain.com id=jitsi-meet.mydomain.com] MucClient.initializeConnectAndJoin#272: Initializing a new MucClient for [ org.jitsi.xmpp.mucclient.MucClientConfiguration id=jitsi-meet.mydomain.com domain=auth.jitsi-meet.mydomain.com hostname=jitsi-meet.mydomain.com port=null username=jibri mucs=[jibribrewery@internal.auth.jitsi-meet.mydomain.com] mucNickname=689b57ba-7e4b-11ec-8f40-001dd84034f1 disableCertificateVerification=true]
2022-01-26 01:58:10.344 WARNING: [29] MucClient.createXMPPTCPConnectionConfiguration#114: Disabling certificate verification!
2022-01-26 01:58:10.382 INFO: [29] [hostname=jitsi-meet.mydomain.com id=jitsi-meet.mydomain.com] MucClient.initializeConnectAndJoin#331: Dispatching a thread to connect and login.
2022-01-26 01:58:10.717 INFO: [29] [hostname=jitsi-meet.mydomain.com id=jitsi-meet.mydomain.com] MucClient$2.connected#304: Connected.
2022-01-26 01:58:10.718 INFO: [29] [hostname=jitsi-meet.mydomain.com id=jitsi-meet.mydomain.com] MucClient.lambda$getConnectAndLoginCallable$8#628: Logging in.
2022-01-26 01:58:10.800 INFO: [29] [hostname=jitsi-meet.mydomain.com id=jitsi-meet.mydomain.com] MucClient$2.authenticated#310: Authenticated, b=false
2022-01-26 01:58:10.850 INFO: [29] [hostname=jitsi-meet.mydomain.com id=jitsi-meet.mydomain.com] MucClient$MucWrapper.join#748: Joined MUC: jibribrewery@internal.auth.jitsi-meet.mydomain.com
2022-01-26 01:59:09.781 FINE: [18] WebhookClient$updateStatus$1.invokeSuspend#107: Updating 0 subscribers of status
2022-01-26 02:00:09.781 FINE: [18] WebhookClient$updateStatus$1.invokeSuspend#107: Updating 0 subscribers of status
2022-01-26 02:01:09.781 FINE: [18] WebhookClient$updateStatus$1.invokeSuspend#107: Updating 0 subscribers of status