topic Re: Toolkit session Server in Operating System - HP-UX

Toolkit session Server

Joey Raj — Thu, 10 May 2001 05:27:24 GMT

Hi,

We are running Hp-UX 10.20 on a C-class, which boots directly into X session. for the past couple of days I am unable to enter into X session and I am getting the error unable to initialize desktop messaging check $home/dt/errorlog.

The Errorlog says Toolkit Session server (ttsession) could not be started.

I am able to login in Failsafe mode but not regular seesion.

Can somebody help me out here.

Thankx,

Joe

Re: Toolkit session Server

Andrew Nosov — Thu, 10 May 2001 06:03:19 GMT

Joseph.
I don't know all the details how TT service works, but when I ran into the same problem a couple years ago one of HP engineers recommended me not to use TT system at all. He said that generally there's no need to use the system. Here are his recommendations of disabling the service.
1. Comment out the line with rpc.ttdbserver in /etc/inetd.conf file.
2. restart inetd
inetd -c
3. Kill rpc.ttdbserver
4. Delete all the directories with the name TT_DB.
I did it and it still works with no problem.
Regards. Andrew.

Re: Toolkit session Server

Joey Raj — Thu, 10 May 2001 06:09:05 GMT

thankx andrew for the tip but we require x session since we do high end graphical drawing using it. But your Idea is really good. Will keep it as a loast option.

Joe

Re: Toolkit session Server

Alex Glennie — Thu, 10 May 2001 09:34:55 GMT

POSSIBLE CAUSEs OF ERROR:

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

TROUBLESHOOTING:

1) From the CDE login select Options -> Session -> Failsafe Session
and login as root.
2) Run /usr/contrib/bin/X11/dr_dt. The end of the output from this
script says: 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 " and "nslookup " should
be the same. This checks for a) duplicate IP addresses or
hostnames or b) problems with name resolution. If nslookup fails
then CDE will fail to start. If the first line returned from nslookup
is: "Name Server" then you are using DNS. Move "/etc/resolv.conf" to
another name, i.e. /etc/resolv.conf.orig and rerun nslookup. If
nslookup now succeeds then try logging into CDE again.
5) Check permissions and ownership of the following files:
-r--r--r-- 1 bin bin 616 Jul 1 16:03 /etc/hosts
-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
spc allow
mserve allow
If not add the lines and run "/usr/sbin/inetd -c" to reread the file.
7) /usr/sbin/ping
You should get back 0% packet loss. If you get something different
then check your network configuration.
8) Make sure the $LANG environment variable is set correctly. It should
be set to C or unset for American-English.
9) Exit the failsafe session. From the CDE login select Options ->
Command Line Login. When the screen turns black, press and
you should get a Console Login prompt. Login as root.
10) mv $HOME/.dt $HOME/.dt.orig
mv $HOME/.dtprofile $HOME/.dtprofile.orig
exit (to return to CDE) - try logging in as root.