Appendix B. Troubleshooting ThinLinc
If inspecting /var/log/vsmagent.log on the server that was selected for the session does not reveal
the reason for the failure, there is a per-session log in
/var/opt/thinlinc/sessions/<username>/last/xinit.log where the output of commands
run during session startup is stored.
In very rare cases, it might also be neccesary to inspect the SSH log on the VSM agent.
B.2. Troubleshooting Specific Problems
B.2.1. Problems Where the Client Reports an Error
In the following sections, we will describe how to cope with problems where the ThinLinc client is
reporting an error.
B.2.1.1. Couldn’t set up secure tunnel to ThinLinc server. (Couldn’t establish
SSH tunnel, SSH terminated.)
This error is caused by failure to connect to the SSH daemon on the ThinLinc server (the server running
the VSM server). This could be caused by the fact that the SSH daemon is simply not running, or that it
is not letting the user in for some reason.
Another possible reason is that there is a firewall between the user and the ThinLinc server, that forbids
communication.
B.2.1.2. "Login Failed! Wrong username or password."
This error is very often caused simply by the user entering an incorrect password. Begin by verifying that
the user is actually entering the correct username and password.
If the username and password are correct and this is the first time the user tries to login, check the SSH
logs of the server. If SSH says that the user is invalid, that means that something is incorrect in the user’s
user information database entry. For example, this may happen if a user stored in eDirectory has two cn
attributes, one of them different than the other.
The getent command can be a valuable tool to dissect problems of this type. If the output of getent
passwd <username> doesn’t produce any output, that is a sign that the user is in fact invalid.
Note: Usernames beginning with numbers (for example 96aabbcc are parsed as numeric uids by
getent, rendering getent rather useless for debugging purposes in environments with username
schemes beginning with numbers.
If usernames with numbers in the beginning are in use, the following python code can be used to
verify a username
python-thinlinc -c ’import pwd, sys; print pwd.getpwnam(sys.argv[1])’ <username>
202
Comentarios a estos manuales