LDAP, CDE and Xsession problem

[Peter Maddison]

We've recently setup an iplanet LDAP server running on Solaris. I've upgraded the first of our HP clients to 11.0 and put HP's LDAP-UX client on it.

Console logins work fine and everything authenticates correctly. However when I try to log in through CDE the login gets all the way through running the profile and then the Xsession crashes.

Has anyone come across this error before?

I changed my profile to do nothing but echo HI and this is the tail of startlog:

--- execing /usr/dt/bin/dtsession using /users/maddispe/.profile...
+ source_profile=. /users/maddispe/.profile
+ source_login=source /users/maddispe/.profile
+ [ -z /usr/dt/bin/dtdbcache -init ]
+ export DT=true
+ /bin/ksh -c . /users/maddispe/.profile; unset DT; /usr/dt/bin/dtdbcache -init; PATH=/usr/dt/bin:$PATH /usr/dt/bin/ttsession -s; /usr/dt/bin/dtsession >| /users/maddispe/.dt/sessionlogs/lntrw122_DISPLAY=lntrw122:0 2>&1
HI
/usr/dt/bin/Xsession[598]: 1598 Bus error
+ rm -f /tmp/dtdbcache_lntrw122:0
X connection to lntrw122:0.0 broken (explicit kill or server shutdown).

[Kellogg Unix Team]

Hi Peter,

I haven't dealt with LDAP but you can do the following to debug the problem further -

move your ~/.dt directory to
remove echo command from your .profile
In your ~/.dtprofile file, comment out the entry "DTSOURCEPROFILE=true" (normally the last entry).

Give it a try and let us know.

HTH
...Manjeet

[Peter Maddison]

Thanks, tried that but I'm still getting the same issue.

I'll try patching CDE today.

Any other suggestions?

[Steve Steel]

Hi


Look at

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xf1d2f841489fd4118fef0090279cd0f9,00.html


Check your shell patches


Regards

Steve Steel

Quote of the moment
-------------------
"We are drowning in information but starved for knowledge."
-- John Naisbitt

[Peter Maddison]

I've now installed the latest pam, cde and shell patches and I'm still getting exactly the same problem.

Any more ideas?

[Alex Glennie]

more ideas .... are you 100 % certain this is due to LDAP and not the upgrade ? ie can you easily remove ldap from the problem scenario and if so does the problem persist ?

Next I'd suggest adding set -x in .dtprofile then reproduce the problem and look at the users startlog again.

also worth a look is running dr_dt and seeing if the upgrade has introduced problems ....

lastly see Rick's suggestion on how to enable CDE debugging : see http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xe15d0fe6d0f7d61190050090279cd0f9,00.html

[Steve Steel]

Hi

startlog and errorlog + /var/dt/Xerrors and run
dr_dt

Also look for any errors from ldap in the system logs

Regards

Steve Steel

Quote of the moment
-------------------
"We are drowning in information but starved for knowledge."
-- John Naisbitt

[Pierrick herve]

Hi Peter,

Do you have this problem for all logins ?

Do you still have this problem with a new created login ?

As you should know : /usr/dt/bin/Xsession
is a shell script that you can modify to obtain a verbose output.

edit /usr/dt/bin/Xsession

I) first modification
1. add a set "set -x" after "#!/usr/bin/ksh"

2. modify (neer line 51)
exec >/dev/null 2>/dev/null
by :
exec > /tmp/debug.xsession 2>/tmp/debug.xsession.error

3. logout/login

4. analyse /tmp/debug.xsession
/tmp/debug.xsession.error
and your local starlog

II)second modification
dtstart_sessionlogfile="/dev/null"
in : dtstart_sessionlogfile="/tmp/dtsession.log"

regards,
Pierrick

[Peter Maddison]

It's funny you should say that Pierrick. I tried another user accout and it worked. I moved my home directory and tried it again and it let me in.

So after all that it is something buried in my home directory. I know it is nothing to do with .dt, .dtprofile, .profile or .xsession.

I should be able to find it now though. Thanks for all your help.

[Rick Beldin]

Whatever is causing this:

/usr/dt/bin/Xsession[598]: 1598 Bus error

is the root of your problem. I suspect that the shell running Xsession is coring. You might have a core file in $HOME for that user.

I would guess that this corresponds to the line in Xsession at the end where the dtsession is started:

exec $startup >$dtstart_sessionlogfile 2>&1" ;;

(or the equivalent one for csh).

If there is a core file, do a file core and then run gdb core to get a backtrace. The will be the result of the file command.

Something in your environment could certainly be causing this. Xsession and all the programs it runs reads and sources a lot of different components.

[Peter Maddison]

I tracked it down to the .Xdefaults file in the end. When the Xserver tried reading it, it crashed.