I am having the exact error while try to ping my windows machine form
ansible automation platform template
Can you let me know what was the fix here i see my ansible.cnfg file has
the temp folder specified
{
"unreachable": true,
"msg": "Failed to create temporary directory.In some cases, yo
I have made changes in inventory file like added network_cli as connection
type and now the ping is working fine
On Sat, Jun 19, 2021 at 5:59 PM Dick Visser wrote:
> Can you wipe and reinstall the Debian system?
>
>
> On Sat, 19 Jun 2021 at 00:04, Antony Stone <
> antony.st...@ansible.open.sourc
Can you wipe and reinstall the Debian system?
On Sat, 19 Jun 2021 at 00:04, Antony Stone <
antony.st...@ansible.open.source.it> wrote:
> On Friday 18 June 2021 at 23:57:57, nitesh shet wrote:
>
> > /var/log$ ls
> > alarm.log
> > apps.log.4.gz
> > dpkg.log
> > lastlog
> > private
> > sysstat
> >
On Friday 18 June 2021 at 23:57:57, nitesh shet wrote:
> /var/log$ ls
> alarm.log
> apps.log.4.gz
> dpkg.log
> lastlog
> private
> sysstat
> ztp.log
> alternatives.log
> apt
> drift
> linecard.log
> restconf-command.log
> tl1-command.log
> apps.log
> btmp
> event.log
> messages.log
> security.log
Jun 18 22:58:41 localhost sal[6649]: 11817:ArpUpdaterTh INFO
{ArpUpdater.cpp:396} handleNLNeighMsg: NeighMsgType: NewNeigh NeighState:
Failed
Jun 18 22:58:41 localhost sal[6649]: 11817:ArpUpdaterTh INFO
{ArpUpdater.cpp:400} handleNLNeighMsg: Delete Arp for 19.88.4.49
Jun 18 22:58:41 localhost s
On Friday 18 June 2021 at 23:56:53, nitesh shet wrote:
> there is no such file on the debian machine
Please paste the output of:
ls /var/log
Antony.
--
I bought a book on memory techniques, but I've forgotten where I put it.
Please
/var/log$ ls
alarm.log apps.log.4.gz dpkg.log lastlog
private sysstat ztp.log
alternatives.log aptdrift linecard.log
restconf-command.log tl1-command.log
apps.log btmp event.log messages.log
security.l
On Friday 18 June 2021 at 23:55:52, nitesh shet wrote:
> now i made it to temproot, now also i am facing the same issue
Please show us what appears in the log files on the Debian machine for the
timestamps when you run the ansible command.
Antony.
--
There are two possible outcomes:
If the
there is no such file on the debian machine
On Sat, Jun 19, 2021 at 3:25 AM Antony Stone <
antony.st...@ansible.open.source.it> wrote:
> On Friday 18 June 2021 at 23:53:02, nitesh shet wrote:
>
> > i did change the file owner to temproot :-
> > total 24
> > drwxrwxrwx 3 temproot osgroup 4096 Jun
now i made it to temproot, now also i am facing the same issue
On Sat, Jun 19, 2021 at 3:24 AM Antony Stone <
antony.st...@ansible.open.source.it> wrote:
> On Friday 18 June 2021 at 23:51:34, nitesh shet wrote:
>
> > grep 1001 /etc/group
> > osgroup:x:1001:
>
> So, there are no other members of t
On Friday 18 June 2021 at 23:53:02, nitesh shet wrote:
> i did change the file owner to temproot :-
> total 24
> drwxrwxrwx 3 temproot osgroup 4096 Jun 18 22:37 .
Okay.
1. Has that made any difference to the output from running your ansible
commands?
2. What do the log files such as /var/log/a
On Friday 18 June 2021 at 23:51:34, nitesh shet wrote:
> grep 1001 /etc/group
> osgroup:x:1001:
So, there are no other members of the group "osgroup".
I still fail to understand why the home directory for "temproot" is not owned
by temproot.
Antony.
--
Police have found a cartoonist dead in
i did change the file owner to temproot :-
total 24
drwxrwxrwx 3 temproot osgroup 4096 Jun 18 22:37 .
drwxr-xr-x 6 root root4096 Jun 18 10:28 ..
-rw-r--r-- 1 root root1930 Jun 18 08:52 .bash_profile
-rw-r--r-- 1 root root 715 Jun 18 08:52 .bashrc
drwxr-xr-x 2 root root
grep 1001 /etc/group
osgroup:x:1001:
On Sat, Jun 19, 2021 at 3:19 AM Antony Stone <
antony.st...@ansible.open.source.it> wrote:
> On Friday 18 June 2021 at 23:45:03, nitesh shet wrote:
>
> > ls -al /home/shared
> > total 24
> > drwxrwxrwx 3 root root4096 Jun 18 22:37 .
>
> This directory
On Friday 18 June 2021 at 23:45:03, nitesh shet wrote:
> ls -al /home/shared
> total 24
> drwxrwxrwx 3 root root4096 Jun 18 22:37 .
This directory is owned by root.
Is there any good reason why you do not do "chown temproot: /home/shared" on
this machine?
> grep temproot /etc/passwd
ls -al /home/shared
total 24
drwxrwxrwx 3 root root4096 Jun 18 22:37 .
drwxr-xr-x 6 root root4096 Jun 18 10:28 ..
-rw-r--r-- 1 root root1930 Jun 18 08:52 .bash_profile
-rw-r--r-- 1 root root 715 Jun 18 08:52 .bashrc
drwxr-xr-x 2 root root4096 Jun 18 11:01 sc
On Friday 18 June 2021 at 23:39:13, nitesh shet wrote:
> /home/shared is the directory on my target or remote machine which has 777
> permission as well as temproot also has sudo permission
Please log on to the Debian machine and paste here the results of the
commands:
ls -al /home/shar
On Friday 18 June 2021 at 23:38:32, nitesh shet wrote:
> no it is not getting creating on my remote machine which is debian
Sorry, I do not understand that answer.
What do you see in the log files on your Debian machine at the time you run the
ansible command on your Centos machine?
I would ex
what does this mean by "target directory" which directory it is referring
to?
On Sat, Jun 19, 2021 at 3:05 AM Wei-Yen Tan wrote:
> Okay apologies.
>
> This is the key message here.
>
> Failed to create temporary directory.In some cases, you may have been able
> to authenticate and did not have p
/home/shared is the directory on my target or remote machine which has 777
permission as well as temproot also has sudo permission
On Sat, Jun 19, 2021 at 3:05 AM Wei-Yen Tan wrote:
> Okay apologies.
>
> This is the key message here.
>
> Failed to create temporary directory.In some cases, you ma
no it is not getting creating on my remote machine which is debian
On Sat, Jun 19, 2021 at 3:05 AM Antony Stone <
antony.st...@ansible.open.source.it> wrote:
> On Friday 18 June 2021 at 23:31:52, nitesh shet wrote:
>
> > i just moved my config file to some unknow directory but after doing that
>
Okay apologies.
This is the key message here.
Failed to create temporary directory.In some cases, you may have been able
to authenticate and did not have permissions on the target directory.
Permissions.
On Sat, 19 Jun 2021 at 9:32 AM nitesh shet wrote:
> i just moved my config file to some u
On Friday 18 June 2021 at 23:31:52, nitesh shet wrote:
> i just moved my config file to some unknow directory but after doing that
> also i am getting the same error
What do the log files such as /var/log/auth.log and /var/log/syslog on the
Debian machine you are targetting tell you is happening
i just moved my config file to some unknow directory but after doing that
also i am getting the same error :-
ansible all -m ping
172.16.12.215 | UNREACHABLE! => {
"changed": false,
"msg": "Failed to create temporary directory.In some cases, you may
have been able to authenticate and did no
On Friday 18 June 2021 at 23:25:20, nitesh shet wrote:
> i just pasted the config file which i got during the ansible installation
> and made modification on that, can you please specify which entry exactly
> do i need to change in that config file?
Er, have you uncommented (ie: removed the leadi
Don't. You don't need to have ansible.cfg to use ansible. Unless there is a
setting you need to change. Take it out
On Sat, 19 Jun 2021 at 9:25 AM nitesh shet wrote:
> i just pasted the config file which i got during the ansible installation
> and made modification on that, can you please specify
i just pasted the config file which i got during the ansible installation
and made modification on that, can you please specify which entry exactly
do i need to change in that config file?
On Sat, Jun 19, 2021 at 2:53 AM Wei-Yen Tan wrote:
> Why do you have so much? I just have two or three ent
Why do you have so much? I just have two or three entries in mine. Role
path. and collections path? Are you just copying and pasting? What
purpose do yoy need to have so many entries?
On Sat, 19 Jun 2021 at 9:20 AM nitesh shet wrote:
> Below is how ansible config file looks like:
>
> # config
Below is how ansible config file looks like:
# config file for ansible -- https://ansible.com/
# ===
# nearly all parameters can be overridden in ansible-playbook
# or with command line flags. ansible will read ANSIBLE_CONFIG,
# ansible.cfg in the curre
The problem is it is NOT writing to the home directory. It is writing to
/tmp directory. Your user has not got rights to the directory. Look for
that setting the error message tells you in the ansible.cfg and take it
out. Behavior should be the same after that
On Sat, 19 Jun 2021 at 9:16 AM nitesh
But i have given 777 permission to my ~ directory and in ansible.cfg also
tried to change the directory path to something else like
/home/temproot/.ansible/tmp and /tmp/.ansible/tmp other than already
existing one.
but nothing worked for me. after that i have kept the config file as it is.
On Sat
When you run ping in Ansible playbook or ansible they are using the same
module. Ansible Ping is not the same as ping. Ansible ping makes an ssh
connection to the server.
When ansible runs a module it writes a file to the home directory of the
user on the remote machine to get the right permission
[servers]
172.16.12.215
[servers:vars]
ansible_user=temproot
ansible_ssh_pass=**
ansible_python_interpreter=/usr/bin/python
ansible_port=8022
still i am getting the same response.:-
ansible all -m ping
172.16.12.215 | UNREACHABLE! => {
"changed": false,
"msg": "Failed to create tempo
On Friday 18 June 2021 at 22:53:26, nitesh shet wrote:
'i haven't written any playbook , i am just trying to run "ansible all -m
ping" from shell.'
Okay.
> [root@in-6centos50-dt ansible]# ssh temproot@172.16.12.215 -p 8022
> temproot@172.16.12.215's password:
On Friday 18 June 2021 at 21:41:25
ansible all -m ping
172.16.12.215 | 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
roo
[root@in-6centos50-dt ansible]# ssh temproot@172.16.12.215 -p 8022
temproot@172.16.12.215's password:
*** Warning
***
The Linux shell access is restricted to authorized users for business
purposes.
Unauthorized access is a violation of
On Friday 18 June 2021 at 22:42:28, nitesh shet wrote:
> temproot is the user to which I manually did the ssh and /home/shared is
> also belongs to the temproot user and even in my inventory also I specially
> mentioned user as temproot.
Please show us a playbook which exhibits this problem (the
temproot is the user to which I manually did the ssh and /home/shared is
also belongs to the temproot user and even in my inventory also I specially
mentioned user as temproot.
~/.ansible/tmp is the path in ansible.cfg
On Sat, 19 Jun 2021, 02:08 Antony Stone, <
antony.st...@ansible.open.source.it>
On Friday 18 June 2021 at 22:33:55, nitesh shet wrote:
> My remote user has sudo permission and I tried changing remote_tmp to
> absolute path in remote host as /home/shared/.ansible/tmp
> Nothing is working, if I do ssh manually to the remote will work.
Which user do you manually SSH to the remo
My remote user has sudo permission and I tried changing remote_tmp to
absolute path in remote host as /home/shared/.ansible/tmp
Nothing is working, if I do ssh manually to the remote will work.
On Sat, 19 Jun 2021, 01:21 Antony Stone, <
antony.st...@ansible.open.source.it> wrote:
> On Friday 18 J
On Friday 18 June 2021 at 21:41:25, nitesh shet wrote:
> Hi experts,
> I am unable to ping to my remote servers via ansible.
Do other ansible commands on the same target machine work okay?
> "msg": "Failed to create temporary directory.In some cases, you may
> have been able to authenticate
Hi experts,
I am unable to ping to my remote servers via ansible. Below are how my
inventory file is looks like:-
[servers]
x.y.z
[servers:vars]
ansible_user=dummy
ansible_ssh_pass=dummy
ansible_python_interpreter=/usr/bin/python
ansible_port=22
ansible_become=yes
if i apply ping module using an
42 matches
Mail list logo
