when I do a ansible all -i inventory/inv_sjc_core -u vegeta -m ping -k it
does not authenticate but if I do a "ssh -l vegeta vegeta01_temp" it works
vegeta01_temp | UNREACHABLE! => {
"changed": false,
"msg": "Authentication or permission failure. In some cases, you may
have been able to authenticate and did not have permissions on the target
directory. Consider changing the remote tmp path in ansible.cfg to a path
rooted in \"/tmp\". Failed command was: ( umask 77 && mkdir -p \"` echo Cmd
exec error./.ansible/tmp/ansible-tmp-1551117540.2506652-80180766644234 `\"
&& echo ansible-tmp-1551117540.2506652-80180766644234=\"` echo Cmd exec
error./.ansible/tmp/ansible-tmp-1551117540.2506652-80180766644234 `\" ),
exited with result 16, stdout output: Syntax error while parsing '/bin/sh
-c '( umask 77 && mkdir -p \"` echo Cmd exec
error./.ansible/tmp/ansible-tmp-1551117540.2506652-80180766644234 `\" &&
echo ansible-tmp-1551117540.2506652-80180766644234=\"` echo Cmd exec
error./.ansible/tmp/ansible-tmp-1551117540.2506652-80180766644234 `\" ) &&
sleep 0''\n\n\nCmd exec error.\n",
"unreachable": true
}
vegeta02_temp | UNREACHABLE! => {
"changed": false,
"msg": "Authentication or permission failure. In some cases, you may
have been able to authenticate and did not have permissions on the target
directory. Consider changing the remote tmp path in ansible.cfg to a path
rooted in \"/tmp\". Failed command was: ( umask 77 && mkdir -p \"` echo Cmd
exec error./.ansible/tmp/ansible-tmp-1551117540.287293-48560425026336 `\"
&& echo ansible-tmp-1551117540.287293-48560425026336=\"` echo Cmd exec
error./.ansible/tmp/ansible-tmp-1551117540.287293-48560425026336 `\" ),
exited with result 16, stdout output: Syntax error while parsing '/bin/sh
-c '( umask 77 && mkdir -p \"` echo Cmd exec
error./.ansible/tmp/ansible-tmp-1551117540.287293-48560425026336 `\" &&
echo ansible-tmp-1551117540.287293-48560425026336=\"` echo Cmd exec
error./.ansible/tmp/ansible-tmp-1551117540.287293-48560425026336 `\" ) &&
sleep 0''\n\n\nCmd exec error.\n",
"unreachable": true
}
[root@ansiblevm ansible]#
On Sunday, February 24, 2019 at 2:22:49 PM UTC-5, [email protected] wrote:
>
> On Saturday, February 23, 2019 at 5:11:45 PM UTC-6, VeGeTa-X wrote:
>>
>> ok fixed the username and password and I am still not able to login using
>> the playbook
>>
>
> Please provide the new error message you're getting. Can you do a simple
> "ansible ping" (
> https://docs.ansible.com/ansible/latest/user_guide/intro_getting_started.html#your-first-commands
> ).
>
> Dan
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/bcec1868-bbbe-4899-9ddd-c699094709b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
