Hay can anyone help me, I’m using OS Debian 10 , Spesification Vcpu 4 Ram 8 when recording fails this notification comes out .
JIBRI CONFIGURATION
/etc/jitsi/jibri/ jibri.conf
/etc/jitsi/jibri/ config.json
/etc/jitsi/jibri/ xorg-video-dummy.conf
JICOFO CONFIGURATION
/etc/jitsi/jicofo jicofo.conf
/etc/jitsi/jicofo sip-communicator.properties
LOG JICOFO | JVB
Jvb.log
root@rapat:~# tail -f /var/log/jitsi/jvb.log
JVB 2022-06-09 02:09:53.052 INFO: [27] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-06-09 02:10:53.052 INFO: [27] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-06-09 02:11:53.052 INFO: [27] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-06-09 02:12:53.052 INFO: [27] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-06-09 02:13:53.052 INFO: [27] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-06-09 02:14:53.053 INFO: [27] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-06-09 02:15:53.052 INFO: [27] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-06-09 02:16:53.052 INFO: [27] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-06-09 02:17:53.052 INFO: [27] VideobridgeExpireThread.expire#140: Running expire()
JVB 2022-06-09 02:18:53.052 INFO: [27] VideobridgeExpireThread.expire#140: Running expire()
Jicofo.log
root@rapat:~# tail -f /var/log/jitsi/jicofo.log
Jicofo 2022-06-08 23:58:16.272 INFO: [236] [room=1234@conference.rapat.space] JitsiMeetConferenceImpl.joinTheRoom#452: Joining 1234@conference.rapat.space
Jicofo 2022-06-08 23:58:17.009 INFO: [53] [room=1234@conference.rapat.space meeting_id=2dbec048-2dfa-4ede-887a-b1eb860d6946] JitsiMeetConferenceImpl.onMemberJoined#599: Member joined:416f57a7
Jicofo 2022-06-08 23:58:25.976 INFO: [53] [room=1234@conference.rapat.space meeting_id=2dbec048-2dfa-4ede-887a-b1eb860d6946] BaseJibri.handleJibriRequest#75: Accepted jibri request: <iq xmlns='jabber:client' to='focus@auth.rapat.space/focus' from='1234@conference.rapat.space/416f57a7' id='Zm9jdXNAYXV0aC5yYXBhdC5zcGFjZS9mb2N1cwA1ZjhlZGQ1Ny1mYTUyLTRkZWUtYTg2Ni1lZGMwOTY3ZjZkZDc6c2VuZElRANTE4a+yDNH4' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' action='start' recording_mode='file' app_data='{"file_recording_metadata":{"share":true}}'/></iq>
Jicofo 2022-06-08 23:58:25.976 SEVERE: [236] [room=1234@conference.rapat.space meeting_id=2dbec048-2dfa-4ede-887a-b1eb860d6946] JibriSession.startInternal#307: Unable to find an available Jibri, can't start
Jicofo 2022-06-08 23:58:25.977 INFO: [236] [room=1234@conference.rapat.space meeting_id=2dbec048-2dfa-4ede-887a-b1eb860d6946] JibriRecorder.handleStartRequest#124: Failed to start a Jibri session, no Jibris available
Jicofo 2022-06-08 23:58:31.016 INFO: [22] [room=1234@conference.rapat.space meeting_id=2dbec048-2dfa-4ede-887a-b1eb860d6946] JitsiMeetConferenceImpl.onMemberLeft#785: Member left:416f57a7
Jicofo 2022-06-08 23:58:31.016 WARNING: [22] [room=1234@conference.rapat.space meeting_id=2dbec048-2dfa-4ede-887a-b1eb860d6946] JitsiMeetConferenceImpl.onMemberLeft#800: Participant not found for 416f57a7. Terminated already or never started?
Jicofo 2022-06-08 23:58:31.016 INFO: [22] [room=1234@conference.rapat.space meeting_id=2dbec048-2dfa-4ede-887a-b1eb860d6946] ColibriV2SessionManager.expire#115: Expiring.
Jicofo 2022-06-08 23:58:31.017 INFO: [22] [room=1234@conference.rapat.space meeting_id=2dbec048-2dfa-4ede-887a-b1eb860d6946] ColibriV2SessionManager.expire#115: Expiring.
Jicofo 2022-06-08 23:58:31.018 INFO: [22] [room=1234@conference.rapat.space meeting_id=2dbec048-2dfa-4ede-887a-b1eb860d6946] JitsiMeetConferenceImpl.stop#429: Stopped.
Prosody.log
Jun 08 08:09:09 startup info Hello and welcome to Prosody version 0.12.0
Jun 08 08:09:09 general warn Lua 5.1 has several issues and support is being phased out, consider upgrading
Jun 08 08:09:09 startup info Prosody is using the epoll backend for connection handling
Jun 08 08:09:09 portmanager info Activated service 's2s' on [::]:5269, [*]:5269
Jun 08 08:09:09 portmanager info Activated service 's2s_direct_tls' on no ports
Jun 08 08:09:09 localhost:tls info Certificates loaded
Jun 08 08:09:09 portmanager info Activated service 'c2s' on [::]:5222, [*]:5222
Jun 08 08:09:09 portmanager info Activated service 'c2s_direct_tls' on no ports
Jun 08 08:09:09 portmanager info Activated service 'legacy_ssl' on no ports
Jun 08 08:09:13 mod_posix warn Received SIGTERM
Jun 08 08:09:13 startup info Shutting down: Received SIGTERM
Jun 08 08:09:13 portmanager info Deactivated service 'c2s'
Jun 08 08:09:13 portmanager info Deactivated service 'c2s_direct_tls'
Jun 08 08:09:13 portmanager info Deactivated service 'legacy_ssl'
Jun 08 08:09:13 portmanager info Deactivated service 's2s'
Jun 08 08:09:13 portmanager info Deactivated service 's2s_direct_tls'
Jun 08 08:09:13 general info Shutting down...
Jun 08 08:09:13 general info Shutdown status: Cleaning up
Jun 08 08:09:13 general info Shutdown complete
Jun 08 08:09:13 startup info Hello and welcome to Prosody version 0.12.0
Jun 08 08:09:13 general warn Lua 5.1 has several issues and support is being phased out, consider upgrading
Jun 08 08:09:13 startup info Prosody is using the epoll backend for connection handling
Jun 08 08:09:13 portmanager info Activated service 's2s' on [::]:5269, [*]:5269
Jun 08 08:09:13 portmanager info Activated service 's2s_direct_tls' on no ports
Jun 08 08:09:14 auth.rapat.space:tls info Certificates loaded
Jun 08 08:09:14 portmanager info Activated service 'c2s' on [::]:5222, [*]:5222
Jun 08 08:09:14 portmanager info Activated service 'c2s_direct_tls' on no ports
Jun 08 08:09:14 portmanager info Activated service 'legacy_ssl' on no ports
Jun 08 08:09:14 lobby.rapat.space:tls info Certificates loaded
Jun 08 08:09:14 breakout.rapat.space:tls info Certificates loaded
Jun 08 08:09:14 breakout.rapat.space:muc_domain_mapper info Loading mod_muc_domain_mapper for host auth.rapat.space!
Jun 08 08:09:14 breakout.rapat.space:muc_domain_mapper info Loading mod_muc_domain_mapper for host lobby.rapat.space!
Jun 08 08:09:14 breakout.rapat.space:muc_domain_mapper info Loading mod_muc_domain_mapper for host breakout.rapat.space!
Jun 08 08:09:14 general info Starting conference duration timer for conference.rapat.space
Jun 08 08:09:14 conferenceduration.rapat.space:conference_duration_component info No muc component found, will listen for it: conference.rapat.space
Nano /etc/hosts
# Your system has configured 'manage_etc_hosts' as True.
# As a result, if you wish for changes to this file to persist
# then you will need to either
# a.) make changes to the master file in /etc/cloud/templates/hosts.debian.tmpl
# b.) change or remove the value of 'manage_etc_hosts' in
# /etc/cloud/cloud.cfg or cloud-config from user-data
#
127.0.1.1 ip-172-31-92-150.ec2.internal ip-172-31-92-150
127.0.0.1 localhost
3.83.55.217 rapat.space ip-172-31-92-150
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
Setting /etc/prosody/conf.avail/domain.cfg.lua
plugin_paths = { "/usr/share/jitsi-meet/prosody-plugins/" }
-- domain mapper options, must at least have domain base set to use the mapper
muc_mapper_domain_base = "rapat.space";
external_service_secret = "T1kITQDBbUcTLTK3";
external_services = {
{ type = "stun", host = "rapat.space", port = 3478 },
{ type = "turn", host = "rapat.space", port = 3478, transport = "udp", secret = true, ttl = 86400, algorithm = "turn" },
{ type = "turns", host = "rapat.space", port = 5349, transport = "tcp", secret = true, ttl = 86400, algorithm = "turn" }
};
cross_domain_bosh = false;
consider_bosh_secure = true;
-- https_ports = { }; -- Remove this line to prevent listening on port 5284
-- by default prosody 0.12 sends cors headers, if you want to disable it uncomment the following (the config is available on 0.12.1)
--http_cors_override = {
-- bosh = {
-- enabled = false;
-- };
-- websocket = {
-- enabled = false;
-- };
--}
-- https://ssl-config.mozilla.org/#server=haproxy&version=2.1&config=intermediate&openssl=1.1.0g&guideline=5.4
ssl = {
protocol = "tlsv1_2+";
ciphers = "ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384"
}
unlimited_jids = {
"focus@auth.rapat.space",
"jvb@auth.rapat.space"
}
VirtualHost "rapat.space"
-- enabled = false -- Remove this line to enable this host
authentication = "internal_plain"
-- Properties below are modified by jitsi-meet-tokens package config
-- and authentication above is switched to "token"
--app_id="example_app_id"
--app_secret="example_app_secret"
-- Assign this host a certificate for TLS, otherwise it would use the one
-- set in the global section (if any).
-- Note that old-style SSL on port 5223 only supports one certificate, and will always
-- use the global one.
ssl = {
key = "/etc/prosody/certs/rapat.space.key";
certificate = "/etc/prosody/certs/rapat.space.crt";
}
av_moderation_component = "avmoderation.rapat.space"
speakerstats_component = "speakerstats.rapat.space"
conference_duration_component = "conferenceduration.rapat.space"
-- we need bosh
modules_enabled = {
"bosh";
"pubsub";
"ping"; -- Enable mod_ping
"speakerstats";
"external_services";
"conference_duration";
"muc_lobby_rooms";
"muc_breakout_rooms";
"av_moderation";
}
c2s_require_encryption = false
lobby_muc = "lobby.rapat.space"
breakout_rooms_muc = "breakout.rapat.space"
main_muc = "conference.rapat.space"
-- muc_lobby_whitelist = { "recorder.rapat.space" } -- Here we can whitelist jibri to enter lobby enabled rooms
Component "conference.rapat.space" "muc"
restrict_room_creation = true
storage = "memory"
modules_enabled = {
"muc_meeting_id";
"muc_domain_mapper";
"polls";
--"token_verification";
"muc_rate_limit";
}
admins = { "focus@auth.rapat.space" }
muc_room_locking = false
muc_room_default_public_jids = true
Component "breakout.rapat.space" "muc"
restrict_room_creation = true
storage = "memory"
modules_enabled = {
"muc_meeting_id";
"muc_domain_mapper";
--"token_verification";
"muc_rate_limit";
"polls";
}
admins = { "focus@auth.rapat.space" }
muc_room_locking = false
muc_room_default_public_jids = true
-- internal muc component
Component "internal.auth.rapat.space" "muc"
storage = "memory"
modules_enabled = {
"ping";
}
admins = { "focus@auth.rapat.space", "jvb@auth.rapat.space" }
muc_room_locking = false
muc_room_default_public_jids = true
VirtualHost "auth.rapat.space"
ssl = {
key = "/etc/prosody/certs/auth.rapat.space.key";
certificate = "/etc/prosody/certs/auth.rapat.space.crt";
}
modules_enabled = {
"limits_exception";
}
authentication = "internal_hashed"
-- Proxy to jicofo's user JID, so that it doesn't have to register as a component.
Component "focus.rapat.space" "client_proxy"
target_address = "focus@auth.rapat.space"
Component "speakerstats.rapat.space" "speakerstats_component"
muc_component = "conference.rapat.space"
Component "conferenceduration.rapat.space" "conference_duration_component"
muc_component = "conference.rapat.space"
Component "avmoderation.rapat.space" "av_moderation_component"
muc_component = "conference.rapat.space"
Component "lobby.rapat.space" "muc"
storage = "memory"
restrict_room_creation = true
muc_room_locking = false
muc_room_default_public_jids = true
modules_enabled = {
"muc_rate_limit";
"polls";
}
-- Enabled dial-in for JaaS customers
-- Note: make sure you have the following packages installed: lua-basexx, liblua5.3-dev, libssl-dev, luarocks
-- and execute $ sudo luarocks install luajwtjitsi 3.0-0
VirtualHost "jigasi.meet.jitsi"
enabled = false -- JaaS customers remove this line
modules_enabled = {
"ping";
"bosh";
}
authentication = "token"
app_id = "jitsi";
asap_key_server = "https://jaas-public-keys.jitsi.net/jitsi-components/prod-8x8"
asap_accepted_issuers = { "jaas-components" }
asap_accepted_audiences = { "jigasi.rapat.space" }
VirtualHost "guest.rapat.space"
authentication = "anonymous"
c2s_require_encryption = false
How To Solve This 
?
