Videobridge missing jetty logs

I was completely baffled when trying to figure out why my colibri websocket connections were being rejected, and there were no helpful errors in the logs. It took me a while to catch on that some of the logs aren’t being captured because of this:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See for further details.

I finally started seeing more useful logs from Jetty when I manually downloaded the jar for sjf4j-simple.

cd /usr/share/jitsi-videobridge/lib
systemctl restart jitsi-videobridge2.service

(The now visible logs revealed that Jetty now rejects connections if the hostname contains _. AFAIK, this was not the case in previous versions of jvb. But that’s a separate issue).

I’m testing this on Ubuntu 18.04 using jitsi-videobridge2=2.2-43-gce94dbb2-1 (associated with latest 2.0.7830 stable release)

Question: Is this a known issue, i.e. missing slf4j bindings for logging? How best do I address this?

@Jonathan_Lennox @Boris_Grozev can we just add that dependency so we see it or better maybe slf4j-jdk14 so it routes to java logging? WDYT?

@shawn can you test do you see the logs if you replace slf4j-simple with slf4j-jdk14?

yup. that works too.

O we already do that for jicofo, maybe we can add it and to jvb dependencies.

Let’s see the PR testing for feat: Routes logs from slf4j to java logging. by damencho · Pull Request #1953 · jitsi/jitsi-videobridge · GitHub

1 Like