New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PM2 kill/stop leads to error #360

Closed

itayw opened this issue Apr 6, 2014 · 1 comment

Assignees

Milestone

Member

itayw commented Apr 6, 2014

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: channel closed
  at process.target.send (child_process.js:402:26)
  at process.uncaughtListener (/Users/Matt/.nvm/v0.10.26/lib/node_modules/pm2/lib/ProcessContainer.js:102:17)
  at process.EventEmitter.emit (events.js:117:20)
  at process._fatalException (node.js:272:26)

itayw added this to the Version 0.4.1 milestone

itayw self-assigned this

itayw added a commit that referenced this issue


          #360 addressing issue of PM2 kill

a8c30e3

Member Author

itayw commented Apr 6, 2014

The message is still there, but the node exists after a kill/stop command.

itayw added a commit that referenced this issue


          #360 disabled logger dispatch tests.

3f4e887

itayw added a commit that referenced this issue


          #360 resolved. fixed PM2 kill issue.

0b7268e

itayw closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment