CDE Hangs on Blue Screen or dtmessaging Does Not Start
The Common Desktop Environment (CDE) hangs on the blue screen or you cannot
When CDE is initialized, it must be able to resolve
its hostname, ensure that it has access to all hosts, and resolve those hosts
defined for the system.
- Who is affected? If all users are not affected, first check the following list.
- Filespace in /home and /var
- Permissions on /dev/null (666)
- Permissions on /dev/lft0 (666)
- Permissions on /dev/tty (666)
- Permissions on /dev/console (622)
- Permissions on /etc/resolv.conf (644)
- Permissions on /usr/dt/bin files
- Check the bold commands and filenames on the left side
of the list below and compare the output on your machine with the corresponding
information on the right.
- df - Check for full filesystems.
- hostname - Should return hostname of machine.
- host <hostname> - Should return fully qualified machine name and IP address.
- host <IP address> - Should return fully qualified machine name and IP address.
- uname -n - Should return hostname.
- ping <hostname> - Should be pingable, check for packet loss.
- ping <IP address> - Should be pingable, check for packet loss.
- host loopback - Should return localhost is 127.0.0.1.
- host 127.0.0.1 - Should return localhost is 127.0.0.1.
- ping loopback - Should be able to ping - check for packet loss.
- ping 127.0.0.1 - Should be able to ping - check for packet loss.
- /etc/hosts - Check for duplicate/erroneous entries and permissions.
- /etc/resolv.conf - Nameserver should be pingable.
- /etc/netsvc.conf - This file may or may not be present, check for typing errors.
In this file, nsorder should be hosts=local,bind
- /etc/X0.hosts - This file may or may not be present, if it is move it to X0.hosts.old.
- netstat -in - Check to ensure no interfaces have an "*" (asterisk).
- lssrc -s inetd - Should be active.
- lssrc -s portmap - Should be active.
- lssrc -g tcpip - Check to see what TCP/IP deamons are running.
- If checking the preceding commands or files does not resolve the problem,
look for errors in the following files:
- If no errors exist in the preceding files, your system may have an
environmental setting that is prohibiting the login. Check the
- echo $LIBPATH - Should report nothing.
- echo $MANPATH - Should report nothing.
[ Doc Ref: 97473376820474 Publish Date: Dec. 19, 2000 4FAX Ref: none ]