|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I had a similar problem in my environment, where the master and the slave nodes use different username for jenkins. Say, "masteruser" for the master node and "slaveuser" for the slave. When login failed for the slave, Jenkins tried to connect to the slave node with "masteruser", according to the log file in the slave node (/var/log/auth.log, since it's Ubuntu-based host).
When this happened, I came back to the slave node configuration page (Manage Jenkins -> Manage Nodes -> (particular slave node) -> Configure). There were multiple credentials in "Launch Method - Credentials" drop down list. I could see four items, saying:
Clearly something weird was going on there (duplicated entries). Anyway, I selected the third one for some reason (second and fourth are definitely the wrong ones), then it suddenly worked.