Jibri - Can't start recording

Hello.

Last week I updated Prosody from 0.10 to 0.11. And since that day I can’t start any record of any meeting. The only message that appears is that “Can’t start recording” (No se pudo iniciar la grabación in spanish). But before the update the recordings working perfectly

Grabacion_reunion

I put the conf.avail/mydomain.cfg.lua

Component "conference.mydomain.com" "muc"
    storage = "memory"
    modules_enabled = {
        "muc_meeting_id";
        "muc_domain_mapper";
        "time_restricted";
        -- "token_verification";
    }
    admins = { "focus@auth.mydomain.com" }
    conference_max_minutes = 240
    muc_room_locking = false
    muc_room_default_public_jids = true

-- internal muc component
Component "internal.auth.mydomain.com" "muc"
    modules_enabled = {
      "ping";
    }
    storage = "memory"
    admins = { "focus@auth.mydomain.com", "jvb@auth.mydomain.com" }
    muc_room_cache_size = 1000
    muc_room_locking = false
    muc_room_default_public_jids = true

VirtualHost "auth.mydomain.com"
    ssl = {
        key = "/etc/prosody/certs/auth.mydomain.com.key";
        certificate = "/etc/prosody/certs/auth.mydomain.com.crt";
    }
    authentication = "internal_plain"

VirtualHost "recorder.mydomain.com"
    modules_enabled = {
      "ping";
    }

And in jicofon.log appears this:

Jicofo 2021-02-23 08:50:19.769 INFO: [110] org.jitsi.jicofo.AbstractChannelAllocator.log() Using jvbbrewery@internal.auth.mydomain.com/3a5d6f6e-45b7-469b-ba9f-43173f20e009 to$
Jicofo 2021-02-23 08:50:19.788 INFO: [111] org.jitsi.jicofo.ParticipantChannelAllocator.log() Sending session-initiate to: 000023@conference.mydomain.com/fee38fe5
Jicofo 2021-02-23 08:50:19.804 INFO: [110] org.jitsi.jicofo.ParticipantChannelAllocator.log() Sending session-initiate to: 000023@conference.mydomain.com/9c1193c1
Jicofo 2021-02-23 08:50:20.099 INFO: [32] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Got session-accept from: 000023@conference.mydomain.com/9c1193c1
Jicofo 2021-02-23 08:50:20.099 INFO: [32] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Received session-accept from 000023@conference.mydomain.com/9c1193c1 with accepted so$
Jicofo 2021-02-23 08:50:20.100 WARNING: [32] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() No jingle session yet for 000023@conference.mydomain.com/fee38fe5
Jicofo 2021-02-23 08:50:20.945 INFO: [32] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Got session-accept from: 000023@conference.mydomain.com/fee38fe5
Jicofo 2021-02-23 08:50:20.948 INFO: [32] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Received session-accept from 000023@conference.mydomain.com/fee38fe5 with accepted so$
Jicofo 2021-02-23 08:50:20.950 INFO: [32] org.jitsi.protocol.xmpp.AbstractOperationSetJingle.log() Notify add SSRC 000023@conference.mydomain.com/9c1193c1 SID: 51h0trpnku97f $
Jicofo 2021-02-23 08:50:25.121 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Updating status from JIBRI: <iq to='focus@auth.mydomain.com/focus57755116468569$
Jicofo 2021-02-23 08:50:25.121 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Got Jibri status update: Jibri jibribrewery@internal.auth.mydomain.com/jibri-ni$
Jicofo 2021-02-23 08:50:25.121 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Jibri is no longer pending, cancelling pending timeout task
Jicofo 2021-02-23 08:50:25.121 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Jibri failed, trying to fall back to another Jibri
Jicofo 2021-02-23 08:50:25.121 SEVERE: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Unable to find an available Jibri, can't start
Jicofo 2021-02-23 08:50:25.122 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Failed to fall back to another Jibri, this session has now failed: org.jitsi.jicofo.rec$
org.jitsi.jicofo.recording.jibri.JibriSession$StartException: All Jibri instances are busy
        at org.jitsi.jicofo.recording.jibri.JibriSession.startInternal(JibriSession.java:359)
        at org.jitsi.jicofo.recording.jibri.JibriSession.start(JibriSession.java:335)
        at org.jitsi.jicofo.recording.jibri.JibriSession.retryRequestWithAnotherJibri(JibriSession.java:649)
        at org.jitsi.jicofo.recording.jibri.JibriSession.handleJibriStatusUpdate(JibriSession.java:719)
        at org.jitsi.jicofo.recording.jibri.JibriSession.processJibriIqFromJibri(JibriSession.java:501)
        at org.jitsi.jicofo.recording.jibri.JibriSession.processJibriIqRequestFromJibri(JibriSession.java:482)
        at org.jitsi.jicofo.recording.jibri.CommonJibriStuff.handleIQRequest(CommonJibriStuff.java:247)
        at org.jitsi.jicofo.recording.jibri.OperationSetJibri.handleIQRequest(OperationSetJibri.java:98)
        at org.jivesoftware.smack.AbstractXMPPConnection$4.run(AbstractXMPPConnection.java:1188)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:834)
Jicofo 2021-02-23 08:50:25.122 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Got jibri status off and failure error
Jicofo 2021-02-23 08:50:25.123 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriRecorder.log() Publishing new jibri-recording-status: <jibri-recording-status xmlns='http://jitsi.org$
Jicofo 2021-02-23 08:50:25.123 INFO: [107] org.jitsi.jicofo.recording.jibri.JibriSession.log() Cleaning up current JibriSession
Jicofo 2021-02-23 08:50:25.378 INFO: [32] org.jitsi.jicofo.ChatRoomRoleAndPresence.log() Chat room event ChatRoomMemberPresenceChangeEvent[type=MemberLeft sourceRoom=org.jitsi.impl.p$
Jicofo 2021-02-23 08:50:25.379 INFO: [32] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() Member 000023@conference.mydomain.com/9c1193c1 is leaving

It’s curious when tells that “Unable to find an available Jibri, can’t start”, because I did “systemctl restart jibri” and the message still appearing.

Any help??

Probably you need to add the jibri account again

prosodyctl register jibri...
prosodyctl register recorder...

Hi @emrah

I add the jibri and the recorder user using prosodyctl, restarted services and the same error (and the log tells the same…)

I put modprobe snd-aloop and now it works. I don’t know why but when I put lsmod | grep snd_aloop doesn’t appear nothing in the terminal.

Now, the record works perfectly. Thanks for the help!

If you want to enable snd_aloop at the startup

echo snd_aloop >>/etc/modules