Sponsored Content
Top Forums UNIX for Advanced & Expert Users The DT messaging system could not be started Post 302267915 by Izoo on Sunday 14th of December 2008 04:14:46 PM
Old 12-14-2008
Bug The DT messaging system could not be started on tru64 unix 5.1a

I do get the same error message running on a compaq alpha box, ES45. This also result on the system losing the network settings when rebooted.
 

7 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

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. 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

6. 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

7. Shell Programming and Scripting

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... (2 Replies)
Discussion started by: Stellaman1977
2 Replies
eli(8)							      System Manager's Manual							    eli(8)

Name
       eli - error log initialization program

Syntax
       eli [ options ]

Description
       The command initializes error logging.  This command enables error logging of hardware and system-related error packets, or error messages,
       from the kernel errorlog buffer.  It can also disable error logging, reconfigure error logging parameters, or initialize the kernel  error-
       log buffer.

Options
       -d     Disables error logging.

       -e     Enables error logging in multiuser mode.

       -f     Forces the subsequent option; the system will not prompt.  This is the only command option you can use with another option.

       -h     Prints information about the command.

       -i     Initializes the kernel errorlog buffer.  The previous contents of the errorlog buffer are lost.

       -l     Logs a one-line status message to the kernel errorlog buffer.

       -n     Only supported for local error logging.  Disables logging error packets to disk by the daemon. High priority error messages continue
	      to be printed at the console.  Note that error log packets can be viewed by using the option in real time, but are never written	to
	      the disk.  For this reason, this option is rarely used.

       -q     Suppresses the periodic display, on the console, of the missed error message that results from a full kernel errorlog buffer.

       -r     Reconfigures error logging.  Use this option after changing the file.

       -s     Enables error logging in single-user mode.

       -w     Enables the missed error message to appear on the console every 15 minutes.  This option is the opposite of

Examples
       This example logs a one-line message into the errorlog file.
       eli -f -l "This is a test message"
       This example logs a message, up to and including the first new line, from the file
       eli -f -l < myfile > /dev/null

Restrictions
       You must have superuser privileges to use the command.

       Only the -f option can be used with other options.  You must use the syntax shown in the examples above.

Diagnostics
       eli: Request Aborted.
       The requested action was aborted.  The reason for the aborted command is included with the output.

Files
See Also
       elcsd.conf(5), elcsd(8), uerf(8)
       Guide to the Error Logger

																	    eli(8)
All times are GMT -4. The time now is 08:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy