Thanks for your response. Sorry for not being sure... But you're saying I'm calling an executable via a pipe lookup ... And I have no idea what that means. I'm certainly not doing it intentionally. You ask me to validate "the binary is there" but I don't know what binary to look for.
Is this happening during the "Gathering Facts" or afterward? Is the error happening on the local side or the remote side? On Tuesday, June 3, 2014 11:56:21 AM UTC-4, James Cammarata wrote: > > Correct, the warning message can be ignored, and there is a configuration > setting (system_warnings in your ansible.cfg) that can be set to "False" to > disable it. > > The fatal error appears to be reporting that the executable you're trying > to call via the pipe lookup is not being found at the path specified. Can > you share what that is, and validate that the binary is there and > executable by the user that the play is running with to make sure there are > no security issues? > > > On Tue, Jun 3, 2014 at 8:34 AM, Daniel Ottey <[email protected] > <javascript:>> wrote: > >> A couple errors have recently cropped up when using Ansible, and the >> latest is causing me to not be able to use it at all. I tried searching >> for the fatal error(s), but was not able to find anythin mysef, I'm >> hopeful that this forum can help me out. >> >> My OS is RHEL 6.4 and it also pulls packages from EPEL. My ansible is >> "ansible 1.5.5" from EPEL. >> >> *Command:* >> >> ANSIBLE_SSH_ARGS="" ansible-playbook -T 30 -c ssh -s -K -i >> ~/my_ansible_inventory.txt -l labadmin.lab.boomi.com --tags zabbix-agent >> /etc/ansible/site.yml >> >> >> The first warning message I have been able to find documented elsewhere, >> and I think it is not related to the fatal error. >> >> *Warning:* >> >> /usr/lib64/python2.6/site-packages/pycrypto-2.6.1-py2.6-linux-x86_64.egg/Crypto/Util/number.py:57: >> >> PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using >> libgmp >= 5 to avoid timing attack vulnerability. >> _warn("Not using mpz_powm_sec. You should rebuild using libgmp >= 5 to >> avoid timing attack vulnerability.", PowmInsecureWarning) >> sudo password: >> >> >> So I think from what I read elsewhere that I can ignore that warning >> until the version of libgmp is updated. >> >> *But here is the fatal error:* >> >> PLAY [apply common configuration to all nodes] >> ******************************** >> >> GATHERING FACTS >> *************************************************************** >> fatal: [labadmin.lab.boomi.com] => Traceback (most recent call last): >> File "/usr/lib/python2.6/site-packages/ansible/runner/__init__.py", >> line 532, in _executor >> exec_rc = self._executor_internal(host, new_stdin) >> File "/usr/lib/python2.6/site-packages/ansible/runner/__init__.py", >> line 564, in _executor_internal >> module_vars = template.template(self.basedir, self.module_vars, >> host_variables) >> File "/usr/lib/python2.6/site-packages/ansible/utils/template.py", line >> 349, in template >> d[k] = template(basedir, v, vars, lookup_fatal, depth, expand_lists, >> fail_on_undefined=fail_on_undefined) >> File "/usr/lib/python2.6/site-packages/ansible/utils/template.py", line >> 331, in template >> m = _legacy_varFind(basedir, varname, vars, lookup_fatal, depth, >> expand_lists) >> File "/usr/lib/python2.6/site-packages/ansible/utils/template.py", line >> 245, in _legacy_varFind >> replacement = instance.run(args, inject=vars) >> File >> "/usr/lib/python2.6/site-packages/ansible/runner/lookup_plugins/pipe.py", >> line 35, in run >> p = subprocess.Popen(term, cwd=self.basedir, shell=False, >> stdin=subprocess.PIPE, stdout=subprocess.PIPE) >> File "/usr/lib64/python2.6/subprocess.py", line 642, in __init__ >> errread, errwrite) >> File "/usr/lib64/python2.6/subprocess.py", line 1234, in _execute_child >> raise child_exception >> OSError: [Errno 2] No such file or directory >> >> >> FATAL: all hosts have already failed -- aborting >> >> PLAY RECAP >> ******************************************************************** >> to retry, use: --limit @/home/dottey/site.retry >> >> labadmin.lab.boomi.com : ok=0 changed=0 unreachable=1 >> failed=0 >> >> >> Any insight into what is causing the fatal error - and if there is >> anything I can do to resolve it? >> >> -- >> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ansible-project/52b74376-888b-4423-a56b-42da16f7d4a5%40googlegroups.com >> >> <https://groups.google.com/d/msgid/ansible-project/52b74376-888b-4423-a56b-42da16f7d4a5%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/e6a15408-3b47-4f9d-9d2d-3cfeafd0299f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
