How to restart PoolController and Dash server - w/ out server reboot #408
-
Hello, Everytime I have an issue with poolcontroler or dash, I am restarting the pi. If I try npm start& again it says the port is already in use. Seems like the network port bindings stay open after a crash/ halt. So, I just reboot. But this is added a ton of time to TS. I have added the use of "screen" to create ssh sessions to resume. This doesn't help with restarting the poolcontroller apps. Any suggestions? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
If you are using pm2 just do |
Beta Was this translation helpful? Give feedback.
-
You should consider running the pi headless using Remote Desktop or VNC. Then you have access to the entire pi without all the ssh pain and no monitors involved. |
Beta Was this translation helpful? Give feedback.
-
You can find directions for PM2 in the wiki. Running commands with the However, if you are want to see what node processes are running you can use |
Beta Was this translation helpful? Give feedback.
You can find directions for PM2 in the wiki. Running commands with the
&
will kill the app if an ssh session is terminated.However, if you are want to see what node processes are running you can use
ps -ef | grep node
. If you want to kill a rogue process you can usesudo kill -9 [process_id]
but if things go south for me I just usually kill everything withsudo killall node
.