Jibri problem

Hello Community;

I just installed JITSI recently and I had a problem with the Jibri configuration

I installed Jitsi in a virtual machine (AWS instance) and I configured in another JIBRI

I changed the grub (aws=>generic)

uname -r ==== 5.15.0-48-generic

I want my recordings to be registered in my Jitsi server but unfortunately I always receive the error message

Here is the jicofo log file

tail -f jicofo.log

Jicofo 2022-09-23 11:24:40.914 INFO: [44] AbstractAuthAuthority.notifyUserAuthenticated#339: Jid 96da5499-5dff-4fb8-9756-6e7feb273c1e@meet.myplatforms.com/spVw205M_QVD authenticated as: 96da5499-5dff-4fb8-9756-6e7feb273c1e@meet.myplatforms.com
Jicofo 2022-09-23 11:24:40.918 INFO: [44] [room=enjoyablefinishesoperatehere@conference.meet.myplatforms.com] JitsiMeetConferenceImpl.<init>#259: Created new conference.
Jicofo 2022-09-23 11:24:40.918 INFO: [44] [room=enjoyablefinishesoperatehere@conference.meet.myplatforms.com] JitsiMeetConferenceImpl.joinTheRoom#443: Joining enjoyablefinishesoperatehere@conference.meet.myplatforms.com
Jicofo 2022-09-23 11:24:41.103 INFO: [27] [room=enjoyablefinishesoperatehere@conference.meet.myplatforms.com meeting_id=5b89a280-2b3c-4c43-b46f-54b3044ce3de] JitsiMeetConferenceImpl.onMemberJoined#590: Member joined:96da5499 stats-id=Sage-F0v region=null audioMuted=true videoMuted=true isJibri=false isJigasi=false
Jicofo 2022-09-23 11:25:43.258 INFO: [13] AbstractAuthAuthority$ExpireTask.run#524: Expiring session:AuthSession[ID=96da5499-5dff-4fb8-9756-6e7feb273c1e@meet.myplatforms.com, JID=96da5499-5dff-4fb8-9756-6e7feb273c1e@meet.myplatforms.com/spVw205M_QVD, SID=d308a06e-accc-4cf7-b44c-5545821a44ed, MUID=f895f4f67a25440217279b2b7416f232, LIFE_TM_SEC=62, R=enjoyablefinishesoperatehere@conference.meet.myplatforms.com]@1467810770
Jicofo 2022-09-23 11:28:33.302 INFO: [27] [room=enjoyablefinishesoperatehere@conference.meet.myplatforms.com meeting_id=5b89a280-2b3c-4c43-b46f-54b3044ce3de] JitsiMeetConferenceImpl.onMemberLeft#797: Member left:96da5499
Jicofo 2022-09-23 11:28:33.302 WARNING: [27] [room=enjoyablefinishesoperatehere@conference.meet.myplatforms.com meeting_id=5b89a280-2b3c-4c43-b46f-54b3044ce3de] JitsiMeetConferenceImpl.onMemberLeft#812: Participant not found for 96da5499. Terminated already or never started?
Jicofo 2022-09-23 11:28:33.302 INFO: [27] [room=enjoyablefinishesoperatehere@conference.meet.myplatforms.com meeting_id=5b89a280-2b3c-4c43-b46f-54b3044ce3de] ColibriV2SessionManager.expire#111: Expiring.
Jicofo 2022-09-23 11:28:33.303 INFO: [27] [room=enjoyablefinishesoperatehere@conference.meet.myplatforms.com meeting_id=5b89a280-2b3c-4c43-b46f-54b3044ce3de] ColibriV2SessionManager.expire#111: Expiring.
Jicofo 2022-09-23 11:28:33.304 INFO: [27] [room=enjoyablefinishesoperatehere@conference.meet.myplatforms.com meeting_id=5b89a280-2b3c-4c43-b46f-54b3044ce3de] JitsiMeetConferenceImpl.stop#420: Stopped.

Can someone help me to fix this ?

I would be available for any other information, I just need help to fix this

1 Like

Can you successfully create a 3way call on your deployment?

Yes Mr.damencho I can do it but i can’t record the video call in my local server !!

Share your jibri.conf and your jibri log (log.0.txt)

As requested , find above :
Jibri.conf
jibri.txt (3.8 KB)

log.0.txt

log.0.txt (62.1 KB)

Thanks you very much for your help !

I think your chrome crashes on that machine.
What is the available RAM that chrome can use on that machine?

1 Like

For Jitsi Meet server (main server)

image

And for Jibri Node :

image

Should I increase ?

Can you share the output for

ps aux
1 Like

Yes Ofc !

For Jibri node (4Go Ram Aws : t3.medium)
ps -aux.txt (11.5 KB)

For Jitsi node (8Go ram Aws: t2.large)
ps-aux-jitsi.txt (11.9 KB)

Thanks you !

There is no running Jibri process on jibri node

Sorry, I didn’t understand what that means exactly?

Should i run a record session


and then execute ps -aux ?

There are two types of recording:

  • locale
  • remote

jibri is only used when you checked recording service. Local recording doesn’t need jibri

You have two installed jibri instances. The first one runs on JMS (Jitsi Meet Server), the other one is on Jibri node but it doesn’t work. Probably its configuration is not correct.

Do you use the same nickname for both Jibris?

In the old version of Jitsi I could make recordings in my local Jitsi server in a previously configured location /var/jbrecord , how can I do it now?

Do you use the same nickname for both Jibris? No, i use a different nickname according to my knowledge, how can I check?

1 Like

Yes ofc i use a different one :

               // The MUC we'll join to announce our presence for
                // recording and streaming services
                control-muc {
                    domain = "internal.auth.meet.myplatforms.com"
                    room-name = "JibriBrewery"
                    nickname = "66df771577634ad3ba43f4c1149bdb34"
                }

and the other


                // The base XMPP domain
                xmpp-domain = "meet.myplatforms.com"

                // The MUC we'll join to announce our presence for
                // recording and streaming services
                control-muc {
                    domain = "internal.auth.meet.myplatforms.com"
                    room-name = "JibriBrewery"
                    nickname = "ec2bcf2fd2b2598bc11095c1a0a81a88"
                }

IMO check Jibris one by one.

For example is there any issue when you stop Jibri on JMS and start it on Jibri node?

I check them I find a problem in both cases :pensive:

image

Is this the option I have to choose for jibri to work and for me to receive the records on my main local Jitsi server? I’m starting to wonder …

This option is right for Jibri. The recorded file will be on Jibri node which recorded the session.