Sounds like you have sketchy DNS then? Might want to look into that...
On Fri, Dec 13, 2013 at 10:44 AM, Drew Decker <[email protected]>wrote: > Just to short hostnames. > > *Prior to FQDN:* > > host1 > host2 > host3 > > (resolv.conf had the search domains) - regular SSHing into machines > worked, but ansible was either slow or never returned a value on “-m ping”. > > *After adding FQDN:* > > host1.domain.com > host2.domain.com > host3.domain.com > > (resolv.conf still has the search domains, but aren’t needed for Ansible > now because I’m using the FQDN) - huge performance increase and no more > failures. > > -- > Drew Decker > Sent with Airmail > > On December 13, 2013 at 9:41:33 AM, James Tanner > ([email protected]<//[email protected]>) > wrote: > > What was in the hosts file prior to the FQDNs ? > > On 12/13/2013 10:38 AM, Drew Decker wrote: > > So, it appears that I’ve figured it out - but don’t really understand why > exactly. As you can see from my previous threads that I was able to SSH > into the host, but Ansible just wouldn’t return anything for a random host, > correct? Another thing I noticed was it was also a bit slow. In our > environment, we have about 4 main domains, for different locations. In the > /etc/resolv.conf file, we have search domains defined so we can use the > short hostnames that are in DNS. This doesn’t appear to have any issues > whatsoever, except sometimes in Ansible; not sure why. > > What I ended up doing was adding the FQDN into the /etc/ansible/hosts > file to each host, and when I did that I got a HUGE performance increase > and I also no longer run into this problem. > > -- > Drew Decker > Sent with Airmail > > On December 12, 2013 at 9:04:19 PM, Drew Decker > ([email protected]<//[email protected]>) > wrote: > > I don't get much with "-vvv" and I've also removed "-s": > > It still hangs and this is the output (after several minutes of waiting > for it to do something): > > $ ansible host -u ddecker -m raw -a "ls" -vvvv > <host> ESTABLISH CONNECTION FOR USER: ddecker > <host> EXEC ['ssh', '-tt', '-vvv', '-o', 'ControlMaster=auto', '-o', > 'ControlPersist=60s', '-o', > 'ControlPath=/home/ddecker/.ansible/cp/ansible-ssh-%h-%p-%r', '-o', > 'Port=22', '-o', 'KbdInteractiveAuthentication=no', '-o', > 'PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey', > '-o', 'PasswordAuthentication=no', '-o', 'ConnectTimeout=10', 'host', 'ls'] > Traceback (most recent call last): > File "/home/ddecker/ansible/bin/ansible", line 157, in <module> > (runner, results) = cli.run(options, args) > File "/home/ddecker/ansible/bin/ansible", line 131, in run > results = runner.run() > File "/home/ddecker/ansible/lib/ansible/runner/__init__.py", line 992, > in run > results = [ self._executor(h, None) for h in hosts ] > File "/home/ddecker/ansible/lib/ansible/runner/__init__.py", line 394, > in _executor > exec_rc = self._executor_internal(host, new_stdin) > File "/home/ddecker/ansible/lib/ansible/runner/__init__.py", line 485, > in _executor_internal > return self._executor_internal_inner(host, self.module_name, > self.module_args, inject, port, complex_args=complex_args) > File "/home/ddecker/ansible/lib/ansible/runner/__init__.py", line 685, > in _executor_internal_inner > result = handler.run(conn, tmp, module_name, module_args, inject, > complex_args) > File "/home/ddecker/ansible/lib/ansible/runner/action_plugins/raw.py", > line 47, in run > result=self.runner._low_level_exec_command(conn, module_args, tmp, > sudoable=True, executable=executable) > File "/home/ddecker/ansible/lib/ansible/runner/__init__.py", line 771, > in _low_level_exec_command > rc, stdin, stdout, stderr = conn.exec_command(cmd, tmp, sudo_user, > sudoable=sudoable, executable=executable) > File > "/home/ddecker/ansible/lib/ansible/runner/connection_plugins/ssh.py", line > 221, in exec_command > rfd, wfd, efd = select.select(rpipes, [], rpipes, 1) > KeyboardInterrupt > > On Thursday, December 12, 2013 8:18:42 PM UTC-6, Brian Coca wrote: >> >> also -vvv is helpful when debugging. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Ansible Project" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ansible-project/KyKeJ_-JGSQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Ansible Project" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ansible-project/KyKeJ_-JGSQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Michael DeHaan <[email protected]> CTO, AnsibleWorks, Inc. http://www.ansibleworks.com/ -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
