You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run "openllm start xxx" to play with it, I can easily use crtl+C to stop it, no http server left.
But once I want to start a backend process by "nohup openllm start llama 2>&1 &", I will lose the control of backend process. It will launch the server as well as lot of http server (per core) at backend. When I kill the main process, those http listener process will be still alive, controlled by some circusd. I am frustrating about it. Everytime I need to reboot OS to restore the env.
Describe the bug
When I run "openllm start xxx" to play with it, I can easily use crtl+C to stop it, no http server left.
But once I want to start a backend process by "nohup openllm start llama 2>&1 &", I will lose the control of backend process. It will launch the server as well as lot of http server (per core) at backend. When I kill the main process, those http listener process will be still alive, controlled by some circusd. I am frustrating about it. Everytime I need to reboot OS to restore the env.
How to make the server easy to stop?
To reproduce
No response
Logs
No response
Environment
openllm, 0.3.3 (compiled: no)
Python (CPython) 3.10.4
System information (Optional)
No response
The text was updated successfully, but these errors were encountered: