Troubleshooting VNC
From FarmShare
(Difference between revisions)
| Line 1: | Line 1: | ||
| + | == Quota conditions == | ||
| + | |||
| + | '''vncserver''' may not start if you are over your [[AFS|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. | ||
| + | <pre>kinit && aklog</pre> | ||
== Resetting the shell configuration == | == 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|Cadence]]) according to instructions is known to cause problems. You can restore the default shell configuration by running '''updaterc'''. | + | 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|Cadence]]) according to instructions is known to cause problems. You can restore the default shell configuration by running '''updaterc'''. |
<pre>/usr/pubsw/bin/updaterc</pre> | <pre>/usr/pubsw/bin/updaterc</pre> | ||
== Resetting VNC state and configuration == | == Resetting VNC state and configuration == | ||
| - | A common troubleshooting method is to reset the VNC configuration by deleting the ~/.vnc application directory. | + | A common troubleshooting method is to reset the VNC configuration by deleting the ~/.vnc application directory. |
<pre>rm -rf ~/.vnc | <pre>rm -rf ~/.vnc | ||
mkdir ~/.vnc | mkdir ~/.vnc | ||
Revision as of 12:27, 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.
