有没有办法在使用 -heart 运行时杀死 erlang 虚拟机?
标题几乎概括了这一点。我有一个使用 -heart 运行的 zotonic 站点,它使用大量的 cpu 时间,而且我无法获得 erlang shell。那么,有没有办法杀死虚拟机呢? killall heart
和 killall beam.smp
无法正常工作。
我发现这个问题: 停止 Erlang 守护进程 ,但它并没有真正回答我的问题。
The title pretty much sums it up. I have a zotonic site running with -heart, it uses lots of cpu time and I can't get an erlang shell. So, is there a way to kill the vm? killall heart
and killall beam.smp
are not working.
I found this question:
Stop Erlang Daemon
, but it does not really answer my question.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
只需使用:
它将杀死核心进程和所有应用程序。
Just use:
It will kill the heart process and all applications.
我也有同样的问题......
而且真的很难杀死它。
我尝试了正常的路径,但无法做到。
所以我做了这个 hack:
首先让我们获取 PID
所以 PID 是 931。
接下来哪个程序创建了该进程?
所以程序是.../bin/beam.smp
所以只要移动它
,现在你杀死它
,我终于能够杀死它了:-)
这证明了 erlangs 的可靠性,人们实际上需要破解它才能关闭该服务。
ps:我最初尝试过 yaws -I [pid] --stop 但它也不起作用。
I had this same issue....
And it was really hard to kill it.
I tried the normal paths and couldn't do it.
So I did this hack:
First let's get the PID
So the PID is 931.
Next which program created that process?
So the program is .../bin/beam.smp
so just move it
And now you kill it
And I finally was able to kill it :-)
It's a testament to erlangs reliability that one actually needs to hack-it in order to be able to take down the service.
ps: I originally tried yaws -I [pid] --stop but it didn't work either.
如果您不介意杀死计算机上的每个虚拟机:
虚拟机和心脏似乎相互监视。如果虚拟机处于崩溃/恢复循环,您可能需要快速运行此命令多次以杀死所有死机。
If you don't mind killing every VM on your machine:
The VM and
heart
seem to monitor each other mutually. In case the VM is in a crash/revive loop, you may need to run this command several times quickly to kill everything dead.