[jitsi-dev] Colibri stats bug


#1

Hello everyone,

We recently experienced a bug with JVB stats. In fact, when we activate jvb stats for few hours we notice that the number of conferences is overestimated (70 conferences for 7 participants). I don't know if it's related but I think it's because of the clients timestamp because I get the warning below in jvb log:

JVB 2017-03-22 16:16:10.152 AVERTISSEMENT: [506] org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating remote clock because the timestamp point is invalid. ssrc=723617384, systemTime=Wed Mar 22 16:19:26 CET 2017, systemTimeMs=1490195966462, rtpTimestamp=1392872213, frequencyHz=0, streamHashCode=105612914

Have you every faced this problem ?

Regards,
Hamza KHAIT


#2

Hello,

···

On 22/03/2017 10:19, KHAIT Hamza - SG/SPSSI/CPII/DOSE/ET/PNE ANNUAIRE ET MESSAGERIE wrote:

Hello everyone,

We recently experienced a bug with JVB stats. In fact, when we activate
jvb stats for few hours we notice that the number of conferences is
overestimated (70 conferences for 7 participants). I don't know if it's
related but I think it's because of the clients timestamp because I get
the warning below in jvb log:

JVB 2017-03-22 16:16:10.152 AVERTISSEMENT: [506]
org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating
remote clock because the timestamp point is invalid. ssrc=723617384,
systemTime=Wed Mar 22 16:19:26 CET 2017, systemTimeMs=1490195966462,
rtpTimestamp=1392872213, frequencyHz=0, streamHashCode=105612914

I don't think those two are related. It could be that the statistics are wrong, or that there really are that many conferences open (e.g. they failed to expire).

Can you share the version of the bridge and the full statistics JSON that you think is problematic?

Boris


#3

Hi Boris,

The version of my JVB is 0.1.820. I only have this small part from the JSON stats (I've created a customised link) :

{
"conferences": 71,
"participants": 27,
"bit_rate_upload": 20713,
"bit_rate_download": 17739,
"current_timestamp": "2017-03-22 10:33:33.021"
}

I will update this issue with the new JSON stats once we notice this stranger behaviour next time.

Thanks for your answer.

Regards
Hamza

···

Le 22/03/2017 16:45, > Boris Grozev (par Internet, dépôt dev-bounces@jitsi.org) a écrit :

Hello,

On 22/03/2017 10:19, KHAIT Hamza - SG/SPSSI/CPII/DOSE/ET/PNE ANNUAIRE > ET MESSAGERIE wrote:

Hello everyone,

We recently experienced a bug with JVB stats. In fact, when we activate
jvb stats for few hours we notice that the number of conferences is
overestimated (70 conferences for 7 participants). I don't know if it's
related but I think it's because of the clients timestamp because I get
the warning below in jvb log:

JVB 2017-03-22 16:16:10.152 AVERTISSEMENT: [506]
org.jitsi.impl.neomedia.rtcp.RemoteClockEstimator.log() Not updating
remote clock because the timestamp point is invalid. ssrc=723617384,
systemTime=Wed Mar 22 16:19:26 CET 2017, systemTimeMs=1490195966462,
rtpTimestamp=1392872213, frequencyHz=0, streamHashCode=105612914

I don't think those two are related. It could be that the statistics
are wrong, or that there really are that many conferences open (e.g.
they failed to expire).

Can you share the version of the bridge and the full statistics JSON
that you think is problematic?

Boris

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev