Issue regarding ports

[Naresh_R_1]

Hi Team,

Noticed that even user disconnects the session port is not getting released and also when we stop mcu server ports still listening what could be the issue

udp6       0      0 fe80::16da:e9ff:f:55906 :::*                                13145/woogeen_webrt
udp6       0      0 2a01:4f8:130:84ee:55945 :::*                                13648/woogeen_webrt
udp6       0      0 2a01:4f8:130:84ee:56036 :::*                                13145/woogeen_webrt
udp6       0      0 fe80::16da:e9ff:f:64320 :::*                                13145/woogeen_webrt
udp6       0      0 2a01:4f8:130:84ee:64542 :::*                                13648/woogeen_webrt
udp6       0      0 fe80::16da:e9ff:f:56373 :::*                                13145/woogeen_webrt
udp6       0      0 2a01:4f8:130:84ee:56532 :::*                                32266/woogeen_webrt
udp6       0      0 2a01:4f8:130:84ee:56623 :::*                                13145/woogeen_webrt
udp6       0      0 2a01:4f8:130:84ee:56653 :::*                                13145/woogeen_webrt
udp6       0      0 fe80::16da:e9ff:f:64984 :::*                                32266/woogeen_webrt
udp6       0      0 fe80::16da:e9ff:f:56811 :::*                                13648/woogeen_webrt
udp6       0      0 fe80::16da:e9ff:f:56995 :::*                                13648/woogeen_webrt
udp6       0      0 2a01:4f8:130:84ee:65376 :::*                                13145/woogeen_webrt
udp6       0      0 2a01:4f8:130:84ee:65480 :::*                                13145/woogeen_webrt
udp6       0      0 fe80::16da:e9ff:f:57410 :::*                                13145/woogeen_webrt

Thanks

Naresh

[Lei_Z_Intel1]

Is this the corner case? We can't reproduce this scenario. The webrtc agent should close the udp port after user disconnect. And all processes will exit after MCU stop. Can you please check whether these processes are still there after MCU stop? Zombie processes?

[Naresh_R_1]

Hi Lei,

Why this is happening  even i stopped completely the services there are so many woogen-webrtc listeners. how should we rectify this.

There are 0 zombie processes under top command

Thanks

Naresh

[Naresh_R_1]

Dear Lei,

Any update on the above issue even i stopped MCU still i can see woogen_webrtc ports listening and after that room failed attached is the logs for your debugging

Thanks

Naresh

[Lei_Z_Intel1]

For such issue, do you have reproduce steps to help us?

[Naresh_R_1]

Dear Lei,

Is there will be issue with machine performance? or OS?

Also Below is the Rabbitmq logs, after restarting webrtc agent works fine. any configuration which i have to make. is this with rabbitmq issue with the components

Does MCU works with latest version of Rabbitmq

=WARNING REPORT==== 10-Oct-2017::15:53:48 ===
closing AMQP connection <0.4420.2> (127.0.0.1:60107 -> 127.0.0.1:5672):
connection_closed_abruptly

=ERROR REPORT==== 10-Oct-2017::15:53:54 ===
connection <0.4306.2>, channel 3 - soft error:
{amqp_error,precondition_failed,"exchange 'woogeenRpc' in vhost '/' in use",
            'exchange.delete'}

=ERROR REPORT==== 10-Oct-2017::15:53:54 ===
connection <0.4322.2>, channel 1 - soft error:
{amqp_error,precondition_failed,"exchange 'woogeenRpc' in vhost '/' in use",
            'exchange.delete'}

=ERROR REPORT==== 10-Oct-2017::15:53:54 ===
connection <0.4349.2>, channel 1 - soft error:
{amqp_error,precondition_failed,"exchange 'woogeenRpc' in vhost '/' in use",
            'exchange.delete'}

=ERROR REPORT==== 10-Oct-2017::15:53:54 ===
connection <0.4349.2>, channel 3 - soft error:
{amqp_error,precondition_failed,"exchange 'woogeenRpc' in vhost '/' in use",
            'exchange.delete'}

=ERROR REPORT==== 9-Oct-2017::15:53:54 ===
connection <0.4349.2>, channel 5 - soft error:
{amqp_error,precondition_failed,
            "exchange 'woogeenMonitoring' in vhost '/' in use",
            'exchange.delete'}

=ERROR REPORT==== 10-Oct-2017::15:53:54 ===
connection <0.4322.2>, channel 5 - soft error:
{amqp_error,precondition_failed,
            "exchange 'woogeenMonitoring' in vhost '/' in use",
            'exchange.delete'}

Thanks

Naresh

[Naresh_R_1]

Hi Team,

Process ID and Webrtc ports are not getting released even after ending the call, and this room failure issue is coming, i have ended the process ID  and it worked.

Why system is not getting releasing ports and process even after end call or restart MCU

Thanks

Naresh

[Qiujiao_W_Intel]

Hi, Naresh,

We just logged to your system and did following actions:

1. ./bin/stop-all.sh to stop MCU and all webrtc related processes were terminated

2. ./bin/start-all.sh to start MCU

3. opened connection in chrome and it worked well

4. ./bin/stop-all.sh to stop MCU again and all webrtc related processes were terminated and not related ported were occupied with following command:

ps aux | grep woogeen

netstat -pan | grep woogeen

we'd like to double confirm with your actions, how do you stop MCU? using "kill -9 xxx" to terminate MCU process will not terminate sub-processes, if you want to terminate MCU not using ./bin/stop-all.sh, please try "kill xxx" or "killall node"

[Naresh_R_1]

Hi Qiujiao,

Do not stop services or ./bin/stop-all.sh i would like you start the services and check netstat -pan | grep woogeen please take a screenshot of it and now and go to the chrome browser and open the basic example app which i have shared you in email, open in multiple tabs or multiple machines refresh multiple times now check netstat -pan | grep woogeen and check the listening ports and pid

now close all the browsers and check again netstat -pan | grep woogeen on server there are several listening ports and pid still active after closing all basic apps also

as you mentioned stopping services and all the ports and pid getting release theres no issue with that

Thanks

Naresh

[Naresh_R_1]

Also please make sure its under Release 3.5.1 Thanks Naresh

[Mark_d_10]

We are also facing this issue.
After all sessions ended and disconnected, in the netstat output the woogeen_webrtc keeps the port on status LISTEN.

We are running version 3.5.1