Welcome, Guest Login

Enterprise Support

Common ADAM Setup Issues

Last Updated: Dec 01, 2017 09:56AM CST
The following issues may occur while installing Adam on a Head node.

Issue:
 
“bash: adam: command not found”


Solution:

Add the adam command to your PATH and reload the .bashrc file:
echo -e ‘\n# Anaconda Adam\nexport PATH=~/adam/bin:$PATH’ >> ~/.bashrc
source ~/.bashrc


Issue:

“adam.utils produces the following error while creating a cluster:
DEBUG - Reason: Unable to load key as RSA/DSA/ECDSA”


Solution:

Check that the path to local(head node) private key is correct and has permissions set to 600 on macOS and Linux:
ls -l ~/.ssh/id_rsa “adam.utils


Issue:
 
DEBUG - Reason: Authentication error to host”


Solution:
 
  1. Add the head node users key id_rsa.pub to the host node user’s authorized_keys.

  2. Enable SSH without password on host node for the user.

  3. Permissions should be correct on host node user’s ~/.ssh(700) and ~/.ssh/authorized_keys(600):
    chmod 700 ~/.ssh
    chmod 600 ~/.ssh/authorized_keys

  4. Any changes to /etc/ssh/sshd_config file require restarting the sshd service:
    sudo service sshd restart

  5. Test Adam’s connection to your host node with the following:
    adam ssh -n my-cluster

  6. Test each host node by adding the number of the host in the ~/.continuum/adam/profile.d/profile.yaml file. The list number starts at zero for the first entry as increments down:
    adam ssh -n my-cluster 0
    adam ssh -n my-cluster 1 “adam.utils

Issue:
 
DEBUG - Opening SSH channel” “adam.utils
- DEBUG - Running command | sudo -S bash -c ‘id’ |”


Solution:

Check that you have enabled the host node user to use sudo without a password or have provided the sudo password in your cluster.yaml file. This can be done by adding the user to the /etc/sudoers file.

Ubuntu Example: For a user named AdamUser AdamUser ALL=(ALL:ALL) NOPASSWD: ALL
CentOS Example: AdamUser ALL=(ALL) NOPASSWD: ALL 

Issue:
 
ERROR: Could not connect to salt REST server: HTTP Error 503: Service Unavailable


Solution:
 
  1. Check that IPTables and SELinux are not blocking the connection on the host nodes:
    sudo iptables —flush

  2. Check that SELINUX is in disabled mode. Using either root or sudo acces, edit the file /etc/sysconfig/selinux:
    sudo vi /etc/selinux/config

    NOTE: You must reboot for the changes to take effect.

    To verify that SELinux is disabled, run:
    sestatus
support@continuum.io
https://cdn.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete