HP-UX Desktop Troubleshooting Guide

# ps ef | grep X
If X is running, try the following xclock test to verify that the local X does not have
any problem. To invoke the xclock test, complete the following steps:
1. Establish a telnet connection to the HP Server.
2. Run the init 2 (or) /sbin/init.d/dtlogin.rc stop command.
3. grep for X and dtlogin process and kill them, if any.
4. Start X by running the /usr/bin/X11/X :0 & command.
5. Run the export DISPLAY=<HP Server IP>:0.0 command.
6. Run the xclock & command. A window with a real time clock image on the HP
Server graphics console appears.
If the xclock test case passes, it indicates that the local X does not have any problem.
If the above xclock test fails, repeat the same steps for xclock. Replace step Step 4
as
# /usr/bin/X11/X :0 -ac &. Check the existence of X.
If X starts, the problem may be related to authorization and further analysis is required.
5.1.5 Check problems related to DNS
Check the permissions of the /etc/hosts and /etc/nsswitch.conf files (the file
must have minimum read permissions for the owner, others, and the group). Also
check the /etc/nsswitch.conf file for the following entries, depending on the
version of the Operating System.
If the Operating System version is 11.11, check for the hosts entry in the
nsswitch.conf file.
This may be:
hosts: dns [NOTFOUND=continue] files : This indicates that DNS will first
try to resolve the hosts entry. If it is not able to do so, the /etc/hosts file will
be checked.
hosts: files [NOTFOUND=return] dns : This indicates that the /etc/hosts
file will be checked first to resolve the hosts entry. In this case, DNS will not
be checked if the /etc/hosts file is unable to resolve the entry.
If the Operating System version is 11.23 or higher, check for the following entries
in the nsswitch.conf file:
hosts entry may be:
hosts: dns [NOTFOUND=continue] files
hosts: files [NOTFOUND=return] dns
5.1 Troubleshooting the HP-Server Console 21