cannot log in!

[Laura Stokes]

I am very new to HPUX, so please bear with me. I have HPUX version 10 and whenever we try to log in using the gui interface I get this error message:
"Unable to initialize or connect to the Desktop messaging system. Check your $HOME/.dt/errorlog for more details"
Clicking OK in this message brings me back to the login screen
This happens logging in as root or a normal user.

I then did a command-line login, and looked at the errorlog file. It says:
"dtsession: the ToolTalk session server (ttsession) could not be started. This indicates that either ToolTalk is not installed or that it is not installed correctly on this machine. Please see your system administrator."

We don't install anything on this system except for client browsers for testing purposes. Does anyone have any thoughts about how I can get the gui interface to work again?

Laura

[Kofi ARTHIABAH]

It looks like you have tooltalk configured as part of the startup... check the file $HOME/.xinitrc (ie. the file is usually in the users' home directory) unless you have a global one in which case you can find it with:

find / -name "*xinitrc*" -print

look in the file for references to tooltalk and disable accordingly.

Good luck

[alberto vasquez]

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

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

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.

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

The output from nslookup and nslookup 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 and nslookup .
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.


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


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.

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

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

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

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.

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.

[alberto vasquez]

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

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

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.

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

The output from nslookup and nslookup 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 and nslookup .
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.


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


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.

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

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

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

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.

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.

[alberto vasquez]

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

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

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.

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

The output from nslookup and nslookup 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 and nslookup .
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.


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


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.

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

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

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

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.

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.

[alberto vasquez]

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

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

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.

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

The output from nslookup and nslookup 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 and nslookup .
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.


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


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.

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

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

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

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.

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.