You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever I attempt to start a slave via an SSH session created via the Node.js ssh2 package Locust never starts. Adding --logfile and --loglevel arguments don't yield any useful information. In fact, the logfile is never created.
I have the locust command wrapped in a simple bash file. When I log in to the slave and execute the bash script things work as expected.
Description of issue / feature request
Whenever I attempt to start a slave via an SSH session created via the Node.js
ssh2
package Locust never starts. Adding--logfile
and--loglevel
arguments don't yield any useful information. In fact, the logfile is never created.I have the
locust
command wrapped in a simple bash file. When I log in to the slave and execute the bash script things work as expected.Expected behavior
Locust slave starts and stays started.
Actual behavior
Locust does not start. More information at https://stackoverflow.com/questions/52745003/locust-slave-wont-star-running-when-executed-via-bash-script-when-using-node-ss
Environment settings (for bug reports)
Steps to reproduce (for bug reports)
Command being executed inside of bash script:
Node.js code for executing bash script:
It is worth noting that the bash script has
+xrw
privileges.The text was updated successfully, but these errors were encountered: