I have a group of old HP-UX servers that I need to manage with
Ansible. I started by installing python-2.7.13 on one server, then testing
with a simple Ansible ping:
sinuid06-> ansible sinuid02 -m ping
sinuid02 | SUCCESS => {
"changed": false,
"ping": "pong"
}
That went well.
Not sure the answer to your question but you can get some more information
from ansible that may help.
Use -v as an option and you'll see a printout of what command lines
ansible is trying to run over the ssh connection.
-Toshio
On Mon, Jul 31, 2017 at 12:55 PM, wrote:
>
>
> I have a g
On Tuesday, August 1, 2017 at 6:51:26 AM UTC-7, Toshio Kuratomi wrote:
>
> Not sure the answer to your question but you can get some more information
> from ansible that may help.
>
> Use -v as an option and you'll see a printout of what command lines
> ansible is trying to run over the ssh
- did not show anything that was helpful:
sinuid06-> ansible sinuid02 -sK -m ping -
Using /InfraRepo/Ansible/config/ansible.cfg as config file
SUDO password:
Loading callback plugin minimal of type stdout, v2.0 from
/usr/lib/python2.7/site-packages/ansible/plugins/callback/__init__.
The debug output from when I ANSIBLE_KEEP_REMOTE_FILES=1 is
significantly different from when I do not set that:
sinuid06-> ANSIBLE_KEEP_REMOTE_FILES=1 ansible sinuid02 -sK -m ping -
Using /InfraRepo/Ansible/config/ansible.cfg as config file
SUDO password:
Loading callback plugin minimal
Using ANSIBLE_KEEP_REMOTE_FILES also disables ssh 'pipelining', so I
suspect just disabling pipelining may may also work.
See
http://docs.ansible.com/ansible/latest/intro_configuration.html#pipelining
Try:
$ ANSIBLE_SSH_PIPELINING=0 ansible -v sinuid02 -sK -m command -a id
And then:
It worked exactly as you predicted, disabling pipelining resulted in
success, enabling pipelining caused failure:
sinuid06-> ANSIBLE_SSH_PIPELINING=0 ansible sinuid02 -bK -m ping -
Using /InfraRepo/Ansible/config/ansible.cfg as config file
SUDO password:
Loading callback plugin minimal
I thought it might be the special characters in my password. They
sometimes do not pass properly in pipeline streams.
I tried the following:
ssh -tt sinuid02 "echo 'my#password' | sudo -S id"
uid=0(root) gid=3(sys)
groups=0(root),1(other),2(bin),4(adm),5(daemon),6(mail),7(lp),20(users),
