• Home
  • Disclaimer
  • Contact
  • Archives
  • About
  • Subscribe
  • Support
  • Advertise

Kernel Talks

Unix, Linux, & Cloud!

  • How-to guides
    • Howto
    • Disk management
    • Configurations
    • Troubleshooting
  • OS
    • HPUX
    • Linux
  • Miscellaneous
    • Software & Tools
    • Cloud Services
    • System services
    • Virtualization
  • Certification Preparations
    • AWS Certified Solutions Architect – Associate
    • AWS Certified Solutions Architect – Professional
    • AWS Certified SysOps Administrator – Associate
    • AWS Certified Cloud Practitioner
    • Certified Kubernetes Administrator
    • Hashicorp Certified Terraform Associate
    • Oracle Cloud Infrastructure Foundations 2020 – Associate
  • Tips & Tricks
  • Linux commands
You are here: Home / Troubleshooting Errors

Troubleshooting Ansible errors

Published: January 17, 2020 | Modified: June 20, 2020



List of errors seen while working on Ansible and their solutions.

Let’s check errors you might come across in Ansible

Error

"msg": "Failed to connect to the host via ssh: ssh: connect to host 172.17.0.9 port 22: No route to host",

Cause and solution

Ansible control machine is not able to reach the client. Make sure client hostname is resolved via –

  • DNS server or
  • /etc/hosts of Ansible control server or
  • By /etc/ansible/hosts or your custom Ansible inventory file.

Also, network connectivity over port 22 from Ansible control machine to the client is working fine (test using telnet)


Error

"msg": "Failed to connect to the host via ssh: Permission denied (publickey,password).",

Cause and solution

Ansible control server is failed to authenticate the connection to the client.

  • Make sure you are using proper Ansible user for which password-less SSH is configured.
  • Test passwordless SSH to client from normal shell prompt and make sure its working fine.
⇠ Previous article
How to define Ansible default user
Next article ⇢
How to move /tmp on a separate disk as a separate mount point

Related stuff:

  • How to resolve mount.nfs: Stale file handle error
  • pvcreate error: Device /dev/xyz not found (or ignored by filtering).
  • networker service not starting
  • device eth0 does not seem to be present, delaying initialization error on Linux VM
  • mount.nfs: requested NFS version or transport protocol is not supported
  • How to troubleshoot RPC: Port mapper failure – Timed out error
  • MobaXterm X11 proxy: Authorisation not recognised
  • How to resolve the fatal error: curses.h: No such file or directory
  • check_mk error Cannot fetch deployment URL via curl error
  • Access denied error in NFS for root account
  • Issues while working on ELK stack
  • How to resolve aclocal: not found error in Ubuntu

Filed Under: Troubleshooting Errors Tagged With: Ansible error solution, Ansible issues, Ansible questions, List of Ansible issues

If you like my tutorials and if they helped you in any way, then

  • Consider buying me a cup of coffee via paypal!
  • Subscribe to our newsletter here!
  • Like KernelTalks Facebook page.
  • Follow us on Twitter.
  • Add our RSS feed to your feed reader.

Share Your Comments & Feedback: Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Get fresh content from KernelTalks

  • Email
  • Facebook
  • RSS
  • Twitter

Get Linux & Unix stuff right into your mailbox. Subscribe now!

* indicates required

This work is licensed under a CC-BY-NC license · Privacy Policy
© Copyright 2016-2023 KernelTalks · All Rights Reserved.
The content is copyrighted to Shrikant Lavhate & can not be reproduced either online or offline without prior permission.