Recording ends as soon as it starts

When I start recording it stops immediately and I get
org.openqa.selenium.WebDriverException: unknown error: net::ERR_NAME_NOT_RESOLVED
in jibri logs.

Error logs in jicofo and jibri are as follows

JICOFO

KKJ7-2118’ type=‘result’><jibri xmlns='http://jitsi.org/protocol/jibri’ status=‘pending’/> for abc@muc.meet.jitsi
Jicofo 2022-06-06 08:00:23.824 INFO: [233] JibriSession.handleJibriStatusUpdate#623: Got Jibri status update: Jibri jibribrewery@internal-muc.meet.jitsi/jibri-372600937 has status pending and failure reason null, current Jibri jid is jibribrewery@internal-muc.meet.jitsi/jibri-372600937
Jicofo 2022-06-06 08:00:23.824 INFO: [233] [room=abc@muc.meet.jitsi meeting_id=19bb5135-4751-498c-ac10-6bc39b45ed9c] JibriRecorder.handleStartRequest#113: Started Jibri session
Jicofo 2022-06-06 08:00:23.958 INFO: [233] JibriSession.processJibriIqFromJibri#435: Updating status from JIBRI: <jibri xmlns='http://jitsi.org/protocol/jibri’ status=‘off’ failure_reason=‘error’ should_retry=‘true’/> for abc@muc.meet.jitsi
Jicofo 2022-06-06 08:00:23.958 INFO: [233] JibriSession.handleJibriStatusUpdate#623: Got Jibri status update: Jibri jibribrewery@internal-muc.meet.jitsi/jibri-372600937 has status off and failure reason error, current Jibri jid is jibribrewery@internal-muc.meet.jitsi/jibri-372600937
Jicofo 2022-06-06 08:00:23.958 INFO: [233] JibriSession.clearPendingTimeout#575: Jibri is no longer pending, cancelling pending timeout task
Jicofo 2022-06-06 08:00:23.959 INFO: [233] JibriSession.handleJibriStatusUpdate#662: Jibri failed, trying to fall back to another Jibri
Jicofo 2022-06-06 08:00:23.959 SEVERE: [233] JibriSession.startInternal#308: Unable to find an available Jibri, can’t start
Jicofo 2022-06-06 08:00:23.960 WARNING: [233] JibriSession.handleJibriStatusUpdate#673: Failed to fall back to another Jibri, this session has now failed: org.jitsi.jicofo.jibri.JibriSession$StartException$AllBusy: All jibri instances are busy
org.jitsi.jicofo.jibri.JibriSession$StartException$AllBusy: All jibri instances are busy
at org.jitsi.jicofo.jibri.JibriSession.startInternal(JibriSession.java:312)
at org.jitsi.jicofo.jibri.JibriSession.start(JibriSession.java:286)
at org.jitsi.jicofo.jibri.JibriSession.retryRequestWithAnotherJibri(JibriSession.java:599)
at org.jitsi.jicofo.jibri.JibriSession.handleJibriStatusUpdate(JibriSession.java:666)
at org.jitsi.jicofo.jibri.JibriSession.processJibriIqFromJibri(JibriSession.java:437)
at org.jitsi.jicofo.jibri.JibriSession.processJibriIqRequestFromJibri(JibriSession.java:421)
at org.jitsi.jicofo.jibri.BaseJibri.doHandleIQRequest(BaseJibri.kt:155)
at org.jitsi.jicofo.jibri.BaseJibri.incomingIqQueue$lambda-0(BaseJibri.kt:56)
at org.jitsi.utils.queue.PacketQueue$HandlerAdapter.handleItem(PacketQueue.java:416)
at org.jitsi.utils.queue.AsyncQueueHandler$1.run(AsyncQueueHandler.java:136)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
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)

JIBRI

Jibri 2022-06-06 15:00:23.699 INFO: [137] AbstractPageObject.visit#32: Visiting url https://meet.jitsi
Jibri 2022-06-06 15:00:23.811 FINE: [41] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse: Could not add a provider for element busy-status from namespace http://jitsi.org/protocol/jibri
Jibri 2022-06-06 15:00:23.812 FINE: [41] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse: Could not add a provider for element health-status from namespace http://jitsi.org/protocol/health
Jibri 2022-06-06 15:00:23.952 SEVERE: [137] [session_id=vpzjpoqaijghpdgh] JibriSelenium$joinCall$1.run#325: An error occurred while joining the call
org.openqa.selenium.WebDriverException: unknown error: net::ERR_NAME_NOT_RESOLVED
(Session info: chrome=96.0.4664.45)
(Driver info: chromedriver=96.0.4664.45 (76e4c1bb2ab4671b8beba3444e61c0f17584b2fc-refs/branch-heads/4664@{#947}),platform=Linux 4.18.0-240.el8.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
Build info: version: ‘unknown’, revision: ‘unknown’, time: ‘unknown’
System info: host: ‘jitsi-fd89cb659-82p7p’, ip: ‘172.17.0.5’, os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘4.18.0-240.el8.x86_64’, java.version: ‘11.0.14’
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities {acceptInsecureCerts: false, acceptSslCerts: false, applicationCacheEnabled: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 96.0.4664.45 (76e4c1bb2ab46…, userDataDir: /tmp/.com.google.Chrome.RI2XxA}, cssSelectorsEnabled: true, databaseEnabled: false, goog:chromeOptions: {debuggerAddress: localhost:46767}, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX, proxy: Proxy(), rotatable: false, setWindowRect: true, strictFileInteractability: false, takesHeapSnapshot: true, takesScreenshot: true, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unexpectedAlertBehaviour: ignore, unhandledPromptBehavior: ignore, version: 96.0.4664.45, webStorageEnabled: true, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}
Session ID: 6d16a9990c92546e0c518ef21d247fae
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
at org.openqa.selenium.remote.http.JsonHttpResponseCodec.reconstructValue(JsonHttpResponseCodec.java:40)
at org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:80)
at org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:44)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:158)
at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:543)
at org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:271)
at org.jitsi.jibri.selenium.pageobjects.AbstractPageObject.visit(AbstractPageObject.kt:35)
at org.jitsi.jibri.selenium.JibriSelenium$joinCall$1.run(JibriSelenium.kt:293)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
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)
Jibri 2022-06-06 15:00:23.954 INFO: [137] [session_id=vpzjpoqaijghpdgh] JibriSelenium.onSeleniumStateChange#215: Transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call
Jibri 2022-06-06 15:00:23.955 INFO: [137] [session_id=vpzjpoqaijghpdgh] StatefulJibriService.onServiceStateChange#39: File recording service transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call
Jibri 2022-06-06 15:00:23.956 INFO: [137] XmppApi$createServiceStatusHandler$1.invoke#311: Current service had an error Error: FailedToJoinCall SESSION Failed to join the call, sending error iq <jibri xmlns='http://jitsi.org/protocol/jibri’ status=‘off’ failure_reason=‘error’ should_retry=‘true’/>
Jibri 2022-06-06 15:00:23.957 FINE: [137] JibriStatsDClient.incrementCounter#38: Incrementing statsd counter: stop:recording

Can jibri ping JMS using its FQDN?

Did you configure the public URL in the Jibri config? That one seems wrong.

Manged to fix this issue. All I had to do was add the api section to the JVB
image

But in return I got another issue with the chrome and the chrome driver

You must be using an old release. That setting no longer exists.

Yes I think so …I’m using stable release 7001

Please update then, we don’t have the resources to support old releases sorry.

Where am I can find this file?

sorry I dont have it in a public repository. but I can share a file with some redacted data