- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
如附件截屏和webrtc-internals dump所示。在有的网络环境中会有这样的问题。在另外的网络环境中则正常。
此问题在3.4及以前版本中从未出现过。
- Tags:
- HTML5
- JavaScript*
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
请告知出现问题的网络拓扑结构,确定同样的网络环境3.4完全没问题3.5有问题吗?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Qiujiao W. (Intel) wrote:
请告知出现问题的网络拓扑结构,确定同样的网络环境3.4完全没问题3.5有问题吗?
服务器有公网IP,直接对外,已经把各个agent.toml的ip_address的值都配置成了公网IP
我在同一台服务器上试过3.4和3.5,十分确定3.4完全没有这个问题,只有3.5有问题
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
测试结果更新:
现在发现,也不全是网络环境的原因,我的桌面Chrome连不上,换成桌面Safari或手机Chrome通过WiFi就能连上,而桌面Chrome换成手机热点的移动网络也能连上。
所以我怀疑是客户端发起请求的时序不同造成的,服务器可能存在race condition的bug。
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3.5 出现 extras/basic_example rest 接口 只有获取 token join 无返回结果
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
谢谢反馈,我们这边会先尝试重现问题,请关注后续进展
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
刚下载安装了最新的3.5.1版本,这个问题依旧。
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
请告知出现问题的网络具体环境以及能够重现这个问题的步骤,同时请将出问题时server端的log文件上传方便定位问题
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
网络环境和上面说的一样。
服务器的woogeen-portal.stdout记录了这样的错误:
2017-12-08 11:46:43.383 - ERROR: V10Client - soac failed: Session 341045591082074430 does NOT exist
2017-12-08 11:46:43.386 - ERROR: V10Client - soac failed: Session 341045591082074430 does NOT exist
2017-12-08 11:46:43.387 - ERROR: V10Client - soac failed: Session 341045591082074430 does NOT exist
2017-12-08 11:46:43.387 - ERROR: V10Client - soac failed: Session 341045591082074430 does NOT exist
2017-12-08 11:46:43.387 - ERROR: V10Client - soac failed: Session 341045591082074430 does NOT exist
2017-12-08 11:46:43.387 - ERROR: V10Client - soac failed: Session 341045591082074430 does NOT exist
2017-12-08 11:46:43.387 - ERROR: V10Client - soac failed: Session 341045591082074430 does NOT exist
2017-12-08 11:46:43.388 - ERROR: V10Client - soac failed: Session 341045591082074430 does NOT exist
2017-12-08 11:46:43.388 - ERROR: V10Client - soac failed: Session 341045591082074430 does NOT exist
2017-12-08 11:46:43.389 - ERROR: V10Client - soac failed: Session 341045591082074430 does NOT exist
2017-12-08 11:46:43.389 - ERROR: V10Client - soac failed: Session 341045591082074430 does NOT exist
2017-12-08 11:46:43.389 - ERROR: V10Client - soac failed: Session 341045591082074430 does NOT exist
2017-12-08 11:46:43.751 - ERROR: V10Client - soac failed: Session 473916352421047900 does NOT exist
2017-12-08 11:46:43.752 - ERROR: V10Client - soac failed: Session 473916352421047900 does NOT exist
2017-12-08 11:46:43.752 - ERROR: V10Client - soac failed: Session 473916352421047900 does NOT exist
2017-12-08 11:46:43.754 - ERROR: V10Client - soac failed: Session 473916352421047900 does NOT exist
2017-12-08 11:46:43.755 - ERROR: V10Client - soac failed: Session 473916352421047900 does NOT exist
2017-12-08 11:46:43.757 - ERROR: V10Client - soac failed: Session 473916352421047900 does NOT exist
2017-12-08 11:46:43.758 - ERROR: V10Client - soac failed: Session 473916352421047900 does NOT exist
2017-12-08 11:46:43.759 - ERROR: V10Client - soac failed: Session 473916352421047900 does NOT exist
2017-12-08 11:46:43.759 - ERROR: V10Client - soac failed: Session 473916352421047900 does NOT exist
2017-12-08 11:46:43.760 - ERROR: V10Client - soac failed: Session 473916352421047900 does NOT exist
2017-12-08 11:46:43.766 - ERROR: V10Client - soac failed: Session 473916352421047900 does NOT exist
2017-12-08 11:46:43.769 - ERROR: V10Client - soac failed: Session 473916352421047900 does NOT exist
2017-12-08 14:22:38.245 - ERROR: V10Client - subscribe failed: Target video stream does NOT satisfy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
我也遇到了一模一样的问题。
先看客户端截图:
相同网络、相同机器,Google Chrome 62 次次报错(可复现),而 Safari 11 从不报错。
换到 4G 网络,同一台机器,情况相同,因此大概率上与网络无关。
相同网络,多台其他机器,相同浏览器,都不会报这个错。
RTC 服务器端 woogeen-portal.stdout:
2017-12-11 15:04:24.244 - ERROR: V10Client - soac failed: Session 35784494993223336 does NOT exist
2017-12-11 15:04:24.244 - ERROR: V10Client - soac failed: Session 35784494993223336 does NOT exist
2017-12-11 15:04:24.245 - ERROR: V10Client - soac failed: Session 35784494993223336 does NOT exist
2017-12-11 15:04:24.245 - ERROR: V10Client - soac failed: Session 35784494993223336 does NOT exist
2017-12-11 15:04:24.245 - ERROR: V10Client - soac failed: Session 35784494993223336 does NOT exist
2017-12-11 15:04:24.245 - ERROR: V10Client - soac failed: Session 35784494993223336 does NOT exist
2017-12-11 15:04:24.245 - ERROR: V10Client - soac failed: Session 35784494993223336 does NOT exist
2017-12-11 15:04:24.986 - ERROR: V10Client - soac failed: Session 659584176648987400 does NOT exist
2017-12-11 15:04:24.987 - ERROR: V10Client - soac failed: Session 659584176648987400 does NOT exist
2017-12-11 15:04:24.987 - ERROR: V10Client - soac failed: Session 659584176648987400 does NOT exist
2017-12-11 15:04:55.889 - ERROR: V10Client - soac failed: Session 562968792825841340 does NOT exist
2017-12-11 15:04:55.890 - ERROR: V10Client - soac failed: Session 562968792825841340 does NOT exist
2017-12-11 15:04:55.892 - ERROR: V10Client - soac failed: Session 562968792825841340 does NOT exist
2017-12-11 15:04:55.893 - ERROR: V10Client - soac failed: Session 562968792825841340 does NOT exist
2017-12-11 15:04:55.895 - ERROR: V10Client - soac failed: Session 562968792825841340 does NOT exist
2017-12-11 15:04:55.961 - ERROR: V10Client - soac failed: Session 562968792825841340 does NOT exist
2017-12-11 15:04:55.963 - ERROR: V10Client - soac failed: Session 562968792825841340 does NOT exist
2017-12-11 15:04:55.963 - ERROR: V10Client - soac failed: Session 562968792825841340 does NOT exist
2017-12-11 15:04:56.214 - ERROR: V10Client - soac failed: Session 536149451643521900 does NOT exist
2017-12-11 15:04:56.214 - ERROR: V10Client - soac failed: Session 536149451643521900 does NOT exist
2017-12-11 15:04:56.216 - ERROR: V10Client - soac failed: Session 536149451643521900 does NOT exist
2017-12-11 15:04:56.217 - ERROR: V10Client - soac failed: Session 536149451643521900 does NOT exist
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, zunlong, 你也是用的3.5.1的包出现的这个问题吗?MCU的部署是在物理机,虚拟机,AWS或者其他云平台?还是本地通过docker启动的呢?另外你们有使用自己的证书替换到webrtc_agent目录吗
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Qiujiao. 是 3.5.1,部署在阿里云和腾讯云上,均出现这个问题。有生成证书替换到 portal/cert 目录。
这种报错不是每个客户端都遇到,我再描述一下遇到的情况:同一个网络下,我这每个浏览器都不会报错,而我的同事用 Chrome 时永远报错,换成 Safari 就没事了,换成其他网络情况相同。
也就是说,我身边的案例中,发生这种情况的客户端很随机,而一旦发生,该客户端就会确定地持续报错。
客户端报错信息非常明确,在 sub 和 pub 时都会报 "Ice procedure failed".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
你跟同事都是在同一个网络环境下,然后你机器上所有浏览器访问都没问题,但是你同事用chrome有问题,safari没问题是吗?请问你跟同事使用的系统都是ios吗?另外你同事使用的chrome版本跟你的chrome版本一致吗,同事出问题的chrome版本是多少?
你身边的案例发生这种情况的客户端很随机,一旦发生该客户端就会确定地持续报错,这个报错的客户端第一次连接就报错吗?还是说一开始出现工作正常但是后面突然报错的?报错的都是在浏览器上出现的吗?android或者ios客户端应用进行连接的时候有报错吗?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
另外同样的环境3.5之前的MCU版本有问题吗
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
我和同事使用的系统都是 macOS High Sierra,Chrome 版本相同。上次贴的图是 Chrome 62,我行,他不行。现在是 Chrome 63,我还行,他还是不行。
这个报错的客户端是第一次连接就报错,在浏览器的 console 上能看到 sub 和 pub 均报相同的错误。我身边的案例里,暂时没有发现 Android 或 iOS 浏览器报类似错误。
在 3.4 和 3.4 update 1 时从未遇到过这个错误。
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Zunlong, 你同事那边有用IPv6的网络吗?请在server端清掉之前的log,然后打开以下log level,重启MCU,然后在你同事机器上重现下Ice procedure failed问题,然后提供下MCU 的log以及chrome上webrtc_internals的dump文件,谢谢:
1. 将conference_agent/log4js_configuration.json文件中的log级别设置成DEBUG:
“Conference:"DEBUG",
"AccessController": "DEBUG"
2. 将webrtc_agent/log4js_configuration.json文件中的log级别设置成DEBUG:
"WebrtcNode": "DEBUG",
"WrtcConnection": "DEBUG"
3. 将webrtc_agent/log4cxx.properties文件中的log级别设置成DEBUG:
log4j.logger.WebRtcConnection=DEBUG
log4j.logger.NiceConnection=DEBUG
4. 在起webrtc agent的terminal上设置以下环境变量:
export G_MESSAGES_DEBUG=all
export NICE_DEBUG=all
然后重启webrtc以及conference agent,请将收集到的mcu log以及webrtc_internal文件上传
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
我也遇到了同样的问题..持续关注中..环境用的阿里云的服务器+3.5.1webrtc+win10 chrome63.0.3239.108(正式版本) (64 位)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sean,谢谢你提供的信息,这个问题我们最近会出一个版本进行解决,请关注后面的版本发布
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3.5.2 基本上修复了这个问题,至少我们这里再没有遇到过 ICE 报错。
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page