Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
308 Views

Error: Joining room failed (v.4.3), when enabling hardware acceleration

Jump to solution

Hello,

Please find the environment:

Operating System: Ubuntu 18.04 Server and CentOS 7.x
Linux Kernel Version: 4.15.0-69-generic
Browser: Google Chrome Version 77.0.3865.90 (Official Build) (64-bit)
Intel CS for WebRTC Version: 4.3
Firewall: No firewall and all ports are opened

We successfully deployed previous versions of Intel CS for WebRTC framework earlier in various environments. When we are trying to install v.4.3, we are getting "Joining room failed" error. We tried with default certificate, SSL certificated which is generated with OpenSSL, and also with purchased certificate. I also tried with AWS environment and in our LAN server also. But, getting the same error, when I am executing the https://1.2.3.4:3004 URL in the browser. I am not getting any errors in the log files also, except the below error.

Please find the below error:
Failed to load resource: net::ERR_CONNECTION_CLOSED
Failed to load resource: the server responded with a status of 404 ()
WebSocket connection to 'wss://1.2.3.4:8080/socket.io/?EIO=3&transport=websocket&sid=cw4bbpFEaMcrKI4UAAAA' failed: WebSocket is closed before the connection is established.
server connection failed: Error: Joining room failed

Any help would be really appreciated.

Thank you.

Best Regards,
Chandramouli.
 

Tags (2)
0 Kudos

Accepted Solutions
Highlighted
Employee
329 Views

Hi,

Have you run `video_agent/init.sh --hardware` after `install_deps.sh --hardware`?

View solution in original post

0 Kudos
33 Replies
Highlighted
Beginner
231 Views

Hello Team,

As this issue is a blocking issue, request you to help us to resolve the problem. Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Highlighted
New Contributor I
231 Views

try to create a new room from console and joining using the https://1.2.3.4:3004/?room=RoomID.

Also, have you updated service id and key under basic example folder sampleserver.js file

 

Thanks

Naresh

0 Kudos
Highlighted
Beginner
231 Views

Hello,

In fact, we no need to update the service id in sampleserver.js file. Because, it is generating the same service id, which is already existing in the sampleserver.js file.

What I noticed is, everything is working fine without hardware acceleration. After installing required dependencies, and enable hardware acceleration, we are getting the above error. Have you tried by enabling the hardware acceleration?

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Highlighted
Beginner
231 Views

Hello Team,

Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Highlighted
Beginner
231 Views

I had problems with this. 

1. Download already compiled 4.2.1 MCU.

2. Do an init-all.sh and DO NOT CHANGE the RabbitMQ password on init. (i assume, you have it default, as i had. If you change it, everything will not work, don't know why). Get the service id and key.

3. After init, i had few problems, the modules had crashed for some reason. To fix this, i had to do install_ffmpeg.sh in following folders: analytics_agent, audio_agent, recording_agent, streaming_agent, video_agent.

4. After this, i installed install_openh264.sh in video_agent folder.

5. start-all.sh, go to console and check the Room ID. Enter https://1.2.3.4:3004/?room=RoomID. 

Also, you may have errors, because you are accessing self signed certificate. Make your own certificate, do an ./initcert.js in each folder of module. Use https://domain:3004/, instead of https://IP:3004/.

0 Kudos
Highlighted
Beginner
231 Views

Hello Team,

I can strongly say that the issue is coming, when we enable hardware acceleration. Anybody done with hardware acceleration? Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Highlighted
Beginner
231 Views

Hello Team,

Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Highlighted
Beginner
231 Views

Hello Team,

Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Highlighted
Employee
231 Views

Hi, Chandramouli.

Hardware acceleration should not brought room connection issue.  Could you please provide more detail information e.g reproduce steps ?

 

Thanks

Yanbin

0 Kudos
Highlighted
Beginner
231 Views

Hello Yanbin,

Good morning and thank you for your reply. Please find the below steps that I followed:

Operating System: Ubuntu 18.04 Server (Minimal version - command line only) and CentOS 7.x (Minimal version - command line only)
Linux Kernel Version: 5.3.6
Intel CS for WebRTC Version: 4.2.1
Firewall: No firewall and all ports are opened
Browser: Google Chrome Version 77.0.3865.90 (Official Build) (64-bit)

Steps:
1) Installed updates and essential common development libraries
2) Installed cmake
3) Installed GmmLib (Intel Graphics Memory Management Library)
4) Installed intel-igc-core, intel-igc-opencl, intel-ocloc
5) Installed WayLand
6) Installed libx11-dev libxext6 libxext-dev libxfixes3 libxfixes-dev libgl1-mesa-glx libgl1-mesa-dev autoconf libtool libdrm-dev xorg xorg-dev openbox
7) Installed Linux VAAPI Video Stack Basic Packages (libx264-dev, libx265-dev)
8) Installed LibDRM
9) Installed 2D Driver(xf86-video-intel)
10) Installed libva
11) Installed Libva-Utils
12) Installed autoconf libtool libdrm-dev xorg xorg-dev openbox libx11-dev libgl1-mesa-glx libgl1-mesa-dev
13) Installed VAAPI backend driver (Intel Media Driver for VAAPI is a new VA-API (Video Acceleration API))
14) Set LIBVA_DRIVERS_PATH, and LIBVA_DRIVER_NAME in /etc/environment file
15) Installed Intel Media SDK
16) Installed Intel OpenVINO toolkit
17) Installed and run OpenVINO demo examples
18) Installed RabbitMQ, and MongoDB
19) Installed NodeJS 8.x
19) Download and unzip CS_WebRTC_Conference_Server_MCU.v4.2.1.Ubuntu.tgz
20) Installed dependencies in video_agent folder (./install_deps.sh --hardware)
21) ./compile_ffmpeg_with_libfdkaac.sh in audio_agent folder
22) cp ffmpeg_libfdkaac_lib/* lib/
23) Installed nasm, yasm packages
24) ./compile_svtHevcEncoder.sh in video_agent folder
25) Changed to values of "hardwareAccelerated" and "enableBetterHEVCQuality" to "true" in video_agent/agent.toml file
26) sudo bin/init-all.sh [--deps] --hardware
27) sudo bin/start-all.sh

These are the steps that I followed. Please correct me, If I installed any unnecessary additional packages that causes to above error (Joining room failed)  that I mentioned.

Thank you

Best Regards,
Chandramouli.

0 Kudos
Highlighted
Employee
231 Views

Hi,

It seems that the room failed to initialize. Can you provide the logs in "logs" directory when hardware mode is on?

 

0 Kudos
Highlighted
Beginner
231 Views

Hello,

Please find the complete log at the below URL:

https://pastebin.com/uajEvjAg

Hence, request you to help us to resolve the issue.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Highlighted
Beginner
231 Views

Hello Team,

Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Highlighted
Beginner
231 Views

Hello Li,

Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Highlighted
Beginner
231 Views

Hello Team,

Any update would be appreciated.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Highlighted
Beginner
231 Views

Hello Team,

Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Highlighted
Beginner
231 Views

Hello Team,

Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

0 Kudos
Highlighted
Employee
231 Views

Hi, the paste logs are not complete.

Can you provide the full content of conference-xxx@xxx_0.log and portal.stdout when the join failed?

0 Kudos
Highlighted
Beginner
231 Views

Hello Li,

Thank you for your reply. Please find the logs that you asked in the below link:

https://pastebin.com/njXkvx5x

If you need any other information, please let me know. I look forward to hearing from you.

Thank you.

Best Regards,
Chandramouli.

0 Kudos