Troubleshooting VNC
From FarmShare
(Difference between revisions)
(→Authentication) |
|||
Line 5: | Line 5: | ||
== Authentication == | == Authentication == | ||
- | Likewise, vncserver may not start if you do not have a valid Kerberos ticket and AFS tokens. Try re-authenticating before starting VNC. | + | Likewise, vncserver may not start if you do not have a valid Kerberos ticket and [[AFS]] tokens. Try re-authenticating before starting VNC. |
<pre>kinit && aklog</pre> | <pre>kinit && aklog</pre> | ||
+ | |||
== Resetting the shell configuration == | == Resetting the shell configuration == | ||
Revision as of 13:20, 26 April 2012
Contents |
Quota conditions
vncserver may not start if you are over your AFS quota.
Authentication
Likewise, vncserver may not start if you do not have a valid Kerberos ticket and AFS tokens. Try re-authenticating before starting VNC.
kinit && aklog
Resetting the shell configuration
Some kinds of changes to ~/.cshrc and ~/.login (or other shell configuration files) may break VNC; in particular, setting up the environment for certain applications (e.g., Cadence) according to instructions is known to cause problems. You can restore the default shell configuration by running updaterc.
/usr/pubsw/bin/updaterc
Resetting VNC state and configuration
A common troubleshooting method is to reset the VNC configuration by deleting the ~/.vnc application directory.
rm -rf ~/.vnc mkdir ~/.vnc vncpasswd
Search the farmshare-discuss archives for posts about VNC.