mqtt-stresser
mqtt-stresser copied to clipboard
Running the example command on macOS Big Sur 11.2.3 (20D91) fails open : no such file or directory
./mqtt-stresser -broker tcp://broker.mqttdashboard.com:1883 -num-clients 10 -num-messages 150 -rampup-delay 1s -rampup-size 10 -global-timeout 180s -timeout 20s open : no such file or directory
Did you build from source? Or download the distributed binary?
No I downloaded V4 from releases and tried mqtt-stresser-darwin-amd64 and mqtt-stresser-darwin-amd64-static
hmm, not able to reproduce on same os (11.2.3)
ab@abechtoldt02 ~/dev/GOPATH/src/github.com/inovex/mqtt-stresser $ wget -q https://github.com/inovex/mqtt-stresser/releases/download/v4/mqtt-stresser-darwin-amd64-static
ab@abechtoldt02 ~/dev/GOPATH/src/github.com/inovex/mqtt-stresser $ chmod +x mqtt-stresser-darwin-amd64-static
ab@abechtoldt02 ~/dev/GOPATH/src/github.com/inovex/mqtt-stresser $ ./mqtt-stresser-darwin-amd64-static
Usage of ./mqtt-stresser-darwin-amd64-static:
-broker string
Broker URL
-cafile string
path to a file containing trusted CA certificates to enable encrypted certificate based communication.
-cert string
client certificate for authentication, if required by server.
-constant-payload string
Use this constant payload in every MQTT message. If not set, an nearly constant autogenerated payload is used.
-global-timeout string
Timeout spanning all operations (default "60s")
But you need to give a broker to work with...
./mqtt-stresser-darwin-amd64-static -broker tcp://broker.mqttdashboard.com:1883 -num-clients 10 -num-messages 150 -rampup-delay 1s -rampup-size 10 -global-timeout 180s -timeout 20s open : no such file or directory
You're right. I can reproduce:
ab@abechtoldt02 ~/dev/GOPATH/src/github.com/inovex/mqtt-stresser $ ./mqtt-stresser-darwin-amd64-static -broker tcp://broker.mqttdashboard.com:1883 -num-clients 10 -num-messages 150 -rampup-delay 1s -rampup-size 10 -global-timeout 180s -timeout 20s
open : no such file or directory
I have same issue on windows using binary from the release page, but it works if I build it from source
Ok, since the issue occurs for two non-linux platform I suspect that the cross compiling in the release toolchain is broken. I will have a look into it.
Is this issue still not resolved as I am experiencing the same issue on macbook?