我用过 Ejabberd版本:15.10 Erlang/OTP版本: 18 Tsung 版本: 1.6.1
当我在“make install”之后启动 tsung 时，使用:
xxxxx:~/.tsung$ tsung -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
什么原因导致失败？
最佳答案
最近在用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's Erlang VM is built with SMP support and if Riak is started on a non-SMP system, an error like this one is logged. This is commonly seen in virtualized environments configured for only one CPU core.
我假设您也在 VM 中运行 Tsung。
尽情享受吧!
引用:
关于erlang - Tsung 启动失败，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/33663932/