-
Notifications
You must be signed in to change notification settings - Fork 322
Open
Description
Description
Using docker jitsi/jibri:stable-10655 some (not all and didn't find a pattern) recordings fails, and let Jibri instance in a busy state.
Current behavior
Recording is present in /config/recording folder but are never uploaded, and Jibri is reporting a busy state and never came available again.
Expected Behavior
Should upload the recording and became available after a recording session.
Possible Solution
don't know
Steps to reproduce
don't know
Environment details
Jibri 2026-01-07 11:58:30.832 INFO: [13873] XmppApi.handleJibriIq#229: Received JibriIq <iq xmlns='jabber:client' to='jibri@auth.*/XmK1XVlEL6PS' from='jibribrewery@internal-muc.*/focus' id='*==' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' action='stop' session_id='375afd59-0b5e-48bf-94ac-24d5d90803ec'/></iq> from environment [MucClient id=prosody hostname=prosody]
...
Jibri 2026-01-07 11:58:33.244 INFO: [13873] [session_id=375afd59-0b5e-48bf-94ac-24d5d90803ec] JibriSelenium.leaveCallAndQuitBrowser#362: Leaving web call
Exactly 3 hours later (looks like a timeout)...
Jibri 2026-01-07 14:58:33.259 SEVERE: [13873] [session_id=375afd59-0b5e-48bf-94ac-24d5d90803ec] JibriSelenium.leaveCallAndQuitBrowser#366: Error trying to leave the call
org.openqa.selenium.WebDriverException: java.net.SocketTimeoutException: timeout
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: host: 'jibri-7d8c68dd48-p7b95', ip: '10.233.67.33', os.name: 'Linux', os.arch: 'amd64', os.version: '5.10.0-0.bpo.12-amd64', java.version: '17.0.17'
Jibri 2026-01-07 14:58:33.260 INFO: [13873] [session_id=375afd59-0b5e-48bf-94ac-24d5d90803ec] JibriSelenium.leaveCallAndQuitBrowser#369: Quitting chrome driver
Even after 3 hours we seems stuck in chromeDriver.quit()
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels