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

Sponsored Content

Operating Systems Solaris Solaris 10 CDE problem - The DT messaging system could not be started Post 302258032 by solaris12345 on Thursday 13th of November 2008 05:01:51 PM

11-13-2008

Registered User

dt Messaging system could not be started

I got what may perhaps be a similar message. When I clicked "OK", I was reverted back to login screen (perhaps cde).

I had previously disconnected the hme0 interface from my dhcp provider and attached it to another router which was supplying dhcp information.

I had however, before doing any of these steps, edited /etc/default/dhcpagent
and removed the "12' from:
PARAM_REQUEST_LIST=1,3,6,15,28,43

So that a hostname may not, by agent, via dhcp server be requested.

Setting hostnames for a system connected to a dhcp server is documented elsewhere - a google search may reveal that.

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)
"
For IPv4, the dhcpagent daemon can be configured to request
a particular host name. See the REQUEST_HOSTNAME description
in the FILES section. When first configuring a client to
request a host name, you must perform the following steps as
root to ensure that the full DHCP negotiation takes place:

# pkill dhcpagent
# rm /etc/dhcp/interface.dhc
# reboot
"

I got the message, believing this to be caused by the dhcp server change, I logged in via "command line login" and, I, did, a reboot...

I did not have the issue when the system rebooted and, I was, via, perhaps, CDE, login.

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, have, the same issue...

solaris12345

View Public Profile for solaris12345

Find all posts by solaris12345

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

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

4. UNIX Desktop Questions & Answers

How to migrate Solaris 10 CDE config to HP-UX CDE.

Hello, Do you guys by any chance know what is the best (if any ) way to move CDE configuration from a SOLARIS 10 machine to HP-UX? Just the config (actions, text files etc). Thanks in advance!

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

6. Solaris

Solaris 8 CDE Problem

All, I'm running Solaris 8 on a Sparcbook. One of my users, when logging in, defaults to Open Windows desktop rather than CDE. All other users get logged into CDE just fine. Is there a file or something that tells the system what default login is? I'm confused as to why it's just for this one...

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

LEARN ABOUT POSIX

dhcp

dhcp(5) 						Standards, Environments, and Macros						   dhcp(5)

NAME

       dhcp - Dynamic Host Configuration Protocol

DESCRIPTION

       Dynamic	Host Configuration Protocol (DHCP) enables host systems in a TCP/IP network to be configured automatically for the network as they
       boot. DHCP uses a client/server mechanism: servers store configuration information  for	clients,  and  provide	that  information  upon  a
       client's request. The information can include the client's IP address and information about network services available to the client.

       This manual page provides a brief summary of the Solaris DHCP implementation.

   Solaris DHCP Client
       The  Solaris  DHCP  client  is implemented as background daemon, dhcpagent(1M). This daemon is started automatically during bootup if there
       exists at least one dhcp.interface file in /etc. Only interfaces with a corresponding /etc/dhcp.interface file are automatically configured
       during  boot.  Network  parameters  needed for system configuration during bootup are extracted from the information recieved by the daemon
       through the use of the dhcpinfo(1) command. The daemon's default behavior can be altered by changing the tunables in the  /etc/default/dhc-
       pagent  file.  The  daemon is controlled by the ifconfig(1M) utility. Check the status of the daemon using the netstat(1M) and ifconfig(1M)
       commands.

   Solaris DHCP Server
       The Solaris DHCP server is implemented as a background daemon, in.dhcpd(1M). This daemon can deliver network configuration  information	to
       either  BOOTP  or  DHCP	clients.  The Solaris DHCP service can be managed using the dhcpmgr(1M) GUI or the command line utilities dhcpcon-
       fig(1M), dhtadm(1M), and pntadm(1M).

   DHCP Configuration Tables
       The Solaris DHCP server stores client configuration information in the following two types of tables:

       dhcptab tables	       Contain macros and options (also known as symbols), used to construct a package	of  configuration  information	to
			       send to each DHCP client. There exists only one dhcptab for the DHCP service. The dhcptab(4) can be viewed and mod-
			       ified using the dhtadm(1M) command or dhcpmgr(1M) graphical utility. See dhcptab(4) for more information about  the
			       syntax of dhcptab records. See dhcp_inittab(4) for more information about the DHCP options and symbols.

       DHCP network tables     DHCP  network  tables,  which  contain  mappings of client IDs to IP addresses and parameters associated with those
			       addresses. Network tables are named with the IP address of the network, and can be created,  viewed,  and  modified
			       using  the  pntadm  command  or	dhcpmgr  graphical utility. See dhcp_network(4) for more information about network
			       tables.

SEE ALSO

       dhcpinfo(1), dhcpagent(1M), dhcpconfig(1M), dhcpmgr(1M),  dhtadm(1M),  ifconfig(1M),  in.dhcpd(1M),  netstat(1M),  pntadm(1M),  syslog(3C),
       dhcp_network(4), dhcptab(4), dhcpsvc.conf(4), dhcp_inittab(4), dhcp_modules(5)

       Solaris DHCP Service Developer's Guide

       Alexander, S., and R. Droms. RFC 2132, DHCP Options and BOOTP Vendor Extensions.  Silicon Graphics, Inc. Bucknell University. March 1997.

       Droms, R. RFC 1534, Interoperation Between DHCP and BOOTP. Bucknell University. October 1993.

       Droms, R. RFC 2131, Dynamic Host Configuration  Protocol. Bucknell University. March 1997.

       Wimer, W. RFC 1542, Clarifications and Extensions for the Bootstrap Protocol. Carnegie Mellon University. October 1993.

SunOS 5.10							    13 Mar 2001 							   dhcp(5)