Recording Stopped (Recording failed to start)

As advised in your other post, this is a resource problem. You can’t successfully run the current Jibri (especially) on 2 CPUs.

Thanks @Freddie for your response. Can Jibri older version, like jibri 8.0-61-g99288dc-1 will work correctly on Jitsi version ii jitsi-meet 2.0.5870-1 .

Thanks in advance.

Yes, older version works fine with the current version of Jitsi Meet. But again, you’ll eventually still run into problems with those low specs.

Hi all, I’ve been trying to seld host jitsi and 6 jibri docker instances on the same server and running into issue that doesn’t let jibri record. Here are the logs. Any help is very much appreciated.

2021-07-24 08:54:13.839 FINE: [39] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse() Could not add a provider for element busy-status from namespace http://jitsi.org/protocol/jibri
2021-07-24 08:54:13.839 FINE: [39] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse() Could not add a provider for element health-status from namespace http://jitsi.org/protocol/health
2021-07-24 08:54:13.843 FINE: [42] org.jitsi.xmpp.mucclient.MucClient.log() Received an IQ with type set: IQ Stanza (jibri http://jitsi.org/protocol/jibri) [to=jibri@auth.sessions.mydomain.one/39535bb8-d1f3-4916-a199-9867870b93cd,from=jibribrewery@internal.auth.sessions.mydomain.one/focus,id=amlicmlAYXV0aC5zZXNzaW9ucy5hdXJlYWwub25lLzM5NTM1YmI4LWQxZjMtNDkxNi1hMTk5LTk4Njc4NzBiOTNjZABXbVlySi0xMTcAkiMA5lRhz0Rjx6Y7tyf3EQ==,type=set,]
2021-07-24 08:54:13.845 INFO: [42] org.jitsi.jibri.api.xmpp.XmppApi.log() Received JibriIq <iq to='jibri@auth.sessions.mydomain.one/39535bb8-d1f3-4916-a199-9867870b93cd' from='jibribrewery@internal.auth.sessions.mydomain.one/focus' id='amlicmlAYXV0aC5zZXNzaW9ucy5hdXJlYWwub25lLzM5NTM1YmI4LWQxZjMtNDkxNi1hMTk5LTk4Njc4NzBiOTNjZABXbVlySi0xMTcAkiMA5lRhz0Rjx6Y7tyf3EQ==' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' action='start' recording_mode='file' room='nervouseffortsexaminedownwards@conference.sessions.mydomain.one' session_id='utygbnbmocifdbrc' app_data='{"file_recording_metadata":{"share":true}}'/></iq> from environment [MucClient id=sessions.mydomain.one hostname=sessions.mydomain.one]
2021-07-24 08:54:13.845 INFO: [42] org.jitsi.jibri.api.xmpp.XmppApi.log() Received start request, starting service
2021-07-24 08:54:13.859 INFO: [42] org.jitsi.jibri.api.xmpp.XmppApi.log() Parsed call url info: CallUrlInfo(baseUrl=<no value>, callName=nervouseffortsexaminedownwards, urlParams=[])
2021-07-24 08:54:13.860 INFO: [42] org.jitsi.jibri.JibriManager.log() Starting a file recording with params: FileRecordingRequestParams(callParams=CallParams(callUrlInfo=CallUrlInfo(baseUrl=<no value>, callName=nervouseffortsexaminedownwards, urlParams=[]), email='', passcode=null, callStatsUsernameOverride=, displayName=), sessionId=utygbnbmocifdbrc, callLoginParams=XmppCredentials(domain=recorder.sessions.mydomain.one, port=null, username=recorder, password=Porsche911))
2021-07-24 08:54:13.877 FINE: [42] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.log() Detected os as OS: LINUX
2021-07-24 08:54:13.880 FINE: [42] org.jitsi.jibri.config.log() ConfigSourceSupplier: Trying to retrieve key 'jibri.call-status-checks.default-call-empty-timeout' from source 'config' as type java.time.Duration
2021-07-24 08:54:13.881 FINE: [42] org.jitsi.jibri.config.log() ConfigSourceSupplier: Successfully retrieved key 'jibri.call-status-checks.default-call-empty-timeout' from source 'config' as type java.time.Duration
2021-07-24 08:54:13.886 FINE: [42] org.jitsi.jibri.config.log() ConfigSourceSupplier: Trying to retrieve key 'jibri.chrome.flags' from source 'config' as type kotlin.collections.List<kotlin.String>
2021-07-24 08:54:13.886 FINE: [42] org.jitsi.jibri.config.log() ConfigSourceSupplier: Successfully retrieved key 'jibri.chrome.flags' from source 'config' as type kotlin.collections.List<kotlin.String>
2021-07-24 08:54:13.934 FINE: [39] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse() Could not add a provider for element busy-status from namespace http://jitsi.org/protocol/jibri
2021-07-24 08:54:13.934 FINE: [39] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse() Could not add a provider for element health-status from namespace http://jitsi.org/protocol/health
Starting ChromeDriver 90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}) on port 26452
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
2021-07-24 08:54:14.586 INFO: [42] org.openqa.selenium.remote.ProtocolHandshake.createSession() Detected dialect: OSS
2021-07-24 08:54:14.599 FINE: [42] org.jitsi.jibri.config.log() FallbackSupplier: checking for value via suppliers:
  LambdaSupplier: 'JibriConfig::recordingDirectory'
  ConfigSourceSupplier: key: 'jibri.recording.recordings-directory', type: 'kotlin.String', source: 'config'
2021-07-24 08:54:14.599 FINE: [42] org.jitsi.jibri.config.log() LambdaSupplier: Trying to retrieve value via JibriConfig::recordingDirectory
2021-07-24 08:54:14.599 FINE: [42] org.jitsi.jibri.config.log() LambdaSupplier: 'JibriConfig::recordingDirectory': found value
2021-07-24 08:54:14.599 FINE: [42] org.jitsi.jibri.config.log() FallbackSupplier: value found via LambdaSupplier: 'JibriConfig::recordingDirectory'
2021-07-24 08:54:14.600 FINE: [42] org.jitsi.jibri.config.log() FallbackSupplier: checking for value via suppliers:
  LambdaSupplier: 'JibriConfig::finalizeRecordingScriptPath'
  ConfigSourceSupplier: key: 'jibri.recording.finalize-script', type: 'kotlin.String', source: 'config'
2021-07-24 08:54:14.600 FINE: [42] org.jitsi.jibri.config.log() LambdaSupplier: Trying to retrieve value via JibriConfig::finalizeRecordingScriptPath
2021-07-24 08:54:14.600 FINE: [42] org.jitsi.jibri.config.log() LambdaSupplier: 'JibriConfig::finalizeRecordingScriptPath': found value
2021-07-24 08:54:14.600 FINE: [42] org.jitsi.jibri.config.log() FallbackSupplier: value found via LambdaSupplier: 'JibriConfig::finalizeRecordingScriptPath'
2021-07-24 08:54:14.600 INFO: [42] org.jitsi.jibri.service.impl.FileRecordingJibriService.log() Writing recording to config/recordings/utygbnbmocifdbrc, finalize script path config/jibri/finalize.sh
2021-07-24 08:54:14.604 FINE: [42] org.jitsi.jibri.statsd.JibriStatsDClient.log() Incrementing statsd counter: start:recording
2021-07-24 08:54:14.605 INFO: [42] org.jitsi.jibri.status.JibriStatusManager.log() Busy status has changed: IDLE -> BUSY
2021-07-24 08:54:14.605 FINE: [42] org.jitsi.jibri.webhooks.v1.WebhookClient.log() Updating 0 subscribers of status
2021-07-24 08:54:14.605 INFO: [42] org.jitsi.jibri.api.xmpp.XmppApi.log() Jibri reports its status is now JibriStatus(busyStatus=BUSY, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections
2021-07-24 08:54:14.606 FINE: [42] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@7e19b9a0
2021-07-24 08:54:14.606 FINE: [42] org.jitsi.xmpp.mucclient.MucClientManager.log() Replacing presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@6831d8fd
2021-07-24 08:54:14.607 INFO: [42] org.jitsi.jibri.api.xmpp.XmppApi.log() Sending 'pending' response to start IQ
2021-07-24 08:54:14.608 FINE: [39] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse() Could not add a provider for element busy-status from namespace http://jitsi.org/protocol/jibri
2021-07-24 08:54:14.609 FINE: [39] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse() Could not add a provider for element health-status from namespace http://jitsi.org/protocol/health
2021-07-24 08:54:14.610 SEVERE: [52] org.jitsi.jibri.service.impl.FileRecordingJibriService.log() Error creating directory
java.nio.file.AccessDeniedException: /run/s6/services/30-jibri/config
        at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
        at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
        at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
        at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384)
        at java.nio.file.Files.createDirectory(Files.java:674)
        at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781)
        at java.nio.file.Files.createDirectories(Files.java:767)
        at org.jitsi.jibri.util.FileUtilsKt.createIfDoesNotExist(FileUtils.kt:26)
        at org.jitsi.jibri.service.impl.FileRecordingJibriService.start(FileRecordingJibriService.kt:143)
        at org.jitsi.jibri.JibriManager$startService$3.run(JibriManager.kt:239)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
2021-07-24 08:54:14.611 INFO: [52] org.jitsi.jibri.api.xmpp.XmppApi.log() Current service had an error Error: ErrorCreatingRecordingsDirectory SYSTEM Could not creat recordings director, sending error iq <iq to='jibribrewery@internal.auth.sessions.mydomain.one/focus' id='9c6sR-40' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' failure_reason='error' should_retry='true'/></iq>
2021-07-24 08:54:14.611 FINE: [52] org.jitsi.jibri.statsd.JibriStatsDClient.log() Incrementing statsd counter: error:recording
2021-07-24 08:54:14.612 INFO: [52] org.jitsi.jibri.status.JibriStatusManager.log() Received component health update: JibriManager has status UNHEALTHY (detail: )
2021-07-24 08:54:14.612 INFO: [52] org.jitsi.jibri.status.JibriStatusManager.log() Health status has changed: HEALTHY -> UNHEALTHY
2021-07-24 08:54:14.612 FINE: [52] org.jitsi.jibri.webhooks.v1.WebhookClient.log() Updating 0 subscribers of status
2021-07-24 08:54:14.613 INFO: [52] org.jitsi.jibri.api.xmpp.XmppApi.log() Jibri reports its status is now JibriStatus(busyStatus=BUSY, health=OverallHealth(healthStatus=UNHEALTHY, details={JibriManager=ComponentHealthDetails(healthStatus=UNHEALTHY, detail=)})), publishing presence to connections
2021-07-24 08:54:14.613 FINE: [52] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@637a829b
2021-07-24 08:54:14.613 FINE: [52] org.jitsi.xmpp.mucclient.MucClientManager.log() Replacing presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@7e19b9a0
2021-07-24 08:54:14.613 FINE: [52] org.jitsi.jibri.statsd.JibriStatsDClient.log() Incrementing statsd counter: stop:recording
2021-07-24 08:54:14.614 INFO: [52] org.jitsi.jibri.JibriManager.log() Stopping the current service
2021-07-24 08:54:14.614 INFO: [52] org.jitsi.jibri.service.impl.FileRecordingJibriService.log() Stopping capturer
2021-07-24 08:54:14.614 INFO: [52] org.jitsi.jibri.util.JibriSubprocess.log() Stopping ffmpeg process
2021-07-24 08:54:14.614 INFO: [52] org.jitsi.jibri.util.JibriSubprocess.log() ffmpeg exited with value null
2021-07-24 08:54:14.614 INFO: [52] org.jitsi.jibri.service.impl.FileRecordingJibriService.log() Quitting selenium
2021-07-24 08:54:14.623 INFO: [52] org.jitsi.jibri.service.impl.FileRecordingJibriService.log() Participants in this recording: []
2021-07-24 08:54:14.623 SEVERE: [52] org.jitsi.jibri.service.impl.FileRecordingJibriService.log() Unable to write metadata file to recording directory config/recordings
2021-07-24 08:54:14.623 INFO: [52] org.jitsi.jibri.selenium.JibriSelenium.log() Leaving call and quitting browser
2021-07-24 08:54:14.624 INFO: [52] org.jitsi.jibri.selenium.JibriSelenium.log() Recurring call status checks cancelled
2021-07-24 08:54:14.631 INFO: [52] org.jitsi.jibri.selenium.JibriSelenium.log() Got 0 log entries for type browser
2021-07-24 08:54:14.639 INFO: [52] org.jitsi.jibri.selenium.JibriSelenium.log() Got 67 log entries for type driver
2021-07-24 08:54:14.648 INFO: [52] org.jitsi.jibri.selenium.JibriSelenium.log() Got 0 log entries for type client
2021-07-24 08:54:14.648 INFO: [52] org.jitsi.jibri.selenium.JibriSelenium.log() Leaving web call
2021-07-24 08:54:14.652 FINE: [39] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse() Could not add a provider for element busy-status from namespace http://jitsi.org/protocol/jibri
2021-07-24 08:54:14.652 FINE: [39] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse() Could not add a provider for element health-status from namespace http://jitsi.org/protocol/health
2021-07-24 08:54:14.664 INFO: [52] org.jitsi.jibri.selenium.JibriSelenium.log() Quitting chrome driver
2021-07-24 08:54:14.731 INFO: [52] org.jitsi.jibri.selenium.JibriSelenium.log() Chrome driver quit
2021-07-24 08:54:14.731 INFO: [52] org.jitsi.jibri.service.impl.FileRecordingJibriService.log() Finalizing the recording
2021-07-24 08:54:14.733 SEVERE: [52] org.jitsi.jibri.service.impl.FileRecordingJibriService.log() Failed to run finalize script
java.io.IOException: Cannot run program "config/jibri/finalize.sh": error=2, No such file or directory
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
        at org.jitsi.jibri.util.ProcessWrapper.start(ProcessWrapper.kt:88)
        at org.jitsi.jibri.service.impl.FileRecordingJibriService.finalize(FileRecordingJibriService.kt:220)
        at org.jitsi.jibri.service.impl.FileRecordingJibriService.stop(FileRecordingJibriService.kt:205)
        at org.jitsi.jibri.JibriManager.stopService(JibriManager.kt:263)
        at org.jitsi.jibri.JibriManager$startService$1.invoke(JibriManager.kt:211)
        at org.jitsi.jibri.JibriManager$startService$1.invoke(JibriManager.kt:85)
        at org.jitsi.jibri.util.StatusPublisher$addStatusHandler$1.invoke(StatusPublisher.kt:37)
        at org.jitsi.jibri.util.StatusPublisher$addStatusHandler$1.invoke(StatusPublisher.kt:29)
        at org.jitsi.jibri.util.StatusPublisher$publishStatus$1.invoke(StatusPublisher.kt:53)
        at org.jitsi.jibri.util.StatusPublisher$publishStatus$1.invoke(StatusPublisher.kt:29)
        at kotlin.collections.CollectionsKt__MutableCollectionsKt.filterInPlace$CollectionsKt__MutableCollectionsKt(MutableCollections.kt:285)
        at kotlin.collections.CollectionsKt__MutableCollectionsKt.retainAll(MutableCollections.kt:276)
        at org.jitsi.jibri.util.StatusPublisher.publishStatus(StatusPublisher.kt:53)
        at org.jitsi.jibri.service.impl.FileRecordingJibriService.start(FileRecordingJibriService.kt:144)
        at org.jitsi.jibri.JibriManager$startService$3.run(JibriManager.kt:239)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: error=2, No such file or directory
        at java.lang.UNIXProcess.forkAndExec(Native Method)
        at java.lang.UNIXProcess.<init>(UNIXProcess.java:247)
        at java.lang.ProcessImpl.start(ProcessImpl.java:134)
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
        ... 20 more
2021-07-24 08:54:14.734 FINE: [52] org.jitsi.jibri.config.log() FallbackSupplier: checking for value via suppliers:
  LambdaSupplier: 'JibriConfig::singleUseMode'
  ConfigSourceSupplier: key: 'jibri.single-use-mode', type: 'kotlin.Boolean', source: 'config'
2021-07-24 08:54:14.734 FINE: [52] org.jitsi.jibri.config.log() LambdaSupplier: Trying to retrieve value via JibriConfig::singleUseMode
2021-07-24 08:54:14.735 FINE: [52] org.jitsi.jibri.config.log() FallbackSupplier: failed to find value via LambdaSupplier: 'JibriConfig::singleUseMode': org.jitsi.metaconfig.ConfigException$UnableToRetrieve$Error: class java.lang.NullPointerException
2021-07-24 08:54:14.735 FINE: [52] org.jitsi.jibri.config.log() ConfigSourceSupplier: Trying to retrieve key 'jibri.single-use-mode' from source 'config' as type kotlin.Boolean
2021-07-24 08:54:14.736 FINE: [52] org.jitsi.jibri.config.log() ConfigSourceSupplier: Successfully retrieved key 'jibri.single-use-mode' from source 'config' as type kotlin.Boolean
2021-07-24 08:54:14.736 FINE: [52] org.jitsi.jibri.config.log() FallbackSupplier: value found via ConfigSourceSupplier: key: 'jibri.single-use-mode', type: 'kotlin.Boolean', source: 'config'
2021-07-24 08:54:14.736 INFO: [52] org.jitsi.jibri.status.JibriStatusManager.log() Busy status has changed: BUSY -> IDLE
2021-07-24 08:54:14.736 FINE: [52] org.jitsi.jibri.webhooks.v1.WebhookClient.log() Updating 0 subscribers of status
2021-07-24 08:54:14.737 INFO: [52] org.jitsi.jibri.api.xmpp.XmppApi.log() Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=UNHEALTHY, details={JibriManager=ComponentHealthDetails(healthStatus=UNHEALTHY, detail=)})), publishing presence to connections
2021-07-24 08:54:14.737 FINE: [52] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@a79b462
2021-07-24 08:54:14.737 FINE: [52] org.jitsi.xmpp.mucclient.MucClientManager.log() Replacing presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@637a829b
2021-07-24 08:54:14.741 FINE: [39] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse() Could not add a provider for element busy-status from namespace http://jitsi.org/protocol/jibri
2021-07-24 08:54:14.741 FINE: [39] org.jitsi.xmpp.extensions.DefaultPacketExtensionProvider.parse() Could not add a provider for element health-status from namespace http://jitsi.org/protocol/health
2021-07-24 08:54:14.742 SEVERE: [52] org.jitsi.jibri.service.impl.FileRecordingJibriService.log() Unable to write to config/recordings
2021-07-24 08:54:14.742 INFO: [52] org.jitsi.jibri.api.xmpp.XmppApi.log() Current service had an error Error: RecordingsDirectoryNotWritable SYSTEM Recordings directory is not writable, sending error iq <iq to='jibribrewery@internal.auth.sessions.mydomain.one/focus' id='9c6sR-45' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' failure_reason='error' should_retry='true'/></iq>
2021-07-24 08:54:14.742 FINE: [52] org.jitsi.jibri.statsd.JibriStatsDClient.log() Incrementing statsd counter: error:recording
2021-07-24 08:54:14.743 INFO: [52] org.jitsi.jibri.status.JibriStatusManager.log() Received component health update: JibriManager has status UNHEALTHY (detail: )
2021-07-24 08:54:14.743 INFO: [52] org.jitsi.jibri.JibriManager.log() No service active, ignoring stop
2021-07-24 08:54:14.746 INFO: [53] org.jitsi.jibri.selenium.pageobjects.HomePage.log() Visiting url <no value>
2021-07-24 08:54:14.749 SEVERE: [53] org.jitsi.jibri.selenium.JibriSelenium.log() An error occurred while joining the call
org.openqa.selenium.NoSuchSessionException: Session ID is null. Using WebDriver after calling quit()?
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: host: 'f90592086e3a', ip: '172.23.0.3', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-147-generic', java.version: '1.8.0_292'
Driver info: driver.version: RemoteWebDriver
        at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:125)
        at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
        at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:543)
        at org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:271)
        at org.jitsi.jibri.selenium.pageobjects.AbstractPageObject.visit(AbstractPageObject.kt:35)
        at org.jitsi.jibri.selenium.JibriSelenium$joinCall$1.run(JibriSelenium.kt:278)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
2021-07-24 08:54:14.750 INFO: [53] org.jitsi.jibri.selenium.JibriSelenium.log() Transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call
2021-07-24 08:54:14.751 INFO: [53] org.jitsi.jibri.service.impl.FileRecordingJibriService.log() File recording service transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call
2021-07-24 08:54:14.751 INFO: [53] org.jitsi.jibri.api.xmpp.XmppApi.log() Current service had an error Error: FailedToJoinCall SESSION Failed to join the call, sending error iq <iq to='jibribrewery@internal.auth.sessions.mydomain.one/focus' id='9c6sR-46' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' failure_reason='error' should_retry='true'/></iq>
2021-07-24 08:54:14.752 INFO: [53] org.jitsi.jibri.JibriManager.log() No service active, ignoring stop

Did you create that directory? Does Jibri have write-access to it?

I did create the directory. Not sure if Jibri has access to it. How can I check if Jibri has access to it ?

Btw I followed the steps at [Setup / Guide] Jitsi Meet Native + Multiple (6) Jibri Docker instances working on the same AWS server

For Installing and running Jibri How much vps resourse required minimum.

Just make sure Jibri owns it:

chown jibri:jibri /config/recordings

Although I’m not sure why you decided your recordings should be stored under the config directory…

At least 4CPUs/8GB RAM to be safe.

Thanks @Freddie for opting to help. I tried the command and it resulted with the error chown: invalid user: ‘jibri:jibri’. With that I also checked if I have jibri user and used the command less /etc/passwd to check and from the result I verified that jibri user doesnt exist on the instance. As I mentioned earlier I’d referred the process at [Setup / Guide] Jitsi Meet Native + Multiple (6) Jibri Docker instances working on the same AWS server and I believe this command prosodyctl register jibri auth.my.domain.com niceAndLongPassword123 was supposed to create the user. Could you guide me how I can investigate the mitigate the issue ?

Also I’m trying to have multiple jibri docker instances running as opposed to single jibri instance.

There is no good reason to have recordings in the config directory and I can change that if you feel that can resolve the issue.

Thank You

TUTORIAL - How to Install the NEW JIBRI

[TUTORIAL] Configuration of the New Jibri (1080p Livestreaming and Recording)

I did this nothing errors comes when I click recording or live stream nothing happens. Means there is no recording done.

Hi, I followed this to install jibri first time nothing errors comes while doing this. But recording is not working and also it is not giving any error.

The best person to help is the author of the post you followed to instal…

I followed this to install

Oh ok. So no docker then, right?
If it is not docker, you might want to describe your setup again…that would provide more info, for helping…

No I have no docker

Ok. Share jibri log file and also jibri.conf file…

where I get log file