jicofo
jicofo copied to clipboard
XMPP disconnected - skipping health check
Description
After upgrade to Version: 1.0-589-gfdfaf78-1 we have warnings about health-checks being skipped in the log.
And bandwidth Estimation stops to work.
Current behavior
Jicofo 2020-06-06 16:32:14.253 WARNING: [205] org.jitsi.jicofo.bridge.JvbDoctor.log() XMPP disconnected - skipping health check for: [email protected]/jvb7.meet.ffmuc.net Jicofo 2020-06-06 16:32:24.253 WARNING: [295] org.jitsi.jicofo.bridge.JvbDoctor.log() XMPP disconnected - skipping health check for: [email protected]/jvb7.meet.ffmuc.net Jicofo 2020-06-06 16:32:34.253 WARNING: [20] org.jitsi.jicofo.bridge.JvbDoctor.log() XMPP disconnected - skipping health check for: [email protected]/jvb7.meet.ffmuc.net Jicofo 2020-06-06 16:32:44.253 WARNING: [215] org.jitsi.jicofo.bridge.JvbDoctor.log() XMPP disconnected - skipping health check for: [email protected]/jvb7.meet.ffmuc.net Jicofo 2020-06-06 16:32:54.253 WARNING: [123] org.jitsi.jicofo.bridge.JvbDoctor.log() XMPP disconnected - skipping health check for: [email protected]/jvb7.meet.ffmuc.net Jicofo 2020-06-06 16:33:04.253 WARNING: [318] org.jitsi.jicofo.bridge.JvbDoctor.log() XMPP disconnected - skipping health check for: [email protected]/jvb7.meet.ffmuc.net Jicofo 2020-06-06 16:33:14.253 WARNING: [324] org.jitsi.jicofo.bridge.JvbDoctor.log() XMPP disconnected - skipping health check for: [email protected]/jvb7.meet.ffmuc.net
Expected Behavior
No warnings
Environment details
Videobridge2 Version: 2.1-236-gfe05f93f-1
We experienced the same issues, upgraded to 1.0.599 4 days ago. Same log messages, same issues with meeting quality.
EDIT: Maybe it has something to do with https://github.com/jitsi/jicofo/pull/539 ?
Having the same issues. Seems to be a commit between 6/3 and 6/11.
This log message is new, but it should not be a problem by itself. It actually indicates that there's a problem with XMPP connection. Are conferences working when this message is logged?
@paweldomas Yes, conferences are working. So this is not a known problem that you see on your end? Do you have recommendations to find the issue?
Isn't it looking up the XmppConnection directly? It's not clear how the connection could be null, given how it's getting/looking it up. Maybe the protocolProvider is just never registered somehow?
@paweldomas It appears the message has been there a while https://github.com/jitsi/jicofo/commit/1df7abb6724f29213d49dd22fd88120e2b2790ce#diff-9214cf301f8d2859506be57e6c3686e1R451 but the connection
is actually null
. Still investigating.
I suspect it might be related to the refactor mentioned above
okay I think the reason is because the registration listener was removed during the refactor and now it works only if the connection is ready on bundle startup and that is not guaranteed
https://github.com/jitsi/jicofo/pull/557