Hi Gurus, Many thanks to those who replied: Ian Veach <imail@nevada.edu> Steve Sandau <ssandau@bath.tmac.com> Claude Charest <charest@Canr.Hydro.Qc.Ca> Claude Charest provided a simple and quick solution. Claude Charest wrote: > I have had the same problem with a SunBlade 150, just > after I installed the "Solaris 9 Maintenance Update 3". > It is related with patch 113796-02 with another patche > in MU3. To solve your problem remove and re-install > patch 113796-02. So, the problem is apparently in a patch installation sequence. I did "patchrm" and "patchadd" and everything is now working fine. Actually I was able to log in to CDE right after "patchrm", but it seems to be important to re-apply the patch afterwards. Thanks a lot, Claude! Here goes my original posting: > From: Alex Pokras > Sent: Friday, June 13, 2003 4:11 PM > To: 'sunmanagers@sunmanagers.org' > Subject: CDE not starting in Sol9 after patch bundle installation > > Hi Gurus, > > I cannot start CDE on my Sun Blade 100 workstation, > running Solaris 9. The famous error message is: > > "The DT messaging system could not be started. > To correct the problem, select the Failsafe session > and log in. Check that the hostname is correct in > these locations: /etc/src.sh /etc/hosts > /usr/adm/inetd.sec" > > etc. I have checked the available sources on the Internet, > including archives of this mail list. Anything that solved > similar problem for different people out there didn't work > for me. In most situation the problem was caused by lack > of disk space or write permissions in user's home dirs. > > But in my case I cannot run the CDE even as "root" (not to > say about all the other users), so there is no permission > problem. There is plenty of disk space available and no > disk quotas enabled on the system. The problem appeared > right after I have installed latest recommended patches > bundle, downloaded from SunSolve). > > I can close the "The DT messaging system could not be > started" pop-up window and even work in CDE somehow, but > with limited functionality. Also another message pops up > frequently saying "Message System inoperative" and urging > to logout and log in again. > > I have tried to track down the problem through error log > files and error messages, but it seems that they don't > reflect the actual problem and are quite misleading. > > About the system: One 500MHz CPU, 256M of RAM. > "uname -a" output: "SunOS cabadm1 5.9 Generic_112233-06 > sun4u sparc SUNW,Sun-Blade-100". Regards, -- Alex Pokras Rogers Cable, Toronto E-mail: apokras@rci.rogers.com _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Mon Jun 16 11:45:44 2003
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:14 EST