CDE Message when logging out.

[Dennis Weitzell]

We are upgrading from HPUX 10.20 to 11.0 on HP-9000 C-class & B-class systems. What occurs when you "exit" CDE is there are three boxes in the logout confirmation window. The first states "Continue logout", the second says "Cancel logout" and the third states:

"Unable to initialize or connect to the Deskop messaging system. Check your HOME/.dt/errorlog for more information. Press OK and your session will exit."

We can click on "Continue logout" and it exits CDE fine. We did not have this message in 10.20 and it only occurs when logging "out." I have also checked the errorlog but nothing helpful shows up there.

I have searched for the message in ITRC and have found most of the problems related to logging "in" or not being able to login to CDE. I tried the "fix" suggestions anyway but nothing seemed to help.

It doesn't seem to break anything but the users are calling and asking what it means. Does anyone have any suggestions???

Thanks

[S.K. Chan]

Did you try to run ..
# /usr/contrib/bin/X11/dr_dt
to get more information of what might be wrong? If you haven't I suggest you do that first.

[Eric Ladner]

Under the Style Manager, you could set the Logout Confirmation Dialog to "off". That's kind of a kludge, but does get you the behaviour you are used to under 10.20.

In the Style Manager, it's under the key on the right.

[Dennis Weitzell]

Yes, I did. I got two WARNINGs from it which were setting permissions/ownership on "/" and "/usr/spool." I made those corrections but it didn't change anything.

I went through the checklist of:
- Run /usr/contrib/bin/Z11/dr_dt
- Check the error logs /var/dt/Xerrors
and $HOME/.dt/errorlog
- Checked the output from
"nslookup and nslookup
- Checked permissions/ownership of:
/etc/hosts and /var/adm/inetd.sec
(inetd.sec didn't exist so created it
but it didn't change)
- Checked "ping for 0% packet loss
- Checked that $LANG was set to "C"

None of these tests seemed to help.

[Kelli Ward]

This is a silly suggestion and probably not the problem, but here goes:

check your systems' date.
I had a system which had the date reset back to 1970 (dead battery) and it gave me all sorts of weird tooltalk, SAM and messaging errors.

Not this error specifically, but what the heck, it worth checking, at least.
Good luck,
Kel

[Kelli Ward]

Also, Upgrades on HP-UX tend to be wrought with problems. You may have better luck backing up your neccessary data, perforning a cold install and recovering your neccessary data. Saves a lot of headaches in the long run. I do not upgrade for this very (personal experience) reason.
(There are many forum posts on this very subject.)
Hope this help,
Kel

[Jeff Schussele]

Dennis,

Is you Tool Talk Message Server running?

#ps -ef | grep ttsession

ALSO IS rpc.ttdbserverd running?

#ps -ef | grep rpc.ttdbserverd

These could be the trouble.

HTH,
Jeff

[Dennis Weitzell]

The system date is ok. Also, we are actually doing a complete rebuild (using ignite) rather than upgrading.

As far as Tool Talk is concerned ... yes, both processes are running.

[Jeff Schussele]

Looking at it further appears ttsession is only active when a desktop session is active.

On the other hand the Tool Talk DB Server needs to be running for the messaging to work - see this link:

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B1171-90162/B1171-90162_top.html&con=/hpux/onlinedocs/B1171-90162/00/00/46-con.html&toc=/hpux/onlinedocs/B1171-90162/00/00/46-toc.html&searchterms=ttsession&queryid=20020301-143135

Could it be that the rpc.ttdbservd is not configured in the inetd.conf file & is therefore not starting?

HTH,
Jeff

[Jeff Schussele]

OK...beginning to look like perms to me.

What happens when root starts & exits a CDE session - same symptoms?

Jeff

[Dennis Weitzell]

Yes, root has the same problem.

[Jeff Schussele]

Well - you've got me stumped.
But I have a strong hunch that's it's either a perms problem or a missing file.

If I had a "working" 11.00 system to compare files & perms against that's what I'd do next. I'd concentrate on the dt fileset first.

If you don't hopefully you have something to cold-install 11.0 unto to compare.

Good luck & sorry I couldn't help more.

Rgds,
Jeff

[K.Vijayaragavan.]

1)From command line mode use the command,

#set_parms initial

to reset the system paramters which includes IP address and network parameters.

Xwindows used to get into such problem if some of the system files are partialy updated with new system parameters(ip address).

2)Check the file permission for the files under /var/spool/sockets. This "sockets" folder and all it's subfolders and files must have permission set with 777 (i.e. rwxrwxrwx).

-Vijay

[Alex Glennie]

1. Can you whilst logged out of CDE try the following :

mv $HOME/.dt .dt_orig ...... log back in and then out again ?

2. run from within CDE -> dtaction ExitSession result ?

3. comment on the contents of the errorlog ?

4. ps -ef | grep dtsession : how many ?

[Dennis Weitzell]

I have not yet tried the set_parms ... I will be trying that soon.

I did check the permissions of /var/spool/sockets and found the files in X11 had permissions of 600. I changed that to 777 but it didn't make any difference.


I also tried moving the .dt directory and running "dtaction ExitSession result." I get an error message window saying:

Either action "ExitSession" was not found or this action does not apply to file: "ws_name:/$HOME/result" with data attribute: "UNKNOWN"

If I just run "dtaction ExitSession," it responds the same as if I had clicked on the EXIT icon ... with the message:

"Unable to initialize or connect to the Deskop messaging system. Check your HOME/.dt/errorlog for more information. Press OK and your session will exit."

The errorlog shows nothing, it is empty.

There is only one session running for "dtsession."

[Dennis Weitzell]

OK ... I tried the "set_parms initial" but that didn't make any difference.

[K.Vijayaragavan.]

Can you post the dr_dt command output?
-K.Vijay.

[K.Vijayaragavan.]

Hi,

Sorry, It may be too late for me to ask this question? But i want to ask.

Are you facing any problem in login using CDE?
As your post subject says "CDE Message when logging out" i am not sure whether you are able to login using CDE?

-K.Vijay

[Steve Steel]

Hi


Rebuild tooltalk or turn it off.

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