HP-UX Desktop Troubleshooting Guide Published: May 2010 Edition: 2
© Copyright 2010 Hewlett-Packard Development Company, L.P. Legal Notice © 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Table of Contents 1 Introduction................................................................................................................................7 1.1 Abstract...........................................................................................................................7 1.2 Intended Audience..........................................................................................................7 1.3 Related Documentation..........................................................
7.2.1.1 For Xf86.........................................................................................................30 7.2.1.2 For Xhp..........................................................................................................32 7.2.2 Error due to Input Devices....................................................................................32 7.2.2.1 Mouse as input device..................................................................................32 7.2.2.1.
List of Figures 5-1 7-1 7-2 7-3 Troubleshooting the HP-Server Console.....................................................................19 X start-up Flow............................................................................................................28 Xserver Startup............................................................................................................29 Xserver Troubleshooting Techniques..........................................................................
List of Tables 7-1 7-2 6 Supported Graphics Cards..........................................................................................30 USB-Mouse Relationship............................................................................................
1 Introduction 1.1 Abstract This troubleshooting guide is based on the problems reported against CDE and X/Motif products. The nature of problems received by the CDEXM team have been associated with the startup function of CDE or Xserver. Problems such as CDE or Xserver not coming up on either the remote system or on the console are common. These problems are generally associated with customizations either in network configuration files or CDE/Xserver related configuration files.
1.5 Terms and Definitions Terms Definitions CDE Common Desktop Environment HP Hewlett-Packard X Xserver DNS Domain Name Server NIS Network Information System XDS X Display Manager XDMCP X Display Manager Control Protocol Prepared by Name Lavleen Kumar Bansal Email ID kumar-bansal.lavleen@hp.com Updated by Name 8 Email ID Dhruv Sabharwal dhruv.sabharwal@hp.com Deepak Jha jha.deepak@hp.com Anil Roundhal anil.roundhal@hp.
2 Overview 2.1 Problem Statement Most of the problems faced by customers on the HP-UX desktop are configuration-related, such as, CDE or Xserver not coming up due to incorrect customization of network or desktop configuration files. These problems usually occur either because of lack of knowledge of the customer or due to human errors. This guide attempts to address these common problems and provide solutions. 2.
3 Basic System Checks This document provides troubleshooting tips to resolve problems commonly encountered by CDE users. However, we strongly recommend that the below-mentioned basic system checks must be performed before proceeding to detailed troubleshooting techniques. 1. Ping the HP Server from the remote machine.
4 Troubleshooting on the Remote System This section covers various troubleshooting techniques for problems related to startup of CDE on a remote system. Also mentioned below are some of the common error messages encountered while invoking CDE on a remote system running an X manager such as ReflectionX or eXcursion. This section also enlists troubleshooting techniques for problems related to startup of CDE due to network issues such as problems related to IP address, hostname, and DNS. 4.
“The specified XDM host is unwilling to manage” This message is commonly encountered when there is a configuration problem. The configuration problem is generally with files such as Xconfig file, Xaccess file, and so on. — Xconfig Configuration The Xconfig file is either located at /etc/dt/config/ or /usr/dt/config/. Xconfig will have a reference to the Xaccess file. Check the Xconfig file in the /etc/dt/config directory first, and then check in the /usr/dt/config file. The reference must be: Dtlogin.
— Xaccess Configuration The Xaccess file is either located at /etc/dt/config/ or /usr/dt/config/. In Xaccess file, the following lines must be uncommented: ◦ # grant service to all remote displays CHOOSER BROADCAST # any indirect host can get a chooser Check the Xaccess file in the /etc/dt/config directory first, then check in the /usr/dt/config file. # # * # # # # # # * # ######################################################################### Entries...
1. dtlogin parent process may not be running on the HP server. — Check for the existence of dtlogin parent process by executing the following command: # ps –ef | grep dtlogin — If the process does not exist, start the dtlogin process by executing the following command and re-check the status: # /sbin/init.d/dtlogin.rc start — If the dtlogin process is started, it may have been possible that the auto-start option of dtlogin was disabled.
4.3.2 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 entry according to the operating system version: • If the operating system version is 11.11, check for the hosts entry in the nsswitch.conf file.
If, the above-mentioned troubleshooting techniques are followed and CDE still does not come up, the /etc/dt/config/Xconfig, /etc/dt/config/Xaccess, /etc/dt/config/Xservers, and /etc/dt/config/Xsession.d files need to be analyzed further.
5 Troubleshooting on the HP-Server This section describes troubleshooting tips for problems related to the startup of the HP-Server console.
5.1 Troubleshooting the HP-Server Console 5.1.1 Check configuration entries in the Xservers and Xconfig file 1. Xservers configuration The Xservers file is located either in the /etc/dt/config/ directory or in the /usr/dt/config directory. Check if the entry Local local@console /usr/bin/X11/X :0 is uncommented in the Xservers file present in either of the directories. # ########################################################################## # 108 * Local local@console /usr/bin/X11/X :0 2.
# 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. 2. 3. 4. 5. 6. Establish a telnet connection to the HP Server. Run the init 2 (or) /sbin/init.d/dtlogin.rc stop command. grep for X and dtlogin process and kill them, if any. Start X by running the /usr/bin/X11/X :0 & command. Run the export DISPLAY=:0.0 command. Run the xclock & command.
The ipnodes entry may be as follows: — ipnodes: dns [NOTFOUND=continue] files — ipnodes: files [NOTFOUND=return] dns. NOTE: Gr8 reference call: http://gr8.mvlabs.corp.hp.com/gr8/stable/callEdit.pl?call=4000142281 For a similar problem related to DNS, please refer the above link. • Check the entries in the /etc/resolv.conf file. Ensure that the following entries are correct if you are using DNS: — domain — nameserver 5.1.
If the above-mentioned command is not displayed, it indicates that the rpcbind process is not running. To start the rpcbind process, execute the # /usr/sbin/rpcbind –w warmstartup command. Once the above-mentioned procedures are followed, run: • • # init 2 # init 3 NOTE: GR8 reference call: http://gr8.mvlabs.corp.hp.com/gr8/stable/callEdit.pl?call=4000142281 For a similar problem as dthello screen, please refer the above link. 5.1.
6 Generic Log Files for CDE Apart from the above-mentioned troubleshooting techniques, there are a few log files that can be checked for analysis. These log files contain useful information, which can help in resolving startup issues related to CDE. Some of the most common files are dtlogin.debug, errorlog, syslog.log, and startlog. Dtlogin..debug This file contains the runtime log of the dtlogin process. The dtlogin process must be started in the debuggable mode to create this file.
7 Troubleshooting Techniques for Xserver This section describes the commonly encountered problems related to Xserver start-up and the troubleshooting techniques one needs to follow in case there are problems related to start-up of Xserver. This section discusses the following topics: 1. X start-up Flow This section elaborates on the manual and automatic start-up of the Xserver.
Figure 7-1 X start-up Flow The X loader binary starts the particular Xserver (Xf86, Xhp or Xvfb) depending upon various parameters and checks. Following are these parameters: 1. The X loader searches for the /etc/X11/Xstart file and tries to read its entry. It will attempt to run the Xserver whose entry is mentioned in this file. A sample Xstart file is as follows: Xf86 :0 2.
Figure 7-2 Xserver Startup The Xserver binary can also be run manually. You can run the X loader by issuing the following command: # /usr/bin/X11/X :display_num (where display_num can be any integer (typically 0)) The X loader will then run the appropriate Xserver as described above. In addition, one can also run the individual Xserver binary manually.
NOTE: Xvfb does not require either graphics card or input devices for its working, so the above mentioned points are not applicable for Xvfb 7.2.1 Error due to unsupported graphics card The Xserver may fail to start if it does not find any of the supported graphics card on the system for the particular Xserver you are trying to run. For information on supported graphics cards, see Table 7-1: Supported Graphics Cards.
# rm –rf /dev/gvid* • Reboot the system (and restart X manually if it does not restart automatically). This will automatically create the device files. Check the entries of the above device files in /etc/X11/XF86Config file. The “Device” section of the configuration file should have the corresponding device file names. For more information on this, see Graphics Administration Guide (GAG). Figure 7-3 is a pictorial representation of this process: Figure 7-3 Xserver Troubleshooting Techniques 7.
7.2.1.2 For Xhp 1. Check if the legacy HP device (typically HP VISUALIZE-FXE card(s)) are available on the system with the following command: # ioscan -kd graph3 This command lists the legacy graphics device(s) connected to the system. If there is no legacy card connected to the system then you cannot run Xhp on the system unless you run this as a print server. For more information on running Xhp as print server, see GAG. 2.
Table 7-2 USB-Mouse Relationship OS Version 11.23 PA or lower 11.23 IPF 11.31 PA 11.
Although Xf86 and Xhp both require some basic information from these start-up files, yet sometimes you may not see Xhp failing to start due to improper configuration files. Xhp for its start-up requires only default information and if it finds it will start successfully. Xf86 however may fail to start because of one of the following errors due to improper entries in /etc/X11/XF86Config file: • • Screen not found Device not found Use SAM/SMH to re-create configuration files in case of any errors. 7.2.
8 Generic Log Files for Xserver Apart from the above-mentioned troubleshooting techniques, there are a few log files that can be checked for analysis. These log files contain useful information, which can help in resolving startup issues related to Xserver. Some of the most common files are /var/dt/Xerrors, /var/X11/Xserver/logs/X*.log (Xf86.log, X0.log etc...), /var/X11/Xserver/logs/Xstartup.0.log. /var/dt/Xerrors X startup errors are logged in this file. /var/X11/Xserver/logs/X*.
9 Summary The above-mentioned troubleshooting techniques are intended to help the RCE or CDEXM lab engineers to resolve the commonly faced problems related to the HP-UX desktop. So it is recommended that the steps mentioned in the guide be performed and all the relevant suggested solutions must be examined before analyzing the problem in detail. This guide is, however, not comprehensive and there may be new or unknown problems that have not been documented here.
