-
Notifications
You must be signed in to change notification settings - Fork 116
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
Failsafe option doesn't work for SSH Auth Failure #165
Comments
Update: this only happens when the failure is an auth failure. Here's the error that makes it crash:
|
Are you running the latest version? I'm unable to reproduce this. $ node --version; fly --version
v6.9.1
0.6.15
# ---
$ cat flightplan.js
var plan = require('flightplan')
plan.target('test', [
{
host: 'nohost',
failsafe: true,
user: 'root'
},
{
host: '<host that exists>',
port: 22,
user: 'root',
failsafe: true
},
{
host: '<host that exists>',
port: 22,
user: 'root',
failsafe: true
},
{
host: 'foobarfofofo',
failsafe: true,
user: 'root'
},
])
plan.remote(function (remote) {
remote.exec('ls -al')
})
# ---
$ fly test
✈ Running default:test
✈ Connecting to 'nohost'
✈ Connecting to '<host that exists>'
✈ Connecting to '<host that exists>'
✈ Connecting to 'foobarfofofo'
● Safely failed connecting to 'nohost': getaddrinfo ENOTFOUND nohost nohost:22
● Safely failed connecting to 'foobarfofofo': getaddrinfo ENOTFOUND foobarfofofo foobarfofofo:22
● Safely failed connecting to '<host that exists>': All configured authentication methods failed
● Safely failed connecting to '<host that exists>': All configured authentication methods failed
✈ Flightplan finished after 463 ms I also tried this using dynamic host configuration with the same result. |
You should be able to reproduce it if you add
|
Looks as though the code's looking to get a final output while the server is giving it another chance at auth? |
I could reproduce this by passing |
Confirming that this works. Thanks. |
I have searched for a solution to this but I haven't been able to find one. Here's the log that flightplan fails with (I have replaced host names)
I have set the property
failsafe
to true for each of the hosts. The error is coming from node-fibers (this code). I am not sure how to proceed. Any help, including workarounds, is appreciated. Thanks.The text was updated successfully, but these errors were encountered: