Kai Stian Olstad [19.07.2016 19:55]: > On 19. juli 2016 18:11, Jörg Kastning wrote: >> <host1.example.com> ESTABLISH SSH CONNECTION FOR USER: None >> <host1.example.com> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o >> ControlPersist=60s -o KbdInteractiveAuthentication=no -o >> PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o >> PasswordAuthentication=no -o ConnectTimeout=10 -o >> ControlPath=/root/.ansible/cp/ansible-ssh-%h-%p-%r host1.example.com >> '/bin/sh -c '"'"'( umask 77 && mkdir -p "` echo >> $HOME/.ansible/tmp/ansible-tmp-1468943476.87-148558126071189 `" && echo >> ansible-tmp-1468943476.87-148558126071189="` echo >> $HOME/.ansible/tmp/ansible-tmp-1468943476.87-148558126071189 `" ) && >> sleep 0'"'"'' > > Here Ansible is doing the ssh and setting up the run. > Since it doesn't fail here, the ssh is working.
Whenever this problem occurred on one of my hosts, the "Subsystem sftp" line in /etc/ssh/sshd_config on that host points to an non-existent sftp-server binary. HTH, Werner -- -- 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/188ecad6-f14b-053f-5840-3ec305ff217e%40ufz.de. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
