cancel
Showing results for 
Search instead for 
Did you mean: 

CDE Login Failure

Lars-Olof Fermvall
Frequent Advisor

CDE Login Failure

Hi!
I have problem with an old (9000-715) system where login via CDE fails. I have looked at some old cases and found a suggestion to collect certain log files to support the fault tracing. What happens is that you get as far as the copyright page and then it sits there with an hour glass up. Is the tooltalk error significant, and how could I fix it?
Nemo enim saltat sobrius, nice forte insanit
11 REPLIES
Tim Adamson_1
Honored Contributor

Re: CDE Login Failure

Was there anything in the errorlog* files in the home directory?

Are you up-to-date with the CDE patching?


Tim
Yesterday is history, tomorrow is a mystery, today is a gift. That's why it's called the present.
T G Manikandan
Honored Contributor

Re: CDE Login Failure

First resolve the warning messages which was
indicated in the dr_dt.log

change the permissions as suggested.

Also check this Troubleshooting Guide


twang
Honored Contributor

Re: CDE Login Failure

Can you break the booting process that hung by pressing the Break key? And what happen once you press the Break key.
Ravi_8
Honored Contributor

Re: CDE Login Failure

Hi,

comment all the lines begin with "dtlogin" in /etc/pam.conf file and add these lines at the end

# for CDE Login

dtlogin auth optional /usr/lib/security/pam_unix.so.1
dtlogin auth optional /usr/lib/security/pam_afs.so try_first_pass ignore_root
dtsesion auth optional /usr/lib/security/pam_unix.so.1
dtsession auth optional /usr/lib/security/pam_afs.so try_first_pass ignore_root

never give up
Ravi_8
Honored Contributor

Re: CDE Login Failure

Hi,

comment all the lines begin with "dtlogin" in /etc/pam.conf file and add these lines at the end

# for CDE Login

dtlogin auth optional /usr/lib/security/pam_unix.so.1
dtsesion auth optional /usr/lib/security/pam_unix.so.1

never give up
Alex Glennie
Honored Contributor

Re: CDE Login Failure

I'd
a) change/correct permissions on /etc/hosts.

b) attempt to login as root ... result ?

c) attempt to login as another user ?

d) attempt to login to a CDE failsafe session result ?

e) if using DNS point nsswitch.conf to
use files first result ?

f) patch for CDE ...... but get back with results from a-e first.
Lars-Olof Fermvall
Frequent Advisor

Re: CDE Login Failure

Thanks for your replies, guys!

I'm sorry, but Wonderful Windows Worms have prevented me from accessing internet (our LAN was shut down just after I posted the message yesterday) or the client site (where I dial in) for some time. I may be able to access the client site later today, but some initial comments/answers based on earlier observations:

CDE Patching - not up to date, butv this is the only system of the same patch level that is having this problem.

I will go through the warning messages.

Glennie, in answer to your questions:

a) will do
b+c) Two users are affected, but root works (at least it used to)
d) Have not tried failsafe (yet)
e) DNS is not used

The rest of your suggestions I will have to look at when I can gain access again.

Just one thing: I a similar posting ("Need Help regarding Login failure in HPserver(9000/800)" Alex Glennie asked the person who made the posting if there were tooltalk related errors, which I do have in syslog - hence my initial question about this.

(PS Points will be awarded once I cracked the problem)
Nemo enim saltat sobrius, nice forte insanit
Steven E. Protter
Exalted Contributor

Re: CDE Login Failure

Make sure the DISPLAY variable is set correctly for the situation as well.

If the user is logging in from workstation 192.168.0.10

Then that user profile should indicate:
DISPLAY=192.168.0.10:0.0
export DISPLAY

When root works and other users don't its usually permissions as noted above.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Lars-Olof Fermvall
Frequent Advisor

Re: CDE Login Failure

Hi Steven!

The problem happens when trying to log in locally (It is a HP9000/715). I added loopback to /etc/hosts yesterday, but have not tested it since (I don't expect any change).

I hope to be able to access the system again soon.
Nemo enim saltat sobrius, nice forte insanit
Lars-Olof Fermvall
Frequent Advisor

Re: CDE Login Failure

I have been logged in now, but didn't get a chance to change/check everything before I lost my support on site. I have sorted out the access problems, I think and attach new dr_dt output files (for vp4, with a problem) (this time also output to stderr included). It is now the same as I get on a system that works (for vp5, which works).
The last test I did, before I had a chance to fix all permission issues, ttddbserver would crash when somebody tried to log in. Error codes as per syslog.log from an earlier entry. It may work tomorrow, if not, I will try the other things suggested.

Later,
Lars-Olof
Nemo enim saltat sobrius, nice forte insanit
Lars-Olof Fermvall
Frequent Advisor

Re: CDE Login Failure

Thanks again for your suggestions. (Points will now bo assigned, even though the problem persists. If you fix it: more points, of course!)

I have been able to check out the system some more, and...
Tim: errorlog is included in the attached files
T.G.: I have fixed up the access right issues, as far as I know, but to avail. The fault tracing guide is good. Output from rpcinfo -p is included in the attached files.
twang: I haven't tested booting, since root can log in to CDE
Ravi: I changed /etc/pam.conf as suggested, but no success. Is a re-boot or re-start of CDE (dtlogin) required?
Alex: Failsafe login works, as does login for root, but not other users. DNS: not used
All: The problem could to be related to ToolTalk(?). Please look in the attached syslog.log file, where these errors always occur at the same time as a login fails:

Aug 22 10:16:09 vpaco160 /usr/dt/bin/rpc.ttdbserver[4264]: NetISAM: lseek failed
Aug 22 10:16:09 vpaco160 NetISAM[4264]: Fatal error: lseek failed - UNIX errno 0
Aug 22 10:16:09 vpaco160 inetd[615]: rpc.ttdbserver/tcp: Exit status 1
Aug 22 10:19:27 vpaco160 /usr/dt/bin/rpc.ttdbserver[4268]: _Tt_rpc_client::init(): fcntl(F_SETFD): m

Has anybody got any idea on how to fix this?
Nemo enim saltat sobrius, nice forte insanit