Authentication or permission failure

Archives Ansible Project
1

Hi!

I’ve updated Ansible from 1.4.4 to 1.5.4 and now I’ve got this new error :

`
fatal: [xxx.xxx.xxx] => Authentication or permission failure. In
some cases, you may have been able to authenticate and did not have
permissions on the remote directory. Consider changing the remote temp
path in ansible.cfg to a path rooted in “/tmp”. Failed command was:
mkdir -p /tmp/ansible-tmp-1396476553.37-249366537253256 && echo
/tmp/ansible-tmp-1396476553.37-249366537253256, exited with result 2

FATAL: all hosts have already failed – aborting
`

in syslog :

`
Apr 3 00:09:13 qualif ansible-accelerate: waiting for data
Apr 3 00:09:13 qualif ansible-accelerate: in recv_data(), waiting for the header
Apr 3 00:09:13 qualif ansible-accelerate: in recv_data(), got the header, unpacking
Apr 3 00:09:13 qualif ansible-accelerate: data received so far (expecting 89): 0
Apr 3 00:09:13 qualif ansible-accelerate: data received so far (expecting 89): 89
Apr 3 00:09:13 qualif ansible-accelerate: received all of the data, returning
Apr 3 00:09:13 qualif ansible-accelerate: got data, decrypting
Apr 3 00:09:13 qualif ansible-accelerate: decryption done
Apr 3 00:09:13 qualif ansible-accelerate: loading json from the data
Apr 3 00:09:13 qualif ansible-accelerate: received a request to validate the user id
Apr 3 00:09:13 qualif ansible-accelerate: validating we’re running as root
Apr 3 00:09:13 qualif ansible-accelerate: response result is {‘rc’: 0}
Apr 3 00:09:13 qualif ansible-accelerate: sending the response back to the controller
Apr 3 00:09:13 qualif ansible-accelerate: done sending the response
Apr 3 00:09:13 qualif ansible-accelerate: waiting for data
Apr 3 00:09:13 qualif ansible-accelerate: in recv_data(), waiting for the header
Apr 3 00:09:13 qualif ansible-accelerate: in recv_data(), got the header, unpacking
Apr 3 00:09:13 qualif ansible-accelerate: data received so far (expecting 233): 0
Apr 3 00:09:13 qualif ansible-accelerate: data received so far (expecting 233): 233
Apr 3 00:09:13 qualif ansible-accelerate: received all of the data, returning
Apr 3 00:09:13 qualif ansible-accelerate: got data, decrypting
Apr 3 00:09:13 qualif ansible-accelerate: decryption done
Apr 3 00:09:13 qualif ansible-accelerate: loading json from the data
Apr 3 00:09:13 qualif ansible-accelerate: received a command request, running it
Apr 3 00:09:13 qualif ansible-accelerate: executing: mkdir -p /tmp/ansible-tmp-1396476553.37-249366537253256 && echo /tmp/ansible-tmp-1396476553.37-249366537253256
Apr 3 00:09:13 qualif ansible-accelerate: got stdout:
Apr 3 00:09:13 qualif ansible-accelerate: got stderr: mkdir: 0: Illegal option -p
Apr 3 00:09:13 qualif ansible-accelerate: thread is done, response from join was {‘stdout’: ‘’, ‘stderr’: ‘mkdir: 0: Illegal option -p\n’, ‘rc’: 2}
Apr 3 00:09:13 qualif ansible-accelerate: response result is {‘stdout’: ‘’, ‘stderr’: ‘mkdir: 0: Illegal option -p\n’, ‘rc’: 2}
Apr 3 00:09:13 qualif ansible-accelerate: sending the response back to the controller
Apr 3 00:09:13 qualif ansible-accelerate: done sending the response
Apr 3 00:09:13 qualif ansible-accelerate: waiting for data
Apr 3 00:09:13 qualif ansible-accelerate: in recv_data(), waiting for the header
Apr 3 00:09:13 qualif ansible-accelerate: received nothing, bailing out
Apr 3 00:09:13 qualif ansible-accelerate: received nothing back from recv_data(), breaking out

`

rolling back to 1.5.0 solves the issue…

2

Please file a bug on this one with steps to reproduce, including a playbook if you can share and we can take a look.

I’d consider SSH pipelining if it works for you though, as it’s mostly as fast as accelerate mode, and also nicer.

We may also want to consider toning down the accelerate mode logging, that’s a little verbose – though maybe helpful in this case.

Thanks!