|
||||||
|
||||||
|
User Information Home
 NCSA's Help Desk is available 24 hours a day, seven days a week, 365 days a year: NCSA SSH TroubleshootingIf you are having problems with SSH then try running the command with the -v option. This will give you a verbose output of the session and can help in figuring out the problem. Afer running ssh with the verbose switch look at the output for errors or warnings. Below is a list of items that you may come across in the verbose listing.
No xauth data: no xauth program was found at configure time. The problem is that the sshd process on the machine you are trying to connect to cannot find the xauth binary. Be sure that the path to the xauth binary is in your path, it's usually in /usr/X11R6/bin.
Failed to get local xauth data. This is common when your home directory resides in AFS on the remote machine. In this case the sshd process it is trying to run xauth and modify your .Xauthority file on the machine you are trying to connect to. However, it cannot modify it because you do not have a token on the remote machine. If you have a valid Kerberos 5 ticket that is passed, or you are using password authentication the you will need to contact us because the machine is not getting you a valid AFS token. Another option is to turn off ForwardX11 in your ~/.ssh/ssh_config file if you are not going to be forwarding X11 clients.
<user>'s password: This is most commonly from typing in the wrong password. Make sure that you are typing in your correct Kerberos(AFS) password. If you are still having problems then contact us.
ld.so.1: ssh: fatal: libucb.so.1: can't open file: errno=2 This problem occurs on Solaris machines and it is because it cannot find certain libraries it needs. Run the following command to add a path to your LD_LIBRARY_PATH environment variable: % setenv LD_LIBRARY_PATH "$LD_LIBRARY_PATH":/usr/ucblibAlso be sure to add the /usr/ucblib to your LD_LIBRARY_PATH
environment variable in your .cshrc file.
|
||||||
|
|
||||||
