Jibri stops livestream randomly

Hi! The problem is, when I start a livestream it starts ok, but in a few minutes it’s just stops with error.
My setup:
one external IP
2 VMs on ubuntu 16.04: one for jitsi server another is for jibri.
Recording is working fine.
Logs from jibri:

2020-04-27 11:03:59.837 FINE: [223] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: start:live_stream
2020-04-27 11:03:59.837 INFO: [223] org.jitsi.jibri.status.JibriStatusManager.log() Busy status has changed: IDLE -> BUSY
2020-04-27 11:03:59.837 INFO: [223] org.jitsi.jibri.api.xmpp.XmppApi.updatePresence() Jibri reports its status is now JibriStatus(busyStatus=BUSY, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections
2020-04-27 11:03:59.837 INFO: [223] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.jibri.JibriStatusPacketExt@1ea53aa8
2020-04-27 11:04:00.888 FINE: [232] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Visiting url https://jitsi.domain.name/statisticalshadesbasetypically#config.iAmRecorder=true&config.externalConnectUrl=null&config.startWithAudioMuted=true&config.startWithVideoMuted=true&interfaceConfig.APP_NAME="Jibri"&config.analytics.disabled=true&config.p2p.enabled=false
2020-04-27 11:04:03.170 INFO: [232] org.jitsi.jibri.selenium.pageobjects.CallPage.visit() Waited 1605 milliseconds for call page to load
2020-04-27 11:04:03.198 INFO: [232] org.jitsi.jibri.selenium.JibriSelenium.onSeleniumStateChange() Transitioning from state Starting up to Running
2020-04-27 11:04:03.198 INFO: [232] org.jitsi.jibri.service.impl.StreamingJibriService.invoke() Selenium joined the call, starting capturer
2020-04-27 11:04:03.265 INFO: [232] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.launch() Starting ffmpeg with command ffmpeg -y -v info -f x11grab -draw_mouse 0 -r 30 -s 1280x720 -thread_queue_size 4096 -i :0.0+0,0 -f alsa -thread_queue_size 4096 -i plug:cloop -acodec aac -strict -2 -ar 44100 -c:v libx264 -preset veryfast -maxrate 2976k -bufsize 5952k -pix_fmt yuv420p -r 30 -crf 25 -g 60 -tune zerolatency -f flv rtmp://a.rtmp.youtube.com/live2/25jt-7z1p-x3b3-1337 ([ffmpeg, -y, -v, info, -f, x11grab, -draw_mouse, 0, -r, 30, -s, 1280x720, -thread_queue_size, 4096, -i, :0.0+0,0, -f, alsa, -thread_queue_size, 4096, -i, plug:cloop, -acodec, aac, -strict, -2, -ar, 44100, -c:v, libx264, -preset, veryfast, -maxrate, 2976k, -bufsize, 5952k, -pix_fmt, yuv420p, -r, 30, -crf, 25, -g, 60, -tune, zerolatency, -f, flv, rtmp://a.rtmp.youtube.com/live2/25jt-7z1p-x3b3-1337])
2020-04-27 11:04:04.833 INFO: [235] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.onFfmpegStateMachineStateChange() Ffmpeg capturer transitioning from state Starting up to Running
2020-04-27 11:04:04.834 INFO: [235] org.jitsi.jibri.service.impl.StreamingJibriService.onServiceStateChange() Streaming service transitioning from state Starting up to Running
2020-04-27 11:04:04.834 INFO: [235] org.jitsi.jibri.api.xmpp.XmppApi.invoke() Current service started up successfully, sending on iq <iq to='jibribrewery@internal.auth.jitsi.domain.name/focus' id='xCIw4-341' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='on'/></iq>
2020-04-27 11:04:18.256 INFO: [48] org.jitsi.jibri.selenium.JibriSelenium.run() Jibri client receive bitrates: {}, all clients muted? false
2020-04-27 11:04:33.216 INFO: [48] org.jitsi.jibri.selenium.JibriSelenium.run() Jibri client receive bitrates: {audio={download=0, upload=22}, download=0, upload=22, video={download=0, upload=0}}, all clients muted? false
2020-04-27 11:04:33.216 INFO: [48] org.jitsi.jibri.selenium.JibriSelenium.invoke() Recurring call status checks generated event org.jitsi.jibri.selenium.SeleniumEvent$NoMediaReceived@2556a75c
2020-04-27 11:04:33.216 INFO: [232] org.jitsi.jibri.selenium.JibriSelenium.onSeleniumStateChange() Transitioning from state Running to Error: SESSION No media received
2020-04-27 11:04:33.216 INFO: [232] org.jitsi.jibri.service.impl.StreamingJibriService.onServiceStateChange() Streaming service transitioning from state Running to Error: SESSION No media received
2020-04-27 11:04:33.217 INFO: [232] org.jitsi.jibri.api.xmpp.XmppApi.invoke() Current service had an error, sending error iq <iq to='jibribrewery@internal.auth.jitsi.domain.name/focus' id='xCIw4-343' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' failure_reason='error'/></iq>
2020-04-27 11:04:33.217 FINE: [232] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: stop:live_stream
2020-04-27 11:04:33.218 INFO: [232] org.jitsi.jibri.JibriManager.stopService() Stopping the current service
2020-04-27 11:04:33.219 INFO: [232] org.jitsi.jibri.service.impl.StreamingJibriService.stop() Stopping capturer
2020-04-27 11:04:33.219 INFO: [232] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() Stopping ffmpeg process
2020-04-27 11:04:33.268 INFO: [235] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.onFfmpegStateMachineStateChange() Ffmpeg capturer transitioning from state Running to Finished
2020-04-27 11:04:33.268 INFO: [232] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() ffmpeg exited with value 255
2020-04-27 11:04:33.269 INFO: [232] org.jitsi.jibri.service.impl.StreamingJibriService.stop() Stopped capturer
2020-04-27 11:04:33.269 INFO: [232] org.jitsi.jibri.service.impl.StreamingJibriService.stop() Quitting selenium
2020-04-27 11:04:33.281 INFO: [232] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 22 log entries for type browser
2020-04-27 11:04:33.326 INFO: [232] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 875 log entries for type driver
2020-04-27 11:04:33.434 INFO: [232] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Got 0 log entries for type client
2020-04-27 11:04:33.434 INFO: [232] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Leaving web call
2020-04-27 11:04:33.599 INFO: [232] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Quitting chrome driver
2020-04-27 11:04:33.672 INFO: [232] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Chrome driver quit
2020-04-27 11:04:33.672 INFO: [232] org.jitsi.jibri.service.impl.StreamingJibriService.stop() Quit selenium
2020-04-27 11:04:33.673 INFO: [232] org.jitsi.jibri.status.JibriStatusManager.log() Busy status has changed: BUSY -> IDLE

browser.log

2020-04-27 11:04:33.284 INFO: [232] browser.leaveCallAndQuitBrowser() [2020-04-27T11:04:18+0500] [SEVERE] https://jitsi.domain.name/libs/lib-jitsi-meet.min.js?v=3992 9:32421 "2020-04-27T06:04:08.681Z" "[modules/detection/ActiveDeviceDetector.js]" "Failed to acquire audio device with error: " undefined
2020-04-27 11:04:33.284 INFO: [232] browser.leaveCallAndQuitBrowser() [2020-04-27T11:04:18+0500] [SEVERE] https://jitsi.domain.name/libs/lib-jitsi-meet.min.js?v=3992 9:32421 "2020-04-27T06:04:08.681Z" "[modules/detection/ActiveDeviceDetector.js]" "Failed to acquire audio device with error: " undefined

Anyone? Please? Not even a suggestion?

Hi! I have the same problem. It seems to happen if participants are inactive for a while, though for shorter time periods than it’s defined in timeouts. Have no idea what to do with it for now.

Yeah this is a feature…if no one else is in the call then Jibri will leave (since there’s nothing to record).

Can we ignore this feature, by setting longer timeout?