Jibri stops recording after 5-7 minutes automatically

@Prashanth @damencho @emrah

Jibri automatically stops recording after 5-7 minutes of recording. It appears the Chrome tab is crashing.

Can you please suggest a solution?

2021-03-11 05:05:50.938 FINE: [18] org.jitsi.jibri.util.ProcessStatePublisher.ffmpeg.invoke() Process ffmpeg hasn’t written in 2 seconds, publishing periodic update
2021-03-11 05:05:50.943 INFO: [242] org.jitsi.jibri.selenium.JibriSelenium.onSeleniumStateChange() Transitioning from state Running to Error: ChromeHung SESSION Chrome hung
2021-03-11 05:05:50.944 FINE: [18] org.jitsi.jibri.util.ProcessStatePublisher.ffmpeg.invoke() Process ffmpeg hasn’t written in 2 seconds, publishing periodic update
2021-03-11 05:05:50.948 INFO: [242] org.jitsi.jibri.service.impl.FileRecordingJibriService.onServiceStateChange() File recording service transitioning from state Running to Error: ChromeHung SESSION Chrome hung
2021-03-11 05:05:50.949 FINE: [18] org.jitsi.jibri.util.ProcessStatePublisher.ffmpeg.invoke() Process ffmpeg hasn’t written in 2 seconds, publishing periodic update
2021-03-11 05:05:50.952 FINE: [18] org.jitsi.jibri.util.ProcessStatePublisher.ffmpeg.invoke() Process ffmpeg hasn’t written in 2 seconds, publishing periodic update
2021-03-11 05:05:50.957 FINE: [18] org.jitsi.jibri.webhooks.v1.WebhookClient.invokeSuspend() Updating 0 subscribers of status
2021-03-11 05:05:50.961 INFO: [242] org.jitsi.jibri.api.xmpp.XmppApi.invoke() Current service had an error Error: ChromeHung SESSION Chrome hung, sending error iq
2021-03-11 05:05:50.964 FINE: [18] org.jitsi.jibri.util.ProcessStatePublisher.ffmpeg.invoke() Process ffmpeg hasn’t written in 2 seconds, publishing periodic update
2021-03-11 05:05:50.966 FINE: [18] org.jitsi.jibri.util.ProcessStatePublisher.ffmpeg.invoke() Process ffmpeg hasn’t written in 2 seconds, publishing periodic update
2021-03-11 05:05:50.969 FINE: [18] org.jitsi.jibri.util.ProcessStatePublisher.ffmpeg.invoke() Process ffmpeg hasn’t written in 2 seconds, publishing periodic update
2021-03-11 05:05:50.972 FINE: [242] org.jitsi.jibri.statsd.JibriStatsDClient.incrementCounter() Incrementing statsd counter: stop:recording
2021-03-11 05:05:50.983 INFO: [242] org.jitsi.jibri.JibriManager.stopService() Stopping the current service
2021-03-11 05:05:50.986 INFO: [242] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Stopping capturer
2021-03-11 05:05:50.987 INFO: [242] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() Stopping ffmpeg process
2021-03-11 05:05:57.382 INFO: [242] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.stop() ffmpeg exited with value 137
2021-03-11 05:05:57.396 INFO: [242] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Quitting selenium
2021-03-11 05:06:00.157 INFO: [242] org.jitsi.jibri.service.impl.FileRecordingJibriService.stop() Participants in this recording:
2021-03-11 05:06:00.211 INFO: [242] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Leaving call and quitting browser
2021-03-11 05:06:00.211 INFO: [242] org.jitsi.jibri.selenium.JibriSelenium.leaveCallAndQuitBrowser() Recurring call status checks cancelled

Since it works longer than 5 mins this may be a resource problem.
Increase your resources to 4 cores / 8 GB RAM

1 Like