Issue with Room

[Naresh_R_1]

Hi Lei,

After updating MCU v 3.2.1 we are facing issue with anyone of the room, not so frequently but sometimes. when restart mcu it works fine

below is the browser log

ERROR: publish failed: Timeout to make rpc to 166c3f2c-3313-358b-11c7-1c3dd51ab4f0.publish

and warning in server log as below

 WARN: WebRtcConnection - Bad source SSRC in RTCP feedback packet: 2412642309

Thanks

Naresh

[Naresh_R_1]

Dear Lei,

Below is the Rabbitmq logs, after restarting webrtc agent works fine. but above said errors are so frequent. any configuration which i have to make

=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]

Dear Team,

Below are the log generated in webrtc logs when room got failed at the server end, there was PID with same ID with listening to udp and tcp which is still listening even after mcu service stopped. killing the PID manually works with the room,

Please check the below logs and suggest whether its a configuration issue or connection issue from client listening ports are not releasing after users close the session also

2017-11-07 12:04:56.819  - INFO: ErizoJS - Connecting to rabbitMQ server...
2017-11-07 12:04:56.859  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2017-11-07 12:04:57.031  - INFO: ErizoJS - webrtc.cfe74c61-578d-48a8-bcd2-eb2324281d8c.47 as rpc server ready
2017-11-07 12:04:57.035  - INFO: ErizoJS - webrtc.cfe74c61-578d-48a8-bcd2-eb2324281d8c.47 as monitor ready
2017-11-08 08:34:44,871  - ERROR: dtls.SSL - Error parsing PKCS#12 file: ./cert/certificate.pfx
2017-11-08 08:37:27,936  - ERROR: NiceConnection - video - NICE Component 1 FAILED
2017-11-08 08:37:27,937  - ERROR: NiceConnection - Nice Failed, stopping ICE
2017-11-08 08:37:27,937  - INFO: WebRtcConnection - WebRtcConnection failed, stopping sending
2017-11-08 08:37:36.424  - INFO: Connections - Connection does NOT exist:01YThryxLxtGbe67AAB4-sub-999283918086632400
2017-11-08 08:37:36.427  - INFO: Connections - Connection does NOT exist:01YThryxLxtGbe67AAB4-sub-629088406810576300
2017-11-08 08:38:00,660  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 08:38:00,751  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 08:38:04,661  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 08:38:04,751  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 08:38:12,661  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 08:38:12,752  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 08:40:17,792  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 08:40:20,569  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 08:40:21,792  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 08:40:24,569  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 08:40:29,793  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 08:40:32,571  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 08:43:15.348  - INFO: Connections - Connection does NOT exist:qHwL13ma-zX_zII9AAB2-sub-629088406810576300
2017-11-08 08:43:15.353  - INFO: Connections - Connection does NOT exist:qHwL13ma-zX_zII9AAB2-sub-999283918086632400
2017-11-08 08:43:15.360  - INFO: Connections - Connection does NOT exist:qHwL13ma-zX_zII9AAB2-sub-71687981698485890
2017-11-08 08:44:13,161  - ERROR: NiceConnection - video - NICE Component 1 FAILED
2017-11-08 08:44:13,161  - ERROR: NiceConnection - Nice Failed, stopping ICE
2017-11-08 08:44:13,162  - INFO: WebRtcConnection - WebRtcConnection failed, stopping sending
2017-11-08 08:44:17,577  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 10:10:30,760  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 10:10:34,760  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 10:10:42,761  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 10:10:58,763  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 10:11:30,767  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 10:12:30,775  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 10:12:34.168  - INFO: Connections - Connection does NOT exist:t-NHnzPcaPx6xw8KAACY-sub-27486526172106670
2017-11-08 10:12:34.179  - INFO: Connections - Connection does NOT exist:t-NHnzPcaPx6xw8KAACY-sub-350608923591033200
2017-11-08 10:13:30,782  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 10:14:30,793  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 10:15:30,805  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 10:16:30,813  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 10:17:30,820  - WARN: Resender - video - Resending DTLS message to 1
2017-11-08 10:18:27,831  - ERROR: dtls.DtlsSocket - SSL error 1
2017-11-08 10:18:27,831  - WARN: dtls.DtlsSocketContext - DTLS Handshake Failure
2017-11-08 10:19:27,838  - ERROR: dtls.DtlsSocket - SSL error 1
2017-11-08 10:19:27,838  - WARN: dtls.DtlsSocketContext - DTLS Handshake Failure
2017-11-08 10:20:27,846  - ERROR: dtls.DtlsSocket - SSL error 1
2017-11-08 10:20:27,846  - WARN: dtls.DtlsSocketContext - DTLS Handshake Failure
2017-11-08 10:21:27,853  - ERROR: dtls.DtlsSocket - SSL error 1
2017-11-08 10:21:27,853  - WARN: dtls.DtlsSocketContext - DTLS Handshake Failure
2017-11-08 10:22:14.544  - INFO: Connections - Connection does NOT exist:ht3_cpwYgaG2JKEhAACX-sub-679644621389644300
2017-11-08 10:22:14.548  - INFO: Connections - Connection does NOT exist:350608923591033200@video.6f00fdb6-7043-0c92-f7e6-1f74d28abf9a.40
2017-11-08 10:47:10.988  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-59f5c46cbf51d46867e324fc-common
2017-11-08 10:47:11.000  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-463671081248402800
2017-11-08 10:47:11.007  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-658910981861916200
2017-11-08 10:47:11.007  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-287108797116228930
2017-11-08 10:47:11.018  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-752554934581144200
2017-11-08 10:47:11.018  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-133022535870556350
2017-11-08 10:47:11.027  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-126552441245772370
2017-11-08 10:47:11.028  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-421966852878216770
2017-11-08 10:47:11.028  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-881819209377684000
2017-11-08 10:47:11.032  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-494715558624080600
2017-11-08 10:47:11.032  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-27486526172106670
2017-11-08 10:47:11.033  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-350608923591033200
2017-11-08 10:47:11.033  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-220347176841252600
2017-11-08 10:47:11.033  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-6755085669197358
2017-11-08 10:47:11.033  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-995127503974902500
2017-11-08 10:47:11.034  - INFO: Connections - Connection does NOT exist:we4KVZSKr6Gt2dxRAAB--sub-529564916310580400
2017-11-08 11:00:53.314  - INFO: Connections - Connection does NOT exist:995127503974902500@video.6f00fdb6-7043-0c92-f7e6-1f74d28abf9a.40
2017-11-08 11:01:28.053  - INFO: Connections - Connection does NOT exist:buBGwasZB5aKQNlMAACa-sub-995127503974902500
2017-11-08 11:01:28.054  - INFO: Connections - Connection does NOT exist:buBGwasZB5aKQNlMAACa-sub-6755085669197358
2017-11-08 11:01:28.057  - INFO: Connections - Connection does NOT exist:buBGwasZB5aKQNlMAACa-sub-59f5c46cbf51d46867e324fc-common

Thanks

Naresh

[Naresh_R_1]

Dear Team,

Anything Update on this?

Thanks

Naresh

[Naresh_R_1]

Hi,

Internal TCP ports and process ID is note getting released even after disconnecting the session 

Thanks

Naresh

[Kiran_Raj_RA]

Hi, Team 

Any update on this

"Complete node is not getting crashed here, other rooms are working when the error comes with 1 room. restarting webrtc-agent works but other rooms also get affect when we restart webrtc-agent."

[Qiujiao_W_Intel]

We  are working on this issue and will try to fix it in next release

[Naresh_R_1]

When can we expect the next release

Thanks

Naresh

[Qiujiao_W_Intel]

current schedule is around the end of this quarter.

[Naresh_R_1]

Hi Qiujiao,

Thanks for the update.

Hope all the above issues fixed with the new release.

Scalability wise we have been configured high end intel Xeon 16 Core Processor with 64 GB Ram machine but it could not handle more than 20 users in forward mode. ports gets occupied and gets RPC connection error. 

Hope intel releases new version with above said issues fixed this time, also do we have release notes.

Thanks

Naresh

[Lei_Z_Intel1]

Hi, buddies

Just let you know the latest Intel CS for WebRTC 4.0 release schedule. It will be around middle of April. Thanks for all your patience!

Best wishes,

Zhai Lei

[Gopi_Krishna_P]

Hi buddies,

Can you please help me out this problem,i am unable to join the room 

[vc1 Release-v4.1]$ vi ./logs/woogeen-portal.stdout
2018-11-30 20:10:46.666  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-11-30 20:10:46.673  - INFO: Main - portal initializing as rpc client ok
2018-11-30 20:10:46.680  - INFO: Main - portal join cluster ok, with rpcID: portal-c5c5a10a6485e463aa83@192.168.75.27
2018-11-30 20:10:46.680  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-11-30 20:10:46.683  - INFO: Main - portal initializing as rpc server ok
2018-11-30 20:10:46.685  - INFO: Main - portal-c5c5a10a6485e463aa83@192.168.75.27 as monitor ready
2018-11-30 20:10:46.961  - INFO: Main - start socket.io server ok.
2018-11-30 20:11:48.619  - INFO: SocketIOServer - Login failed: Joining room failed
2018-11-30 20:16:39.114  - INFO: SocketIOServer - Login failed: Joining room failed
2018-12-03 11:47:13.330  - INFO: SocketIOServer - Login failed: Joining room failed
2018-12-03 11:47:56.897  - INFO: SocketIOServer - Login failed: Joining room failed
2018-12-03 12:53:58.712  - WARN: Main - Exiting on SIGTERM
2018-12-03 12:53:58.713  - INFO: LoadCollector - To stop load collector.

[Qiujiao_W_Intel]

Hi, Krishna, could you open a new thread on your issue and provide more information like what version do you use and how do you deploy MCU? Did you set unsupported video or audio codec in 3300/console, if so join room will also fail. Please provide whole MCU log for debugging.