I'd say to approach this issue as a problem with the remote_user you're
using. So it's worth checking if remote_user has all required privileges to
become root.
Another quick test is to set remote_tmp to just /tmp.
Hope that's helpful
El vie, 18 mar 2022 a las 20:00, igor haase (<i.ha...@bosselnet.ch>)
escribió:
> Hi fellows,
>
> yesterday I wrote this invontory.yaml file:
> all:
> hosts:
> webserver1:
> ansible_host: 37.221.xxx.xxx
> webserver2:
> ansible_host: 202.61.xxx.xxx
> webserver3:
> ansible_host: 202.61.xxx.xxx
> dbserver1:
> ansible_host: 91.132.xxx.xxx
> dbserver2:
> ansible_host: 185.170.xxx.xxx
> vpnserver1:
> ansible_host: 46.38.234.xxx.xxx
> nameserver1:
> ansible_host: 92.60.xxx.xxx
> mailserver1:
> ansible_host: 93.177.xxx.xxx
> mailserver2:
> ansible_host: 185.233.xxx.xxx
>
> children:
> webservers:
> hosts:
> webserver1: 37.221.xxx.xxx
> webserver2: 202.61.xxx.xxx
> webserver3: 202.61.xxx.xxx
> dbservers:
> dbserver1: 91.132.xxx.xxx
> dbserver2: 185.170.xxx.xxx
> vpnservers:
> vpnserver1: 46.38.xxx.xxx
> mailservers:
> mailserver1: 93.177.xxx.xxx
> mailserver2: 185.233.xxx.xxx
> nameservers:
> nameserver1: 92.60.xxx.xxx
>
> to test the ansible-navigator. Everything runs fine, but when I try to
> reach webserver1 like this: ansible -vvv -i inventory.yaml webserver1 -m
> setup
> I get:
>
>
>
>
> *UNREACHABLE! => { "changed": false, "msg": "Failed to create
> temporary directory.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\", for more error
> information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo
> /root/.ansible/tmp `\"&& mkdir \"` echo
> /root/.ansible/tmp/ansible-tmp-1647368810.1744432-79926-217579336494646 `\"
> && echo ansible-tmp-1647368810.1744432-79926-217579336494646=\"` echo
> /root/.ansible/tmp/ansible-tmp-1647368810.1744432-79926-217579336494646 `\"
> ), exited with result 1", "unreachable": true} *
>
> So I changed the the path to remote tmp_dir in the ansible.cfg several
> times but it does not work yet. Has anyone an idea how to fix that?
>
> Many thanks in advance,
>
> Igor
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-devel/36ebfeea-a460-4dd3-9113-fffd01ead6c0n%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-devel/36ebfeea-a460-4dd3-9113-fffd01ead6c0n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-devel/CAFtje5NqsWym6PGjVE-5U7VPp17qvjwPzeQuA7HOListrEn8rg%40mail.gmail.com.
