Reply: Set Up Jibri for Jitsi Recording/Streaming

HowJibri sepated

Hi admin Nerd On The Street,

i want to ask, Regarding setting JIbri.

On your VIdeo and Wiki is install jibri same with jitsi-meet right?

how abouit install JIbri separate with jitsi meet?

Your English is all wrong here. This is what you should have typed instead:

"On your video and wiki, Jibri is installed on the same server as Jitsi Meet, right? How would I install Jibri on a separate server from Jitsi Meet?"

sorry my English poor. hahaha.

thanks jacobgkau for your help.

Hi , jacob..

I have the same question too, how to install jibri separate with jitsi meet server ? any tutorial for example using ubuntu 16.04 ?
i've try to installing jibri more than 10 times.. all always failed .
today i try again with ubuntu 16.04 same result, jibri failed  :

root@jibri:~# systemctl status jibri.service
● jibri.service - Jibri Process
Loaded: loaded (/etc/systemd/system/jibri.service; disabled; vendor preset: e
Active: failed (Result: start-limit-hit) since Sab 2020-07-25 16:46:54 WIB; 4
Process: 32133 ExecStop=/opt/jitsi/jibri/graceful_shutdown.sh (code=exited, st
Process: 32116 ExecStart=/opt/jitsi/jibri/launch.sh (code=exited, status=143)
Main PID: 32116 (code=exited, status=143)

Jul 25 16:46:54 jibri graceful_shutdown.sh[32133]:
Jul 25 16:46:54 jibri graceful_shutdown.sh[32133]: [149B blob data]
Jul 25 16:46:54 jibri systemd[1]: jibri.service: Control process exited, code=ex
Jul 25 16:46:54 jibri systemd[1]: jibri.service: Main process exited, code=exite
Jul 25 16:46:54 jibri systemd[1]: Stopped Jibri Process.
Jul 25 16:46:54 jibri systemd[1]: jibri.service: Unit entered failed state.
Jul 25 16:46:54 jibri systemd[1]: jibri.service: Failed with result ‘exit-code’.
Jul 25 16:46:54 jibri systemd[1]: jibri.service: Start request repeated too quic
Jul 25 16:46:54 jibri systemd[1]: Failed to start Jibri Process.
Jul 25 16:46:54 jibri systemd[1]: jibri.service: Failed with result 'start-limit
lines 1-17/17 (END)…skipping…
● jibri.service - Jibri Process
Loaded: loaded (/etc/systemd/system/jibri.service; disabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Sab 2020-07-25 16:46:54 WIB; 4s ago
Process: 32133 ExecStop=/opt/jitsi/jibri/graceful_shutdown.sh (code=exited, status=7)
Process: 32116 ExecStart=/opt/jitsi/jibri/launch.sh (code=exited, status=143)
Main PID: 32116 (code=exited, status=143)

Jul 25 16:46:54 jibri graceful_shutdown.sh[32133]: Dload Upload Total Spent Left Speed
Jul 25 16:46:54 jibri graceful_shutdown.sh[32133]: [149B blob data]
Jul 25 16:46:54 jibri systemd[1]: jibri.service: Control process exited, code=exited status=7
Jul 25 16:46:54 jibri systemd[1]: jibri.service: Main process exited, code=exited, status=143/n/a
Jul 25 16:46:54 jibri systemd[1]: Stopped Jibri Process.
Jul 25 16:46:54 jibri systemd[1]: jibri.service: Unit entered failed state.
Jul 25 16:46:54 jibri systemd[1]: jibri.service: Failed with result ‘exit-code’.
Jul 25 16:46:54 jibri systemd[1]: jibri.service: Start request repeated too quickly.
Jul 25 16:46:54 jibri systemd[1]: Failed to start Jibri Process.
Jul 25 16:46:54 jibri systemd[1]: jibri.service: Failed with result ‘start-limit-hit’.


please help ..

Thanks n regards,

Hi Jacob,
First of all thank you for this wonderful job you did by bringing up this amazing tutorial. It help me a lot.
I have a question
After setup Jitsi-meet and Jibri on the same server, all services are up, but when I try the recording I getting the below error in jifoco.

Jicofo 2020-08-12 10:26:46.474 INFO: [32] org.jitsi.protocol.xmpp.AbstractOperationSetJingle.log() Notify add SSRC alpha@conference.meet.mydomainname.com/0903d704 SID: 74qtnb0s8op3a Sources{ audio: [ssrc=1138734508 ] video: [ssrc=1983346342 ssrc=2232631458 ssrc=3420564180 ] }@1024830952 source_Groups{ video:[ SourceGroup(SIM)[ ssrc=1983346342 ssrc=2232631458 ssrc=3420564180 ] ] }@1739488804
Jicofo 2020-08-12 10:27:16.320 SEVERE: [293] org.jitsi.jicofo.recording.jibri.JibriSession.log() Unable to find an available Jibri, can't start
Jicofo 2020-08-12 10:27:16.321 INFO: [293] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Failed to start a Jibri session, no Jibris available

Kindly can you help me to fix that?
Thank you

I am getting this issue where the jibri is unable to join the jitisi meeting,



2020-08-31 09:19:12.991 INFO: [253] browser.leaveCallAndQuitBrowser() [2020-08-31T09:19:12+0000] [INFO] [1cb0be3164567934bff43cf93a42d5a7] COMMAND ExecuteScript {
   "args": [  ],
   "script": "                    try {\n                        return APP.conference._room.isJoined();\n                    } catch (e) {\n                        return e.message;\n                    }"
}

2020-08-31 09:19:12.995 INFO: [253] browser.leaveCallAndQuitBrowser() [2020-08-31T09:19:12+0000] [INFO] Waiting for pending navigations…

2020-08-31 09:19:12.995 INFO: [253] browser.leaveCallAndQuitBrowser() [2020-08-31T09:19:12+0000] [FINE] DevTools WebSocket Command: Runtime.evaluate (id=235) 55BD1FEDDE61F118CBFF95FA4B47C9F9 {
   "expression": "1"
}

2020-08-31 09:19:12.995 INFO: [253] browser.leaveCallAndQuitBrowser() [2020-08-31T09:19:12+0000] [FINE] DevTools WebSocket Response: Runtime.evaluate (id=235) 55BD1FEDDE61F118CBFF95FA4B47C9F9 {
   "result": {
      "description": "1",
      "type": "number",
      "value": 1
   }
}

2020-08-31 09:19:12.996 INFO: [253] browser.leaveCallAndQuitBrowser() [2020-08-31T09:19:12+0000] [INFO] Done waiting for pending navigations. Status: ok

2020-08-31 09:19:12.996 INFO: [253] browser.leaveCallAndQuitBrowser() [2020-08-31T09:19:12+0000] [FINE] DevTools WebSocket Command: Runtime.evaluate (id=236) 55BD1FEDDE61F118CBFF95FA4B47C9F9 {
   "awaitPromise": true,
   "expression": "(function() { // Copyright © 2012 The Chromium Authors. All rights reserved.\n// Use of this source code is governed by a BSD-style license that can be\n// found in the LICENSE file.\n\n/**\n * Enum f…",
   "returnByValue": true
}

2020-08-31 09:19:12.996 INFO: [253] browser.leaveCallAndQuitBrowser() [2020-08-31T09:19:12+0000] [FINE] DevTools WebSocket Response: Runtime.evaluate (id=236) 55BD1FEDDE61F118CBFF95FA4B47C9F9 {
   "result": {
      "type": "object",
      "value": {
         "status": 0,
         "value": "Cannot read property 'isJoined' of undefined"
      }
   }
}


also gettting this

  }, {
      "className": "Error",
      "description": "Error: Strophe: BOSH-Connection failed: host-unknown\n    at Object.r.Strophe.log (https://meet.mogokdhamma.co.uk/libs/lib-jitsi-meet.min.js?v=4289:17:15232)\n    at Object.error (https://meet.mogokd...",
      "objectId": "{"injectedScriptId":2,"id":5}",
      "preview": {
         "description": "Error: Strophe: BOSH-Connection failed: host-unknown\n    at Object.r.Strophe.log (https://meet.mogokdhamma.co.uk/libs/lib-jitsi-meet.min.js?v=4289:17:15232)\n    at Object.error (https://meet.mogokd...",
         "overflow": false,
         "properties": [ {
            "name": "stack",
            "type": "string",
            "value": "Error: Strophe: BOSH-Connection failed: host-unkno?.co.uk/libs/lib-jitsi-meet.min.js?v=4289:1:50018)"
         }, {
            "name": "message",
            "type": "string",
            "value": "Strophe: BOSH-Connection failed: host-unknown"
         } ],
         "subtype": "error",
         "type": "object"
      },
      "subtype": "error",
      "type": "object"
   } ],

Hi Jacob
I have install jitsi and jibri on linode server Ubantu .
i am following your video but my jitsi can not call recording and live steaming .
Please Help


 systemctl status jibri.service
● jibri.service - Jibri Process
     Loaded: loaded (/etc/systemd/system/jibri.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2021-04-21 13:24:44 UTC; 1 day 20h ago
   Main PID: 167986 (java)
      Tasks: 40 (limit: 1073)
     Memory: 94.0M
     CGroup: /system.slice/jibri.service
             └─167986 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Djava.util.logging.config.file=/etc/jitsi/jibri/logging.properties -Dconfig.file=/etc/jitsi/jibri>

Apr 21 13:24:44 jitsi systemd[1]: Started Jibri Process.
Apr 21 13:24:48 jitsi launch.sh[167986]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
Apr 21 13:24:48 jitsi launch.sh[167986]: SLF4J: Defaulting to no-operation (NOP) logger implementation
Apr 21 13:24:48 jitsi launch.sh[167986]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.