Operating System - HP-UX
1754968 Members
3278 Online
108828 Solutions
New Discussion

CDE login starts then dies on HP11.11 after ignite

 
Ted_5
Occasional Advisor

CDE login starts then dies on HP11.11 after ignite

HP 11.11 (11i) 9000/859

After ignite build, The CDE login starts and then when you try to login, it dies.
Ctrl/c goes to the consol login.

restart dtlogin and the same thing happens

The /var/dt/Xerrors file contains:

error (pid 5091): server for display mynode:0 terminated unexpectedly 0
XIO: fatal IO error 232 (conection reset by peer) on Xserver "mynode:0.0"
after 1606 requests (1581 Known processed) with 0 events remaining.

I also install patch PHSS_24087 but with no luck.

The same think happen with /usr/contrib/bin/X11/startx or twm.

I can rlogin to the system, set display to another node and run ./dtsession
this gives the full CDE from the mynode system to the other system.

Runing dtlogin remotly shows no errors except in the /var/dt/Xerrors file.

How can I check the graphics controller and drivers to make sure they are
correct?


Also: any other ideas??

Thanks

Ted



1 REPLY 1
Alex Glennie
Honored Contributor

Re: CDE login starts then dies on HP11.11 after ignite

Check the obvious first : ensure networking and hostname resolution are working : backward and forward nslookup of ip & hostname check out ?

run dr_dt CDE diagnostic : check perms , missing filesets ?

Is it possible to install from media other than ignite in case of corruption ?

All users affected ? can they log into a failsafe session ? Are they using the default Lang/Locale - C

If the users accounts have been restored ... try creating a brand new user ?

Lastly :

1. install PHSS_21811 11.i Xserver patch ?

2. core file produced ? tusc Xserver process for clues ? Top output - is the dtlogin or Xserver eating CPU at this time ?

3. Whats the H/W and the graphics H/W ? (graphinfo will tell you ....)

4. How many processors ......? Is it posible to disabble all bar 1 cpu .... does the problem still occur ?

5. Advise : log a call with HP if above does not yield further clues.It just maybe something new ?