Hi, we’ve been running a stable Jitsi Meet for some months now (no updates/changes in the last two months). A couple of days ago, we started having issues with live streaming. The dreaded “Failed to start” message poppep up after streaming was requested by the user.
But… in no few occasions the stream reached Youtube, so Jibri was actually starting.
Some log reading showed an exact 15 seconds delay between the “org.jitsi.jicofo.recording.jibri.JibriSession.log() Starting Jibri” message and the “org.jitsi.jicofo.recording.jibri.JibriSession.log() Unexpected response to start request: null”.
We don’t know what is causing Jibri to take longer to reply (running in Gcloud with 4 CPUs and 8GB), but it seems to be missing the deadline by very little.
Is it possible to increase the timeout for this operation only?
Is there anything we can do to speed up Jibri’s start up?
Where can we increase this timeout (in code, I guess)? Is it