Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cloud recording is not working when password is set. #1927

Open
TGC-PratikNanavare opened this issue Oct 9, 2024 · 1 comment
Open

Cloud recording is not working when password is set. #1927

TGC-PratikNanavare opened this issue Oct 9, 2024 · 1 comment

Comments

@TGC-PratikNanavare
Copy link

When i set the password for the meeting and try to start recording the recording is not able to start.

Jibri Logs :-

Jibri 2024-10-09 05:40:27.210 FINE: [18] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status Jibri 2024-10-09 05:41:04.268 FINE: [119] [hostname=xmpp.meet.jitsi id=xmpp.meet.jitsi] MucClient$3.handleIQRequest#513: Received an IQ with type set: IQ Stanza (jibri http://jitsi.org/protocol/jibri) [to=jibri@auth.meet.jitsi/K7qoGYDX97YC,from=jibribrewery@internal-muc.meet.jitsi/focus,id=amlicmlAYXV0aC5tZWV0LmppdHNpL0s3cW9HWURYOTdZQwA1NFRIMS0xODY5NQACg8ukyUqJHg==,type=set,] Jibri 2024-10-09 05:41:04.269 INFO: [119] XmppApi.handleJibriIq#239: Received JibriIq <iq xmlns='jabber:client' to='jibri@auth.meet.jitsi/K7qoGYDX97YC' from='jibribrewery@internal-muc.meet.jitsi/focus' id='amlicmlAYXV0aC5tZWV0LmppdHNpL0s3cW9HWURYOTdZQwA1NFRIMS0xODY5NQACg8ukyUqJHg==' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' action='start' recording_mode='file' room='pratik_nanavare-717@muc.meet.jitsi' session_id='xjojgcwjqzfxwhac' app_data='{"file_recording_metadata":{"share":true}}'/></iq> from environment [MucClient id=xmpp.meet.jitsi hostname=xmpp.meet.jitsi] Jibri 2024-10-09 05:41:04.269 INFO: [119] XmppApi.handleStartJibriIq#271: Received start request, starting service Jibri 2024-10-09 05:41:04.271 INFO: [119] XmppApi.handleStartService#382: Parsed call url info: CallUrlInfo(baseUrl=https://record.viziondev1.com:9445/, callName=pratik_nanavare-717, urlParams=[]) Jibri 2024-10-09 05:41:04.272 INFO: [119] JibriManager.startFileRecording#152: Starting a file recording with params: FileRecordingRequestParams(callParams=CallParams(callUrlInfo=CallUrlInfo(baseUrl=https://record.viziondev1.com:9445/, callName=pratik_nanavare-717, urlParams=[]), email='', passcode=null, callStatsUsernameOverride=, displayName=), sessionId=xjojgcwjqzfxwhac, callLoginParams=XmppCredentials(domain=recorder.meet.jitsi, port=null, username=recorder, password=*****)) Jibri 2024-10-09 05:41:04.272 FINE: [119] [session_id=xjojgcwjqzfxwhac] FfmpegCapturer.<init>#92: Detected os as OS: LINUX Jibri 2024-10-09 05:41:04.273 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: ConfigSourceSupplier: Trying to retrieve key 'jibri.chrome.flags' from source 'config' as type kotlin.collections.List<kotlin.String> Jibri 2024-10-09 05:41:04.274 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: ConfigSourceSupplier: Found value [--ignore-certificate-errors] for key 'jibri.chrome.flags' from source 'config' as type kotlin.collections.List<kotlin.String> Starting ChromeDriver 126.0.6478.182 (5b5d8292ddf182f8b2096fa665b473b6317906d5-refs/branch-heads/6478@{#1776}) on port 10808 Only local connections are allowed. Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe. ChromeDriver was started successfully. Jibri 2024-10-09 05:41:04.658 INFO: [119] org.openqa.selenium.remote.ProtocolHandshake.createSession: Detected dialect: OSS Jibri 2024-10-09 05:41:04.663 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: FallbackSupplier: checking for value via suppliers: LambdaSupplier: 'JibriConfig::recordingDirectory' ConfigSourceSupplier: key: 'jibri.recording.recordings-directory', type: 'kotlin.String', source: 'config' Jibri 2024-10-09 05:41:04.663 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: LambdaSupplier: Trying to retrieve value via JibriConfig::recordingDirectory Jibri 2024-10-09 05:41:04.663 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: FallbackSupplier: failed to find value via LambdaSupplier: 'JibriConfig::recordingDirectory': org.jitsi.metaconfig.ConfigException$UnableToRetrieve$Error: class java.lang.NullPointerException Jibri 2024-10-09 05:41:04.664 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: ConfigSourceSupplier: Trying to retrieve key 'jibri.recording.recordings-directory' from source 'config' as type kotlin.String Jibri 2024-10-09 05:41:04.664 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: ConfigSourceSupplier: Found value /config/recordings for key 'jibri.recording.recordings-directory' from source 'config' as type kotlin.String Jibri 2024-10-09 05:41:04.664 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: FallbackSupplier: value found via ConfigSourceSupplier: key: 'jibri.recording.recordings-directory', type: 'kotlin.String', source: 'config' Jibri 2024-10-09 05:41:04.664 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: FallbackSupplier: checking for value via suppliers: LambdaSupplier: 'JibriConfig::finalizeRecordingScriptPath' ConfigSourceSupplier: key: 'jibri.recording.finalize-script', type: 'kotlin.String', source: 'config' Jibri 2024-10-09 05:41:04.665 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: LambdaSupplier: Trying to retrieve value via JibriConfig::finalizeRecordingScriptPath Jibri 2024-10-09 05:41:04.665 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: FallbackSupplier: failed to find value via LambdaSupplier: 'JibriConfig::finalizeRecordingScriptPath': org.jitsi.metaconfig.ConfigException$UnableToRetrieve$Error: class java.lang.NullPointerException Jibri 2024-10-09 05:41:04.666 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: ConfigSourceSupplier: Trying to retrieve key 'jibri.recording.finalize-script' from source 'config' as type kotlin.String Jibri 2024-10-09 05:41:04.666 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: ConfigSourceSupplier: Found value /opt/jitsi/jibri/finalize_recording.sh for key 'jibri.recording.finalize-script' from source 'config' as type kotlin.String Jibri 2024-10-09 05:41:04.666 FINE: [119] MainKt$setupMetaconfigLogger$1.debug#232: FallbackSupplier: value found via ConfigSourceSupplier: key: 'jibri.recording.finalize-script', type: 'kotlin.String', source: 'config' Jibri 2024-10-09 05:41:04.666 FINE: [119] JibriStatsDClient.incrementCounter#38: Incrementing statsd counter: start:recording Jibri 2024-10-09 05:41:04.666 INFO: [119] JibriStatusManager$special$$inlined$observable$1.afterChange#75: Busy status has changed: IDLE -> BUSY Jibri 2024-10-09 05:41:04.667 FINE: [119] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status Jibri 2024-10-09 05:41:04.667 INFO: [119] XmppApi.updatePresence#212: Jibri reports its status is now JibriStatus(busyStatus=BUSY, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections Jibri 2024-10-09 05:41:04.667 FINE: [119] MucClientManager.setPresenceExtension#160: Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@75f3b8a5 Jibri 2024-10-09 05:41:04.667 FINE: [119] MucClientManager.saveExtension#185: Replacing presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@5256a62f Jibri 2024-10-09 05:41:04.668 INFO: [119] XmppApi.handleStartJibriIq#284: Sending 'pending' response to start IQ Jibri 2024-10-09 05:41:04.669 INFO: [128] AbstractPageObject.visit#32: Visiting url https://record.viziondev1.com:9445/ Jibri 2024-10-09 05:41:04.671 FINE: [106] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse: Could not add a provider for element busy-status from namespace http://jitsi.org/protocol/jibri Jibri 2024-10-09 05:41:04.671 FINE: [106] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse: Could not add a provider for element health-status from namespace http://jitsi.org/protocol/health Jibri 2024-10-09 05:41:07.018 INFO: [128] AbstractPageObject.visit#38: Waited 2.348507516s for driver to load page Jibri 2024-10-09 05:41:07.019 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSelenium.joinCall$lambda$3#306: callStatsUsername is working Jibri 2024-10-09 05:41:07.268 INFO: [128] AbstractPageObject.visit#32: Visiting url https://record.viziondev1.com:9445//pratik_nanavare-717#config.iAmRecorder=true&config.externalConnectUrl=null&config.startWithAudioMuted=true&config.startWithVideoMuted=true&interfaceConfig.APP_NAME="Jibri"&config.analytics.disabled=true&config.p2p.enabled=false&config.prejoinPageEnabled=false&config.prejoinConfig.enabled=false&config.requireDisplayName=false Jibri 2024-10-09 05:41:07.734 INFO: [128] AbstractPageObject.visit#38: Waited 466.021484ms for driver to load page Jibri 2024-10-09 05:41:07.856 FINE: [128] CallPage$visit$1$1.invoke#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined') Jibri 2024-10-09 05:41:27.210 FINE: [18] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status Jibri 2024-10-09 05:41:38.166 SEVERE: [128] CallPage.visit#65: Timed out waiting for call page to load Jibri 2024-10-09 05:41:38.166 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSelenium.joinCall$lambda$3#325: cromeDriver not working Jibri 2024-10-09 05:41:38.166 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSelenium.onSeleniumStateChange#218: Transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call Jibri 2024-10-09 05:41:38.166 INFO: [128] [session_id=xjojgcwjqzfxwhac] StatefulJibriService.onServiceStateChange#39: File recording service transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call Jibri 2024-10-09 05:41:38.166 INFO: [128] XmppApi$createServiceStatusHandler$1.invoke#320: Current service had an error Error: FailedToJoinCall SESSION Failed to join the call, sending error iq <iq xmlns='jabber:client' to='jibribrewery@internal-muc.meet.jitsi/focus' id='12L73-117' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' failure_reason='error' should_retry='true'/></iq> Jibri 2024-10-09 05:41:38.166 FINE: [128] JibriStatsDClient.incrementCounter#38: Incrementing statsd counter: stop:recording Jibri 2024-10-09 05:41:38.166 INFO: [128] JibriManager.stopService#274: Stopping the current service Jibri 2024-10-09 05:41:38.167 INFO: [128] [session_id=xjojgcwjqzfxwhac] FileRecordingJibriService.stop#192: Stopping capturer Jibri 2024-10-09 05:41:38.167 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSubprocess.stop#75: Stopping ffmpeg process Jibri 2024-10-09 05:41:38.167 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSubprocess.stop#89: ffmpeg exited with value null Jibri 2024-10-09 05:41:38.167 INFO: [128] [session_id=xjojgcwjqzfxwhac] FileRecordingJibriService.stop#194: Quitting selenium Jibri 2024-10-09 05:41:38.167 INFO: [128] [session_id=xjojgcwjqzfxwhac] FileRecordingJibriService.stop#201: No media was recorded, deleting directory and skipping metadata file & finalize Jibri 2024-10-09 05:41:38.167 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSelenium.leaveCallAndQuitBrowser#345: Leaving call and quitting browser Jibri 2024-10-09 05:41:38.168 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSelenium.leaveCallAndQuitBrowser#348: Recurring call status checks cancelled Jibri 2024-10-09 05:41:38.180 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSelenium.leaveCallAndQuitBrowser#354: Got 38 log entries for type browser Jibri 2024-10-09 05:41:38.226 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSelenium.leaveCallAndQuitBrowser#354: Got 1428 log entries for type driver Jibri 2024-10-09 05:41:38.281 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSelenium.leaveCallAndQuitBrowser#354: Got 0 log entries for type client Jibri 2024-10-09 05:41:38.281 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSelenium.leaveCallAndQuitBrowser#363: Leaving web call Jibri 2024-10-09 05:41:38.295 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSelenium.leaveCallAndQuitBrowser#370: Quitting chrome driver Jibri 2024-10-09 05:41:38.388 INFO: [128] [session_id=xjojgcwjqzfxwhac] JibriSelenium.leaveCallAndQuitBrowser#372: Chrome driver quit Jibri 2024-10-09 05:41:38.388 INFO: [128] JibriStatusManager$special$$inlined$observable$1.afterChange#75: Busy status has changed: BUSY -> IDLE Jibri 2024-10-09 05:41:38.388 FINE: [128] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status Jibri 2024-10-09 05:41:38.389 INFO: [128] XmppApi.updatePresence#212: Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections Jibri 2024-10-09 05:41:38.389 FINE: [128] MucClientManager.setPresenceExtension#160: Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@40afbada Jibri 2024-10-09 05:41:38.389 FINE: [128] MucClientManager.saveExtension#185: Replacing presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@75f3b8a5 Jibri 2024-10-09 05:41:38.393 FINE: [106] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse: Could not add a provider for element busy-status from namespace http://jitsi.org/protocol/jibri Jibri 2024-10-09 05:41:38.394 FINE: [106] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse: Could not add a provider for element health-status from namespace http://jitsi.org/protocol/health Jibri 2024-10-09 05:42:27.210 FINE: [18] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status Jibri 2024-10-09 05:43:27.210 FINE: [18] WebhookClient$updateStatus$1.invokeSuspend#109: Updating 0 subscribers of status

@saghul
Copy link
Member

saghul commented Oct 22, 2024

What version of the images are you running?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants