Jibri service is on, but in the browser it shows just "preparing to start recording", after sometime it says reload page

Govindanupam1234 · March 22, 2023, 1:30pm

Hi team,
i am facing below issue… Please help

Details to know before proceeding further step

I am using (jitsi , jibri, jvb, prosody, web ) docker unstable version.
chrome is fine absolutely fine with no issue

Only Issue is with the recording, iam unable to record meeting properly

Please find enclosed jibri logs

Thanks and regards

Govindanupam1234 · March 22, 2023, 1:31pm

Jibri 2023-03-21 11:54:22.720 SEVERE: [45] [session_id=rqucsdgvchnrnsgd] JibriSelenium.leaveCallAndQuitBrowser#360: Error trying to leave the call
org.openqa.selenium.JavascriptException: javascript error: You have already left the conference
(Session info: chrome=109.0.5414.74)
(Driver info: chromedriver=109.0.5414.74 (e7c5703604daa9cc128ccf5a5d3e993513758913-refs/branch-heads/5414@{#1172}),platform=Linux 5.4.0-113-generic 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: ‘9cdcd7572fbe’, ip: ‘172.21.0.5’, os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘5.4.0-113-generic’, java.version: ‘11.0.18’
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities {acceptInsecureCerts: false, acceptSslCerts: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 109.0.5414.74 (e7c5703604da…, userDataDir: /tmp/.com.google.Chrome.sKfWCo}, cssSelectorsEnabled: true, databaseEnabled: false, goog:chromeOptions: {debuggerAddress: localhost:46149}, 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: 109.0.5414.74, webStorageEnabled: true, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}
Session ID: ff1b17409e299b736c54ac3c375e7677
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.executeScript(RemoteWebDriver.java:480)
at org.jitsi.jibri.selenium.pageobjects.CallPage.leave(CallPage.kt:333)
at org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser(JibriSelenium.kt:358)
at org.jitsi.jibri.service.impl.FileRecordingJibriService.stop(FileRecordingJibriService.kt:197)
at org.jitsi.jibri.JibriManager.stopService(JibriManager.kt:263)
at org.jitsi.jibri.api.xmpp.XmppApi.handleStopJibriIq(XmppApi.kt:350)
at org.jitsi.jibri.api.xmpp.XmppApi.handleJibriIq(XmppApi.kt:244)
at org.jitsi.jibri.api.xmpp.XmppApi.handleIq(XmppApi.kt:225)
at org.jitsi.xmpp.mucclient.MucClient.handleIq(MucClient.java:542)
at org.jitsi.xmpp.mucclient.MucClient$3.handleIQRequest(MucClient.java:505)
at org.jivesoftware.smack.AbstractXMPPConnection$3.run(AbstractXMPPConnection.java:1565)
at org.jivesoftware.smack.AbstractXMPPConnection$10.run(AbstractXMPPConnection.java:2143)
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)

Govindanupam1234 · March 22, 2023, 1:32pm

Jibri 2023-03-21 11:54:22.782 INFO: [45] [session_id=rqucsdgvchnrnsgd] JibriSelenium.leaveCallAndQuitBrowser#363: Quitting chrome driver
Jibri 2023-03-21 11:54:22.845 FINE: [69] CallPage.visit$lambda-2$lambda-1#58: Not joined yet: null
Jibri 2023-03-21 11:54:23.205 INFO: [45] [session_id=rqucsdgvchnrnsgd] JibriSelenium.leaveCallAndQuitBrowser#365: Chrome driver quit
Jibri 2023-03-21 11:54:23.205 INFO: [45] JibriStatusManager$special$$inlined$observable$1.afterChange#72: Busy status has changed: BUSY → IDLE
Jibri 2023-03-21 11:54:23.205 FINE: [45] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
Jibri 2023-03-21 11:54:23.206 INFO: [45] XmppApi.updatePresence#209: Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})),
publishing presence to connections
Jibri 2023-03-21 11:54:23.206 FINE: [45] MucClientManager.setPresenceExtension#160: Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@2631a2c4
Jibri 2023-03-21 11:54:23.206 FINE: [45] MucClientManager.saveExtension#185: Replacing presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@77b71459
Jibri 2023-03-21 11:54:23.230 FINE: [44] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse: Could not add a provider for element busy-status from namespace
http://jitsi.org/protocol/jibri
Jibri 2023-03-21 11:54:23.231 FINE: [44] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse: Could not add a provider for element health-status from namespace http://jitsi.org/protocol/health

Govindanupam1234 · March 22, 2023, 1:38pm

Hi team,

Please help

thanks and regards

Freddie · March 22, 2023, 1:39pm

My first guess is this could be a port problem. Are you able to successfully host a meeting with 3 participants (no need to initiate recording)?

Govindanupam1234 · March 22, 2023, 1:43pm

Hi freddie,
Good day…

Oh, please let me know which configuration file i need to look into…
And yes iam able to connect 3 users in the meeting with no issue

thanks and regards,

Govindanupam1234 · March 22, 2023, 1:55pm

Hi team,
Please help me
thanks and regards

Govindanupam1234 · March 22, 2023, 1:58pm

Freddie · March 22, 2023, 2:22pm

So clearly, this is not a true statement:

Govindanupam1234 · March 22, 2023, 2:26pm

Hi freddie

I just now checked again to verify.

and now iam not able to connect 1 or 3 users to the meeting. I created a new bug for this please help

thanks and regards

Govindanupam1234 · March 23, 2023, 3:59am

Hi team.

Please help

saghul · March 23, 2023, 9:47am

You are using an unstable release. Don’t do that unless you know what you are doing. I’d suggest you use the latest stable release and take it from there.

Govindanupam1234 · March 23, 2023, 1:59pm

Hi saghul

Thank you very much for helping me out…

I just did what you mentioned… checked and its working absolutely perfect

Thanks and regards