Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Locust slave will not start when attempting to start via Node.js SSH2 connection. #900

Closed
vital101 opened this issue Oct 10, 2018 · 0 comments

Comments

@vital101
Copy link

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)

  • OS: Ubuntu 16.04
  • Python version: Python 2.7
  • Locust version: 0.9.0

Steps to reproduce (for bug reports)

Command being executed inside of bash script:

locust --slave --master-host=<masterIpAddress> --logfile=/root/locustlog.log --loglevel=debug &

Node.js code for executing bash script:

await ssh.connect({
    host: ipAaddress,
    username: "root",
    privateKey,
});
const command = "/bin/bash /root/start.sh";
await ssh.execCommand(command, { options: { pty: true } });

It is worth noting that the bash script has +xrw privileges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant