Occasionally in Jibri I get the following error:
Build info: version: ‘unknown’, revision: ‘unknown’, time: ‘unknown’
System info: host: ‘ip-172-31-94-109’, ip: ‘172.31.94.109’, os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘5.4.0-58-generic’, java.version: ‘11.0.17’
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities {acceptInsecureCerts: false, acceptSslCerts: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 107.0.5304.62 (1eec40d3a576…, userDataDir: /tmp/.com.google.Chrome.WsYiTE}, cssSelectorsEnabled: true, databaseEnabled: false, goog:chromeOptions: {debuggerAddress: localhost:40367}, 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: 108.0.5359.94, webStorageEnabled: true, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}
Session ID: 7c114dc14cff8a86c227de0e1db72e49
at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:81)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:271)
at org.jitsi.jibri.selenium.pageobjects.CallPage.leave(CallPage.kt:345)
at org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser(JibriSelenium.kt:358)
at org.jitsi.jibri.service.impl.StreamingJibriService.stop(StreamingJibriService.kt:141)
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)
2022-12-04 14:39:20.998 INFO: [46] [session_id=vfpumzajqiujiics] JibriSelenium.leaveCallAndQuitBrowser#363: Quitting chrome driver
2022-12-04 14:39:21.067 INFO: [46] [session_id=vfpumzajqiujiics] JibriSelenium.leaveCallAndQuitBrowser#365: Chrome driver quit
2022-12-04 14:39:21.067 INFO: [46] [session_id=vfpumzajqiujiics] StreamingJibriService.stop#142: Quit selenium
2022-12-04 14:39:21.067 INFO: [46] JibriStatusManager$special$$inlined$observable$1.afterChange#72: Busy status has changed: BUSY → IDLE
2022-12-04 14:39:21.068 FINE: [46] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status
2022-12-04 14:39:21.068 INFO: [46] XmppApi.updatePresence#209: Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections
Which seems to be WebDriverWait.timeoutException.
Is there a way to increase the timout for Jibri? Or is the a Chrome time out?