Regarding No space left on device error

399 views
Skip to first unread message

Ashok Reddy

unread,
Jan 18, 2024, 12:54:29 AM1/18/24
to Ansible Project
Hi All, 

I have been facing the following issue: 

/home/ansible/.ansible/tmp/ansible-tmp: No space left on device. 

I have cleared the space in Ansible server and another server but the issue still persists. 

Can some one please help me?

Dick Visser

unread,
Jan 18, 2024, 7:47:40 AM1/18/24
to ansible...@googlegroups.com
This could be about not enough inodes

Try this and see if the IUse% is near 100%:


df -i




--
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 ansible-proje...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAKRLcHirXmja0tfd821B701n9fnQWkv%2BcSk60UQNTdRvzQvArg%40mail.gmail.com.

Ashok Reddy

unread,
Jan 18, 2024, 7:51:19 AM1/18/24
to ansible...@googlegroups.com
Okay Vesser Thanks and will check

Evan Hisey

unread,
Jan 18, 2024, 12:34:09 PM1/18/24
to ansible...@googlegroups.com
Ashok-
 Just to state the obvious, because it can trip you up. Was the space you cleared available to/under  /home/ansible? I have seen this be a symlink to other locations than what you expect, and also seen this error when you hit quota limits on the user which can also trigger against privilege changes to root or a secondary account.

--

Ashok Reddy

unread,
Jan 18, 2024, 7:08:11 PM1/18/24
to ansible...@googlegroups.com

Ashok Reddy

unread,
Jan 18, 2024, 8:19:53 PM1/18/24
to ansible...@googlegroups.com
Hi Visser, 


The Iuse percentage is not an issue as per the above screenshot 

On Thu, 18 Jan 2024 at 8:47 PM, Dick Visser <dnmv...@gmail.com> wrote:

Dick Visser

unread,
Jan 18, 2024, 11:24:36 PM1/18/24
to ansible...@googlegroups.com
Try the other tips from previous poster Evan, or try to seek help from the group that manages the system (if that is not you).

 In any case this isn't an ansible issue, but some local storage/configuration issue on your side.


Sent from Gmail Mobile


Jatashankar Mishra

unread,
Jan 19, 2024, 12:07:03 AM1/19/24
to ansible...@googlegroups.com
I think you should provide some more details 

What task failed what was run? 

Also share df -h 

Thank you
Jata

Ashok Reddy

unread,
Jan 19, 2024, 12:22:19 AM1/19/24
to ansible...@googlegroups.com
Okay Visser and Thanks for your inputs.

Hearn, Stan J.

unread,
Jan 19, 2024, 7:53:47 AM1/19/24
to ansible...@googlegroups.com

Can you run this from your Ansible control node against the target as the ansible user?

 

ansible 'TARGETNAME' -m command -a 'df -h /home/'

ansible 'TARGETNAME' -m command -a 'df -h /home/ansible/'

ansible 'TARGETNAME' -m command -a 'df -h /home/ansible/.ansible'

ansible 'TARGETNAME' -m command -a 'df -h /home/ansible/.ansible/tmp'

Ashok Reddy

unread,
Jan 19, 2024, 7:57:02 AM1/19/24
to ansible...@googlegroups.com
Okay Stan and I will run and let you know. Thanks for your inputs.

Todd Lewis

unread,
Jan 19, 2024, 11:40:22 AM1/19/24
to Ansible Project
I've seen "No space left on device" reported when the actual issue was that the filesystem being operated on was mounted read-only rather than read-write.

Ashok Reddy

unread,
Jan 19, 2024, 11:43:23 AM1/19/24
to ansible...@googlegroups.com
Thanks Todd for your inputs.

--
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 ansible-proje...@googlegroups.com.

Hearn, Stan J.

unread,
Jan 19, 2024, 1:37:51 PM1/19/24
to ansible...@googlegroups.com

That's a great point Todd.

 

If the TARGET is Linux, run this and look for 'ro' read-only or 'rw' read-write.

 

ansible 'TARGET' -m shell -a 'cat /proc/mounts | grep "/home "'

--

Ashok Reddy

unread,
Jan 19, 2024, 11:41:04 PM1/19/24
to ansible...@googlegroups.com

Nico Kadel-Garcia

unread,
Jan 20, 2024, 2:51:11 PM1/20/24
to ansible...@googlegroups.com
One possibilit is that a transient file is created by the ansible
task, and cleared away if the file generation fails.

Ashok Reddy

unread,
Jan 20, 2024, 10:45:05 PM1/20/24
to ansible...@googlegroups.com
Thanks Nico for your inputs.

--
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 ansible-proje...@googlegroups.com.

Ashok Reddy

unread,
Jan 21, 2024, 9:03:10 PM1/21/24
to ansible...@googlegroups.com
Hi I have verified in the particular server :





On Sat, 20 Jan 2024 at 2:37 AM, 'Hearn, Stan J.' via Ansible Project <ansible...@googlegroups.com> wrote:

Ashok Reddy

unread,
Jan 21, 2024, 9:20:30 PM1/21/24
to ansible...@googlegroups.com
 I did google and check the whether the file system has read only or read/write permissions. I am little bit confused about whether is in Ansible server or target server. The other builds, which are successfull in Ansible server. The issue might be in target server but not sure. and Not sure how to fix the transient file issue.

On Sun, 21 Jan 2024 at 3:50 AM, Nico Kadel-Garcia <nka...@gmail.com> wrote:
--
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 ansible-proje...@googlegroups.com.

Ashok Reddy

unread,
Jan 22, 2024, 1:22:18 AM1/22/24
to ansible...@googlegroups.com


On Sat, 20 Jan 2024 at 2:37 AM, 'Hearn, Stan J.' via Ansible Project <ansible...@googlegroups.com> wrote:

Evan Hisey

unread,
Jan 23, 2024, 5:23:47 PM1/23/24
to ansible...@googlegroups.com
Ashok-
 Are you having a space issue or a host issue? According to the error you trying to access hosts not in your inventory.

Ashok Reddy

unread,
Jan 23, 2024, 8:16:02 PM1/23/24
to ansible...@googlegroups.com
Hi Ehisey, 

I have been facing the space issue. 

Evan Hisey

unread,
Jan 24, 2024, 12:37:20 PM1/24/24
to ansible...@googlegroups.com
Ashok-
 Why did you provide an error with host access issues? It is confusing the problem, or did you mean to post a different error message?

Ashok Reddy

unread,
Jan 25, 2024, 5:30:51 AM1/25/24
to ansible...@googlegroups.com
Hi Ehisey, 

I have posted the issue, which I have been facing. Sorry for causing inconvenience and thanks for your inputs.

Dick Visser

unread,
Jan 25, 2024, 7:20:35 AM1/25/24
to ansible...@googlegroups.com
On Thu, 25 Jan 2024 at 11:30, Ashok Reddy <ashok...@gmail.com> wrote:
Hi Ehisey, 

I have posted the issue, which I have been facing. Sorry for causing inconvenience and thanks for your inputs.

So far it's not even clear where your error occurs. You did not supply basic information such as:

* what the inventory looks like
* what the playbook looks like
* what command(s) you invoked
* where the error is being emitted

Provide those, as text, not as photos.
Photos of computer screens are hard to index, which prevents other people having the same problem from finding the topic.

You've been trying a few things, but to me it is unclear if you tried this on the management station, or on the node(s) that are being managed.
Host names like 'plansalphm0a' or 'uldobnjswbhm0a' don't make it clearer.
Please make it clear what the role of those hosts is.

But in the end, this is still a local system problem, not an ansible problem. Ansible is just "the messenger".

thx!

Dick

Ashok Reddy

unread,
Jan 25, 2024, 7:28:24 AM1/25/24
to ansible...@googlegroups.com
Okay Dick and will provide the info . Thanks for your input.

--
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 ansible-proje...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages