Welcome, Guest Login

Enterprise Support

Common ADAM Setup Issues

Last Updated: Jan 18, 2017 04:20PM CST

Installing ADAM on Head node:

    “bash: adam: command not found”

        - Be sure to 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 


Running “adam up” to create cluster:


  “adam.utils - DEBUG - Reason: Unable to load key as RSA/DSA/ECDSA”

        - Be sure path to local(head node) private key is correct and has permissions set to 600 on Mac/Linux

        $ ls -l ~/.ssh/id_rsa 

    “adam.utils - DEBUG - Reason: Authentication error to host”

        - Be sure you have added the head node users id_rsa.pub key to the host node user’s authorized_keys

        - Be sure that you have enabled ssh without password on host node for the user

        - Be sure permissions are correct on host node user’s ~/.ssh(700) and ~/.ssh/authorized_keys(600)
         $ chmod 700 ~/.ssh 
         $ chmod 600 ~/.ssh/authorized_keys 

        *Any changes to /etc/ssh/sshd_config will require restarting the sshd service

         $ sudo service sshd restart 

        *You can test Adam’s connection to your host node with the following:

         $ adam ssh -n my-cluster 

        *Each host node can be tested 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 - DEBUG - Opening SSH channel”

    “adam.utils - DEBUG - Running command | sudo -S bash -c ‘id’ |”

        -Be sure 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(if the user's name is AdamUser it would be "AdamUser    ALL=(ALL:ALL)    NOPASSWD:   ALL" for Ubuntu and "AdamUser    ALL=(ALL)    NOPASSWD:   ALL" for CentOS)


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

        -Be sure IPTables and SELinux are not blocking the connection on the host nodes:

         $ sudo iptables —flush 

        Edit the /etc/selinux/config file

         $ sudo vi /etc/selinux/config 

        Change to SELINUX=disabled. Save the file and reboot.

         $ reboot 

        Check that SELinux is disabled:

         $ sestatus 

        *After reboot you will need to flush iptables again.


seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found