jibri
jibri copied to clipboard
jitsi
Failed to load class "org.slf4j.impl.StaticLoggerBinder"
When restarting jibri I have a message:
root@meet:~# service jibri restart
root@meet:~# service jibri status
● jibri.service - Jibri Process
Loaded: loaded (/etc/systemd/system/jibri.service; disabled; vendor preset: enabled)
Active: active (running) since Thu 2020-12-17 15:47:57 CET; 3s ago
Main PID: 3205 (java)
Tasks: 49 (limit: 65000)
Memory: 145.8M
CGroup: /system.slice/jibri.service
└─3205 java -Djava.util.logging.config.file=/etc/jitsi/jibri/logging.properties -Dconfig.file=/etc/jitsi/jibri/jibri.conf -jar /opt/jitsi/jibri/jibri.jar --config
Dec 17 15:47:57 meet systemd[1]: jibri.service: Main process exited, code=exited, status=143/n/a
Dec 17 15:47:57 meet systemd[1]: jibri.service: Failed with result 'exit-code'.
Dec 17 15:47:57 meet systemd[1]: Stopped Jibri Process.
Dec 17 15:47:57 meet systemd[1]: Started Jibri Process.
Dec 17 15:47:57 meet launch.sh[3205]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
Dec 17 15:47:57 meet launch.sh[3205]: SLF4J: Defaulting to no-operation (NOP) logger implementation
Dec 17 15:47:57 meet launch.sh[3205]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Dec 16 09:24:31 meet Xorg[15986]: X.Org X Server 1.20.4
Dec 16 09:24:31 meet Xorg[15986]: X Protocol Version 11, Revision 0
Dec 16 09:24:31 meet Xorg[15986]: Build Operating System: Linux 4.19.0-12-amd64 x86_64 Debian
Dec 16 09:24:31 meet Xorg[15986]: Current Operating System: Linux meet 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64
Dec 16 09:24:31 meet Xorg[15986]: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 root=UUID=f0246083-4c1c-4d5e-a898-2979746b99cf ro quiet
Dec 16 09:24:31 meet Xorg[15986]: Build Date: 01 December 2020 05:59:57PM
Dec 16 09:24:31 meet Xorg[15986]: xorg-server 2:1.20.4-1+deb10u2 (https://www.debian.org/support)
Dec 16 09:24:31 meet Xorg[15986]: Current version of pixman: 0.36.0
Dec 16 09:24:31 meet Xorg[15986]: #011Before reporting problems, check http://wiki.x.org
Dec 16 09:24:31 meet Xorg[15986]: #011to make sure that you have the latest version.
Dec 16 09:24:31 meet Xorg[15986]: Markers: (--) probed, (**) from config file, (==) default setting,
Dec 16 09:24:31 meet Xorg[15986]: #011(++) from command line, (!!) notice, (II) informational,
Dec 16 09:24:31 meet Xorg[15986]: #011(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Dec 16 09:24:31 meet Xorg[15986]: (++) Log file: "/var/log/jitsi/jibri/xorg.log", Time: Wed Dec 16 15:24:31 2020
Dec 16 09:24:31 meet Xorg[15986]: (++) Using config file: "/etc/jitsi/jibri/xorg-video-dummy.conf"
Dec 16 09:24:31 meet Xorg[15986]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
Dec 16 09:24:32 meet launch.sh[15985]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
Dec 16 09:24:32 meet launch.sh[15985]: SLF4J: Defaulting to no-operation (NOP) logger implementation
Dec 16 09:24:32 meet launch.sh[15985]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
root@meet:~# journalctl -u jibri
-- Logs begin at Thu 2020-12-17 15:41:52 CET, end at Thu 2020-12-17 21:15:54 CET. --
Dec 17 15:42:38 meet systemd[1]: Started Jibri Process.
Dec 17 15:42:39 meet launch.sh[728]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
Dec 17 15:42:39 meet launch.sh[728]: SLF4J: Defaulting to no-operation (NOP) logger implementation
Dec 17 15:42:39 meet launch.sh[728]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Dec 17 15:46:22 meet systemd[1]: Stopping Jibri Process...
Dec 17 15:46:22 meet graceful_shutdown.sh[2379]: % Total % Received % Xferd Average Speed Time Time Time Current
Dec 17 15:46:22 meet graceful_shutdown.sh[2379]: Dload Upload Total Spent Left Speed
Dec 17 15:46:22 meet graceful_shutdown.sh[2379]: [149B blob data]
Dec 17 15:46:22 meet systemd[1]: jibri.service: Control process exited, code=exited, status=7/NOTRUNNING
Dec 17 15:46:22 meet systemd[1]: jibri.service: Main process exited, code=exited, status=143/n/a
Dec 17 15:46:22 meet systemd[1]: jibri.service: Failed with result 'exit-code'.
Dec 17 15:46:22 meet systemd[1]: Stopped Jibri Process.
Dec 17 15:46:22 meet systemd[1]: Started Jibri Process.
Dec 17 15:46:24 meet launch.sh[2387]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
Dec 17 15:46:24 meet launch.sh[2387]: SLF4J: Defaulting to no-operation (NOP) logger implementation
Dec 17 15:46:24 meet launch.sh[2387]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Dec 17 15:47:56 meet systemd[1]: Stopping Jibri Process...
Dec 17 15:47:56 meet graceful_shutdown.sh[3201]: % Total % Received % Xferd Average Speed Time Time Time Current
Dec 17 15:47:56 meet graceful_shutdown.sh[3201]: Dload Upload Total Spent Left Speed
Dec 17 15:47:56 meet graceful_shutdown.sh[3201]: [149B blob data]
Dec 17 15:47:56 meet systemd[1]: jibri.service: Control process exited, code=exited, status=7/NOTRUNNING
Dec 17 15:47:57 meet systemd[1]: jibri.service: Main process exited, code=exited, status=143/n/a
Dec 17 15:47:57 meet systemd[1]: jibri.service: Failed with result 'exit-code'.
Dec 17 15:47:57 meet systemd[1]: Stopped Jibri Process.
Dec 17 15:47:57 meet systemd[1]: Started Jibri Process.
Dec 17 15:47:57 meet launch.sh[3205]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
Dec 17 15:47:57 meet launch.sh[3205]: SLF4J: Defaulting to no-operation (NOP) logger implementation
Dec 17 15:47:57 meet launch.sh[3205]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
What version of Jibri is this? I can't reproduce it on latest stable. Does it log this in the actual jibri logs?
2020-12-17 21:29:57.124 INFO: [1] org.jitsi.jibri.Main.handleCommandLineArgs() Jibri run with args [--config, /etc/jitsi/jibri/config.json]
2020-12-17 21:29:57.212 INFO: [1] org.jitsi.jibri.Main.setupLegacyConfig() Checking legacy config file /etc/jitsi/jibri/config.json
2020-12-17 21:29:57.212 INFO: [1] org.jitsi.jibri.Main.setupLegacyConfig() Legacy config file /etc/jitsi/jibri/config.json doesn't exist
2020-12-17 21:29:57.765 INFO: [1] org.jitsi.jibri.webhooks.v1.JwtInfo.Companion.fromConfig() got jwtConfig: {}
2020-12-17 21:29:57.766 INFO: [1] org.jitsi.jibri.webhooks.v1.JwtInfo.Companion.fromConfig() Unable to create JwtInfo: com.typesafe.config.ConfigException$Missing: reference.conf @ jar:file:/opt/jitsi/jibri/jibri.jar!/reference.conf: 52: No configuration setting found for key 'signing-key-path'
2020-12-17 21:29:57.885 INFO: [1] org.jitsi.jibri.Main.main() Using port 8001 for internal HTTP API
2020-12-17 21:29:57.902 FINE: [18] org.jitsi.jibri.webhooks.v1.WebhookClient.invokeSuspend() Updating 0 subscribers of status
2020-12-17 21:29:58.165 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.updatePresence() Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing presence to connections
2020-12-17 21:29:58.170 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() Connecting to xmpp environment on meet.example.com with config XmppEnvironmentConfig(name=meet-prod-environment, xmppServerHosts=[meet.example.com], xmppDomain=meet.example.com, controlLogin=XmppCredentials(domain=auth.meet.example.com, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.meet.example.com, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.meet.example.com, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)
2020-12-17 21:29:58.171 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted
2020-12-17 21:29:58.186 INFO: [1] org.jitsi.jibri.Main.main() Using port 8002 for HTTP API
2020-12-17 21:29:58.206 WARNING: [27] org.jitsi.xmpp.mucclient.MucClient.log() Disabling certificate verification!
2020-12-17 21:29:58.440 INFO: [27] org.jitsi.xmpp.mucclient.MucClient.log() Connected.
2020-12-17 21:29:58.441 INFO: [27] org.jitsi.xmpp.mucclient.MucClient.log() Logging in.
2020-12-17 21:29:58.518 INFO: [27] org.jitsi.xmpp.mucclient.MucClient.log() Joined MUC: [email protected]
I don't know where this is coming from, but is it actually causing an issue? Usually this is harmless.