Home > Dt Messaging > Dt Messaging System Could Not Be Started Solaris 8

Dt Messaging System Could Not Be Started Solaris 8

Check tos ee any magic cookie related error messges in these > locations: > /var/adm/messages > $HOME/.dt/errorlog > > The darn thing is I can't boot to root's CDE either! For me, this means since I put the host in my NIS domain, I failed to add a client entry into the NIS host table. Hi, I think the "DT" is the desktop and it is assuming you have a graphics card and it can't get the graphical X Windows working. S99dtlogin - CDE daemon, starts CDE by default /etc/rc3.d S15nfs.server - used to share file systems, a bad idea for firewalls. navigate here

South Carolina bill would mandate ransomware to see porn [Security] by humanfilth295. Check the following files for IP address correctness - /etc/hosts - /etc/netmasks - /etc/defaultrouter ForumsJoin Search similar:Not sure if actually infected. ipnodes: files dns networks: files protocols: files rpc: files ethers: files netmasks: files bootparams: files publickey: files 9. http://www.unix.com/solaris/33110-solaris-10-cde-problem-dt-messaging-system-could-not-started.html

Check for consistency and correctness of hostname and IP address throughout system files. Toolbox.com is not affiliated with or endorsed by any company listed at this site. The same β€œThe DT messaging system could not be started..." error message appeared. This showed that no filesystem was even close to being full.

The root user does have a .dtprofile file but everything in this file is commented out. d. I tried to create a user dir in /export/home by creating > the directory under /export/home/username then adding > username hostname:/export/home/username to /etc/auto_mount > and commenting out +auto_home, then running a Is ttsession running?

ttdbck: isopen("./TT_DB/property_table"): No such file or directory 2. Look at the inetd.conf file for a conflict. ====================================================================== 4. If you still Go to Solution 3 Participants yuzh LVL 38 Unix OS32 liddler LVL 18 Unix OS9 mrquin LVL 3 Unix OS1 3 Comments LVL 38 Overall: Level 38 Check tos ee any magic cookie related error messges in these locations: /var/adm/messages $HOME/.dt/errorlog The darn thing is I can't boot to root's CDE either!

Check to see that the hostname is correct in these locations: /etc/src.sh /etc/hosts /user/adm/inetd.sec 4. If not, how can I fix it? Updated on 2013-04-01T14:26:38Z at 2013-04-01T14:26:38Z by SystemAdmin nagger 100000MRSJ 342 Posts Re: Keep getting “The DT Messaging System could not be started” error message ‏2013-03-25T22:59:06Z This is the accepted answer. Select Failsave session from the login screen's option menu and login. 3.

In spite of my doing the edit in the /etc/default/dhcpagent and as i believe(I'm pretty sure I rebooted), rebooting after doing such edit (this requires a reboot, see dhcpagent man page) have a peek at this web-site Air Pods [Apple] by Jackarino© DSLReports · Est.1999feedback · terms · Mobile mode

OSDir.com os.solaris.sunhelp Subject: CDE error - DT messaging system could not bestarted Date Index Thread: Prev Home | Invite Peers | More UNIX Groups Your account is ready. I had previously disconnected the hme0 interface from my dhcp provider and attached it to another router which was supplying dhcp information.

I've got the following in my /etc/hosts 127.0.0.1 localhost 192.168.0.11 myhostname I can access to other systems outside of the LAN with SSh or ping hosts with no problem (when I check over here Get 1:1 Help Now Advertise Here Enjoyed your answer? inetd refused to be tickled into restarting rpc.ttdbserverd, not that that had anything to do with it. This can occur for a variety of reasons.

Check for errors in the global customization of CDE: - mv /etc/dt /etc/old.dt C. Check for errors in the local customization of CDE. Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We his comment is here If it does not exist it will get recreated.

Hi All, I was able to resolve this issue by commenting out the line on dhcpcd in /etc/rc.tcpip. Check to see that the hostname is correct in: /etc/hosts Other hostname problems can be corrected by using the command: smit mktcpip 4. I don't know if I've quota running, but quota -v username doesn't return any numbers (user's UID 100).

ENOENT (2) A file or directory in the pathname does not exist.” β€œWorkspace Manager: I/O error on display:: : 0.0” I did confirm that the file dtrmrules.driver does not exist though

To correct the problem: 1. Takes input username/password and starts bringing up CDE display and session 4. Covered by US Patent. To correct the problem: Choose [OK] to return to the login screen.

Another suggestion was 1. Forum Operations by The UNIX and Linux Forums MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Courses Contribute Products BackProducts Gigs Live Courses Vendor Services Groups I will leave a recommendation in the Cleanup topic area that this question is: PAQ No refund Please leave any comments here within the next four days. weblink If rpcbind seems to be hung, either reboot the server or follow the steps from docs.sun.com on "How to

hosts: files dns # Note that IPv4 addresses are searched for in all of the ipnodes databases # before searching the hosts databases. S76snmpdx - snmp daemon I ran the following command, and uncommented the bottom entries of my /etc/inetd.conf file: #grep -v "^#" /etc/inetd.conf 100232/10 tli rpc/udp wait root /usr/sbin/sadmind sadmind rquotad/1 tli Another system was also moved from one dhcp server to another in a similar manner, however, the login interface on that was, perhaps, Sun's Java...and on that system, I did not, Please check to following files to be sure the hostname is correct/etc/hosts/etc/src.sh/usr/adm/inetd.srcI'm not sure what the problem is with DT messaging system.

Check the following files for hostname consistency: - /etc/hosts - /etc/nodename - /etc/hostname. All you can do is to press OK and it takes you back to Login (Manager) display. Network configuration Any network configuration problems will usually result in dtlogin problems. This is the accepted answer.

After you see a CDE desktop display ( nothing else), following error message is displayed in a pop- up window and you are blocked. DNS - Reverse lookup failure - DNS entry did not match system entry - Check entry in the ptr.XXX.dbfile regards khairul

vvv Home | News | Sitemap | FAQ | advertise | OSDir is an Inevitable website. All of the relevant possible solutions are in this document.

Ensure the rpc daemon is running. 1. Check for the presence of a line file:hosts If this line exists, comment it out. ====================================================================== 3. This file is created for each session and is unique to that session. IP address loghost 2.

I have seen this problem a few times. Log in as root from command line using commands: # OPENWINHOME=/usr/openwin #export OPENWINHOME # $OPENWINHOME/bin/xinit I am logging in directly into the machine through the CDE (Common Desktop Environment). Any information would be appreciated, thank you. -Gani- Next Message by Date: tape drive keep giving problem Hello all.

I've run out of option here. On Solaris 2.x can do this with command: share -F nfs -o root= /usr/dt Change the machine Refer to man page for share_nfs for more information.