a month ago
Hello Railway Support,
I need help with a stuck process from an old Railway web Console session.
A Node.js diagnostic command was started interactively and became stuck waiting for terminal input. The browser session was refreshed, but the process appears to remain active inside the container.
The process is PID 73, a child of shell PID 72. We have verified that it is associated with the same terminal session and is not the normal application entry point.
I need to terminate only the abandoned Console session or its stuck diagnostic process, without stopping, restarting, or redeploying the running API service.
Is there an officially supported way to safely terminate an abandoned web Console session and its child processes?
I am requesting guidance only. Please do not restart the service or modify the deployment, database, or environment variables without explicit approval.
Thank you.
1 Reply
a month ago
We don't have a separate control that ends an old Console session for you. The processes it started run inside your container like any other process, so you remove them from a new shell in that same container.
Open a fresh shell, either from the service's Console tab or with railway ssh from the CLI. Run ps -ef and confirm that PID 73 and its parent PID 72 are still the diagnostic command and the shell you identified. Then run kill 73, or kill 72 to end the abandoned shell as well. If a process ignores that, kill -9 73 forces it to stop. You can also do it in one line with railway ssh -- kill 73. Ending these processes does not restart or redeploy the service, but don't signal PID 1 or your API's own process, since that is the app itself.
If your service runs more than one replica, check that you're on the replica where the process is running. railway ssh --deployment-instance <instance-id> lets you connect to a specific one.
To avoid this next time, railway ssh --session runs your shell inside a persistent tmux session. If your connection drops, you can reconnect to that session and stop the command yourself.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago