HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- CDE login problem
Operating System - HP-UX
1834296
Members
2184
Online
110066
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
05-01-2001 05:11 AM
05-01-2001 05:11 AM
Cannot log on the HP-UX 10.20 9000/715 system after succesfull OS install neither from CDE console nor via X terminal emulator (telnet works though). Getting the following error from the desktop:
"Unnable to initialize or connect to the Desktop messaging system. Check your $HOME/.dt/errorlog for more information".
Here is what in the errorlog:
------------------------
Tue May 01 09:09:14 2001
dtsession: 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. Please see your System
Administrator.
Tue May 01 09:09:28 2001
dtsession: Screen lock when the screen saver is turned on is not available on this server. Your screen will no
t be locked when the screen saver is turned on.
Tue May 01 09:09:31 2001
Workspace Manager: I/O error on display:: 205.153.28.217:0.0
-----------------
How to fix it?
Thanks,
Eugene
"Unnable to initialize or connect to the Desktop messaging system. Check your $HOME/.dt/errorlog for more information".
Here is what in the errorlog:
------------------------
Tue May 01 09:09:14 2001
dtsession: 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. Please see your System
Administrator.
Tue May 01 09:09:28 2001
dtsession: Screen lock when the screen saver is turned on is not available on this server. Your screen will no
t be locked when the screen saver is turned on.
Tue May 01 09:09:31 2001
Workspace Manager: I/O error on display:: 205.153.28.217:0.0
-----------------
How to fix it?
Thanks,
Eugene
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2001 05:19 AM
05-01-2001 05:19 AM
Solution
MOST LIKELY CAUSE(S) :
The /usr/dt/bin/ttsession couldn't start due to networking problems,
name resolution, or problems with ttsession.
TROUBLESHOOTING:
1) From the CDE login select Options -> Session -> Failsafe Session
and login as root.
2) Run /usr/contrib/bin/X11/dr_dt. The end of the output from this
script says: X ERRORs and X WARNINGs. These errors and warnings
should be resolved before CDE will run properly.
3) Check the error log /var/dt/Xerrors
Check the error log $HOME/.dt/errorlog
4) The output from "nslookup" and "nslookup " should
be the same. This checks for a) duplicate IP addresses or
hostnames or b) problems with name resolution. If nslookup fails
then CDE will fail to start. If the first line returned from nslookup
is: "Name Server" then you are using DNS. Move "/etc/resolv.conf" to
another name, i.e. /etc/resolv.conf.orig and rerun nslookup. If
nslookup now succeeds then try logging into CDE again.
5) Check permissions and ownership of the following files:
-r--r--r-- 1 bin bin 616 Jul 1 16:03 /etc/hosts
-r--r--r-- 1 root sys 1010 Jun 25 18:22 /var/adm/inetd.sec
6) Check the contents of /var/adm/inetd.sec. It should contain
dtspc allow
spc allow
mserve allow
If not add the lines and run "/usr/sbin/inetd -c" to reread the file.
7) /usr/sbin/ping
You should get back 0% packet loss. If you get something different
then check your network configuration.
8) Make sure the $LANG environment variable is set correctly. It should
be set to C or unset for American-English.
9) Exit the failsafe session. From the CDE login select Options ->
Command Line Login. When the screen turns black, press and
you should get a Console Login prompt. Login as root.
10) mv $HOME/.dt $HOME/.dt.orig
mv $HOME/.dtprofile $HOME/.dtprofile.orig
exit (to return to CDE) - try logging in as root.
The /usr/dt/bin/ttsession couldn't start due to networking problems,
name resolution, or problems with ttsession.
TROUBLESHOOTING:
1) From the CDE login select Options -> Session -> Failsafe Session
and login as root.
2) Run /usr/contrib/bin/X11/dr_dt. The end of the output from this
script says: X ERRORs and X WARNINGs. These errors and warnings
should be resolved before CDE will run properly.
3) Check the error log /var/dt/Xerrors
Check the error log $HOME/.dt/errorlog
4) The output from "nslookup
be the same. This checks for a) duplicate IP addresses or
hostnames or b) problems with name resolution. If nslookup fails
then CDE will fail to start. If the first line returned from nslookup
is: "Name Server" then you are using DNS. Move "/etc/resolv.conf" to
another name, i.e. /etc/resolv.conf.orig and rerun nslookup. If
nslookup now succeeds then try logging into CDE again.
5) Check permissions and ownership of the following files:
-r--r--r-- 1 bin bin 616 Jul 1 16:03 /etc/hosts
-r--r--r-- 1 root sys 1010 Jun 25 18:22 /var/adm/inetd.sec
6) Check the contents of /var/adm/inetd.sec. It should contain
dtspc allow
spc allow
mserve allow
If not add the lines and run "/usr/sbin/inetd -c" to reread the file.
7) /usr/sbin/ping
You should get back 0% packet loss. If you get something different
then check your network configuration.
8) Make sure the $LANG environment variable is set correctly. It should
be set to C or unset for American-English.
9) Exit the failsafe session. From the CDE login select Options ->
Command Line Login. When the screen turns black, press
you should get a Console Login prompt. Login as root.
10) mv $HOME/.dt $HOME/.dt.orig
mv $HOME/.dtprofile $HOME/.dtprofile.orig
exit (to return to CDE) - try logging in as root.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2001 11:12 AM
05-01-2001 11:12 AM
Re: CDE login problem
Thank you Alex for your help.
The problem was caused by the system network config: I found that ping worked whereas ping didn't. So I fix it by proper configuring DNS.
Regards,
Eugene
The problem was caused by the system network config: I found that ping
Regards,
Eugene
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2001 03:50 PM
11-12-2001 03:50 PM
Re: CDE login problem
I also have a problem in CDE Login. The errolog is same, just I don't have this message :
dtsession: Screen lock when the screen saver is turned on is not available on this server. Your screen will not be locked when the screen saver is turned on.
I follow the troubleshooting as per Alex's advice, but still fail to login to CDE.
This thing only happen when I login as "builder" name. When I login as root, no problem. The different is if I login as root, I don't run any program. Just go into CDE. If I login as "builder" I must run my application program. The CDE is appeared, but I can not do anything. I must click 'OK' button in the window displaying error message and the back to login window again.
Please advise how to fix it.
Regards,
Hendra
dtsession: Screen lock when the screen saver is turned on is not available on this server. Your screen will not be locked when the screen saver is turned on.
I follow the troubleshooting as per Alex's advice, but still fail to login to CDE.
This thing only happen when I login as "builder" name. When I login as root, no problem. The different is if I login as root, I don't run any program. Just go into CDE. If I login as "builder" I must run my application program. The CDE is appeared, but I can not do anything. I must click 'OK' button in the window displaying error message and the back to login window again.
Please advise how to fix it.
Regards,
Hendra
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP