TRU64 5.1B Login freeze

[DaveHarrison]

This is what I have from the errorlog:

---------------------------------------------------------------------------
Mon Jan 07 16:43:55 2008
Workspace Manager: I/O error on display:: :0.0


ERROR: Unable to start required local loopback device lo0, CDE unavialable.
ERROR: Unable to start required local loopback device lo0, CDE unavialable.
ERROR: Unable to start required local loopback device lo0, CDE unavialable.
ERROR: Unable to start required local loopback device lo0, CDE unavialable.
ERROR: Unable to start required local loopback device lo0, CDE unavialable.
ERROR: Unable to start required local loopback device lo0, CDE unavialable.

---------------------------------------------------------------------------

I gather from this its lost its loopback somehow, but from logging in as root, it can see the loopback no problem.

1 thing I do know has changed is the original user "unit" has been locked as the new user "unitf" has been created.

I'm going to unlock that account now and see if that makes any difference.

Both users, root and unitf can log into the fail-safe session, however once I was in there, I didnt really know what or how to diagnose so I stopped there.

The hostname matches up in both the rc.config and hosts file, however in the hosts file there is other types of the name next to the IP add but this has been like that since the servers were built.

(e.g.
127.0.0.1 localhost
172.16.51.1 Servera1 serveras1 Serv1
172.16.51.2 Servera2 serveras2 Serv2 )

I cant seem to find the file /etc/resolv.conf?? hosts is ok and setup. There's no multiple lines of the same IP in there.

The network runs on a fixed IP range so theres no DHCP configured although I now NTP has been setup as well but the servers have been restarted a number of times since that and all was ok.

I've just checked the owner of the account and unitf owns the unitf account and all inside it.


The ls -ld /cluster/members/member/tmp/.X11-unix command has returned:

drwxrwxrwt 2 root daemon 8192 Jan 9 12:30 .X11-unix

daemon??? is that right??


The ls -ld /cluster/members/member/tmp/.X11-unix/X0 returned:

drwxrwxrwx 1 root daemon 8192 Jan 9 12:30 .

again with daemon? daemon isn't something I've made...


If the original account created is locked, would this cause a problem to accounts in the same group?

Thanks to everyone who's helping btw

[DaveHarrison]

Have just unlocked the original user, no difference.

Have just found that the Hosts file was actually missing the 127.0.0.1 loopback as someone had changed it for NTP. I've put that back and...

still not working. Still claims it cant use the loopback

I've just logged into the fail-safe as well and ran an ifconfig and the loopback is running there fine..

[Pieter 't Hart]

check /etc/passwd wich shell is configured for these users (root unit and unitf).
check the appropriate login scripts for these users for differences
(.profile or .login, .dtprofile, etc)

[DaveHarrison]

In the passwd file, the scripts are different.

root is /usr/bin/ksh
unitf is /bin/ksh

would this cause a problem?

[Rick Retterer]

Hi Dave,
I can only get to this group in the evenings.

Yes, there appears to be a problem with the loopback device.

Would you like to remove CDE dependancy on the network altogether? You really won't loose that much functionality and it should not affect security any.

Before you do this, you will need to remove the 0050.init2 script from the /usr/dt/config/Xsession.d directory completely.

To disable the tooltalk is a series of two steps.

1. The desktop portion of the network configuration must be disabled by
adding the line:

DTNONETWORK=true;export DTNONETWORK

to the user(s) $HOME/.dtprofile file.

NOTE: The default .dtprofile is /usr/dt/config/sys.dtprofile. If the
network setting is to be permanent for all future users, the preceeding line

line may be added to this file, which will then propagate to each
user's .dtprofile.

2. The command that executes the ttdb daemon,located in the
/etc/inetd.conf, must be commented out.
The following is provided as an example. (The example has the command
line wrapped for readability. In the /etc/inetd.conf file it is on one
line):

**************** Original ************************

rpc.ttdbserverd stream rpc/tcp wait root /usr/dt/bin/rpc.ttdbserverd
rpc.ttdbserverd

to


**************** Modified ************************

#rpc.ttdbserverd stream rpc/tcp wait root /usr/dt/bin/rpc.ttdbserverd
rpc.ttdbserverd


This will disable ToolTalk, which may have an impact. Some
applications as some make use of the ToolTalk protocol, and some
applications do not... Testing may be necessary to determine the
impact on the environment.

As a side note, the portmap daemon is started in the /sbin/init.d/nfs
script. The portmap daemon is a server that converts Remote Procedure
Call (RPC) program numbers into Defense Advanced Research Projects
Agency (DARPA) protocol port numbers. It must be running in order to
make RPC calls.

If one wants to disable rpc (remote procedure calls) on the system in
question, then the /sbin/init.d/nfs script should be copied to
nfs_original to preserve the original file, with changes to the nfs
script being made to satisfy the needs, i.e. not starting the portmap
daemon...

Give that a try and see if that helps any.

Cheers,
Rick

[DaveHarrison]

HURRAH!

Thats fixed it!!

The users can now login!

Thanks Rick

Also to:
Steven
Ivan
Pieter
Victor

for helping out!

[Rick Retterer]

Cool!!

Rick.