Skip to content
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.

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

Sending SIGUSR1 to node v0.12.7 process stops it #2579

Closed
diversario opened this issue Aug 27, 2015 · 2 comments
Closed

Sending SIGUSR1 to node v0.12.7 process stops it #2579

diversario opened this issue Aug 27, 2015 · 2 comments
Labels
invalid Issues and PRs that are invalid. process Issues and PRs related to the process subsystem.

Comments

@diversario
Copy link

I was trying to attach node-inspector to a running process and saw something odd – having a group of active processes, each using 10-20% CPU, sending kill -s SIGUSR1 <pid> makes that particular process go to 0% CPU, memory usage would not change either.

I was able to debug v0.10 processes successfully using the same technique.

This is happening on a CentOS 6 (kernel 2.6.32-504.el6.x86_64), node v0.12.7.

@Fishrock123 Fishrock123 added the process Issues and PRs related to the process subsystem. label Aug 27, 2015
@diversario
Copy link
Author

Ok, follow up.

I was trying to debug remotely so I had to forward one port by setting up an SSH tunnel. As it turned out, node-inspector (which I was using) needs two ports open on the target machine, one for HTTP and another one for websockets. Setting up a second tunnel for the WS port made node-inspector work and, once it connected to the stalled process, the process resumed.

@diversario
Copy link
Author

Probably a non-issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid Issues and PRs that are invalid. process Issues and PRs related to the process subsystem.
Projects
None yet
Development

No branches or pull requests

3 participants