From: Bill Fenwick (bill@digicomp.com)
Date: Wed Sep 04 2002 - 14:47:38 EDT
Hi, all
Thanks to the following people for responding:
dana@dtn.com
Martha Crocker <martha.crocker@philips.com>
Kacem El Kassemi <kaceme@netscape.net>
Joon M. Hansen <joon.martin.hansen@eterra.no>
The problem turned out to be with the users' home directories, which
were NFS-mounted from the same E250 server I used to run jumpstart. The
jumpstart files on the server were in the same directory that housed the
users' home dirs, and I changed /etc/dfs/dfstab so that this directory
was read-only as part of the jumpstart process. Hence, when the
workstations NFS-mounted the directory, the user areas were read-only,
and when they logged in, CDE couldn't write to various files in the home
directory and died with the vague DT messaging error.
Other suggestions were to check the directory permissions, check the
/etc/net/*/hosts files, delete the files in /var/dt/tmp, and make sure
rpcbind is running (for ttdbserverd).
Original question:
> A client of ours has two E250 servers and eight SunBlade 100
> workstations, all running the 4/01 update of Solaris 8.
>
> They are unable to log in through CDE on any of the workstations,
> unless they use the root account. On login with any other account,
> the following window pops up after the ID and password have been entered:
>
> The DT messaging system could not be started.
>
> To correct this problem:
>
> 1. Choose OK to return to the login screen
> 2. Select FailSafe Session from the login screen's option menu and
> log in
> 3. Check to see that the hostname is correct in these locations:
>
> /etc/src.sh
> /etc/hosts
> /usr/adm/inetd.sec
>
>
> I've since found out that this is an old message Sun hasn't updated
> and refers to a couple files (src.sh and inetd.sec) that Sun doesn't use.
>
> I've searched the archives and google for info about this problem and
> have come up with some things to try, including
>
> checking /etc/inet/hosts for localhost and for corrupt entries
> deleting all .Xauthority files
> using pkgchk to make sure there aren't any files or links missing
> (found a couple and fixed them with no effect)
> using pkgchk to check SUNWtltk (tooltalk package)
>
>
> When the DT messaging error window appears, the following processes
> are running on the machine:
>
> angop8 345 312 0 10:08:31 ? 0:00 /bin/ksh
> /usr/dt/bin/Xsession
> angop8 311 302 0 10:07:39 ? 0:01 /usr/openwin/bin/Xsun :0
> -nobanner -auth /var/dt/A:0-SDaWLa
> angop8 354 345 0 10:08:31 ? 0:00 /usr/openwin/bin/fbconsole
> angop8 390 387 0 10:08:33 pts/4 0:00 csh -c unsetenv _
> PWD; unsetenv DT; setenv DISPLAY :0; angop8
> 358 1 0 10:08:32 ? 0:00 /usr/openwin/bin/speckeysd
> angop8 402 398 0 10:08:34 ? 0:00 dtwm
> angop8 387 345 0 10:08:33 pts/4 0:00 /usr/dt/bin/sdt_shell -c
> unsetenv _ PWD; unsetenv DT; setenv D
> angop8 389 1 0 10:08:33 ? 0:00 /usr/dt/bin/dsdm
> angop8 398 390 0 10:08:34 pts/4 0:00 /usr/dt/bin/dtsession
> angop8 413 1 0 10:08:46 ? 0:00 /bin/ksh
> /usr/dt/bin/sdtvolcheck -d -z 5 cdrom,zip,jaz,dvdrom,rmdisk
> angop8 437 413 0 10:08:56 ? 0:00 /bin/cat
> /tmp/.removable/notify413
>
> Then after the OK button is clicked, these disappear except for the
> sdtvolcheck and cat /tmp/.removable processes. Using the "w" command
> still shows the user (angop8) logged in:
>
> 11:50am up 2:13, 2 users, load average: 0.03, 0.02, 0.02
> User tty login@ idle JCPU PCPU what
> angop8 console 9:39am 2:11 dtwm
>
>
> Anybody have any ideas on what else I should look at to find out where
> this error is coming from and why CDE won't start??
>
> TIA and IWS.
>
-- Bill Fenwick Email: fenwick@digicomp.com Digicomp Research Voice: (607) 273-5900 ext 32 _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:52 EDT