Xmanager Forum

HP-UX XDMCP crash.

Last post: Friday, January 15, 2010 1:44 AM by Support, 3 reply

 
Wednesday, December 16, 2009 2:23 AM - Neill MItchell

HP-UX XDMCP crash.

 
I have 3 HP-UX boxes that I connect to. I use the same X Profile for each but two of them fail after the CDE log-in is completed. I am at a loss as to what is happening.

Here is the log for the good one: (I have added the full logs as attachments X3.log is the bad one.


Monitors: 2
Selected Monitor: Plug and Play Monitor
Same display format: 0
Virtual screen x 0, y 0, w 2560 h 1024
Root Window x 1280, y 0, w 1280, h 998
Exact StoreColor: 0
Reverse RGB Order: 0

Screen 0: 1280 x 998
Keyboard file version: 3.0
Keyboard file: UK102 keyboard
Keyboard type: 1
nKeys, minKC, maxKC, mapWidth, nCompose: 102, 8, 110, 4, 0
Number of keycodes: 103
Number of KeySyms: 412
Bytes of KeySyms: 1648
OpenFont(client 0): 'fixed'
OpenFont(client 0): 'cursor'

=== OS Version Information ===
Platform id : 2
Major Version : 5
Minor Version : 1
Build Number : 2600
Description : "Service Pack 3"
Country Code : 44
Country String: United Kingdom
ANSI Code Page: 1252
Language ID : 9
==============================

Waiting for client connections ...

Xdmcp Request Address: 10.44.8.23
Xdmcp Connection Address 0: 10.44.3.216
Xdmcp: sent a REQUEST message
Xdmcp: received an ACCEPT message
Xdmcp: sent a MANAGE message.
Xdmcp: Connection has been established. Going to run session...
Xdmcp KeepAliveTime: 0 seconds
OpenFont(client 3): 'cursor'
OpenFont(client 3): 'Fixed'
OpenFont(client 3): 'fixed'
OpenFont(client 3): '-dt-interface system-medium-r-normal-l sans-18-180-72-72-p-106-hp-roman8'
OpenFont(client 3): '-dt-interface system-medium-r-normal-l sans-18-180-72-72-p-106-hp-roman8'
OpenFont(client 3): '-dt-interface user-medium-r-normal-l sans-17-170-72-72-m-100-hp-roman8'
OpenFont(client 3): '-dt-interface user-medium-r-normal-l sans-17-170-72-72-m-100-hp-roman8'
.................................................
OpenFont(client 2): '-dt-interface user-bold-r-normal-m sans-14-140-72-72-m-90-hp-roman8'

------------------------------------------------------------------------------------------------------
And the bad log:


Monitors: 2
Selected Monitor: Plug and Play Monitor
Same display format: 0
Virtual screen x 0, y 0, w 2560 h 1024
Root Window x 1280, y 0, w 1280, h 998
Exact StoreColor: 0
Reverse RGB Order: 0

Screen 0: 1280 x 998
Keyboard file version: 3.0
Keyboard file: UK102 keyboard
Keyboard type: 1
nKeys, minKC, maxKC, mapWidth, nCompose: 102, 8, 110, 4, 0
Number of keycodes: 103
Number of KeySyms: 412
Bytes of KeySyms: 1648
OpenFont(client 0): 'fixed'
OpenFont(client 0): 'cursor'

=== OS Version Information ===
Platform id : 2
Major Version : 5
Minor Version : 1
Build Number : 2600
Description : "Service Pack 3"
Country Code : 44
Country String: United Kingdom
ANSI Code Page: 1252
Language ID : 9
==============================

Waiting for client connections ...

Xdmcp Request Address: 10.44.8.20
Xdmcp Connection Address 0: 10.44.3.216
Xdmcp: sent a REQUEST message
Xdmcp: received an ACCEPT message
Xdmcp: sent a MANAGE message.
Xdmcp: Connection has been established. Going to run session...
Xdmcp KeepAliveTime: 0 seconds
OpenFont(client 3): 'cursor'
OpenFont(client 3): 'Fixed'
OpenFont(client 3): 'fixed'
OpenFont(client 3): '-dt-interface system-medium-r-normal-l sans-18-180-72-72-p-106-hp-roman8'
OpenFont(client 3): '-dt-interface system-medium-r-normal-l sans-18-180-72-72-p-106-hp-roman8'
OpenFont(client 3): '-dt-interface user-medium-r-normal-l sans-17-170-72-72-m-100-hp-roman8'
OpenFont(client 3): '-dt-interface user-medium-r-normal-l sans-17-170-72-72-m-100-hp-roman8'
OpenFont(client 3): '-dt-interface system-medium-r-normal-xxl sans-24-240-75-75-p-136-hp-roman8'
OpenFont(client 3): '-dt-interface system-medium-r-normal-xxl sans-24-240-75-75-p-136-hp-roman8'
Xdmcp: Control client is closed and the entire session is closed.
All clients are closed down. Going to server reset...
Terminate at server reset is active.

Exiting the waiting loop ...

X server was terminated normally.


Program Ver. : Xmanager 2.x
Connection Method : XDMCP connection
Wednesday, December 16, 2009 9:51 PM - Support

Re: HP-UX XDMCP crash.

 
This problem may occur when:

1. User account is currupted or misconfigured. To find out if this is the cause, try doing the following tests:

- Log in with the same user account from the console.
- Log in using a different user account.
- Log in using a root user account
- Create a new user account and login

2. The DISPLAY value configured manually. Find the login script that is read upon user login and comment out the line that starts like:

export DISPLAY...

or

setenv DISPLAY...



If the problem persists, please send us the following files:

- /var/dt/Xerrors
- $HOME/.dt/errorlog
- $HOME/.dt/startlog
Thursday, January 14, 2010 1:31 AM - Neill Mitchell

Re: HP-UX XDMCP crash.

 
To clarify - I can get to the CDE login page - it fails before the copywrite etc info.


I can run the following:

DISPLAY=:0.0;export DISPLAY
xclock

And it works fine, in fact any Xapplication can be run like this - It's just running the CDE using XDMCP that doesn't (on 2 of 3 identical HP-UX boxes).

All user accounts login fine from the console & via Telent.

No User account (even new ones) can successfully log-in via XDMCP.

var/dt/Xerror is Nil bytes.

errorlog and startlog have no new entries
Friday, January 15, 2010 1:44 AM - Support

Re: HP-UX XDMCP crash.

 
If you can see the login screen, it means Xmanager is setup and running correctly. This problem is most like the configuration/security setup issue on the remote host.

It is difficult to analyze the problem without any error logs. Xmanager log simply shows that the remote host disconnected the sessions. Please configure your remote host to produce all error logs for XDMCP connection and send it to us via email as support@netsarang.com.

Also, please answer the following questions:

1. When did the problem start happening?
2. When Xmanager crashes, does it create any error message?

---
Technical Support