Node start failed in VMQ_MZbench example
niclaszll opened this issue · comments
I am trying to run the VMQ_MZbench sample test, i.e. with the following code (only the MQTT broker has been customized):
#!benchDL
#######
# Scenario:
# A single subscriber reading from "prefix/clients/#" topic filter
# 1k publisher publishing to exclusive topic "prefix/clients/{client_id}"
# Overall msg rate: 1k msg/s
# Message size: 150 random bytes
# Running time: 5 min
#######
make_install(git = "https://github.com/vernemq/vmq_mzbench.git",
branch = "master")
pool(size = 1,
worker_type = mqtt_worker):
connect([t(host, "broker.mqttdashboard.com"),
t(port,1883),
t(client,"subscriber1"),
t(clean_session,true),
t(keepalive_interval,60),
t(proto_version,4), t(reconnect_timeout,4)
])
wait(1 sec)
subscribe("prefix/clients/#", 0)
pool(size = 1000,
worker_type = mqtt_worker,
worker_start = poisson(1000 rps)):
connect([t(host, "broker.mqttdashboard.com"),
t(port,1883),
t(client,fixed_client_id("pool1", worker_id())),
t(clean_session,true),
t(keepalive_interval,60),
t(proto_version,4), t(reconnect_timeout,4)
])
set_signal(connect1, 1)
wait_signal(connect1, 1000)
wait(4 sec)
loop(time = 5 min, rate = 1 rps):
publish_to_self("prefix/clients/", random_binary(150), 0)
disconnect()
However, I get the following errors:
17:47:19.109 [error] [ API ] <0.502.0> [ REMOTE EXEC ] Command execution failed: Cmd: bash -c -l "export PATH='/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'; cd /tmp/mz/bench-1-1626198400 && ~/.local/share/mzbench/bin/mzbench start " Exit code: 1 Output: Node start failed
--
17:47:19.111 [error] [ API ] <0.493.0> Stage 'pipeline - provisioning': failed Command returned 1: bash -c -l "export PATH='/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'; cd /tmp/mz/bench-1-1626198400 && ~/.local/share/mzbench/bin/mzbench start " Command output: Node start failed
I am using the latest Dockerfile, built directly from the master branch. The simple test example (when creating a new benchmark) works without any problems.
Just tested it with this Dockerfile - works perfectly, so it seems to be a Docker-related problem.
@niclaszll Geting this error.
rajyadav@rajyadavs-MBP docker-mzbench % docker logs de0370da11cf243484180a8cbe2488412a4ca1de5ceafcb2f7b09cc370ca10b0
Executing make -C /app/mzbench/bin/../server generate
................Stdout+Stderr:
make: Entering directory '/app/mzbench/server'
rm -rf .make/git-rev-*
mkdir -p .make && touch .make/git-rev-27fd1910293d12223c60a8b7bb5ef8abe8e918b8
/app/mzbench/bin/rebar3 compile
===> Fetching rebar_rsync_deps (from {git,"https://github.com/ethercrow/rebar3_rsync_resource",
{ref,"53eb6aa50db8e0de7cf5833a48e48c205f5c8d56"}})
===> Compiling rebar_rsync_deps
_build/default/plugins/rebar_rsync_deps/src/rebar_rsync_resource.erl:14: Warning: variable 'Dir' is unused
_build/default/plugins/rebar_rsync_deps/src/rebar_rsync_resource.erl:17: Warning: variable 'State' is unused
_build/default/plugins/rebar_rsync_deps/src/rebar_rsync_resource.erl:29: Warning: variable 'Dir' is unused
===> Using custom resource rebar_rsync_resource that implements a deprecated api. It should be upgraded to rebar_resource_v2.
===> Using custom resource rebar_rsync_resource that implements a deprecated api. It should be upgraded to rebar_resource_v2.
===> Verifying dependencies...
===> Fetching cowboy (from {git,"git://github.com/ninenines/cowboy.git",
{ref,"90ae31998e8d0887b9efe4b441136ac047708bb9"}})
===> Failed to fetch and copy dep: {git,"git://github.com/ninenines/cowboy.git",
{ref,
"90ae31998e8d0887b9efe4b441136ac047708bb9"}}
make: *** [Makefile:87: .make/compilation-up-to-date] Error 1
make: Leaving directory '/app/mzbench/server'