Jibri Recording Unavailable Error

meet
#1

Hi,

We have configured jitsi-meet on a google-cloud instance and jibri on another gcp instance. Jitsi-meet works as expected, but we have issues in setting up recording enabled using jibri.

i have attached the logs of jibri and jicofo.

jibri logs:

root@instance-3:/var/log/jitsi/jibri# tail -f log.0.txt
2019-05-07 16:48:14.994 INFO: [1] org.jitsi.jibri.Main.main() Using port 3333 for internal HTTP API
2019-05-07 16:48:14.994 INFO: [1] org.jitsi.jibri.Main.main() Using port 2222 for the HTTP API
2019-05-07 16:48:16.003 INFO: [1] org.jitsi.jibri.Main.loadConfig() Parsed config:
JibriConfig(recordingDirectory=/tmp/recordings, enabledStatsD=true, finalizeRecordingScriptPath=/tmp/finalize_recording.sh, xmppEnvironments=[XmppEnvironmentConfig(name=domain.com, xmppServerHosts=[domain.com], xmppDomain=domain.com, controlLogin=XmppCredentials(domain=domain.com, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.domain.com, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.domain.com, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)])
2019-05-07 16:48:16.999 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.internal.InternalHttpApi registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.jibri.api.http.internal.InternalHttpApi will be ignored.
2019-05-07 16:48:17.621 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() Connecting to xmpp environment on domain.com with config XmppEnvironmentConfig(name=domain.com, xmppServerHosts=[domain.com], xmppDomain=domain.com, controlLogin=XmppCredentials(domain=auth.domain.com, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.domain.com, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.domain.com, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)
2019-05-07 16:48:17.642 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted
2019-05-07 16:48:47.692 WARNING: [20] org.jivesoftware.smackx.ping.PingManager.pingServerIfNecessary() XMPPConnection was not authenticated
2019-05-07 16:48:47.999 SEVERE: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() Error connecting to xmpp environment: org.jivesoftware.smack.SmackException$ConnectionException: The following addresses failed: ‘domain.com:5222’ failed because: domain.com/x.x.x.x exception: java.net.SocketTimeoutException: connect timed out
2019-05-07 16:48:48.098 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.HttpApi registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.jibri.api.http.HttpApi will be ignored.

jicofo.log:

Jicofo 2019-05-07 16:48:23.027 INFO: [25] org.jitsi.jicofo.FocusManager.log() XMPP provider reg state: RegistrationState=Registered
Jicofo 2019-05-07 16:48:23.041 INFO: [25] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.doConnect().309 XMPP provider Jabber:focus@auth.domain.com/focus84244005529697@localhost connected (JID: focus@auth.domain.com/focus84244005529697)
Jicofo 2019-05-07 16:48:25.077 INFO: [47] org.jitsi.jicofo.xmpp.FocusComponent.handleConferenceIq().402 Focus request for room: mini@conference.domain.com
Jicofo 2019-05-07 16:48:25.089 INFO: [47] org.jitsi.jicofo.FocusManager.log() Created new focus for mini@conference.domain.com@auth.domain.com. Conference count 1,options:
Jicofo 2019-05-07 16:48:25.090 INFO: [47] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Lip-sync enabled in mini@conference.domain.com
Jicofo 2019-05-07 16:48:25.091 INFO: [47] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Joining the room: mini@conference.domain.com
Jicofo 2019-05-07 16:48:25.220 WARNING: [47] org.jitsi.xmpp.component.ComponentBase.verifyProcessingTime().540 PROCESSING TIME LIMIT EXCEEDED - it took 147ms to process:
Jicofo 2019-05-07 16:48:26.049 INFO: [37] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberJoined sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@3f43e486 member=ChatMember[mini@conference.domain.com/1f28b760, jid: null]@1994971815]
Jicofo 2019-05-07 16:48:26.053 INFO: [37] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Granted owner to mini@conference.domain.com/1f28b760
Jicofo 2019-05-07 16:48:26.053 INFO: [37] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member mini@domain.com/1f28b760 joined.
Jicofo 2019-05-07 16:50:52.647 SEVERE: [100] org.jitsi.jicofo.recording.jibri.JibriSession.log() Unable to find an available Jibri, can’t start
Jicofo 2019-05-07 16:50:52.648 INFO: [100] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Failed to start a Jibri session, no Jibris available

Kindly suggest if something is still missing.