Jibri recording stops after a while on raspberry pi

If you’re hosting BOTH Jitsi and Jibri on the same server.

For the default installation, jitsi (not jitsi + jibri) needs 8 GB RAM. Everything seems normal at the beginning but jicofo and jvb can use up to 4 GB of RAM before the garbage collector flushs it. If there is not enogh RAM then some processes will be crashed at some point.

For jibri the recommended resources are 4 cores and 4 GB RAM for each recording but ffmpeg needs more RAM if the CPU is slow. On the slow system (for example if it’s reserved only one core for jibri) ffmpeg starts to use RAM more aggresively

1 Like

It’s important to note the type of hardware as well. A normal PC/server can manage much better with less resources than a raspberry pi. You can get away with Jitsi+Jibri on 4CPUs/8GB RAM on a regular PC/server (although Jibri has been known to eventually ravage the RAM on lengthy recordings). Raspberry pis are minimalist machines. They were designed to handle the most basic tasks. Trying to provision a raspberry pi to do more resource-intensive work will require heavier specifications.

1 Like

I don’t know if it’s possible for ffmpeg to use the Raspberry Pi’s H264 hardware encoder/decoder. If it’s possible then this can made a huge difference