Dell Wyse Enhanced Ubuntu Linux T50 Manual de usuario Pagina 213

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 220
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 212
Appendix B. Troubleshooting ThinLinc
B.2.1.3. The SSH connection succeeded, but the ThinLinc server connection
failed.Perhaps this server doesn’t run a ThinLinc server?
This error is most often caused by the fact that the VSM server is not running on the server. Start the
VSM server and try again.
A user entering the wrong hostname, for example the hostname of one of the VSM agents, would also
get this error message. Check that the user has entered the correct hostname. In very rare cases, this
could also be caused by incorrect DNS data.
B.2.1.4. ThinLinc login failed. (Couldn’t create session on selected server)
Check the VSM server log to see which VSM agent was selected. Check the VSM agent log on the
selected server to see what happened.
One common reason for this error is that the user database on the selected server is failing, so the user
does exist on the VSM server, but not on the VSM agent.
B.2.1.5. ThinLinc login failed. (Cannot find any working terminal server).
This error is reported if there were no working VSM agents available according to the load balance
information in the VSM server.
In a system with few VSM agent servers, restoring a VSM agent that has been down for some reason
doesn’t take effect immediately - the load balance information is only updated once every 40 seconds by
default. Either wait for the load balance cycle to complete, or restart the VSM server. In a small cluster it
might be a good idea to lower the load balance cycle, by setting the parameter
/vsmserver/load_balance_cycle.
The load balance information can be inspected in the ThinLinc Web Administration, see Chapter 16.
B.2.1.6. ThinLinc login failed (The terminal server couldn’t create your session)
When this error occurs, the user was valid on the VSM server, but for some reason, the session couldn’t
be created on the VSM agent.
One very common reason for this problem is that the VSM agent has lost its connection to the user
database backend (LDAP, Windows domain or other database), so the user exists on the VSM server, but
not on the VSM agent. If this is the case, the VSM agent log on the selected server will clearly state that
the user doesn’t exist on the system.
Another very common reason is home directory trouble on the VSM agent. Verify that the home
directory exists on the selected server, and that it is owned by the correct uidNumber/gidNumber. Of
course, the user must have write permissions on his/her home directory.
To verify that the home directory works, the following command can be used:
ssh <username>@<agenthost> touch .
If the home directory is correctly mounted and writable by the user, the above command will not produce
any output except the password question.
203
Vista de pagina 212

Comentarios a estos manuales

Sin comentarios