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

start MCU server

Hello

I'm trying to install the MCU server version 2.1.1
I get an error on the console when I try to start the server with this command bin/start-all.sh. Before I did carefully all the steps suggested in the MCU server UserGuide.

the log file woogeen-nuve.stdout shows the following information:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: listen EADDRINUSE
    at errnoException (net.js:904:11)
    at Server._listen2 (net.js:1042:14)
    at listen (net.js:1064:10)
    at Server.listen (net.js:1138:5)
    at EventEmitter.app.listen (/home/Documents/Release-v2.1.1/node_modules/express/lib/application.js:595:24)
    at Object.<anonymous> (/home/Documents/Release-v2.1.1/nuve/nuveAPI/nuve.js:1:2669)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)

 

the log file woogeen-mcu.stdout shows the following information:

2015-05-22 11:23:43.582  - INFO: RPC - Exchange rpcExchange is open
2015-05-22 11:23:43.584  - INFO: RPC - ClientQueue amq.gen-QRqzQyMbxcJvNxiYTiFcTR is open
2015-05-22 11:23:48.629  - INFO: ErizoController - Failed to join nuve network.

I appreciate your help.Thanks

Tags (2)
0 Kudos
4 Replies
Highlighted
Beginner
2 Views

use /restart-all.sh. You have

use /restart-all.sh. You have already started one instance that why it is telling you its EADDRINUSE. If not, then try a different port in config for nuve.

If yon can't stop it by restart-all.sh,  use  ps -ef | grep -i node and kill -9 <processId> which represents nuve, erizo and other related ones.

Regards

0 Kudos
Highlighted
2 Views

Hi Dennis,

Hi Dennis,

The best practice that Farrukh shared should help you fix your issue. What's more, EADDRINUSE tries to tell us this is the error of address-in-use...

0 Kudos
Highlighted
Beginner
2 Views

Hi

Hi

The problem was solved by restarting the server.

Thanks.

0 Kudos
Highlighted
2 Views

OK. Cool. Hard reboot is also

OK. Cool. Hard reboot is also a good approach.

0 Kudos