Error message related to ToolTalk

[Ramesh.K.R.]

Hi,

We are using HPUX 11.0 on our system. In the "syslog", we are getting the following messages frequently. What we want to know is, why in the first place we are getting this & is there a way to suppress this message. It will be of immense help, if we get the resolution early.

Message Displayed:
May 21 12:22:22 cmps1 syslog: libtt[12179]: ttdt_Xt_input_handler():
tttk_message_receive(): TT_ERR_NOMP^INo ttsession process is running,
probably because tt_open() has not been called yet. If this code is returned
from tt_open() it means ttsession could not be started, which generally
means ToolTalk is not installed on this system.

Expecting a speedy response from experts.

Thanks & Regards,
Ramesh.K.R.
HP-eSDI
Bangalore

[Steven Sim Kok Leong]

Hi,

The TookTalk service generally tries to restart ttsession if it is not running. So this error indicates that the ToolTalk service is either not installed or is not installed correctly.

Check whether the ttsession binary exists and whether the ownership and permissions of this binary is correct:

bash-2.05a$ ll /usr/dt/bin/ttsession
-r-xr-xr-x 1 bin bin 184320 May 24 2001 /usr/dt/bin/ttsession

Hope this helps. Regards.

Steven Sim Kok Leong

[Ramesh.K.R.]

Hi Steven,

We do have the binary & the permission is also correct. Here is the info:
# ll ttsession
-r-xr-xr-x 1 bin bin 258048 Sep 10 1999 ttsession

What else could be wrong??

Ramesh.K.R.

[Steven Sim Kok Leong]

Hi,

Can you try to manually start this and see if there are any errors:

# /usr/dt/bin/ttsession

Check also the permissions of

# ll -d /usr
# ll -d /usr/dt
# ll -d /usr/bin

Hope this helps. Regards.

Steven Sim Kok Leong

[Ramesh.K.R.]

Hi,

I checked all the permissions. They are ok. Owner & Group are bin and the permissions are 555. I even started the "ttsession" i can not see any errors in syslog. Any more pointers??

Ramesh.K.R.

[Steven Sim Kok Leong]

Hi,

Are you running remote syslogging? Is this "cmps1" by any chance a remote server that is syslogging to this local server? If it is, then you have to check on the cmps1 server.

Hope this helps. Regards.

Steven Sim Kok Leong

[Steve Steel]

Hi

This is best done when CDE is not in use.

Tooltalk is the protocol used by CDE to communicate.

Your problem is.
The TT_DB database is corrupt.

1)vi /etc/inetd.conf
2)Find
rpc stream tcp swait root /usr/dt/bin/rpc.ttdbserver 100083 1 /usr/dt/bin/rpc.tt
dbserver
3)Comment it out.
4)inetd -c
5)Find the $PPID of /usr/dt/bin/rpc.ttdbserver and kill -9 $PPID
6)mv /TT_DB/ to other name on root and any local directories where it exists.
ll /TT_DB /*/TT_DB and remove all directories found which are local.
7)vi /etc/inetd.conf
8)Find
rpc stream tcp swait root /usr/dt/bin/rpc.ttdbserver 100083 1 /usr/dt/bin/rpc.ttdbserver
9)Remove the comment and reopen the line.
10)inetd -c

The first rpc request will rebuild the database.

steve Steel

[Ramesh.K.R.]

Hi,

Steven -- Yes. it is a remote "syslog". But, we tried on the remote m/c also. Same problem exists.

Steve Steel -- I could not find the /TT_DB on our m/c's What could be the reason?

Ramesh.K.R.

[Sanjay_6]

Hi Ramesh,

Try this link,

http://support1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000057991580

Hope this helps.

Regds

[Alex Glennie]

also be aware of PHSS_26491 s700_800 11.00 CDE DevKit JUNE2001 Periodic Patch

ie the bit about .... No 6. maybe relevant :

. [PHSS_15798/PACHRDME/English] :
1) dthello writes a core file in the user's home directory
2) buffer flow in libDtSvc. 3) ttsession logging spurious errors to syslog.
4) TT_ERR_NOMP errors in syslog after logging out of CDE session
5) At logout, syslog.log gets "No ttsession process is running" errors
6) "ttdt_Xt_input_handler(): tttk_message" entry in syslog generated.
7) dtwm logs libtt[]: _Tt_rpc_client::init() while logging out from CDE
8) libtt[1264]: _Tt_rpc_client::init(): logged after logging out from CDE
9) " No ttsession running " error message in syslog.
10)"Tt_rpc_client::init(): fcntl(F_SETFD): m "errors in syslog.log
11) "DtTermDisplaySend" function can not handle a string
greater than 1024 byte