"master killed, committing suicide" problem with starting basic project

[Jaroslaw Zabiello]

I use OS X 10.8.2, simple derby new myapp; cd myapp; node server.js ends with strange error:

...

Starting cluster with 1 workers in undefined mode
`kill -s SIGUSR2 94953` to force cluster reload
Go to: http://localhost:80/

events.js:68
        throw arguments[1]; // Unhandled 'error' event
                       ^
Error: listen EACCES
    at errnoException (net.js:769:11)
    at Server._listen2 (net.js:892:19)
    at listen (net.js:936:10)
    at Server.listen (net.js:985:5)
    at EventEmitter.proto.run (/Users/hipertracker/tmp/myapp/myapp/node_modules/derby/lib/derby.server.js:59:34)
    at Object.<anonymous> (/Users/hipertracker/tmp/myapp/myapp/server.js:1:80)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
$    info  - socket.io started
master killed, committing suicide

details: https://gist.github.com/3862046

[Daniel Saewitz]

I helped Jaroslaw in IRC. 

For future reference, `Error: listen EACCES` implies that you're binding to a port that already has something running. He was binding by default to port 80. By opening `./server.js` and modifying the `run` command with a second parameter we can change the server's port.

For example:

    require('derby').run(__dirname + '/lib/server', 3000) // bind to 3000