New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User is having connectivity issues - Grey video #3528

Open
SeveHo opened this Issue Oct 11, 2018 · 24 comments

Comments

Projects
None yet
8 participants
@SeveHo

SeveHo commented Oct 11, 2018

Description

We have recently faced the issue that the video turns grey with the error message User is having connectivity issues after some time and does not turn back to color mode even though the network seems to be fine and the video quality is perfect (but grey). This occurs in every p2p session but also sometimes in multi user mode.

We have also recognized that when the video stays grey in a p2p session and a third user joins the colored mode is back for all of the users. After the third users left the guy video is back immediately.

I've seen some discussions about this now but there are no ideas from the community on how to fix this yet (see: https://community.jitsi.org/t/user-is-having-connectivity-issues/15278).

Does someone of the devs have an idea on how to fix this?

Expected Behavior

Normal colored video when network is fine.

Possible Solution

Remove grey colored video on low bandwidth (preferred solution) or fix connectivity check so that the video turns back to colored mode when bandwidth is good enough.

Steps to reproduce

Open a conference on an environment with the latest stable packages. You will see the issue after a bit.

Environment details

  • jitsi-videobridge: 1087-1
  • jicofo: 1.0-437-1
  • jitsi-meet-web: 1.0.3036-1
@saghul

This comment has been minimized.

Member

saghul commented Oct 11, 2018

Do you get anything in the JS logs when this starts to happen?

@SeveHo

This comment has been minimized.

SeveHo commented Oct 11, 2018

Addition:
I was not able to reproduce this with a p2p session when both users are in the same network.

@SeveHo

This comment has been minimized.

SeveHo commented Oct 11, 2018

The JS log looks like this when it happens:
bildschirmfoto 2018-10-11 um 11 57 43

@saghul

This comment has been minimized.

Member

saghul commented Oct 11, 2018

Those logs are not useful, alas. Do you experience the same problem on meet.jit.si ? Any chance your server can be underdimensioned?

@SeveHo

This comment has been minimized.

SeveHo commented Oct 11, 2018

No the server is fine. CPU load at 20% max. RAM and Storage are fine as well. Same on meet.jit.si

@pdarcos

This comment has been minimized.

pdarcos commented Oct 11, 2018

I can confirm I also see this behavior quite often lately

@c526537207

This comment has been minimized.

c526537207 commented Oct 12, 2018

The bandwidth is too low

@paweldomas

This comment has been minimized.

Member

paweldomas commented Oct 12, 2018

I suspect that there can be a bug where in p2p mode we have two media stream for each video: one p2p and one jvb. When the jvb video is suspended it gets "frozen" and by mistake the app looks at this status instead of unfrozen video's (the p2p one would be unfrozen I guess). It would not explain why this could happen in non-p2p conference. Does it happen only in a p2p conference ?

@havid0707

This comment has been minimized.

havid0707 commented Oct 12, 2018

I also encountered this problem, basically reproduce every time in the case of P2p

@havid0707

This comment has been minimized.

havid0707 commented Oct 12, 2018

@saghul NO js error/warning log on console and backend.
meet.jit.si seems work well, my install component is:
Got xmpp version: Prosody(0.9.10,Linux)
Got focus version: JiCoFo(1.0.1.0-438,Linux)
Got videobridge version: JVB(0.1.1089,Linux)

The version of Jitsi meet is older

@havid0707

This comment has been minimized.

havid0707 commented Oct 12, 2018

Console Log for Caller / Callee
callee.log
caller.log

@havid0707

This comment has been minimized.

havid0707 commented Oct 12, 2018

jicofo.log
jvb.log

Jicofo Sip properties:
org.jitsi.jicofo.HEALTH_CHECK_INTERVAL=-1

Considering that so many people are experiencing this problem, can you help us to check it out, it is difficult for us to upgrade to the latest every time. @saghul

@AdilHoumadi

This comment has been minimized.

AdilHoumadi commented Oct 12, 2018

We are experiencing the same issue here!

@pdarcos

This comment has been minimized.

pdarcos commented Oct 12, 2018

The bug I've observed may be related to this issue since I get a lot of connectivity issues messages even when both clients are on same LAN. I also get the grey screen most of the time too.
Logs attached

Chrome_69.0.3497.100_high_sierra.log
Chrome_69.0.3497.100_ubuntu_18.04.1.log

@pdarcos

This comment has been minimized.

pdarcos commented Oct 13, 2018

It happens pretty much every time.

chrome_high_sierra.log

@paweldomas

This comment has been minimized.

Member

paweldomas commented Oct 15, 2018

I suspect that when .play() exception happens parts of the app are not initialised correctly

@paweldomas

This comment has been minimized.

Member

paweldomas commented Oct 15, 2018

but there's also this:
Logger.js:125 [modules/RTC/TraceablePeerConnection.js] <r._remoteTrackAdded>: TPC[1,p2p:false] remote track added: 3844631a-735e-4aa8-89b6-e778f2e38cb8-6 video Logger.js:125 [modules/RTC/TraceablePeerConnection.js] <r._remoteTrackAdded>: TPC[1,p2p:false] associated ssrc 92ec9eb4 2557751743 Logger.js:125 [modules/RTC/TraceablePeerConnection.js] <r._remoteTrackAdded>: TPC[1,p2p:false] remote track added: 3844631a-735e-4aa8-89b6-e778f2e38cb8-6 video Logger.js:125 [modules/RTC/TraceablePeerConnection.js] <r._remoteTrackAdded>: TPC[1,p2p:false] associated ssrc 92ec9eb4 2557751743 Logger.js:125 [modules/RTC/TraceablePeerConnection.js] <r._createRemoteTrack>: TPC[1,p2p:false] overwriting remote track! RemoteTrack[92ec9eb4, video, p2p: false] 92ec9eb4 video

@paweldomas

This comment has been minimized.

Member

paweldomas commented Oct 15, 2018

I think it's the remote track overwrite error. For some reason the peerconnection started firing "remote stream added" event twice and this confuses the app.

@pdarcos

This comment has been minimized.

pdarcos commented Oct 15, 2018

I agree @paweldomas

That remote track overwrite error shows up a lot and confuses everything

@paweldomas

This comment has been minimized.

Member

paweldomas commented Oct 15, 2018

@paweldomas

This comment has been minimized.

Member

paweldomas commented Oct 15, 2018

@damencho

This comment has been minimized.

Member

damencho commented Oct 16, 2018

@SeveHo @pdarcos @havid0707 can you update to jitsi-meet from unstable build 3378 it should contain the fix.

@SeveHo

This comment has been minimized.

SeveHo commented Oct 17, 2018

I'll try it out. Thank you @paweldomas @damencho!

@pdarcos

This comment has been minimized.

pdarcos commented Oct 20, 2018

Thanks @paweldomas

I've updated and the issue seems to be fixed (mostly). Every once in awhile I still get the grey screen and connectivity issues message but it happens much less often.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment