-
Notifications
You must be signed in to change notification settings - Fork 314
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
I am getting Recording failed to start after preparing the recording #467
Comments
You'd have more luck in community.jitsi.org for something like this. |
Thanks for your response @bbaldino I installed Jitsi and Jibri on same instance. I tried in community as well. please find my configurations below, If I do anything wrong please correct me. Jibri config
}
}
} browser log 2022-02-18 05:57:44.357 INFO: [56] JibriSelenium.leaveCallAndQuitBrowser#348: [2022-02-18T05:57:44+0000] [INFO] [ac87537906dbe65ac2e0db3cf3d66ff4] COMMAND GetLog { 2022-02-18 05:57:44.357 INFO: [56] JibriSelenium.leaveCallAndQuitBrowser#348: [2022-02-18T05:57:44+0000] [FINE] DevTools WebSocket Command: Runtime.evaluate (id=242) 09196120ADD77AD976F0BE90FAC6B25B { 2022-02-18 05:57:44.357 INFO: [56] JibriSelenium.leaveCallAndQuitBrowser#348: [2022-02-18T05:57:44+0000] [FINE] DevTools WebSocket Response: Runtime.evaluate (id=242) 09196120ADD77AD976F0BE90FAC6B25B { |
Hi,
I am attached below my logs, please help me to get resolve this.
Jicofo log
Jicofo 2022-02-17 10:13:56.471 INFO: [33] JibriSession.processJibriIqFromJibri#435: Updating status from JIBRI: for [email protected]
Jicofo 2022-02-17 10:13:56.471 INFO: [33] JibriSession.handleJibriStatusUpdate#623: Got Jibri status update: Jibri [email protected]/jibri has status pending and failure reason null, current Jibri jid is [email protected]/jibri
Jicofo 2022-02-17 10:13:56.471 INFO: [33] [room=[email protected] meeting_id=bc816cba-badc-43cf-92c8-17c81093e74d] JibriRecorder.handleStartRequest#113: Started Jibri session
Jicofo 2022-02-17 10:14:28.442 INFO: [33] JibriSession.processJibriIqFromJibri#435: Updating status from JIBRI: for [email protected]
Jicofo 2022-02-17 10:14:28.442 INFO: [33] JibriSession.handleJibriStatusUpdate#623: Got Jibri status update: Jibri [email protected]/jibri has status off and failure reason error, current Jibri jid is [email protected]/jibri
Jicofo 2022-02-17 10:14:28.442 INFO: [33] JibriSession.clearPendingTimeout#575: Jibri is no longer pending, cancelling pending timeout task
Jicofo 2022-02-17 10:14:28.442 INFO: [33] JibriSession.handleJibriStatusUpdate#662: Jibri failed, trying to fall back to another Jibri
Jicofo 2022-02-17 10:14:28.442 SEVERE: [33] JibriSession.startInternal#308: Unable to find an available Jibri, can't start
Jicofo 2022-02-17 10:14:28.443 WARNING: [33] 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:158)
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.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Jicofo 2022-02-17 10:14:28.444 INFO: [33] [room=[email protected] meeting_id=bc816cba-badc-43cf-92c8-17c81093e74d] JibriRecorder.publishJibriRecordingStatus#158: Got jibri status off and failure error
Jicofo 2022-02-17 10:14:28.444 INFO: [33] [room=[email protected] meeting_id=bc816cba-badc-43cf-92c8-17c81093e74d] JibriRecorder.publishJibriRecordingStatus#183: Publishing new jibri-recording-status: in: [email protected]
Jicofo 2022-02-17 10:14:28.445 INFO: [33] JibriSession.cleanupSession#390: Cleaning up current JibriSession
Jicofo 2022-02-17 10:14:31.657 INFO: [22] [room=[email protected] meeting_id=bc816cba-badc-43cf-92c8-17c81093e74d] JitsiMeetConferenceImpl.onMemberLeft#795: Member left:4507ef8f
Jicofo 2022-02-17 10:14:31.657 WARNING: [22] [room=[email protected] meeting_id=bc816cba-badc-43cf-92c8-17c81093e74d] JitsiMeetConferenceImpl.onMemberLeft#810: Participant not found for 4507ef8f. Terminated already or never started?
Jicofo 2022-02-17 10:14:31.658 INFO: [22] [room=[email protected] meeting_id=bc816cba-badc-43cf-92c8-17c81093e74d] JitsiMeetConferenceImpl.stop#436: Stopped
Jibri log
2022-02-17 10:14:24.376 FINE: [54] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-02-17 10:14:24.883 FINE: [54] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-02-17 10:14:25.390 FINE: [54] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-02-17 10:14:25.896 FINE: [54] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-02-17 10:14:26.403 FINE: [54] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-02-17 10:14:26.910 FINE: [54] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-02-17 10:14:27.417 FINE: [54] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-02-17 10:14:27.924 FINE: [54] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-02-17 10:14:28.430 FINE: [54] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-02-17 10:14:28.435 SEVERE: [54] CallPage.visit#65: Timed out waiting for call page to load
2022-02-17 10:14:28.437 INFO: [54] [session_id=mledrcfqjzvsqchc] JibriSelenium.onSeleniumStateChange#215: Transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call
2022-02-17 10:14:28.438 INFO: [54] [session_id=mledrcfqjzvsqchc] StatefulJibriService.onServiceStateChange#39: File recording service transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call
2022-02-17 10:14:28.439 INFO: [54] XmppApi$createServiceStatusHandler$1.invoke#243: Current service had an error Error: FailedToJoinCall SESSION Failed to join the call, sending error iq
2022-02-17 10:14:28.439 FINE: [54] JibriStatsDClient.incrementCounter#38: Incrementing statsd counter: stop:recording
2022-02-17 10:14:28.440 INFO: [54] JibriManager.stopService#260: Stopping the current service
2022-02-17 10:14:28.440 INFO: [54] [session_id=mledrcfqjzvsqchc] FileRecordingJibriService.stop#181: Stopping capturer
2022-02-17 10:14:28.440 INFO: [54] [session_id=mledrcfqjzvsqchc] JibriSubprocess.stop#75: Stopping ffmpeg process
2022-02-17 10:14:28.440 INFO: [54] [session_id=mledrcfqjzvsqchc] JibriSubprocess.stop#89: ffmpeg exited with value null
2022-02-17 10:14:28.440 INFO: [54] [session_id=mledrcfqjzvsqchc] FileRecordingJibriService.stop#183: Quitting selenium
2022-02-17 10:14:28.441 INFO: [54] [session_id=mledrcfqjzvsqchc] FileRecordingJibriService.stop#190: No media was recorded, deleting directory and skipping metadata file & finalize
2022-02-17 10:14:28.441 INFO: [54] [session_id=mledrcfqjzvsqchc] JibriSelenium.leaveCallAndQuitBrowser#336: Leaving call and quitting browser
2022-02-17 10:14:28.441 INFO: [54] [session_id=mledrcfqjzvsqchc] JibriSelenium.leaveCallAndQuitBrowser#339: Recurring call status checks cancelled
2022-02-17 10:14:28.456 INFO: [54] [session_id=mledrcfqjzvsqchc] JibriSelenium.leaveCallAndQuitBrowser#345: Got 21 log entries for type browser
2022-02-17 10:14:28.503 INFO: [54] [session_id=mledrcfqjzvsqchc] JibriSelenium.leaveCallAndQuitBrowser#345: Got 1047 log entries for type driver
2022-02-17 10:14:28.630 INFO: [54] [session_id=mledrcfqjzvsqchc] JibriSelenium.leaveCallAndQuitBrowser#345: Got 0 log entries for type client
2022-02-17 10:14:28.630 INFO: [54] [session_id=mledrcfqjzvsqchc] JibriSelenium.leaveCallAndQuitBrowser#354: Leaving web call
2022-02-17 10:14:28.660 INFO: [54] [session_id=mledrcfqjzvsqchc] JibriSelenium.leaveCallAndQuitBrowser#361: Quitting chrome driver
2022-02-17 10:14:28.730 INFO: [54] [session_id=mledrcfqjzvsqchc] JibriSelenium.leaveCallAndQuitBrowser#363: Chrome driver quit
2022-02-17 10:14:28.731 INFO: [54] JibriStatusManager$$special$$inlined$observable$1.afterChange#72: Busy status has changed: BUSY -> IDLE
2022-02-17 10:14:28.731 FINE: [54] WebhookClient$updateStatus$1.invokeSuspend#107: Updating 0 subscribers of status
2022-02-17 10:14:28.732 INFO: [54] XmppApi.updatePresence#144: Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections
2022-02-17 10:14:34.345 FINE: [17] WebhookClient$updateStatus$1.invokeSuspend#107: Updating 0 subscribers of status
The text was updated successfully, but these errors were encountered: