Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).
Announcements
Intel Customer Support will be observing the Martin Luther King holiday on Monday, Jan. 17, and will return on Tues. Jan. 18.
For the latest information on Intel’s response to the Log4j/Log4Shell vulnerability, please see Intel-SA-00646
1135 Discussions

Ports are not releasing after executing "bin/stop-all.sh" script

Chandramouli_P
Beginner
118 Views

Hello,

After executing "sudo bin/stop-all.sh" commands, ports are not releasing automatically that is used by MCU application. When we restart the MCU by executing "sudo bin/start-all.sh", it is throwing the errors that ports are already in use. To resolve this, we are restarting the server every time or kill the processes manually each and every time. I believe that this is the bad practice. How to avoid this scenario?

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

Thank you.

Best Regards,
Chandramouli.

0 Kudos
7 Replies
Chandramouli_P
Beginner
118 Views

Hello,

Any update would be appreciated. Thank you.

Best Regards,
Chandramouli.

Chandramouli_P
Beginner
118 Views

Hello,

Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

Lei_Z_Intel1
Employee
118 Views

Which MCU version are you using?

Chandramouli_P
Beginner
118 Views

Hello Lei Zhai,

We wish you a very happy new year. We are using Intel CS for WebRTC v4.1. Any help would be appreciated.

Thank you.

Best Regards,
Chandramouli.

Qiujiao_W_Intel
Employee
118 Views

Hi, Chandramouli, can you reproduce this issue? If yes, could you provide us the log file of portal? This situation may happen when portal process doesn't work well.

Chandramouli_P
Beginner
118 Views

Hello Qiujiao,

I faced this issue when we setup MCU along with MongoDB, RabbitMQ together in a single server. Now, I setup MCU and MongoDB in two different machines. Now, I am not getting this issue.

Thank you.

Best Regards,
Chandramouli.

Qiujiao_W_Intel
Employee
118 Views

Umm, that does not make sense. Another possibility for this issue may be that related log files have been removed before stopping all modules, since we need refer to related process id in log file.

Reply