TUTORIAL: Jibri Overview, Troubleshooting Tips & Tricks - Solve your Jibri Problems, Quickly!

Yes

Yes, it’s working.

Wait - do you get an error message on recording or it appears to record fine but no file is produced? Because your logs you shared don’t show any errors, so it seems like something else is going on.

There’s no error message/pop-up, not even the “preparing to record the meeting”.

It had java-11-openjdk-amd64 set as default.
I updated it using above instructions to
/usr/lib/jvm/adoptopenjdk-8-hotspot-amd64/bin/java.
And, replaced the java in /opt/jitsi/jibri/launch.sh

Now, jitsi-videobridge2.service & jibri.service are failing to start

jibri.service - Jibri Process
     Loaded: loaded (/etc/systemd/system/jibri.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2022-11-23 06:25:36 UTC; 5min ago
    Process: 482240 ExecStart=/opt/jitsi/jibri/launch.sh (code=exited, status=1/FAILURE)
   Main PID: 482240 (code=exited, status=1/FAILURE)
jitsi-videobridge2.service - Jitsi Videobridge
     Loaded: loaded (/lib/systemd/system/jitsi-videobridge2.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Wed 2022-11-23 06:29:23 UTC; 228ms ago
    Process: 485920 ExecStart=/bin/bash -c exec /usr/share/jitsi-videobridge/jvb.sh ${JVB_OPTS} < /dev/null >> ${LOGFILE} 2>&1>
    Process: 485921 ExecStartPost=/bin/bash -c echo $MAINPID > /var/run/jitsi-videobridge/jitsi-videobridge.pid (code=exited, >
   Main PID: 485920 (code=exited, status=1/FAILURE)

It works with Java 11, no need to do that downgrade.
If you saw java8 recommendation, it’s probably an old one - I believe for a long time now everything is being tested with java11

Okay, I’ll revert back to 11 then.

Same as before after reverting.

did he will help us with docker jibri sip ,
I don’t now :joy: :joy: :joy: :joy:

any step about jibri sip with docker :grinning:

Hello everyone, I encountered a strange problem. When I restarted the prosody service, the video recording service did not work, The prompt on the meeting page is that all devices are busy, this is consistent with the prompt given in jicofo’s log,but after several restarts, jibri works again。I don’t know if you’ve ever had this problem。

It seems jicofo can’t find jibri service,I suspect the problem is in the prosody service,I’m sorry, the log was not saved when the problem occurred.

These are the logs I intercepted with problems,At present, this problem seems to have been solved, but I still don’t understand the cause of the error. I respect this suggestion to resolve my problem.

jicofo.log (174.3 KB)
log.0.txt (15.1 KB)
prosody.log (24.7 KB)

My JITSI & JIbri are on same server. When i start recording it waits and then give error.please see attached logs and snapshots


Jicofo Log

grep 'SEVERE' /var/log/jitsi/jicofo.log
Jicofo 2023-01-30 07:34:32.626 SEVERE: [38] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 07:41:05.798 SEVERE: [43] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 07:41:31.685 SEVERE: [52] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 08:15:07.384 SEVERE: [59] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 08:17:13.083 SEVERE: [39] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 08:22:32.372 SEVERE: [43] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 08:27:17.911 SEVERE: [41] [room=abc@conference.jibri-dev.on-fi                                                                             re.com meeting_id=2c5680b8-065d-4f55-8695-4bae73e86f17] JibriSession.startIntern                                                                             al#304: Unable to find an available Jibri, can't start
Jicofo 2023-01-30 08:40:41.736 SEVERE: [45] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 08:41:08.080 SEVERE: [24] [room=abc@conference.jibri-dev.on-fi                                                                             re.com meeting_id=0e91cbe4-b11b-45fa-a098-8b810f0a3730] JibriSession.startIntern                                                                             al#304: Unable to find an available Jibri, can't start
Jicofo 2023-01-30 08:41:18.489 SEVERE: [24] [room=abc@conference.jibri-dev.on-fi                                                                             re.com meeting_id=0e91cbe4-b11b-45fa-a098-8b810f0a3730] JibriSession.startIntern                                                                             al#304: Unable to find an available Jibri, can't start
Jicofo 2023-01-30 08:46:26.817 SEVERE: [43] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 08:46:57.328 SEVERE: [51] [room=abc@conference.jibri-dev.on-fi                                                                             re.com meeting_id=3ed8a9d1-cc6a-4ffe-a600-51c41aa74864] JibriSession.startIntern                                                                             al#304: Unable to find an available Jibri, can't start
Jicofo 2023-01-30 08:52:02.627 SEVERE: [53] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 08:52:41.925 SEVERE: [24] [room=abc@conference.jibri-dev.on-fi                                                                             re.com meeting_id=152f26b4-715b-47b2-9801-5f58128b2cd5] JibriSession.startIntern                                                                             al#304: Unable to find an available Jibri, can't start
Jicofo 2023-01-30 08:55:58.436 SEVERE: [42] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 08:57:13.019 SEVERE: [23] [room=abc@conference.jibri-dev.on-fi                                                                             re.com meeting_id=9b647fba-ebf0-45b7-b4c5-5a6b39fec722] JibriSession.startIntern                                                                             al#304: Unable to find an available Jibri, can't start
Jicofo 2023-01-30 08:59:00.319 SEVERE: [43] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 08:59:59.228 SEVERE: [49] [room=abc@conference.jibri-dev.on-fi                                                                             re.com meeting_id=08dcf431-d64f-4956-9b4e-17b552c1e553] JibriSession.startIntern                                                                             al#304: Unable to find an available Jibri, can't start
Jicofo 2023-01-30 09:27:38.240 SEVERE: [60] [room=abc@conference.jibri-dev.on-fi                                                                             re.com meeting_id=0ae10f0e-0194-4c19-9ad2-e295cddad3be] JibriSession.startIntern                                                                             al#304: Unable to find an available Jibri, can't start
Jicofo 2023-01-30 09:34:35.024 SEVERE: [65] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 09:35:26.965 SEVERE: [71] [room=abc@conference.jibri-dev.on-fi                                                                             re.com meeting_id=fdb69176-d24f-4360-9c82-018ef6169467] JibriSession.startIntern                                                                             al#304: Unable to find an available Jibri, can't start
Jicofo 2023-01-30 09:38:27.852 SEVERE: [76] [xmpp_connection=client] XmppProvide                                                                             rImpl$XmppConnectionListener.connectionClosedOnError#361: XMPP connection closed                                                                              on error: system-shutdown You can read more about the meaning of this stream er                                                                             ror at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
Jicofo 2023-01-30 09:39:24.332 SEVERE: [84] [room=abc@conference.jibri-dev.on-fi                                                                             re.com meeting_id=964a97d7-50cd-47df-8800-88eee32ef7db] JibriSession.startIntern                                                                             al#304: Unable to find an available Jibri, can't start

Jibri Log

root@jibri-dev:/home/ubuntu# grep 'SEVERE' /var/log/jitsi/jibri/log.0.txt
2023-01-30 08:59:59.212 SEVERE: [61] CallPage.visit#65: Timed out waiting for call page to load
2023-01-30 09:27:38.237 SEVERE: [82] CallPage.visit#65: Timed out waiting for call page to load
2023-01-30 09:35:26.963 SEVERE: [102] CallPage.visit#65: Timed out waiting for call page to load
2023-01-30 09:39:24.328 SEVERE: [119] CallPage.visit#65: Timed out waiting for call page to load

IIRC from your other posts, you set the external IP as Jitsi address in /etc/hosts. In this case, jibri will try to connect to jitsi through your router and this requires some additional configurations on the router side

I am using AWS cloud platform. What changes are required in that case then. Thanks

how did you solved this

hello friend, can you help me to see the problem
Click the record button, and after 10 seconds, it will prompt that the recording failed

Hello ,

I have deployed a jibri server on a separate server from jitsi and ended up connecting them.

The recording works and also gives me the option to download video files.

However, in my policy I would like only the moderator to have the Start recording button and this is not the case with my configuration apparently.

Can you please help me to set up the configuration according to my needs

Thank you in advance.

This suggests that you’ve enabled both server-side recording (Jibri) and local recording. While server-side recording can only be initiated by a Moderator, Local Recording can be initiated by anyone in a meeting (since it’s client-side). If you don’t want non-Moderators to be able to use the recording feature in Jitsi, you have to disable Local Recording and only use Jibri.

still need Uninstall xserver-xorg on Ubuntu 20.04

sudo apt-get remove xserver-xorg
sudo apt-get -y autoremove xserver-xorg
sudo apt-get -y purge xserver-xorg
sudo apt-get -y autoremove --purge xserver-xorg
reboot

Can deploying jibri in docker container avoid conflicts with the server desktop?