Thank you for the print idea. I was able to trace it to the following
commands:
/usr/bin/facter --puppet –json
Looks like the version of facter doesn't like the --puppet option. WIll
probably have to look into uprading it.
Thanks again.
--
You received this message because you are
On 15.01.2020 00:53, Chris Thro wrote:
Thank you. I did the strace and it shows that it is just repeating the same
two lines over and over again.
select(7, [4 6], [], [4 6], {1, 0}) = 0 (Timeout)
wait4(29548, 0x7fff6a145c84, WNOHANG, NULL) = 0
When I checked the details of the select I get
Thank you. I did the strace and it shows that it is just repeating the same
two lines over and over again.
select(7, [4 6], [], [4 6], {1, 0}) = 0 (Timeout)
wait4(29548, 0x7fff6a145c84, WNOHANG, NULL) = 0
When I checked the details of the select I get the following:
lsof -p 10984 -ad 4,6
On 14.01.2020 00:46, Chris Thro wrote:
Out of hundreds of hosts we have one host always hangs when gathering
facts
when using become.
Create a playbook with the following:
- hosts: all
call the playbook with the -b flag
The last thing reported in the log is "Escalation succeeded".
No matter
Hi,
Problems I already encounter :
- NFS Stale
- rpm database corruption
- lock on lvm
Regards,
Jy
Le 14 janvier 2020 00:46:56 GMT+01:00, Chris Thro a
écrit :
>Out of hundreds of hosts we have one host always hangs when gathering
>facts
>when using become.
>
>Create a playbook with the
Out of hundreds of hosts we have one host always hangs when gathering facts
when using become.
Create a playbook with the following:
- hosts: all
call the playbook with the -b flag
The last thing reported in the log is "Escalation succeeded".
No matter how long I wait it never returns the