Jibri " The recording has stopped"


#1

Hi,
I have installed Jibri server on Ubuntu 16, the connective seems to work between Jicofo, Prosody and jibir. However, every time I hit “record” in jistis meet the operation time out with message the " recording has stopped"

Any hep much appreciate.

Thank you


#2

Here is jicofo logs:
Jicofo 2019-03-04 07:21:14.134 INFO: [39] org.jitsi.jicofo.recording.jibri.JibriSession.log() Got Jibri status update: Jibri jibribrewery(at)link has status off and failure reason error, current Jibri jid is jibribrewery(at)link
Jicofo 2019-03-04 07:21:14.134 INFO: [39] org.jitsi.jicofo.recording.jibri.JibriSession.log() Jibri is no longer pending, cancelling pending timeout task
Jicofo 2019-03-04 07:21:14.134 INFO: [39] org.jitsi.jicofo.recording.jibri.JibriSession.log() Jibri failed, trying to fall back to another Jibri
Jicofo 2019-03-04 07:21:14.135 SEVERE: [39] org.jitsi.jicofo.recording.jibri.JibriSession.log() Unable to find an available Jibri, can’t start
Jicofo 2019-03-04 07:21:14.135 INFO: [39] org.jitsi.jicofo.recording.jibri.JibriSession.log() Failed to fall back to another Jibri, this session has now failed
Jicofo 2019-03-04 07:21:14.136 INFO: [39] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Got jibri status off and failure error
Jicofo 2019-03-04 07:21:14.136 INFO: [39] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Publishing new jibri-recording-status: in: rectest(at)link
Jicofo 2019-03-04 07:21:14.139 INFO: [39] org.jitsi.jicofo.recording.jibri.JibriSession.log() Cleaning up current JibriSession
Jicofo 2019-03-04 07:21:14.667 INFO: [38] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().136 Received Jibri jibribrewery(at)link status
Jicofo 2019-03-04 07:21:14.668 INFO: [38] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().174 Jibri: jibribrewery(at)link available: true

Jibri Logs:

2019-03-04 07:20:05.588 INFO: [43] org.jitsi.jibri.status.JibriStatusManager.log() Busy status has changed: BUSY -> IDLE
2019-03-04 07:20:05.589 INFO: [43] org.jitsi.jibri.api.xmpp.XmppApi.invoke() Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connection prod environment
2019-03-04 07:20:40.340 INFO: [25] org.jitsi.jibri.api.xmpp.XmppApi.handleJibriIq() Received JibriIq from environment prod environment
2019-03-04 07:20:40.341 INFO: [25] org.jitsi.jibri.api.xmpp.XmppApi.handleStartJibriIq() Received start request
2019-03-04 07:20:40.341 INFO: [25] org.jitsi.jibri.api.xmpp.XmppApi.handleStartJibriIq() Sending ‘pending’ response to start IQ
2019-03-04 07:20:40.342 INFO: [43] org.jitsi.jibri.api.xmpp.XmppApi.run() Starting service
2019-03-04 07:20:40.342 INFO: [43] org.jitsi.jibri.api.xmpp.XmppApi.handleStartService() Parsed call url info: CallUrlInfo(baseUrl=https://vb.mydomain.com, callName=rectest, urlParams=)
2019-03-04 07:20:40.343 INFO: [43] org.jitsi.jibri.JibriManager.startFileRecording() Starting a file recording with params: FileRecordingRequestParams(callParams=CallParams(callUrlInfo=CallUrlInfo(baseUrl=https://vb.mydomain.com, callName=rectest, urlParams=)), sessionId=jefzwmjhvagvqmhb, callLoginParams=XmppCredentials(domain=recorder.vb.mydomain.com, username=recorder, password=jibrirecorderpass)) finalize script path: /recording/finalize_recording.sh and recordings directory: /recording
2019-03-04 07:20:41.231 INFO: [43] org.openqa.selenium.remote.ProtocolHandshake.createSession() Detected dialect: OSS
2019-03-04 07:20:41.244 FINE: [43] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.() Detected os as OS: LINUX
2019-03-04 07:20:41.249 INFO: [43] org.jitsi.jibri.service.impl.FileRecordingJibriService.() Writing recording to /recording/jefzwmjhvagvqmhb
2019-03-04 07:20:41.252 FINE: [43] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: start:recording
2019-03-04 07:20:41.255 INFO: [43] org.jitsi.jibri.status.JibriStatusManager.log() Busy status has changed: IDLE -> BUSY
2019-03-04 07:20:41.257 INFO: [43] org.jitsi.jibri.api.xmpp.XmppApi.invoke() Jibri reports its status is now JibriStatus(busyStatus=BUSY, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connection prod environment
2019-03-04 07:20:42.635 FINE: [50] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Visiting url https://vb.mydomain.com/rectest#config.iAmRecorder=true&config.externalConnectUrl=null&config.startWithAudioMuted=true&config.startWithVideoMuted=true&interfaceConfig.APP_NAME=“Jibri”
2019-03-04 07:21:14.129 SEVERE: [50] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Timed out waiting for call page to load
2019-03-04 07:21:14.130 INFO: [50] org.jitsi.jibri.selenium.JibriSelenium.onSeleniumStateChange() Transitioning from state Starting up to Error: SESSION Failed to join call
2019-03-04 07:21:14.131 INFO: [50] org.jitsi.jibri.service.impl.FileRecordingJibriService.onServiceStateChange() File recording service transitioning from state Starting up to Error: SESSION Failed to join call
2019-03-04 07:21:14.131 INFO: [50] org.jitsi.jibri.api.xmpp.XmppApi.invoke() Current service had an error, sending error iq
2019-03-04 07:21:14.133 FINE: [50] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: stop:recording
2019-03-04 07:21:14.136 INFO: [50] org.jitsi.jibri.JibriManager.stopService() Stopping the current service
2019-03-04 07:21:14.136 INFO: [50] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Stopping capturer
2019-03-04 07:21:14.137 INFO: [50] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() Stopping ffmpeg process
2019-03-04 07:21:14.137 INFO: [50] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() ffmpeg exited with value null
2019-03-04 07:21:14.137 INFO: [50] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Quitting selenium
2019-03-04 07:21:14.144 INFO: [50] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Participants in this recording:
2019-03-04 07:21:14.169 INFO: [50] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 10 log entries for type browser
2019-03-04 07:21:14.295 INFO: [50] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 1001 log entries for type driver
2019-03-04 07:21:14.528 INFO: [50] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 0 log entries for type client
2019-03-04 07:21:14.529 INFO: [50] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Leaving web call
2019-03-04 07:21:14.538 INFO: [50] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Quitting chrome driver
2019-03-04 07:21:14.654 INFO: [50] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Chrome driver quit
2019-03-04 07:21:14.655 INFO: [50] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Finalizing the recording


#3

For some reason jibri is not able to load the page for more than 30 seconds.


#4

Yeah, I kind get that, but any suggestion why? one more thing is do we need to open any ports between Jibri server and Jitsi meet? does jibri access the jitsi meet webpage is that what the error message saying?

P.S. I did follow the video online to install jibri.
Thank you for your help


#5

here is my kernel version if that makes any difference:
Linux jibrirecording 4.4.0-142-generic #168-Ubuntu SMP Wed Jan 16 21:00:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux


#6

I have found out some jicofo errors is that and issue and how to fix, Please Help.

Jicofo 2019-03-05 04:34:53.796 INFO: [67] org.jitsi.jicofo.xmpp.FocusComponent.handleConferenceIq().402 Focus request for room: link
Jicofo 2019-03-05 04:34:53.796 INFO: [67] org.jitsi.jicofo.FocusManager.log() Created new focus for link@auth.vb.mydomain.com. Conference count 1,options:
Jicofo 2019-03-05 04:34:53.796 INFO: [67] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Lip-sync enabled in link
Jicofo 2019-03-05 04:34:53.796 INFO: [67] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Joining the room: link
Jicofo 2019-03-05 04:34:53.963 INFO: [37] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberJoined sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@68e3ee4f member=ChatMember[link/3f189932, jid: null]@2098186605]
Jicofo 2019-03-05 04:34:53.964 INFO: [37] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Granted owner to link/3f189932
Jicofo 2019-03-05 04:34:53.965 INFO: [37] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member link/3f189932 joined.
Jicofo 2019-03-05 04:35:04.469 INFO: [118] org.jitsi.jicofo.recording.jibri.JibriSession.log() Starting Jibrilink/jibri-nickname for stream ID: null in room: link
Jicofo 2019-03-05 04:35:04.482 INFO: [118] org.jitsi.jicofo.recording.jibri.JibriSession.log() Got Jibri status update: Jibrilink/jibri-nickname has status pending and failure reason null, current Jibri jid islink/jibri-nickname
Jicofo 2019-03-05 04:35:04.482 INFO: [118] org.jitsi.jicofo.recording.jibri.JibriSession.log() Starting session with Jibrilink/jibri-nickname
Jicofo 2019-03-05 04:35:04.482 INFO: [118] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Started Jibri session
Jicofo 2019-03-05 04:35:05.365 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().136 Received Jibrilink/jibri-nickname status
Jicofo 2019-03-05 04:35:05.365 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().174 Jibri:link/jibri-nickname available: false
Jicofo 2019-03-05 04:35:38.146 INFO: [118] org.jitsi.jicofo.recording.jibri.JibriSession.log() Updating status from JIBRI: for link
Jicofo 2019-03-05 04:35:38.146 INFO: [118] org.jitsi.jicofo.recording.jibri.JibriSession.log() Got Jibri status update: Jibrilink/jibri-nickname has status off and failure reason error, current Jibri jid islink/jibri-nickname
Jicofo 2019-03-05 04:35:38.146 INFO: [118] org.jitsi.jicofo.recording.jibri.JibriSession.log() Jibri is no longer pending, cancelling pending timeout task
Jicofo 2019-03-05 04:35:38.146 INFO: [118] org.jitsi.jicofo.recording.jibri.JibriSession.log() Jibri failed, trying to fall back to another Jibri
Jicofo 2019-03-05 04:35:38.146 SEVERE: [118] org.jitsi.jicofo.recording.jibri.JibriSession.log() Unable to find an available Jibri, can’t start
Jicofo 2019-03-05 04:35:38.146 INFO: [118] org.jitsi.jicofo.recording.jibri.JibriSession.log() Failed to fall back to another Jibri, this session has now failed
Jicofo 2019-03-05 04:35:38.146 INFO: [118] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Got jibri status off and failure error
Jicofo 2019-03-05 04:35:38.147 INFO: [118] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Publishing new jibri-recording-status: in: link
Jicofo 2019-03-05 04:35:38.149 INFO: [118] org.jitsi.jicofo.recording.jibri.JibriSession.log() Cleaning up current JibriSession
Jicofo 2019-03-05 04:35:38.716 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().136 Received Jibrilink/jibri-nickname status
Jicofo 2019-03-05 04:35:38.716 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().174 Jibri:link/jibri-nickname available: true
Jicofo 2019-03-05 04:35:48.807 INFO: [37] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberLeft sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@68e3ee4f member=ChatMember[link/3f189932, jid: 3f189932-aa39-4125-8d41-97defb8467f3@vb.mydomain.com/12343578-760d-439b-999d-02dacaaf1855]@2098186605]
Jicofo 2019-03-05 04:35:48.807 INFO: [37] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Owner has left the room !


#7

Those are likely just more symptoms of Jibri not being able to load the page, that’s what you need to figure out. If I click on the link in your Jibri logs (https://vb.mydomain.com/rectest#config.iAmRecorder=true&config.externalConnectUrl=null&config.startWithAudioMuted=true&config.startWithVideoMuted=true&interfaceConfig.APP_NAME=“Jibri”) I can’t reach it either. Are you sure it’s reachable from the Jibri machine?


#8

Hi @webhay,

As @bbaldino suggested, try hitting the call page url from the jibri machine. Is it able to ping the Jitsi server? The necessary ports would be open on your system, else the Jibri<-> Jitsi connection should fail, which is not the case.
Have you jwt-tokens implemented on Jitsi?

Abhijit


#9

Thank you so much guys for helping, Appreciate your support, I have done that few minutes ago, However, since I have server edition only I can do wget below is my results, please tell me if I am missing something.
wget link/randomdwarfsofferlightly#config.iAmRecorder=true&config.externalConnectUrl=null&config.startWithAudioMuted=true&config.startWithVideoMuted=true&interfaceConfig.APP_NAME=“Jibri”
[14] 112051
[15] 112052
[16] 112053
[17] 112054
–2019-03-05 06:00:37-- link/randomdwarfsofferlightly
Resolving Mydomain (mydomain)… 40.83.22.4
Connecting to mydomain (mydomain)|40.83.22.4|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: unspecified [text/html]
Saving to: ‘randomdwarfsofferlightly’

randomdwarfsofferlightly [ <=> ] 28.58K --.-KB/s in 0s

2019-03-05 06:00:37 (118 MB/s) - ‘randomdwarfsofferlightly’ saved [29271]

config.externalConnectUrl=null: command not found
config.startWithAudioMuted=true: command not found
config.startWithVideoMuted=true: command not found
interfaceConfig.APP_NAME=Jibri: command not found
[14] Done wget link/randomdwarfsofferlightly#config.iAmRecorder=true
[17] Exit 127 config.startWithVideoMuted=true


#10

I don’t have jwt-token implemented this is just plain vanilla Jitsi/Jibri installation, And yes I can ping back and forth between jitis VB and jibri server.

Thank you for your help.


#11

Hi @webhay,

This looks good. The wget isn’t failing and gets connected to the Jitsi Server. Are the chrome and Chromedriver to the latest versions?

Abhijit


#12

Sorry, not sure what else to tell you, my best guess is a network problem of some sort…so whatever you can do to verify connectivity between Jibri and the webserver.


#13

I am still struggling with this I have got this error from Prosody when I restart is that could be related to this issue:
Mar 07 06:32:22 jitsi-videobridge prosody[28145]: …done.
Mar 07 06:32:22 jitsi-videobridge systemd[1]: Stopped LSB: Prosody XMPP Server.
Mar 07 06:32:22 jitsi-videobridge systemd[1]: Starting LSB: Prosody XMPP Server…
Mar 07 06:32:22 jitsi-videobridge prosody[28160]: * Starting Prosody XMPP Server prosody
Mar 07 06:32:22 jitsi-videobridge prosody[28160]: …done.
Mar 07 06:32:22 jitsi-videobridge systemd[1]: Started LSB: Prosody XMPP Server.
Mar 07 06:32:22 jitsi-videobridge prosody[28186]: portmanager: Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Mar 07 06:32:22 jitsi-videobridge prosody[28186]: portmanager: Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

Please let me know, thank you for your help.


#14

2019-03-07 17:29:36.480 INFO: [45] browser.leaveCallAndQuitBrowser() [2019-03-07T17:29:05+0000] [SEVERE] https://vb.MyDomain.com/libs/lib-jitsi-meet.min.js?v=3216 5:257248 “[JitsiMeetJS.js]” "\u003CObject.getGlobalOnErrorHandler>: " “UnhandledError: null” “Script: null” “Line: null” “Column: null” "StackTrace: " Error: Strophe: Server did not offer a supported authentication mechanism
at Object.i.Strophe.log (https://vb.MyDomain.com/libs/lib-jitsi-meet.min.js?v=3216:40:17856)
at Object.error (https://vb.MyDomain.com/libs/lib-jitsi-meet.min.js?v=3216:6:18436)
at r.Connection._no_auth_received (https://vb.MyDomain.com/libs/lib-jitsi-meet.min.js?v=3216:6:29998)
at r.Connection._connect_cb (https://vb.MyDomain.com/libs/lib-jitsi-meet.min.js?v=3216:6:31205)
at e.Bosh._onRequestStateChange (https://vb.MyDomain.com/libs/lib-jitsi-meet.min.js?v=3216:6:49165)
2019-03-07 17:29:36.480 INFO: [45] browser.leaveCallAndQuitBrowser() [2019-03-07T17:29:05+0000] [SEVERE] https://vb.MyDomain.com/libs/lib-jitsi-meet.min.js?v=3216 5:257248 “[modules/xmpp/strophe.util.js]” "\u003CObject.i.Strophe.log>: " “Strophe: Server did not offer a supported authentication mechanism”
2019-03-07 17:29:36.480 INFO: [45] browser.leaveCallAndQuitBrowser() [2019-03-07T17:29:05+0000] [SEVERE] https://vb.MyDomain.com/libs/app.bundle.min.js?v=3216 34:28194 “[connection.js]” "\u003Cr.c>: " “CONNECTION FAILED:” “connection.otherError”
2019-03-07 17:29:36.481 INFO: [45] browser.leaveCallAndQuitBrowser() [2019-03-07T17:29:05+0000] [SEVERE] https://vb.MyDomain.com/libs/app.bundle.min.js?v=3216 34:28194 “[react/features/base/connection/actions.web.js]” "\u003C>: " “connection.otherError”


#15

This is not used and you can ignore it.


#16

Try adding consider_bosh_secure = true; to the general section of your prosody config. Does that change anything?


#17

Thank you for helping sir,
I have added it to /etc/prosdy/conf.d/mydomain.com.cfg.lua right after

c2s_require_encryption = false
consider_bosh_secure = true
but this did nothing all the errors still there. I have open all the ports on the jitsi met server and jibri server as well. I till get the same issue.

I have download and reinstalled the chrome driver again. but nothing seems to help.

Any more ideas to get this working. I am running this on Azure Ubuntu 18 LTS.

Please let me know.

Thank you so much for the support.


#18

Here is my setup versions in case there is issue with the versions:
jibri:
Installed: 7.2.71-1
jicofo:
Installed: 1.0-458-1
prosody:
Installed: 0.10.0-1build1

Please let me know if there is any conflict.


#19

Hello there, do you guys see anything wrong in the above info? please let me know.


#20

I have added this setting consider_bosh_secure = true to this file:
/etc/prosody/prosody.cfg.lua that made it to work. before I added to the prosody domain name specific file that is why it wasn’t working. I am documenting this here for anyone else.
Thank you for your help.