Forever not cleaning up ~/.forever/pids/

[ghost]

forever list command crashes because there are too many .fvr files (over 100). Maybe it is forever needs to clean up after it deletes or the list command should be fixed if there are too many files.

info: Running action: list
pipe(): Too many open files

node.js:134
        throw e; // process.nextTick error, or 'error' event on first tick
        ^
Error: Error spawning
    at ChildProcess.spawn (child_process.js:243:28)
    at child_process.js:31:15
    at child_process.js:77:15
    at child_process.js:38:27
    at checkProcess (/usr/local/lib/node_modules/forever/lib/forever.js:482:3)
    at /usr/local/lib/node_modules/forever/lib/forever.js:372:7
    at Array.forEach (native)
    at Object.cleanUp (/usr/local/lib/node_modules/forever/lib/forever.js:371:15)
    at Object.exec (/usr/local/lib/node_modules/forever/lib/forever/cli.js:44:22)
    at Object.<anonymous> (/usr/local/lib/node_modules/forever/bin/forever:185:13)

[indexzero]

@NlCO This is a good find. Forever is trying to cleanup the processes, but it's exceeding the number of open file descriptors at one time because it is using the parallel async.forEach(). I will write a patch to batch these unlink operations so this doesn't happen in the future.

This will be more common as haibu users increase because each haibu process also has a corresponding .fvr file.

[indexzero]

In the meantime, you can get around this by running:

killall node && rm -rf ~/.forever

I don't know how killall works on Ubuntu, so let me know if you hit a snag there.