Jibri server not found while recording meeting

Hello Everyone
we have configured jibri on docker container in order to record conference meeting, and i have allowed all the ports it required to run jibri, and after running container jibri service is running correctly. but when i try to record the conference it say recorders failed to start, when i checked the log of jicofo is shows jibri server not found. below i am giving jicofo server logs.

Jicofo 2019-01-17 05:53:23.744 INFO: [38] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member docker@conference.jitsiapp.xxx.xxx.xxx/997efd0c joined.
Jicofo 2019-01-17 05:53:34.266 INFO: [99] org.jitsi.jicofo.recording.jibri.JibriSession.log() Starting Jibri jibribrewery@internal.auth.jitsiapp.xxx.xxx.xxx/jibri for stream ID: null in room: docker@conference.jitsiapp.xxx.xxx.xxx
Jicofo 2019-01-17 05:53:34.285 INFO: [99] org.jitsi.jicofo.recording.jibri.JibriSession.log() Got Jibri status update: Jibri jibribrewery@internal.auth.jitsiapp.xxx.xxx.xxx/jibri has status pending and failure reason null
Jicofo 2019-01-17 05:53:34.286 INFO: [99] org.jitsi.jicofo.recording.jibri.JibriSession.log() Starting session with Jibri jibribrewery@internal.auth.jitsiapp.xxx.xxx.xxx/jibri
Jicofo 2019-01-17 05:53:34.287 INFO: [99] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Started Jibri session
Jicofo 2019-01-17 05:53:45.179 INFO: [38] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().136 Received Jibri jibribrewery@internal.auth.jitsiapp.xxx.xxx.xxx/jibri status
Jicofo 2019-01-17 05:53:45.182 INFO: [38] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().174 Jibri: jibribrewery@internal.auth.jitsiapp.xxx.xxx.xxx/jibri available: false
Jicofo 2019-01-17 05:53:45.185 INFO: [99] org.jitsi.jicofo.recording.jibri.JibriSession.log() Updating status from JIBRI: for docker@conference.jitsiapp.xxx.xxx.xxx
Jicofo 2019-01-17 05:53:45.185 INFO: [99] org.jitsi.jicofo.recording.jibri.JibriSession.log() Got Jibri status update: Jibri jibribrewery@internal.auth.jitsiapp.xxx.xxx.xxx/jibri has status off and failure reason error
Jicofo 2019-01-17 05:53:45.186 INFO: [99] org.jitsi.jicofo.recording.jibri.JibriSession.log() Jibri is no longer pending, cancelling pending timeout task
Jicofo 2019-01-17 05:53:45.186 INFO: [99] org.jitsi.jicofo.recording.jibri.JibriSession.log() Jibri failed, trying to fall back to another Jibri
Jicofo 2019-01-17 05:53:45.187 SEVERE: [99] org.jitsi.jicofo.recording.jibri.JibriSession.log() Unable to find an available Jibri, can’t start
Jicofo 2019-01-17 05:53:45.187 INFO: [99] org.jitsi.jicofo.recording.jibri.JibriSession.log() Failed to fall back to another Jibri, this session has now failed
Jicofo 2019-01-17 05:53:45.188 INFO: [99] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Got jibri status off and failure error
Jicofo 2019-01-17 05:53:45.189 INFO: [99] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Publishing new jibri-recording-status: in: docker@conference.jitsiapp.xxx.xxx.xxx
Jicofo 2019-01-17 05:53:45.190 INFO: [99] org.jitsi.jicofo.recording.jibri.JibriSession.log() Cleaning up current JibriSession
Jicofo 2019-01-17 05:53:45.234 INFO: [38] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().136 Received Jibri jibribrewery@internal.auth.jitsiapp.xxx.xxx.xxx/jibri status
Jicofo 2019-01-17 05:53:45.235 INFO: [38] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().174 Jibri: jibribrewery@internal.auth.jitsiapp.xxx.xxx.xxx/jibri available: false
Jicofo 2019-01-17 05:53:45.353 INFO: [38] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().136 Received Jibri jibribrewery@internal.auth.jitsiapp.xxx.xxx.xxx/jibri status
Jicofo 2019-01-17 05:53:45.354 INFO: [38] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().174 Jibri: jibribrewery@internal.auth.jitsiapp.xxx.xxx.xxx/jibri available: false
Jicofo 2019-01-17 05:54:18.095 INFO: [38] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberLeft sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@72a26ce3 member=ChatMember[docker@conference.jitsiapp.xxx.xxx.xxx/997efd0c, jid: 997efd0c-3ec6-4866-bbf7-e0a855cffcf0@guest.jitsiapp.xxx.xxx.xxx/3e0a0c8e-0b89-498c-9f6a-40a6f986f81e]@626003009]
Jicofo 2019-01-17 05:54:18.095 INFO: [38] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member docker@conference.jitsiapp.xxx.xxx.xxx/997efd0c is leaving
Jicofo 2019-01-17 05:54:18.096 WARNING: [38] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Participant not found for docker@conference.jitsiapp.xxx.xxx.xxx/997efd0c terminated already or never started ?
Jicofo 2019-01-17 05:54:18.117 INFO: [38] org.jitsi.jicofo.FocusManager.log() Disposed conference for room: docker@conference.jitsiapp.xxx.xxx.xxx conference count: 0

Thanks
Regard Nexio

You’re running Jibri in a docker container? That’s not a configuration we’ve played with, so I’d call it experimental at best. Can you attach Jibri logs?

Hello bbaldino,
thank you for response, here i mentioned jibri(on docker container) log
$ cat log.0.txt
2019-01-18 08:16:05.553 INFO: [1] org.jitsi.jibri.Main.main() Jibri run with args [–config, /etc/jitsi/jibri/config.json]
2019-01-18 08:16:05.559 INFO: [1] org.jitsi.jibri.Main.main() Using config file /etc/jitsi/jibri/config.json
2019-01-18 08:16:05.560 INFO: [1] org.jitsi.jibri.Main.main() Using port 3333 for internal HTTP API
2019-01-18 08:16:05.560 INFO: [1] org.jitsi.jibri.Main.main() Using port 2222 for the HTTP API
2019-01-18 08:16:06.351 INFO: [1] org.jitsi.jibri.Main.loadConfig() Parsed config:
JibriConfig(recordingDirectory=/srv/recordings, enabledStatsD=true, finalizeRecordingScriptPath=/path/to/finalize_recording.sh, xmppEnvironments=[XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[jitsiapp.xxx.xxx.xxx], xmppDomain=jitsiapp.xxx.xxx.xxx, controlLogin=XmppCredentials(domain=auth.jitsiapp.xxx.xxx.xxx, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.jitsiapp.xxx.xxx.xxx, roomName=JibriBrewery, nickname=jibri12), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.jitsiapp.xxx.xxx.xxx, username=recorder, password=xxxx), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)])
2019-01-18 08:16:07.078 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-01-18 08:16:07.426 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() Connecting to xmpp environment on jitsiapp.xxx.xxx.xxx with config XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[jitsiapp.xxx.xxx.xxx], xmppDomain=jitsiapp.xxx.xxx.xxx, controlLogin=XmppCredentials(domain=auth.jitsiapp.xxx.xxx.xxx, username=jibri, password=xxxxxx), controlMuc=XmppMuc(domain=internal.auth.jitsiapp.xxx.xxx.xxx, roomName=JibriBrewery, nickname=jibri12), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.jitsiapp.xxx.xxx.xxx, username=recorder, password=xxxxxx), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)
2019-01-18 08:16:07.436 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-01-18 08:16:07.810 INFO: [1] class org.jitsi.xmpp.mucclient.MucClient.connected() [prod environment: auth.jitsiapp.xxx.xxx.xxx@jitsiapp.xxx.xxx.xxx] Xmpp connection status: connected
2019-01-18 08:16:07.905 INFO: [1] class org.jitsi.xmpp.mucclient.MucClient.authenticated() [prod environment: auth.jitsiapp.xxx.xxx.xxx@jitsiapp.xxx.xxx.xxx] Xmpp connection status: authenticated (resume from previous? false)
2019-01-18 08:16:07.981 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.

Thanks
Regard Nexio

Jibri is not seeing any requests, so Jicofo isn’t seeing the Jibri at all. Do you have the JibriBrewery config on both Jibri and Jicofo? Can you attach Jicofo logs?