Desktop messaging system could not be started

[steve_12]

I just did a brand new install of the 11.0. After installation and answering all the networking questions (DHCP, hostname, etc.) I reboot. OS starts up, desktop comes up. But I get an error box that pops up :

"The desktop messaging system could not be started. To correct the problem :

(1) Choose OK to return to the login screen.
(2) Select Failsafe Session from the login screen's option menu and log in.
(3) Check to see that the desktop is properly installed, the hostname is correct (/etc/hosts) and that the network is properly configured.

For additional information, see the CDE User's Guide."

This box cannot be bypassed, closed, etc. You HAVE to click OK, which then takes you back to login screen. The only way to bypass it, is like it said, login with failsafe mode (sort of like win95 safe mode). I have checked the /etc/hosts file and the IP and hostname are set fine. I have pinged the IP and get a response. I am not sure what is wrong. I have re-installed and gotten the same error.

My co-worked who received an AIX box the other day had the same error on install, re-installed and somehow it magically dissappered. We are both not GURU's on installed this stuff, but we know enough basics to get by.

[steve_12]

Some more info...

the /etc/hosts and /etc/rc.config.d/netconf files both list the hostname correctly and IP.

When checking /var/dt/Xerrors the following comes up :

"error (pid 1661): Hostname test is invalid. Setting DISPLAY to ':0'"

I can do a nslookup on test fine as well as pinging 127.0.0.1 with success.

[nnf97]

Take a look at doc Id KBRC00000036 on the Technical Knowledge Base.

It seems to be a cure for your ills.

Nabeel

[Alex Glennie]

whats the ip address for test, is it the same as for local host loopback ?

what's in /etc/hosts ? and netconf ? can u post em ?

tip if kbr doc does not fix run dr_dt for clues.

[Alex Glennie]

Also if this machine is standalone and is not on a network, then you will have
to "trick" CDE into thinking that there is a network present using the loopback:



Assign the loopback address (127.0.0.1) as the system's IP address in
/etc/rc.config.d/netconf


Set up /etc/hosts to include an entry for the host with the
following IP address:
127.0.0.1 hostname_of_system
127.0.0.1 localhost loopback



Ensure that the network configuration is accurate:
nslookup (hostname)
nslookup (IP address)

These two commands should return exactly the same information. If they
do not, then check /etc/hosts or /etc/resolv.conf for
inconsistencies.


Work from the lowest common denominator - take DNS completely out of the
picture:



mv /etc/resolv.conf /etc/resolv.old


nslookup (hostname)
NOTE: This should report that it is using /etc/hosts


Return to CDE login screen and test login functionality

If the login completes, have the network administrator check the DNS
configuration on both the client and the server. If the configuration seems
unflawed, modify the file /etc/nsswitch.conf to prevent CDE from
checking DNS for its own node name.



vi /etc/nsswitch.conf


set the hosts line to read:

hosts: files [NOTFOUND=continue UNAVAIL=return TRYAGAIN=return] dns



If, after testing and confirming all of the above, CDE still will not allow you
to login in, check /var/dt/Xerrors for any X or CDE errors that would be
preventing successful login.

[steve_12]

I cannot seem to access doc Id KBRC00000036. Is this valid? I have checked my rights and I do have access to the TKB but for some reason when entering in this ID to the search it produces no results.

Can this doc or snippet that will help me be posted here or can someone tell me how I can access this doc? Thank you.

Steve

[Alex Glennie]

KBRC00000036

Logging into CDE I get the following error:

Unable to initialize or connect to the Desktop messaging system. Check your
$HOME/.dt/errorlog for more information.

RESOLUTION

The /usr/dt/bin/ttsession couldn't start due to networking problems, name resolution, or
problems with ttsession.

1.From the CDE login select Options -> Session -> Failsafe Session and login as root.

2.Run /usr/contrib/bin/X11/dr_dt | more.
The end of the output from this script should give X ERRORs and X WARNINGs. These
errors and warnings should be resolved before CDE will run properly.

3.Check the error log /var/dt/Xerrors
Check the error log $HOME/.dt/errorlog

4.The output from nslookup &LThostname> and nslookup &LTIP> should be the
same. This checks for
a) duplicate IP addresses or hostnames or
b) problems with name resolution.

If nslookup does not succeed, CDE will fail to start.
If the first line returned from nslookup is: "Name Server" DNS is in use. If you are using
DNS and nslookup fails, move /etc/resolv.conf to another name, i.e.
/etc/resolv.conf.orig and rerun nslookup &LThostname> and nslookup
&LTIP>.
If nslookup now succeeds then try logging into CDE again. DNS will need to be updated
to correctly reflect the name and ip of this system. This is very common with new systems
added to a network.

5.Check permissions and ownership of the following files:

-r--r--r-- 1 bin bin 616 Jul 1 16:03 /etc/hosts

-rw-r--r-- 1 root sys 833 Jun 8 1999 /etc/nsswitch.conf

-rw-r--r-- 1 root sys 159 Jun 8 1999 /etc/resolv.conf
-r--r--r-- 1 root sys 1010 Jun 25 18:22 /var/adm/inetd.sec


6.Check the contents of /var/adm/inetd.sec. It should contain

dtspc allow [hostnames or '*'. No aliases]
spc allow [hostnames or '*'. No aliases]
mserve allow [hostnames or '*'. No aliases]

If not add the lines and run /usr/sbin/inetd -c to reread the file.

7./usr/sbin/ping &LThostname>
You should get back 0% packet loss. If you get something different then check your
network configuration.

8.Check the user's $HOME for a .TTauthority file. Ensure it is owned by the user and has
the appropriate group.

9.Make sure the $LANG environment variable is set correctly. It should either be set to "C"
or unset for American-English.

10.If none of the above have resolved the problem, exit the failsafe session. From the CDE
login screen select Options -> Command Line Login. When the screen turns black, press
[return] and you should get a Console Login prompt. Login as root.

11.For a user that cannot login, mv $HOME/.dt $HOME/.dt.orig
mv $HOME/.dtprofile $HOME/.dtprofile.orig
exit (to return to the CDE login screen) - try logging in as that user.