Ansible gather facts fails [closed]
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I manage my servers with ansible, with some servers I get the following error message.
Of course I could simply disable Gathering Facts, but for some Playbooks I need to detect some system specific elements.
TASK [Gathering Facts] ***********************************************************************************************************************************************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TimeoutError: Timer expired after 10 seconds
fatal: [XXXXX]: FAILED! => "changed": false, "cmd": "/sbin/udevadm info --query property --name /dev/md2", "msg": "Timer expired after 10 seconds", "rc": 257
to retry, use: --limit @/home/xxxx/telegraf/test.retry
linux udev ansible
closed as unclear what you're asking by Jeff Schaller, Stephen Kitt, thrig, G-Man, Thomas Nov 29 at 10:47
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
0
down vote
favorite
I manage my servers with ansible, with some servers I get the following error message.
Of course I could simply disable Gathering Facts, but for some Playbooks I need to detect some system specific elements.
TASK [Gathering Facts] ***********************************************************************************************************************************************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TimeoutError: Timer expired after 10 seconds
fatal: [XXXXX]: FAILED! => "changed": false, "cmd": "/sbin/udevadm info --query property --name /dev/md2", "msg": "Timer expired after 10 seconds", "rc": 257
to retry, use: --limit @/home/xxxx/telegraf/test.retry
linux udev ansible
closed as unclear what you're asking by Jeff Schaller, Stephen Kitt, thrig, G-Man, Thomas Nov 29 at 10:47
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
@user323246 did you delete your account after posting this?
– Jeff Schaller
Nov 28 at 16:16
Does the target server have a /dev/md2? It's apparent that it timed out, but did you not expect that or does it need more time to complete?
– Jeff Schaller
Nov 28 at 16:39
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I manage my servers with ansible, with some servers I get the following error message.
Of course I could simply disable Gathering Facts, but for some Playbooks I need to detect some system specific elements.
TASK [Gathering Facts] ***********************************************************************************************************************************************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TimeoutError: Timer expired after 10 seconds
fatal: [XXXXX]: FAILED! => "changed": false, "cmd": "/sbin/udevadm info --query property --name /dev/md2", "msg": "Timer expired after 10 seconds", "rc": 257
to retry, use: --limit @/home/xxxx/telegraf/test.retry
linux udev ansible
I manage my servers with ansible, with some servers I get the following error message.
Of course I could simply disable Gathering Facts, but for some Playbooks I need to detect some system specific elements.
TASK [Gathering Facts] ***********************************************************************************************************************************************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TimeoutError: Timer expired after 10 seconds
fatal: [XXXXX]: FAILED! => "changed": false, "cmd": "/sbin/udevadm info --query property --name /dev/md2", "msg": "Timer expired after 10 seconds", "rc": 257
to retry, use: --limit @/home/xxxx/telegraf/test.retry
linux udev ansible
linux udev ansible
edited Nov 28 at 16:22
Jeff Schaller
37.2k1052121
37.2k1052121
asked Nov 28 at 15:19
user323246
closed as unclear what you're asking by Jeff Schaller, Stephen Kitt, thrig, G-Man, Thomas Nov 29 at 10:47
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as unclear what you're asking by Jeff Schaller, Stephen Kitt, thrig, G-Man, Thomas Nov 29 at 10:47
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
@user323246 did you delete your account after posting this?
– Jeff Schaller
Nov 28 at 16:16
Does the target server have a /dev/md2? It's apparent that it timed out, but did you not expect that or does it need more time to complete?
– Jeff Schaller
Nov 28 at 16:39
add a comment |
@user323246 did you delete your account after posting this?
– Jeff Schaller
Nov 28 at 16:16
Does the target server have a /dev/md2? It's apparent that it timed out, but did you not expect that or does it need more time to complete?
– Jeff Schaller
Nov 28 at 16:39
@user323246 did you delete your account after posting this?
– Jeff Schaller
Nov 28 at 16:16
@user323246 did you delete your account after posting this?
– Jeff Schaller
Nov 28 at 16:16
Does the target server have a /dev/md2? It's apparent that it timed out, but did you not expect that or does it need more time to complete?
– Jeff Schaller
Nov 28 at 16:39
Does the target server have a /dev/md2? It's apparent that it timed out, but did you not expect that or does it need more time to complete?
– Jeff Schaller
Nov 28 at 16:39
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
@user323246 did you delete your account after posting this?
– Jeff Schaller
Nov 28 at 16:16
Does the target server have a /dev/md2? It's apparent that it timed out, but did you not expect that or does it need more time to complete?
– Jeff Schaller
Nov 28 at 16:39