What -vvvv does for me is that it adds the lines starting with ESTABLISH CONNECTION, REMOTE_MODULE and EXEC to the output. I am not sure whether it is all it should do as this is my first encounter with Ansible.
I've run into the problem you describe as well, but corrected it by manually removing the offending line from the "~/.ssh/known_hosts" file. /var/log/auth.log looks good to me (as expected). On Wednesday, April 29, 2015 at 1:09:26 PM UTC+2, Sibin Arsenijevic wrote: > > I had exactly the same bug only a bit different problem. Ubuntu 14.04, > ansible installed from your repo via apt. > > user@machine:~/ansible$ ansible --version > ansible 1.9.0.1 > > user@machine:~/ansible$ ansible -m ping machine2 *-vvvv* > SSH password: > SUDO password[defaults to SSH password]: > <192.168.35.81> ESTABLISH CONNECTION FOR USER: user > <192.168.35.81> REMOTE_MODULE ping > <192.168.35.81> EXEC sshpass -d6 ssh -C -tt -vvv -o ControlMaster=auto -o > ControlPersist=60s -o > ControlPath="/home/user/.ansible/cp/ansible-ssh-%h-%p-%r" -o > StrictHostKeyChecking=no -o Port=22 -o > IdentityFile="/home/user/.ssh/ansible" -o GSSAPIAuthentication=no -o > PubkeyAuthentication=no -o ConnectTimeout=10 192.168.1.1 /bin/sh -c 'mkdir > -p $HOME/.ansible/tmp/ansible-tmp-1430303346.24-38061325826660 && chmod > a+rx $HOME/.ansible/tmp/ansible-tmp-1430303346.24-38061325826660 && echo > $HOME/.ansible/tmp/ansible-tmp-1430303346.24-38061325826660' > machine2.domain.com | FAILED => SSH Error: Permission denied > (publickey,password). > while connecting to 192.168.1.1:22 > *It is sometimes useful to re-run the command using -vvvv, which prints > SSH debug output to help diagnose the issue*. > > So no SSH debug output even when run with -vvvv. > > But i guess i have found what was causing it in my case at least. I had an > offending key (because that ip used to belong to other host) in > known_hosts. I have removed the offending key using ssh-keygen -R and it > now works as it should. I found my problem by going through SSH logs > directly since Ansible didn't output any of the ssh debug logs. > > I understand that your problem is different as you have tried connecting > using the ssh and host_key is not a problem but this still points to > inconsistency in -vvvv behaviour. > > Hope this helps a bit :) > > > On Tuesday, April 28, 2015 at 11:07:13 PM UTC+2, dusank wrote: >> >> Any luck reproducing the bug? >> >> On Tuesday, April 28, 2015 at 10:18:09 PM UTC+2, Brian Coca wrote: >>> >>> hmm, im running with 2.6.4, let me update the image. >>> >>> >>> >>> -- >>> Brian Coca >>> >> -- 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/6a605e48-6e6c-4536-8253-8dbffbeffad0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
