Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).
Announcements
Welcome to the Intel Community. If you get an answer you like, please mark it as an Accepted Solution to help others. Thank you!
For the latest information on Intel’s response to the Log4j/Log4Shell vulnerability, please see Intel-SA-00646

Joining room failed

youngY
Beginner
276 Views

Hi, everyone.

I've encountered one issue. I deployed the server on a computer with CentOs 7.6.The wrong message "Joining room failed."

In conference-XX.log:

2020-10-20 16:28:52.255 - DEBUG: WorkingNode - No native logger for reconfiguration
2020-10-20 16:28:52.282 - INFO: WorkingNode - pid: 4003
2020-10-20 16:28:52.282 - INFO: WorkingNode - Connecting to rabbitMQ server...
2020-10-20 16:28:52.290 - INFO: AmqpClient - Connecting to rabbitMQ server OK, options: { host: 'localhost', port: 5672 }
2020-10-20 16:28:52.440 - INFO: WorkingNode - conference-23f4c994b0321797c603@192.168.5.18_2 as rpc server ready
2020-10-20 16:28:52.441 - INFO: WorkingNode - conference-23f4c994b0321797c603@192.168.5.18_2 as monitor ready
2020-10-20 18:00:19.449 - ERROR: RoomController - new mix terminal failed. room_id: 5f8e8e18aac2c20d3895e317 reason: node not ready
2020-10-20 18:00:19.450 - ERROR: RoomController - init fail. view: common reason: node not ready
2020-10-20 18:00:19.450 - ERROR: Conference - roomController init failed. node not ready
2020-10-20 18:00:19.451 - ERROR: Conference - Init room failed, reason: roomController init failed. reason: node not ready
2020-10-20 18:00:19.452 - WARN: Conference - Participant 0Omxf6vb0jqYB3RfAAAE join room 5f8e8e18aac2c20d3895e317 failed, err: roomController init failed. reason: node not ready

Any help will be appreciated. Thanks.

0 Replies
Reply