Jibri Depency Error org.slf4j.impl.StaticLoggerBinder

Dear Jitsi Community

Jibri service status get some log depency error.

root@jibri:/home/doadmin# systemctl status jibri
● jibri.service - Jibri Process
Loaded: loaded (/etc/systemd/system/jibri.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2021-07-08 15:32:27 UTC; 14h ago
Process: 30244 ExecStop=/opt/jitsi/jibri/graceful_shutdown.sh (code=exited, status=0/SUCCESS)
Main PID: 30255 (java)
Tasks: 40 (limit: 2288)
CGroup: /system.slice/jibri.service
└─30255 /usr/lib/jvm/adoptopenjdk-8-hotspot-amd64/bin/java -Djava.util.logging.config.file=/etc/jitsi/jibri/logging.properties -Dconfig.fi

Jul 08 15:32:27 jibri.onplateau.com systemd[1]: jibri.service: Failed with result ‘exit-code’.
Jul 08 15:32:27 jibri.onplateau.com systemd[1]: Stopped Jibri Process.
Jul 08 15:32:27 jibri.onplateau.com systemd[1]: Started Jibri Process.
Jul 08 15:32:29 jibri.onplateau.com launch.sh[30255]: SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.
Jul 08 15:32:29 jibri.onplateau.com launch.sh[30255]: SLF4J: Defaulting to no-operation (NOP) logger implementation
Jul 08 15:32:29 jibri.onplateau.com launch.sh[30255]: SLF4J: See SLF4J Error Codes for further details.
Jul 08 15:32:39 jibri.onplateau.com launch.sh[30255]: Starting ChromeDriver 91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads
Jul 08 15:32:39 jibri.onplateau.com launch.sh[30255]: Only local connections are allowed.
Jul 08 15:32:39 jibri.onplateau.com launch.sh[30255]: Please see ChromeDriver - WebDriver for Chrome - Security Considerations for suggestions on keeping
Jul 08 15:32:39 jibri.onplateau.com launch.sh[30255]: ChromeDriver was started successfully.

Somebody can give me an idea what I should
have into consideration?

Thank you in advance.

Kind regards,

Welcome to the forum.

Try doing a recording and see if it works.

Hi Freddie,

Recording is working but after a few minutes i got Recording Stopped error. When I examine it, i realized that memory is not enough. When i got Recording Stopped error, memory is refreshed.

Does that depency [org.slf4j.impl.StaticLoggerBinder] error cause different problems?

Thanks.

No, you can ignore it.

Make sure you have enough resources (CPU, RAM) for trouble-free Jibri recording.

1 Like

Ok, thanks for your responses Freddie.

Freddie Hi,

I’ve 4GB memory on Jibri Server (Separate). But while recording after 2-3 minutes later I got Recording Stopped error again. Can you give me an idea what I should have into consideration?

Thanks.

How many cores do you have?

Hi emrah,

Now i got, 2 core CPU and 4 GB RAM in Seperated Jibri Server.

It was working before March update with 2 CPU and 2 GB RAM.

Can be about ffmpeg resolution’s default?

Thanks for reply.

The memory problem occurs mostly when the CPU power is low. The default resolution was changed from 720p to 1080p on the new jibri version and this needs more CPU power.

You can increase the number of cores (at least 4) or you may change the resolution (for example to 720p)

How can i change resolution? Can you share information about that?

/etc/jitsi/jibri/xorg-video-dummy.conf

#Virtual 1920 1080
Virtual 1280 720

/etc/jitsi/jibri/jibri.conf

ffmpeg {
    resolution = "1280x720"
systemctl stop jibri-xorg.service
sleep 5
systemctl start jibri.service
1 Like

Thank for support @emrah

That was fix my issue now.

1 Like