我使用了Ejabberd版本:15.10 Erlang/OTP版本: 18 Tsung版本: 1.6.1
当我在"make“之后开始唱时,请使用:
xxxxx:~/.崇元-f jabber_register.xml start
例: jabber_register.xml是从例子中复制出来的。
然后证明:
Starting Tsung
Log directory is: /home/user/.tsung/log/20151112-1105
[os_mon] memory supervisor port (memsup): Erlang has closed
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed是什么导致了失败?
发布于 2015-12-02 09:07:26
我最近使用了riak,并遇到了类似的问题。
这是启动riak的完整控制台信息:
config is OK
-config /var/lib/riak/generated.configs/app.2015.12.02.16.53.53.config -args_file /var/lib/riak/generated.configs/vm.2015.12.02.16.53.53.args -vm_args /var/lib/riak/generated.configs/vm.2015.12.02.16.53.53.args
Exec: /usr/lib64/riak/erts-5.10.3/bin/erlexec -boot /usr/lib64/riak/releases/2.0.4/riak -config /var/lib/riak/generated.configs/app.2015.12.02.16.53.53.config -args_file /var/lib/riak/generated.configs/vm.2015.12.02.16.53.53.args -vm_args /var/lib/riak/generated.configs/vm.2015.12.02.16.53.53.args -pa /usr/lib64/riak/lib/basho-patches -- console
Root: /usr/lib64/riak
Erlang R16B02_basho6 (erts-5.10.3) [source-bcd8abb] [64-bit] [smp:1:1] [async-threads:64] [kernel-poll:true] [frame-pointer]
[os_mon] memory supervisor port (memsup): Erlang has closed
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
{"Kernel pid terminated",application_controller," {application_start_failure,riak_core,{invalid_ring_state_dir,{riak_core_app,start,[normal,[]]}}}"}
Crash dump was written to: /var/log/riak/erl_crash.dump
Kernel pid terminated (application_controller) ({application_start_failure,riak_core,{invalid_ring_state_dir,{riak_core_app,start,[normal,[]]}}})我在riak官方网站上发现了一些资源,并且了解了问题所在。
Riak的Erlang是在SMP支持下构建的,如果Riak是在非SMP系统上启动的,就会记录类似的错误。这在仅为一个CPU核心配置的虚拟化环境中是常见的。
我以为你也是在VM中运行宗的。
享受吧!
参考:
https://stackoverflow.com/questions/33663932
复制相似问题