Error: listen EADDRINUS when I do ./nodebb dev


  • GNU/Linux

    I don't know why nodebb give me this error when I do ./nodebb dev

    Error: listen EADDRINUSE :::4567
        at Object.exports._errnoException (util.js:1036:11)
        at exports._exceptionWithHostPort (util.js:1059:20)
        at Server._listen2 (net.js:1252:14)
        at listen (net.js:1288:10)
        at Server.listen (net.js:1384:5)
        at listen (/vagrant/nodebb/src/webserver.js:260:17)
        at /vagrant/nodebb/src/webserver.js:68:3
        at EventEmitter.<anonymous> (/vagrant/nodebb/src/emitter.js:17:5)
        at emitNone (events.js:86:13)
        at EventEmitter.emit (events.js:185:7)
        at /vagrant/nodebb/src/meta/css.js:117:14
        at /vagrant/nodebb/node_modules/async/lib/async.js:726:13
        at /vagrant/nodebb/node_modules/async/lib/async.js:52:16
        at /vagrant/nodebb/node_modules/async/lib/async.js:269:32
        at /vagrant/nodebb/node_modules/async/lib/async.js:44:16
        at /vagrant/nodebb/node_modules/async/lib/async.js:723:17
        at /vagrant/nodebb/node_modules/async/lib/async.js:167:37
        at /vagrant/nodebb/src/meta/css.js:206:8
        at /vagrant/nodebb/src/meta/css.js:165:4
        at /vagrant/nodebb/node_modules/less/node_modules/graceful-fs/graceful-fs.js:43:10
        at FSReqWrap.oncomplete (fs.js:123:15)
    18/11 17:12 [1163] - error: NodeBB address in use, exiting...
    [cluster] Child Process (1163) has exited (code: 0, signal: null)
    
    

    Anyone can help me?


  • Global Moderator

    You probably already have a nodebb process already running.


  • Admin

    To piggyback on @PitaJ's reply, take a look at what is running with ps aux | grep node

    You can probably use kill to terminate it, if ./nodebb stop won't work.


  • GNU/Linux

    @julian @PitaJ this is my result after that I have do fir "./nodebb stop" and after "ps aux | grep node" in Centos:

    0_1479735622500_Senzanome.png

    I do "vagrant up" to start a centos machine.


Log in to reply
 

Looks like your connection to NodeBB was lost, please wait while we try to reconnect.