jibri: Recording failed to start

@aaronkvanmeerten Hello, I have configured the jibri and jitsi-meet according the documentation. When I press start-recording button, it asks for the token. I input any random string into the input field. Now when i press submit button, I get “recording filed to start”. And I get the following log in the jibri:

Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: 2018-06-07 10:37:20.792 INFO: [27] org.jitsi.jibri.api.xmpp.XmppApi.handleJibriIq() Received JibriIq <iq to='jibri@auth.meet-07.talview.com/91bd686a-3a02-47bf-ab6c-73fc38884a35' from='jibribrewery@conference.meet-07.talview.com/focus' id='amlicmlAYXV0aC5tZWV0LTA3LnRhbHZpZXcuY29tLzkxYmQ2ODZhLTNhMDItNDdiZi1hYjZjLTczZmMzODg4NGEzNQA2QnpFcy04NTMA2Jsppq3uszSJAh2S6vO7dw==' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' action='start' recording_mode='file' room='jibribrewery@conference.meet-07.talview.com'/></iq> from environment prod environment
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: 2018-06-07 10:37:20.792 INFO: [27] org.jitsi.jibri.api.xmpp.XmppApi.handleStartJibriIq() Received start request
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: 2018-06-07 10:37:20.792 INFO: [27] org.jitsi.jibri.api.xmpp.XmppApi.handleStartJibriIq() Sending 'pending' response to start IQ
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: 2018-06-07 10:37:20.793 INFO: [39] org.jitsi.jibri.api.xmpp.XmppApi.run() Starting service
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: 2018-06-07 10:37:20.794 INFO: [39] org.jitsi.jibri.api.xmpp.XmppApi.handleStartService() Parsed call url info: CallUrlInfo(baseUrl=https://meet-07.talview.com, callName=jibribrewery, urlParams=[])
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: 2018-06-07 10:37:20.794 SEVERE: [39] org.jitsi.jibri.api.xmpp.XmppApi.run() Error in startService task: java.lang.IllegalStateException: startIq.sessionId must not be null with stack:
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: org.jitsi.jibri.api.xmpp.XmppApi.handleStartService(XmppApi.kt:263)
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: org.jitsi.jibri.api.xmpp.XmppApi.access$handleStartService(XmppApi.kt:61)
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: org.jitsi.jibri.api.xmpp.XmppApi$handleStartJibriIq$1.run(XmppApi.kt:179)
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: java.util.concurrent.FutureTask.run(FutureTask.java:266)
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: java.lang.Thread.run(Thread.java:748)
Jun  7 10:37:20 ubuntu-xenial launch.sh[25852]: 2018-06-07 10:37:20.794 INFO: [39] org.jitsi.jibri.api.xmpp.XmppApi.run() Sending start service response iq: <iq to='jibribrewery@conference.meet-07.talview.com/focus' id='lMvnJ-114' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' failure_reason='error'/></iq

And The log in the browser is :

[modules/xmpp/recording.js] <i.toggleRecording>:  Toggle recording (old state, new state):  off on
Logger.js:125 [modules/xmpp/recording.js] <i.setRecordingJibri>:  Set jibri recording: on <iq to=​"jibribrewery@conference.meet-07.talview.com/​focus" type=​"set" xmlns=​"jabber:​client" id=​"ada20387-2633-4941-b039-21853386ecdb:​sendIQ">​…​</iq>​
Logger.js:125 [modules/xmpp/recording.js] <i.setRecordingJibri>:  <iq to=​"jibribrewery@conference.meet-07.talview.com/​focus" type=​"set" xmlns=​"jabber:​client" id=​"ada20387-2633-4941-b039-21853386ecdb:​sendIQ">​…​</iq>​
Logger.js:125 [modules/xmpp/ChatRoom.js] <t.value>:  Ignore focus: jibribrewery@conference.meet-07.talview.com/focus, real JID: focus@auth.meet-07.talview.com/focus160172783844770
Logger.js:125 [modules/xmpp/recording.js] <i.handleJibriPresence>:  Handle Jibri presence : pending null
Logger.js:125 [conference.js] <n.<anonymous>>:  Received recorder status change:  pending undefined
Logger.js:125 [modules/xmpp/recording.js] <>:  Result <iq xmlns=​"jabber:​client" type=​"result" to=​"84f40a3e-8b36-4b97-8083-e994d38d5f58@meet-07.talview.com/​63f254a5-9fdc-4f38-89f5-59689a24b692" from=​"jibribrewery@conference.meet-07.talview.com/​focus" id=​"ada20387-2633-4941-b039-21853386ecdb:​sendIQ">​</iq>​
Logger.js:125 [modules/xmpp/ChatRoom.js] <t.value>:  Ignore focus: jibribrewery@conference.meet-07.talview.com/focus, real JID: focus@auth.meet-07.talview.com/focus160172783844770
Logger.js:125 [modules/xmpp/recording.js] <i.handleJibriPresence>:  Handle Jibri presence : off null
Logger.js:125 [conference.js] <n.<anonymous>>:  Received recorder status change:  off undefined
Logger.js:125 [modules/xmpp/ChatRoom.js] <t.value>:  Ignore focus: jibribrewery@conference.meet-07.talview.com/focus, real JID: focus@auth.meet-07.talview.com/focus160172783844770
Logger.js:125 [modules/xmpp/recording.js] <i.handleJibriPresence>:  Handle Jibri presence : off null

Can you please let me know what mistake am i doing?

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 24 (10 by maintainers)

Most upvoted comments

@bbaldino i installed jibri on different machine but i am getting error recording failed to start screenshot from 2019-01-29 17-28-07

Hi y’all, It appears you may be running mismatched versions.

I suggest trying out the latest Jibri and jitsi meet packages from unstable. There was a point where the new jibri and new jicofo and new jitsi-meet no longer worked with older combinations.

Currently meet.jit.si is running:

Jicofo 1.0-415-1 JVB 1063-1 Jitsi Meet Web 1.0.2854-1 Jibri 4.0.53-1