From 5659946adff84bbf79556371dd37538503f8bd28 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Steenis Date: Fri, 14 Sep 2018 23:48:04 +0200 Subject: [PATCH] Add RKE troubleshooting and move SSH troubleshooting --- content/rke/v0.1.x/en/troubleshooting/_index.md | 6 ++++++ .../ssh-connectivity-errors}/_index.md | 14 ++++++++------ 2 files changed, 14 insertions(+), 6 deletions(-) create mode 100644 content/rke/v0.1.x/en/troubleshooting/_index.md rename content/{rancher/v2.x/en/installation/ha/rke-add-on/troubleshooting/ssh-tunneling => rke/v0.1.x/en/troubleshooting/ssh-connectivity-errors}/_index.md (75%) diff --git a/content/rke/v0.1.x/en/troubleshooting/_index.md b/content/rke/v0.1.x/en/troubleshooting/_index.md new file mode 100644 index 00000000000..e47db3d5079 --- /dev/null +++ b/content/rke/v0.1.x/en/troubleshooting/_index.md @@ -0,0 +1,6 @@ +--- +title: Troubleshooting +weight: 400 +--- + +* [SSH Connectivity Errors]({{< baseurl >}}/rke/v0.1.x/en/troubleshooting/ssh-connectivity-errors/) diff --git a/content/rancher/v2.x/en/installation/ha/rke-add-on/troubleshooting/ssh-tunneling/_index.md b/content/rke/v0.1.x/en/troubleshooting/ssh-connectivity-errors/_index.md similarity index 75% rename from content/rancher/v2.x/en/installation/ha/rke-add-on/troubleshooting/ssh-tunneling/_index.md rename to content/rke/v0.1.x/en/troubleshooting/ssh-connectivity-errors/_index.md index d9e2d477628..790bb241676 100644 --- a/content/rancher/v2.x/en/installation/ha/rke-add-on/troubleshooting/ssh-tunneling/_index.md +++ b/content/rke/v0.1.x/en/troubleshooting/ssh-connectivity-errors/_index.md @@ -1,8 +1,9 @@ --- -title: Failed to set up SSH tunneling for host -weight: 10 +title: SSH Connectivity Errors +weight: 100 aliases: -- /rancher/v2.x/en/installation/troubleshooting-ha/ssh-tunneling/ +- /rancher/v2.x/en/installation/ha/rke-add-on/troubleshooting/ssh-tunneling/ + --- ### Failed to set up SSH tunneling for host [xxx.xxx.xxx.xxx]: Can't retrieve Docker Info @@ -12,14 +13,14 @@ aliases: * User specified to connect with does not have permission to access the Docker socket. This can be checked by logging into the host and running the command `docker ps`: ``` -$ ssh user@server +$ ssh -i ssh_privatekey_file user@server user@server$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ``` See [Manage Docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) how to set this up properly. -* When using RedHat/CentOS as operating system, you cannot use the user `root` to connect to the nodes because of [Bugzilla #1527565](https://bugzilla.redhat.com/show_bug.cgi?id=1527565). You will need to add a separate user and configure it to access the Docker socket. See [Manage Docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) how to set this up properly. +* When using RedHat/CentOS as operating system, you cannot use the user `root` to connect to the nodes because of [Bugzilla #1527565](https://bugzilla.redhat.com/show_bug.cgi?id=1527565). You will need to add a separate user and configure it to access the Docker socket. See [Manage Docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) how to set this up properly. * SSH server version is not version 6.7 or higher. This is needed for socket forwarding to work, which is used to connect to the Docker socket over SSH. This can be checked using `sshd -V` on the host you are connecting to, or using netcat: ``` @@ -30,6 +31,7 @@ SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.10 #### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: Error configuring SSH: ssh: no key found * The key file specified as `ssh_key_path` cannot be accessed. Make sure that you specified the private key file (not the public key, `.pub`), and that the user that is running the `rke` command can access the private key file. +* The key file specified as `ssh_key_path` is malformed. Check if the key is valid by running `ssh-keygen -y -e -f private_key_file`. This will print the public key of the private key, which will fail if the private key file is not valid. #### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain @@ -37,7 +39,7 @@ SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.10 #### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: Error configuring SSH: ssh: cannot decode encrypted private keys -* If you want to use encrypted private keys, you should use `ssh-agent` to load your keys with your passphrase. If the `SSH_AUTH_SOCK` environment variable is found in the environment where the `rke` command is run, it will be used automatically to connect to the node. +* If you want to use encrypted private keys, you should use `ssh-agent` to load your keys with your passphrase. You can configure RKE to use that agent by specifying `--ssh-agent-auth` on the command-line, it will use the `SSH_AUTH_SOCK` environment variable in the environment where the `rke` command is run. #### Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?