The DT messaging system could not be started.


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting The DT messaging system could not be started.
# 1  
Old 06-29-2018
The DT messaging system could not be started.

Good Morning,

Users can no longer log into SunBlade 2500 Solaris 9 system (though root still can). Here's what I'm getting and what I've done. I'm most suspicious of the full drive since that pops up twice and I did see one looks full. What's a good way to reduce what's on it?- or.. what else look possible as a cause?

Code:
Action Required
 The DT messaging system could not be started.
 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 if the hostname is correct in these locations:
 /etc/src.sh
 /etc/hosts
 /usr/adm/inetd.sec
4. Check to see any magic cookie related error messages in these locations:
 /var/adm/messages 
 $HOME/.dt/errorlog
 For additional information, see the DT User's guide.

Checking these files, I found that:

Code:
               /etc/src.sh

does not exist

Code:
              /etc/hosts host

host appears ok

Code:
             /usr/adm/inetd.sec

does not exist


Code:
             /var/adm/messages

there are 4 versions of this file. I never found "magic" or "cookie" though there were other multiple error entries- the most common I see are (ignore all the "<FONT size=3><FONT face=Calibri> stuff, I think its a paste issue:


Code:
DirectoryE mount[1029]: [ID 218687] user.error] N_NAS:/mnt/pools/A/A0/NSFShare: Permission denied
DirectoryE ufs: [ID 845546 kern.notice] NOTICE: alloc: /: file system full
A few "reboot after panic" entries
DirectoryE savecore: [ID 170680] not enough space in /var/crash/DirectoryE (268 MB avail, 278 MB needed)

and then checking
Code:
Bjones/.dt/errorlog  (and errorlog.old)

both were empty



Also, I noticed a message window behind the other window (likely the other users got it as well):

Code:
 Trash Can
 
 Unable to access this trash information file:
 /home/Bjones/.dt/Trash/.trashinfo
 All trash operations will not be performed The most common causes are:
                 -Network authentication
                 -Insufficient disk space.
                 -Wrong permissions $HOME/.dt/Trash.


Last edited by Stellaman1977; 06-29-2018 at 01:08 PM..
# 2  
Old 06-29-2018
How can root login? Text on the console? Or over the network?

You mention a full drive. What message are you getting? If root can login and open a terminal, you should be able to check that easily.

Code:
df -v

Check /etc/hosts for the hostname and correct ip.
This User Gave Thanks to hicksd8 For This Post:
# 3  
Old 07-03-2018
Thanks.. It was the full drive. I was able to clear off a 120MB file and the user accounts started working again.
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. HP-UX

Help needed HP UX 11.11i new install on C8000 Desktop messaging system error CAN'T FIX

Hi, I have a HP UX C8000 box , have installed 11.11i from 4 x cds numerous times to try to get a functioning Network or to try and get rid of this error on start up, after new install and 1st startup I get an error "The desktop messaging system could not be started" and then advice about... (12 Replies)
Discussion started by: C8000
12 Replies

2. Solaris

Solaris 8, you boot the system but does not have anything on the screen (not started)

Greetings to all. I have two computers, Sun Blade 150. the first, had the Solaris 8 system, and that system needed to clone the "second" to start it with the same settings. Use a program to clone the drive, and then have cloned, had the error: Can't read disk label. Can't open disk... (4 Replies)
Discussion started by: feliz-58
4 Replies

3. UNIX for Advanced & Expert Users

The DT messaging system could not be started

Hello All, I am getting " The DT messaging system could not be started" message when wants to login as root on a box running on tru64 5.1A. /etc/hosts is ok. when i see in .dt/errorlog it shows message server could not be started. Thanks for help. Awadhesh (2 Replies)
Discussion started by: Awadhesh
2 Replies

4. Solaris

Solaris 10 CDE problem - The DT messaging system could not be started

A Google search with: +Solaris +"The DT messaging system could not be started" returns 138 hits. All of the relevant possible solutions are in this document. My apologies for such a long document but I thought I would try to minimize the resolution attempts that I've already tried. System... (1 Reply)
Discussion started by: rpollard001
1 Replies

5. IP Networking

DT messaging could not be started

this id the message i get with a suggestions to check those files: /etc/src.sh /etc/hosts /usr/adm/inetd.sec i have little knowledge of hoe to edit those files/ i went to the etc library and didn't found src.sh file. what should i do? also didn't find the inetd.sec file In the host... (3 Replies)
Discussion started by: amirp
3 Replies

6. HP-UX

HP VUE Messaginbg system could not be started

hi guys..its been a while since my last post... a friend of mine has a problem with their HP Openview and has the following error: The HP VUE messaging system could not be started. To correct the problem: 1. Choose to return to the login-screen. 2. Select failsafe session.... ... ... (2 Replies)
Discussion started by: inquirer
2 Replies

7. UNIX for Dummies Questions & Answers

The Desktop Messaging System Could Not Be Started HP-UX

Hi People! I've just got a HP-UX system dumped on me. I've started it, followed all the install/setup questions, and everything was going ok, right upto when going into the desktop enviroment I got the message "The Desktop Messaging System Could Not Be Started". Now I've checked the... (8 Replies)
Discussion started by: cpiuk
8 Replies
Login or Register to Ask a Question