[bug] Conferenceduration and speakerstats unavailable after upgrading Debian unstable to 1.0.4044-1

I am testing the unstable Debian packages. Last night I did the following upgrades:

[UPGRADE] jitsi-meet:amd64 2.0.4473-1 -> 2.0.4499-1
[UPGRADE] jitsi-meet-prosody:amd64 1.0.4027-1 -> 1.0.4044-1
[UPGRADE] jitsi-meet-turnserver:amd64 1.0.4027-1 -> 1.0.4044-1
[UPGRADE] jitsi-meet-web:amd64 1.0.4027-1 -> 1.0.4044-1
[UPGRADE] jitsi-meet-web-config:amd64 1.0.4027-1 -> 1.0.4044-1
[UPGRADE] jitsi-videobridge2:amd64 2.1-186-g29a8b927-1 -> 2.1-189-gfdd68a74-1

Now I see lots of severe errors in jicofo.log:

Jicofo 2020-04-23 08:12:34.698 SEVERE: [41] org.jitsi.impl.protocol.xmpp.OpSetSimpleCapsImpl.getFeatures().144 Failed to discover features for conferenceduration.XXX.social: XMPP error reply received from conferenceduration.XXX.social: XMPPError: service-unavailable - cancel
Jicofo 2020-04-23 08:12:34.700 SEVERE: [41] org.jitsi.impl.protocol.xmpp.OpSetSimpleCapsImpl.getFeatures().144 Failed to discover features for speakerstats.XXX.social: XMPP error reply received from speakerstats.XXX.social: XMPPError: service-unavailable - cancel

Is there something else I can do besides downgrading?

Turning debugging on in prosody, I see the following related messages:

Apr 23 10:13:34 c2s55d05cc40c70 debug   Received[c2s]: <iq type='get' to='conferenceduration.XXX.social' id='08VJq-112124'>
Apr 23 10:13:34 conference.XXX.social:muc_domain_mapper    debug   No room name provided so rewriting only host 'to' conferenceduration.XXX.social
Apr 23 10:13:34 conference.XXX.social:muc_domain_mapper    debug   Rewrote to conference.XXX.social
Apr 23 10:13:34 conference.XXX.social:muc_domain_mapper    debug   No need to rewrite focus@auth.XXX.social/focus1468373849459846 (not from the MUC host) 08VJq-112124, conferenceduration.XXX.social
Apr 23 10:13:34 stanzarouter    debug   Unhandled c2s stanza: iq; xmlns=http://jabber.org/protocol/disco#info
Apr 23 10:13:34 c2s55d05cc40c70 debug   Sending[c2s]: <iq type='error' id='08VJq-112124' to='conferenceduration.XXX.social' from='conference.XXX.social'>
Apr 23 10:13:34 c2s55d05cc40c70 debug   Received[c2s]: <iq type='get' to='speakerstats.XXX.social' id='08VJq-112128'>
Apr 23 10:13:34 conference.XXX.social:muc_domain_mapper    debug   No need to rewrite out 'to' speakerstats.XXX.social
Apr 23 10:13:34 conference.XXX.social:muc_domain_mapper    debug   No need to rewrite focus@auth.XXX.social/focus1468373849459846 (not from the MUC host) 08VJq-112128, <nil>
Apr 23 10:13:34 stanzarouter    debug   Unhandled c2s stanza: iq; xmlns=http://jabber.org/protocol/disco#info
Apr 23 10:13:34 c2s55d05cc40c70 debug   Sending[c2s]: <iq type='error' id='08VJq-112128' to='focus@auth.XXX.social/focus1468373849459846' from='speakerstats.XXX.social'>

Hence this might be inrelated to the upgrade and maybe due to activating statistics via MUC (incorrectly)?

Update: Even though this is marked as SEVERE in jicofo, the only noticable side effect seems to be that there is only speaker time listed for the moderator.

Same here, noticed it after an update today (running current GIT, built manually). Not sure if it could be related to https://github.com/jitsi/jicofo/commit/ea7022b9ea6840defcae58d67c49aa4c204828a7

Yep that seems related (But I am at no means familiar with the code). Was about to open an issue on github, but there is a message "Before posting, please make sure you check https://community.jitsi.org " that seems to indicate that it is enough to post it here.

Is there a common procedure for marking this thread as a bug report?

Moved this to “Developers” in the hope that it gains more attention there.

Issue opened : https://github.com/jitsi/jicofo/issues/490

Thanks a lot.

It’s safe to ignore this error.

Well, in that case the tag SEVERE might not be the right one.
Still the speaker stastics shown seem wrong now.

1 Like

@Pawel_Domas Can you elaborate on the why it’s safe to ignore? Any plan to change it’s level to Info or something else but more relevant?

I don’t know exactly why “speakerstats” and “conferenceduration” do not respond to feature discovery query, but it’s not used for anything in Jicofo, so can be ignored. It’s just that Jicofo gets a list of all XMPP components configured on the domain and tries to check each one in order to see if it’s a videobridge or something else it could make use of.

And yes the logging level probably can be lowered to a warning.

I might have missed something (or installed an upgrade). Nevertheless the duration and the stats work again, iif I am not mistaken. Hence this can be considered bogus or solved.