-
Notifications
You must be signed in to change notification settings - Fork 152
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
Service races when port is in use (this was under pm2) #417
Comments
I don't recall off the top of my head if we do exit 1 if the port is in use. Obviously we should. |
If the Ident Port is in use it'll error out with
|
If the AS Port is in use it'll error out with
|
So my guess is its pm2 trying to restart it stupidly quickly and the expensive startup is repeated over and over consuming loads of CPU |
OK, that was mostly my suspicion as well. |
I think we're likely to not fix this. I suggest using docker / systemd or another management process that gives you some delay. |
I was working on setting things up in pm2, and ended up looking at my CPU graph and saw that it was getting pegged at 100%, and the issue that I was seeing was related to the AS attempting to request the ports (AS and ident) and failing.
I'm not sure if this issue exists when running straight from node, or if the service itself is running into this issue, but from what it looked like, I think that the node instance wasn't quitting, but kept running. I could try to duplicate, but I'm not sure how to right off the top of my head.
The text was updated successfully, but these errors were encountered: