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

Start MCU server error - version:4.0

After I install all software in CentOS 7.2 (node:V6.9.5 MongoDB:v3.4.15 )and run start_all.sh to start MCU server, it's error.The log:

[root@mfsmaster Release-v4.0]# sh bin/start-all.sh
starting nuve, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-nuve.stdout
starting cluster-manager, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-cluster-manager.stdout
2018-05-29 16:33:15.301  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-05-29 16:33:15.310  - INFO: Main - Cluster manager up! id: 686683468
2018-05-29 16:33:15.311  - INFO: ClusterManager - Run as candidate.
2018-05-29 16:33:15.507  - INFO: ClusterManager - Run as master.
2018-05-29 16:33:15.520  - INFO: ClusterManager - Cluster manager is in service as master!
starting audio-agent, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-audio-agent.stdout
2018-05-29 16:33:16.401  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-05-29 16:33:16.420  - INFO: ErizoAgent - audio agent join cluster ok.
2018-05-29 16:33:16.432  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-05-29 16:33:16.440  - INFO: ErizoAgent - as rpc server ok.
2018-05-29 16:33:16.442  - INFO: ErizoAgent - as monitoring target ok.
starting conference-agent, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-conference-agent.stdout
2018-05-29 16:33:17.502  - INFO: ErizoAgent - No loader.json found.
2018-05-29 16:33:17.576  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-05-29 16:33:17.590  - INFO: ErizoAgent - conference agent join cluster ok.
2018-05-29 16:33:17.603  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-05-29 16:33:17.609  - INFO: ErizoAgent - as rpc server ok.
2018-05-29 16:33:17.612  - INFO: ErizoAgent - as monitoring target ok.
starting recording-agent, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-recording-agent.stdout
2018-05-29 16:33:18.695  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-05-29 16:33:18.711  - INFO: ErizoAgent - recording agent join cluster ok.
2018-05-29 16:33:18.724  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-05-29 16:33:18.732  - INFO: ErizoAgent - as rpc server ok.
2018-05-29 16:33:18.735  - INFO: ErizoAgent - as monitoring target ok.
starting sip-agent, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-sip-agent.stdout
2018-05-29 16:33:19.797  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-05-29 16:33:19.813  - INFO: ErizoAgent - sip agent join cluster ok.
2018-05-29 16:33:19.825  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-05-29 16:33:19.832  - INFO: ErizoAgent - as rpc server ok.
2018-05-29 16:33:19.835  - INFO: ErizoAgent - as monitoring target ok.
starting streaming-agent, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-streaming-agent.stdout
2018-05-29 16:33:20.925  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-05-29 16:33:20.941  - INFO: ErizoAgent - streaming agent join cluster ok.
2018-05-29 16:33:20.951  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-05-29 16:33:20.959  - INFO: ErizoAgent - as rpc server ok.
2018-05-29 16:33:20.961  - INFO: ErizoAgent - as monitoring target ok.
starting video-agent, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-video-agent.stdout
2018-05-29 16:33:22.050  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-05-29 16:33:22.068  - INFO: ErizoAgent - video agent join cluster ok.
2018-05-29 16:33:22.080  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-05-29 16:33:22.089  - INFO: ErizoAgent - as rpc server ok.
2018-05-29 16:33:22.092  - INFO: ErizoAgent - as monitoring target ok.
starting webrtc-agent, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-webrtc-agent.stdout
2018-05-29 16:33:23.166  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-05-29 16:33:23.184  - INFO: ErizoAgent - webrtc agent join cluster ok.
2018-05-29 16:33:23.195  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-05-29 16:33:23.203  - INFO: ErizoAgent - as rpc server ok.
2018-05-29 16:33:23.206  - INFO: ErizoAgent - as monitoring target ok.
starting management-console, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-management-console.stdout
Start management-console HTTP server
starting portal, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-portal.stdout
2018-05-29 16:33:25.412  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-05-29 16:33:25.423  - INFO: Main - portal initializing as rpc client ok
2018-05-29 16:33:25.434  - INFO: Main - portal join cluster ok, with rpcID: portal-f04d1f1b5a693fe48f5f@192.168.2.60
2018-05-29 16:33:25.435  - INFO: ClusterWorker - Join cluster woogeen-cluster OK.
2018-05-29 16:33:25.439  - INFO: Main - portal initializing as rpc server ok
2018-05-29 16:33:25.443  - INFO: Main - portal-f04d1f1b5a693fe48f5f@192.168.2.60 as monitor ready
events.js:160
      throw er; // Unhandled 'error' event
      ^

starting sip-portal, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-sip-portal.stdout
2018-05-29 16:33:26.750  - INFO: AmqpClient - Connecting to rabbitMQ server OK, hostPort: { host: 'localhost', port: 5672 }
2018-05-29 16:33:26.765  - INFO: SipPortal - sip-portal up!
2018-05-29 16:33:26.773  - INFO: SipPortal - initSipRooms ok
starting app, stdout -> /home/root/intelCS/Release-v4.0/logs/woogeen-app.stdout
1 rooms in this service.
sampleRoom Id: 5b0cb058753dc0ab9d32e02d

How to fixed it? Thanks.

Tags (2)
0 Kudos
1 Reply
Highlighted
Beginner
40 Views

The reason is the port 8080 is used.

0 Kudos