[jitsi-dev] Unrecoverable connectivity issues?


#1

Hi all,

On some servers where I run the Videobridge and Meet, a conference can be
set up successfully (all participants can see and hear each-other), but
will often fail within a minute or two. One or more of the participants
will see a frozen image and the "experiencing connectivity issues" error
message. This state does not recover.

Typically, I'd find something like this (see attachment) in the log when
the problem occurs.

Any thoughts on what's causing this, or how to analyze this issue?

Regards,

  Guus

log-snippet.txt (3.68 KB)


#2

Hi Guus,

Which JVB version are you running? We’ve recently fixed an issue in the bridge that was causing this (you want JVB >= 1055).

Regards,
George

···

On May 1, 2018, at 7:04 AM, Guus der Kinderen <guus.der.kinderen@gmail.com> wrote:

Hi all,

On some servers where I run the Videobridge and Meet, a conference can be set up successfully (all participants can see and hear each-other), but will often fail within a minute or two. One or more of the participants will see a frozen image and the "experiencing connectivity issues" error message. This state does not recover.

Typically, I'd find something like this (see attachment) in the log when the problem occurs.

Any thoughts on what's causing this, or how to analyze this issue?

Regards,

  Guus
<log-snippet.txt>_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#3

Hi George,

Thanks, that sounds like a likely candidate :slight_smile:

I'm finding it hard to deduce what version identifier I should compare this
with. I'm using this Maven artifact: 1.1-20180130.233151-31

When I look at the automated tags, the JVB today is just over 3000. That
makes 1055 not a 'recent fix'. Where should I look for "1055"?

Regards,

  Guus

···

On 1 May 2018 at 16:49, George Politis <gp@jitsi.org> wrote:

Hi Guus,

Which JVB version are you running? We’ve recently fixed an issue in the
bridge that was causing this (you want JVB >= 1055).

Regards,
George

> On May 1, 2018, at 7:04 AM, Guus der Kinderen < > guus.der.kinderen@gmail.com> wrote:
>
> Hi all,
>
> On some servers where I run the Videobridge and Meet, a conference can
be set up successfully (all participants can see and hear each-other), but
will often fail within a minute or two. One or more of the participants
will see a frozen image and the "experiencing connectivity issues" error
message. This state does not recover.
>
> Typically, I'd find something like this (see attachment) in the log when
the problem occurs.
>
> Any thoughts on what's causing this, or how to analyze this issue?
>
> Regards,
>
> Guus
> <log-snippet.txt>_______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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


#4

Hi Guus,

tags over 3000 are jitsi-meet_3004 which is the corresponding
jitsi-meet meta debian package, a combination of jitsi-meet+jicofo+jvb
versions (https://github.com/jitsi/jitsi-meet-debian-meta). The tag
you need is https://github.com/jitsi/jitsi-videobridge/releases/tag/1055.

Regards
damencho

···

On Tue, May 1, 2018 at 10:05 AM, Guus der Kinderen <guus.der.kinderen@gmail.com> wrote:

Hi George,

Thanks, that sounds like a likely candidate :slight_smile:

I'm finding it hard to deduce what version identifier I should compare this
with. I'm using this Maven artifact: 1.1-20180130.233151-31

When I look at the automated tags, the JVB today is just over 3000. That
makes 1055 not a 'recent fix'. Where should I look for "1055"?

Regards,

  Guus

On 1 May 2018 at 16:49, George Politis <gp@jitsi.org> wrote:

Hi Guus,

Which JVB version are you running? We’ve recently fixed an issue in the
bridge that was causing this (you want JVB >= 1055).

Regards,
George

> On May 1, 2018, at 7:04 AM, Guus der Kinderen >> > <guus.der.kinderen@gmail.com> wrote:
>
> Hi all,
>
> On some servers where I run the Videobridge and Meet, a conference can
> be set up successfully (all participants can see and hear each-other), but
> will often fail within a minute or two. One or more of the participants will
> see a frozen image and the "experiencing connectivity issues" error message.
> This state does not recover.
>
> Typically, I'd find something like this (see attachment) in the log when
> the problem occurs.
>
> Any thoughts on what's causing this, or how to analyze this issue?
>
> Regards,
>
> Guus
> <log-snippet.txt>_______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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

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


#5

Thanks!

···

On 1 May 2018 at 17:13, Damian Minkov <damencho@jitsi.org> wrote:

Hi Guus,

tags over 3000 are jitsi-meet_3004 which is the corresponding
jitsi-meet meta debian package, a combination of jitsi-meet+jicofo+jvb
versions (https://github.com/jitsi/jitsi-meet-debian-meta). The tag
you need is https://github.com/jitsi/jitsi-videobridge/releases/tag/1055.

Regards
damencho

On Tue, May 1, 2018 at 10:05 AM, Guus der Kinderen > <guus.der.kinderen@gmail.com> wrote:
> Hi George,
>
> Thanks, that sounds like a likely candidate :slight_smile:
>
> I'm finding it hard to deduce what version identifier I should compare
this
> with. I'm using this Maven artifact: 1.1-20180130.233151-31
>
> When I look at the automated tags, the JVB today is just over 3000. That
> makes 1055 not a 'recent fix'. Where should I look for "1055"?
>
> Regards,
>
> Guus
>
> On 1 May 2018 at 16:49, George Politis <gp@jitsi.org> wrote:
>>
>> Hi Guus,
>>
>> Which JVB version are you running? We’ve recently fixed an issue in the
>> bridge that was causing this (you want JVB >= 1055).
>>
>> Regards,
>> George
>>
>> > On May 1, 2018, at 7:04 AM, Guus der Kinderen > >> > <guus.der.kinderen@gmail.com> wrote:
>> >
>> > Hi all,
>> >
>> > On some servers where I run the Videobridge and Meet, a conference can
>> > be set up successfully (all participants can see and hear
each-other), but
>> > will often fail within a minute or two. One or more of the
participants will
>> > see a frozen image and the "experiencing connectivity issues" error
message.
>> > This state does not recover.
>> >
>> > Typically, I'd find something like this (see attachment) in the log
when
>> > the problem occurs.
>> >
>> > Any thoughts on what's causing this, or how to analyze this issue?
>> >
>> > Regards,
>> >
>> > Guus
>> > <log-snippet.txt>_______________________________________________
>> > dev mailing list
>> > dev@jitsi.org
>> > Unsubscribe instructions and other list options:
>> > http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>> _______________________________________________
>> dev mailing list
>> dev@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/dev
>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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


#6

For posterity: George was right (again). Updating the the latest code-base
dramatically improved the stability of the call.

I do wonder: I never observed the instability on meet.jit.si - even though
that presumably has been running in the past with the same problem. How
come that there, things seemed to be a lot more stable? In our environment
(AWS-hosted on generous spec'ed hosts), most calls would enter a state of
un-usability after a matter of minutes. What triggers the problem?

···

On 1 May 2018 at 17:20, Guus der Kinderen <guus.der.kinderen@gmail.com> wrote:

Thanks!

On 1 May 2018 at 17:13, Damian Minkov <damencho@jitsi.org> wrote:

Hi Guus,

tags over 3000 are jitsi-meet_3004 which is the corresponding
jitsi-meet meta debian package, a combination of jitsi-meet+jicofo+jvb
versions (https://github.com/jitsi/jitsi-meet-debian-meta). The tag
you need is https://github.com/jitsi/jitsi-videobridge/releases/tag/1055.

Regards
damencho

On Tue, May 1, 2018 at 10:05 AM, Guus der Kinderen >> <guus.der.kinderen@gmail.com> wrote:
> Hi George,
>
> Thanks, that sounds like a likely candidate :slight_smile:
>
> I'm finding it hard to deduce what version identifier I should compare
this
> with. I'm using this Maven artifact: 1.1-20180130.233151-31
>
> When I look at the automated tags, the JVB today is just over 3000. That
> makes 1055 not a 'recent fix'. Where should I look for "1055"?
>
> Regards,
>
> Guus
>
> On 1 May 2018 at 16:49, George Politis <gp@jitsi.org> wrote:
>>
>> Hi Guus,
>>
>> Which JVB version are you running? We’ve recently fixed an issue in the
>> bridge that was causing this (you want JVB >= 1055).
>>
>> Regards,
>> George
>>
>> > On May 1, 2018, at 7:04 AM, Guus der Kinderen >> >> > <guus.der.kinderen@gmail.com> wrote:
>> >
>> > Hi all,
>> >
>> > On some servers where I run the Videobridge and Meet, a conference
can
>> > be set up successfully (all participants can see and hear
each-other), but
>> > will often fail within a minute or two. One or more of the
participants will
>> > see a frozen image and the "experiencing connectivity issues" error
message.
>> > This state does not recover.
>> >
>> > Typically, I'd find something like this (see attachment) in the log
when
>> > the problem occurs.
>> >
>> > Any thoughts on what's causing this, or how to analyze this issue?
>> >
>> > Regards,
>> >
>> > Guus
>> > <log-snippet.txt>_______________________________________________
>> > dev mailing list
>> > dev@jitsi.org
>> > Unsubscribe instructions and other list options:
>> > http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>> _______________________________________________
>> dev mailing list
>> dev@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/dev
>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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


#7

Hi Guus,

Thanks for reporting back and for sharing the good news! I’m excited to hear that this change has had a noticeable (positive) impact on your deployments.

We've been running with this bug for months, at least (maybe over a year). It’s flown under the radar because the symptoms did not _appear_ as aggressive to compel an investigation. But lately Chrome started having these "connectivity issues" more often on our deployments. Pure chance? Maybe, maybe not; unfortunately, I can’t really tell what’s changed, which, means that I don’t have a good explanation for your valid question.

Best,
George

···

On May 7, 2018, at 8:05 AM, Guus der Kinderen <guus.der.kinderen@gmail.com> wrote:

For posterity: George was right (again). Updating the the latest code-base dramatically improved the stability of the call.

I do wonder: I never observed the instability on meet.jit.si <http://meet.jit.si/> - even though that presumably has been running in the past with the same problem. How come that there, things seemed to be a lot more stable? In our environment (AWS-hosted on generous spec'ed hosts), most calls would enter a state of un-usability after a matter of minutes. What triggers the problem?

On 1 May 2018 at 17:20, Guus der Kinderen <guus.der.kinderen@gmail.com <mailto:guus.der.kinderen@gmail.com>> wrote:
Thanks!

On 1 May 2018 at 17:13, Damian Minkov <damencho@jitsi.org <mailto:damencho@jitsi.org>> wrote:
Hi Guus,

tags over 3000 are jitsi-meet_3004 which is the corresponding
jitsi-meet meta debian package, a combination of jitsi-meet+jicofo+jvb
versions (https://github.com/jitsi/jitsi-meet-debian-meta). The tag
you need is https://github.com/jitsi/jitsi-videobridge/releases/tag/1055.

Regards
damencho

On Tue, May 1, 2018 at 10:05 AM, Guus der Kinderen > <guus.der.kinderen@gmail.com <mailto:guus.der.kinderen@gmail.com>> wrote:
> Hi George,
>
> Thanks, that sounds like a likely candidate :slight_smile:
>
> I'm finding it hard to deduce what version identifier I should compare this
> with. I'm using this Maven artifact: 1.1-20180130.233151-31
>
> When I look at the automated tags, the JVB today is just over 3000. That
> makes 1055 not a 'recent fix'. Where should I look for "1055"?
>
> Regards,
>
> Guus
>
> On 1 May 2018 at 16:49, George Politis <gp@jitsi.org <mailto:gp@jitsi.org>> wrote:
>>
>> Hi Guus,
>>
>> Which JVB version are you running? We’ve recently fixed an issue in the
>> bridge that was causing this (you want JVB >= 1055).
>>
>> Regards,
>> George
>>
>> > On May 1, 2018, at 7:04 AM, Guus der Kinderen > >> > <guus.der.kinderen@gmail.com <mailto:guus.der.kinderen@gmail.com>> wrote:
>> >
>> > Hi all,
>> >
>> > On some servers where I run the Videobridge and Meet, a conference can
>> > be set up successfully (all participants can see and hear each-other), but
>> > will often fail within a minute or two. One or more of the participants will
>> > see a frozen image and the "experiencing connectivity issues" error message.
>> > This state does not recover.
>> >
>> > Typically, I'd find something like this (see attachment) in the log when
>> > the problem occurs.
>> >
>> > Any thoughts on what's causing this, or how to analyze this issue?
>> >
>> > Regards,
>> >
>> > Guus
>> > <log-snippet.txt>_______________________________________________
>> > dev mailing list
>> > dev@jitsi.org <mailto:dev@jitsi.org>
>> > Unsubscribe instructions and other list options:
>> > http://lists.jitsi.org/mailman/listinfo/dev
>>
>>
>> _______________________________________________
>> dev mailing list
>> dev@jitsi.org <mailto:dev@jitsi.org>
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/dev
>
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org <mailto:dev@jitsi.org>
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

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

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