No value for $TERM and no -T specified No value for $TERM and no -T specified Warning: Permanently added 'cesg-node12.biochem.wisc.edu,10.0.0.12' (RSA) to the list of known hosts. ----------------------------------------------------------------------------- LAM attempted to execute a process on the remote node "cesg-node12.biochem.wisc.edu", but received some output on the standard error. LAM tried to use the remote agent command "/usr/bin/ssh" to invoke "echo $SHELL" on the remote node. This can indicate an authentication error with the remote agent, or can indicate an error in your $HOME/.cshrc, $HOME/.login, or $HOME/.profile files. The following is a list of items that you may wish to check on the remote node: - You have an account and can login to the remote machine - Incorrect permissions on your home directory (should probably be 0755) - Incorrect permissions on your $HOME/.rhosts file (if you are using rsh -- they should probably be 0644) - You have an entry in the remote $HOME/.rhosts file (if you are using rsh) for the machine and username that you are running from - Your .cshrc/.profile must not print anything out to the standard error - Your .cshrc/.profile should set a correct TERM type - Your .cshrc/.profile should set the SHELL environment variable to your default shell Try invoking the following command at the unix command line: /usr/bin/ssh -x cesg-node12.biochem.wisc.edu -n echo $SHELL You will need to configure your local setup such that you will *not* be prompted for a password to invoke this command on the remote node. No output should be printed from the remote node before the output of the command is displayed. When you can get this command to execute successfully by hand, LAM will probably be able to function properly. ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- lamboot encountered some error (see above) during the boot process, and will now attempt to kill all nodes that it was previously able to boot (if any). Please wait for LAM to finish; if you interrupt this process, you may have LAM daemons still running on remote nodes. ----------------------------------------------------------------------------- No value for $TERM and no -T specified No value for $TERM and no -T specified ----------------------------------------------------------------------------- It seems that there is no lamd running on this host, which indicates that the LAM/MPI runtime environment is not operating. The LAM/MPI runtime environment is necessary for the "mpirun" command. Please run the "lamboot" command the start the LAM/MPI runtime environment. See the LAM/MPI documentation for how to invoke "lamboot" across multiple machines. ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- It seems that there is no lamd running on this host, which indicates that the LAM/MPI runtime environment is not operating. The LAM/MPI runtime environment is necessary for the "lamhalt" command. Please run the "lamboot" command the start the LAM/MPI runtime environment. See the LAM/MPI documentation for how to invoke "lamboot" across multiple machines. -----------------------------------------------------------------------------