System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Aloha! CDE Desktop error after changing the Server's DNS FQDN. Mahalo!

Chris-Elmore
Visitor

Aloha! CDE Desktop error after changing the Server's DNS FQDN. Mahalo!

Aloha my HP Friends!

My 2 HP-UX 11v3 Server's CDE Desktops are having the same error after changing both Server's DNS FQDNs. Previously, we were able to login to CDE as ROOT. After making the change to the FQDN from hi.ngb.army.mil to ngb.army.mil CDE has this error on both my HP Servers. When I try to connect, I can see the CDE desktop in the X-window session before it closes out with the press of the OK buttion. If I login to the Failsefe Session, i can get in. As far as I can tell, the networking is not having any issues. This one has me wondering what else to try and check next.

Your expert help is greatly appreciated!

 

'The desktop messaging system could not be started.

To correct the problem:

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 that the desktop is properly installed, the hostname is correct (/etc/hosts) and that the network is properly configured.

For additional information, see the CDE User's Guide.

[OK]'

 

I've browsed some of the other threads related to CDE and I've done the obvious things like checking to see if can resolve my hostname or ping in or out from the boxes at the command line and all seems to be ok. Everything else seems to work, except the CDE after I changed the Server FQDN. I also want to mention that it's happened to both my HP Servers.

Thanks in advance for your time and aloha.

Very Respectfully,

Chris Elmore

1 REPLY
Steven Schweda
Honored Contributor

Re: Aloha! CDE Desktop error after changing the Server's DNS FQDN. Mahalo!

> [...] after changing both Server's DNS FQDNs. [...]

   What, exactly, was changed?  DNS data base(s)?  "/etc/hosts"?

> 3. Check to see that [...] the hostname is correct (/etc/hosts) and
> that the network is properly configured.

   I know only enough about CDE to be dangerous, but that's where I'd
start.  Specifically, I'd be looking for inconsistencies between the DNS
data (name-to-number and the reverse) and "/etc/hosts".  And "hostname",
too, probably.  In my (limited, long-ago) experience, name-address
inconsistencies are the easiest way to get this effect ("The desktop
messaging system could not be started.").

> [...] As far as I can tell, the networking is not having any issues.


   As usual, showing actual commands with their actual output can be
more helpful than vague descriptions or interpretations.  In this case,
I'd try something like, say:
      nslookup ngb.army.mil
and then:
      nslookup <whatever_address_you_got_from_the_previous_command>

And then see if those values agree with what's in "/etc/hosts".  And,
just in case:
      hostname

> [...] When I try to connect, I can see the CDE desktop in the X-window
> session [...]

   Are you sitting at a keyboard+mouse+display set which is connected
directly to the HP-UX system, or are you running an X server on some
other (Windows PC or other) system?  What, exactly, does "try to
connect" mean here?  Log in at a CDE login box, or tell the remote X
server to connect (somehow) to the HP-UX system, or what?