CentOS Questions

  • Home
  • Centos
  • About
  • Contact

Error

Centos

Kubeadm join getting error getsockopt: no route to host

Kubeadm join getting error getsockopt: no route to host After installing the master node I went to add some nodes into our cluster and recieved an error. This is the error I received: [root@fuselaxnode2 ~]# kubeadm join 10.230.107.137:6443 –token TOKEN –discovery-token-ca-cert-hash sha256:SHA_HASH [preflight] Running pre-flight checks. [WARNING FileExisting-crictl]: crictl not Read more…

By Jeff Masud, 7 yearsMay 7, 2018 ago
Search
Recent Posts
  • Rook-Ceph crush map has legacy tunables (require firefly, min is hammer)
  • SSL connection has failed on cPanel Exim server
  • VMware vSphere Client 5.0 on Windows 10
  • Kubernetes 1.11 API certificate expired
  • NTP force time update
Categories
AMD Radeon Apache Centos Ceph Claymore Cpanel DNS Email Gitlab GPU Hard Drive Hyper-V iDRAC Iostat IPMI IPv6 Java Juniper Kernel Kubernetes Mining Nagios Nginx ntpd OSX Pfsense Prometheus Rook Rsync SAS SolusVM Sophos SSL Storage Ubuntu Uncategorized Varnish VirtualBox VMware Windows Server Wipefs WooCommerce WordPress Xen Yum
Archives
  • May 2021
  • March 2020
  • January 2020
  • September 2019
  • May 2019
  • February 2019
  • November 2018
  • October 2018
  • September 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • February 2017
  • About
  • Blog
  • Contact
  • Front Page
Hestia | Developed by ThemeIsle