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

Unable to connect to Intel CS 3.5.2 from Chrome

Dear Intel CS Team,

I have been using my intel cs for webrtc 3.5.2 for couple of months along with recording without any issues. Suddenly I am facing a problem, as mentioned in the screenshot. After few minutes or first session suddenly it stops subscribing / publishing at client end. I need to manually restart the server after some time for next connection and issue is repeated. Below is my configuration

Intel CS for Webrtc Server: 3.5.2

Server: CentOS Linux release 7.4.1708 (Core)

Google Chrome Version 67.0.3396.99 (Official Build) (64-bit)

I have also attached server logs. Any idea what is going on wrong.. Please help. 

Thank you.

Best Regards,
Bipin Kesharwani

Tags (2)
0 Kudos
4 Replies
Highlighted
66 Views

Here is restart log.. It seems nuve is getting terminated due to some error.

[root@vc Release-v3.5.2]# bin/restart-all.sh
no nuve to stop
no cluster-manager to stop
no audio-agent to stop
stopping conference-agent.
stopping recording-agent
stopping sip-agent.
stopping streaming-agent
stopping video-agent.
stopping webrtc-agent
stopping portal
stopping sip-portal
stopping app
starting nuve, stdout -> /root/Release-v3.5.2/logs/woogeen-nuve.stdout
starting cluster-manager, stdout -> /root/Release-v3.5.2/logs/woogeen-cluster-manager.stdout
2018-07-31 14:32:48.244  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-07-31 14:32:48.280  - INFO: Main - Cluster manager up! id: 706410773
2018-07-31 14:32:48.283  - INFO: ClusterManager - Run as candidate.
2018-07-31 14:32:48.491  - INFO: ClusterManager - Run as master.
2018-07-31 14:32:48.511  - INFO: ClusterManager - Cluster manager is in service as master!
starting audio-agent, stdout -> /root/Release-v3.5.2/logs/woogeen-audio-agent.stdout
2018-07-31 14:32:49.263  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-07-31 14:32:49.304  - INFO: ErizoAgent - audio agent join cluster ok.
2018-07-31 14:32:49.383  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-07-31 14:32:49.397  - INFO: ErizoAgent - as rpc server ok.
2018-07-31 14:32:49.403  - INFO: ErizoAgent - as monitoring target ok.
starting conference-agent, stdout -> /root/Release-v3.5.2/logs/woogeen-conference-agent.stdout
2018-07-31 14:32:50.242  - INFO: ErizoAgent - No loader.json found.
2018-07-31 14:32:50.368  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-07-31 14:32:50.416  - INFO: ErizoAgent - conference agent join cluster ok.
2018-07-31 14:32:50.443  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-07-31 14:32:50.461  - INFO: ErizoAgent - as rpc server ok.
2018-07-31 14:32:50.471  - INFO: ErizoAgent - as monitoring target ok.
starting recording-agent, stdout -> /root/Release-v3.5.2/logs/woogeen-recording-agent.stdout
2018-07-31 14:32:51.662  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-07-31 14:32:51.694  - INFO: ErizoAgent - recording agent join cluster ok.
2018-07-31 14:32:51.715  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-07-31 14:32:51.730  - INFO: ErizoAgent - as rpc server ok.
2018-07-31 14:32:51.735  - INFO: ErizoAgent - as monitoring target ok.
starting sip-agent, stdout -> /root/Release-v3.5.2/logs/woogeen-sip-agent.stdout
2018-07-31 14:32:52.913  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-07-31 14:32:52.953  - INFO: ErizoAgent - sip agent join cluster ok.
2018-07-31 14:32:52.966  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-07-31 14:32:52.984  - INFO: ErizoAgent - as rpc server ok.
2018-07-31 14:32:52.989  - INFO: ErizoAgent - as monitoring target ok.
starting streaming-agent, stdout -> /root/Release-v3.5.2/logs/woogeen-streaming-agent.stdout
2018-07-31 14:32:54.074  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-07-31 14:32:54.118  - INFO: ErizoAgent - streaming agent join cluster ok.
2018-07-31 14:32:54.139  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-07-31 14:32:54.149  - INFO: ErizoAgent - as rpc server ok.
2018-07-31 14:32:54.155  - INFO: ErizoAgent - as monitoring target ok.
starting video-agent, stdout -> /root/Release-v3.5.2/logs/woogeen-video-agent.stdout
2018-07-31 14:32:55.722  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-07-31 14:32:55.763  - INFO: ErizoAgent - video agent join cluster ok.
2018-07-31 14:32:55.775  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-07-31 14:32:55.783  - INFO: ErizoAgent - as rpc server ok.
2018-07-31 14:32:55.792  - INFO: ErizoAgent - as monitoring target ok.
starting webrtc-agent, stdout -> /root/Release-v3.5.2/logs/woogeen-webrtc-agent.stdout
2018-07-31 14:32:56.659  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-07-31 14:32:56.695  - INFO: ErizoAgent - webrtc agent join cluster ok.
2018-07-31 14:32:56.719  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-07-31 14:32:56.729  - INFO: ErizoAgent - as rpc server ok.
2018-07-31 14:32:56.735  - INFO: ErizoAgent - as monitoring target ok.
starting portal, stdout -> /root/Release-v3.5.2/logs/woogeen-portal.stdout
2018-07-31 14:32:58.086  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-07-31 14:32:58.122  - INFO: Main - portal initializing as rpc client ok
2018-07-31 14:32:58.213  - INFO: Main - portal join cluster ok, with rpcID: portal-e34a26344f8ac50a6fd5@vc.com
2018-07-31 14:32:58.215  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-07-31 14:32:58.272  - INFO: Main - portal initializing as rpc server ok
2018-07-31 14:32:58.299  - INFO: Main - portal-e34a26344f8ac50a6fd5@vc.com as monitor ready
starting sip-portal, stdout -> /root/Release-v3.5.2/logs/woogeen-sip-portal.stdout
2018-07-31 14:32:59.343  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-07-31 14:32:59.381  - INFO: SipPortal - sip-portal up!
2018-07-31 14:32:59.447  - INFO: SipPortal - initSipRooms ok
starting app, stdout -> /root/Release-v3.5.2/logs/woogeen-app.stdout
6 rooms in this service.

0 Kudos
Highlighted
66 Views

From the screenshot, it shows that something wrong happened in nuve, please provide nuve and cluster manager log for us to check what happened. From video log we can see following print: 2018-07-31 10:45:53.680 - INFO: ErizoAgent - as monitoring target ok. 2018-07-31 10:45:55.348 - WARN: ErizoAgent - video agent overloaded! 2018-07-31 10:45:56.349 - WARN: ErizoAgent - video agent overloaded! 2018-07-31 10:45:57.353 - WARN: ErizoAgent - video agent overloaded! it means that device where video agent is in full load, the default max load for each module is 0.85, please check cpu, memory usage and bandwidth, Please also provide your deployment for each module and what's your testing scenario and how to reproduce it, thanks
0 Kudos
Highlighted
66 Views

Dear Quijao,

I have identified that rabbitmq service is also going down after this incident. Here is log of the same. I had to comment room deletion function in sample nodejs server for making things work. Could you please identify any solution for the same.

Thank you

0 Kudos
Highlighted
66 Views

Hi, did you delete room while there are connections in room?  please provide more detailed info. And as i mentioned in previous reply, please check your CPU and memory usage when this issue happened, and also provide your cluster deployment info .

0 Kudos