- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: CDE error
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2002 01:49 PM
02-08-2002 01:49 PM
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."
I have done all above, and I believe everything is OK - are there any signs for #'s 2 & 3 in above list that I can check from the command line?
Thanks
Jeff
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2002 01:54 PM
02-08-2002 01:54 PM
Re: CDE error
# nslookup hostname
# nslookup ip_address_for_host
Do this for both the hostname and IP address of your system. Each should return the proper value for the other. If they don't then you need to fix whatever the problem is.
If you are using DNS, check your /etc/nsswitch.conf file for the line:
hosts: files [NOTFOUND=continue] dns
I would put files first and then dns so that local hostname lookups don't have to go to DNS.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2002 01:56 PM
02-08-2002 01:56 PM
Solutionhttp://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x72b479bffde7d4118fef0090279cd0f9,00.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2002 02:17 PM
02-08-2002 02:17 PM
Re: CDE error
GL,
C
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2002 07:48 AM
02-09-2002 07:48 AM
Re: CDE error
you told us, that you checked your networking configuration. Did you also check the entries in the namsvrs file? Is there an entry for DNS or NIS and that service is not used? If so, you get the CDE- error you described.
Allways stay on the bright side of life!
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2002 11:45 AM
02-11-2002 11:45 AM
Re: CDE error
That link was most helpful, I ran the dr_dt command and was able to find the source of my problem (I hope) - the file /var/adm/inetd.sec is missing, how would I go about recreating this or is it automatically done on install?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2002 11:51 AM
02-11-2002 11:51 AM
Re: CDE error
There should be a sample inetd.sec in /usr/newconfig/var/adm/inetd.sec that you can look at.
Keep in mind that anytime you modify /var/adm/inetd.sec you will need to get inetd to re-read its configuration with an 'inetd -c'.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2002 11:54 AM
02-11-2002 11:54 AM
Re: CDE error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2002 01:00 PM
02-11-2002 01:00 PM
Re: CDE error
permissions=dr-xr-xr-x
owner=root
group=sys
For HP CDE to function correctly, it should be a directory with the following configuration:
permissions=drwxr-xr-x
owner=root
group=root
If I change the group with chgrp root /, then it says the group should be sys. If I change the permissions using chmod u+w /, then it reports that the permissions should be dr-xr-xr-x
What's going on - I am fairly new to UNIX, having a real hard time getting the A-class server up using CDE
Thanks
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2002 01:05 PM
02-11-2002 01:05 PM
Re: CDE error
drwxr-xr-x 31 root root 2048 Feb 6 09:38 /
CDE is working fine on my machine with those permissions.
Have checked hostname resolution?
# nslookup hostname
should return appropriate IP address
# nslookup ip_address
should return appropriate hostname
Incorrect resolution can cause some screwy problems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2002 01:08 PM
02-11-2002 01:08 PM
Re: CDE error
The permissions should be like this,
/etc/hosts -r--r--r-- bin:bin
/etc/nsswitch.conf -rw-r--r-- root:sys
/etc/resolv.conf -rw-r--r-- root:sys
/var/adm/inetd.sec -r--r--r-- root:sys
$HOME drwxr-xr-x (user):(group)
$HOME/.dt drwxr-xr-x (user):(group)
$HOME/.TTauthority drwxr-xr-x (user):(group)
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2002 01:10 PM
02-11-2002 01:10 PM
Re: CDE error
You can give this link a try,
http://us-support2.external.hp.com/cki/bin/doc.pl/sid=b41445fe0a48140f36/screen=ckiDisplayDocument?docId=200000058694013
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2002 01:38 PM
02-11-2002 01:38 PM
Re: CDE error
*** ERROR(4): dtsession: PID 3311: Mon Feb 11 15:39:44 2002
The ToolTalk session server (ttsession) could not be started. This indicates that either ToolTalk is not installed or that it is not installed correctly on this machine
When I log in via Failsafe mode, ttsession and rpc.ttdbserver are both running in the process management window of SAM, directed to the proper IP of my X-terminal. BTW, I'm using Xfree86 w/Cygwin to access CDE, using the command
Xwin -query [host] -from [terminal] -fp tcp/[host]:7100
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2002 02:12 PM
02-11-2002 02:12 PM
Re: CDE error
this link explains the tooltalk errors,
http://us-support2.external.hp.com/cki/bin/doc.pl/sid=7473c4de07d627f70c/screen=ckiDisplayDocument?docId=200000058693859
Also check out this link,
http://us-support2.external.hp.com/cki/bin/doc.pl/sid=7473c4de07d627f70c/screen=ckiDisplayDocument?docId=200000058693886
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2002 09:07 PM
02-11-2002 09:07 PM
Re: CDE error
#set_parms hostname
#set_parms ip_address
Specify the same host name and IP addresses once again. This should update all the required files with the right hostname and ip address.
After this, ensure that /etc/hosts file has read permission to all.(becasue the set_parms command will update the /etc/hosts file and sets it permission as per the default umask setting)
Most of the time this error used to appear because of improper permission set on the /etc/hosts file or even if there is an IP Clash.
To determine whether there is an IP clash or not, you can disconnect your server from the network and ping the IP address of the server from some other system in the network.
Hope this helps you!
-K.Vijay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2002 10:24 AM
02-12-2002 10:24 AM