CDE can't open on hpux system keeps saying it will restart after you log out

[Jim Veach]

I've spent a long time away from unix. I' getting errors stateing that it can't open sockets and to check to see if the process is already running. I have two system
which I have not rebooted which work, however when I logged in on this machine
it worked until I exited then this problem showed up. I notice if I log out of the
CDE instead of exiting the CDE remains. Any ideas where to start?

[Steven E. Protter]

I would start looming at the startup script order in /sbin/rc3.d and the DISPLAY variable.

It could perhaps be hardcoded incorrectly in /etc/profile or .profile for the user.

More evidence should be in /var/adm/syslog/syslog.log and /etc/rc.log

Post what you find.

SEP

[Jim Veach]

Here are a couple of files slet me know if you see anything.

Thanks

[Kenneth Platz]

Try checking your permissions on /tmp and /var/tmp. They should be 777. This could be the cause of the problem.

[Jim Veach]

made no diff here is the mesage on the screen which keeps rolling by
Suspending desktop login
press enter for a login prompt
login. desktop login will resume shortly after you log out.

resumeing desktop login

the x-server cannot started on display osprey:0

[Alex Glennie]

anything in /var/dt/Xerrors ?

try running /usr/contrib/bin/X11/dr_dt ....

try /sbin/init 2

/usr/bin/X11/X :0

result/error ? fyi use to kill it

can you login to a failsafe session via CDE's options panel ?

are you using dns to resolve the local hostname ... trying using /etc/hosts instead ....result ?

[Jim Veach]

Yea
server unexpectly died
server for display osprey:0 can't be started

fatal server error
Cannot establish any listening sockets - Make sure Xserver isnt already running.

[Kenneth Platz]

Try doing a "netstat -an" and see if anything is listening on port 6000.

Also, check permissions on /var/spool/sockets (mode 777), and /var/spool/sockets/X11 (mode 777)

[Jim Veach]

did the chmod but no change there
the netstat -an showed a lot of stuff but nothing on port 6000

I still have two workstations up with the cde working this one only failed
after a reboot of the server and an exit from the cde
if I log out of the others it maintains the cde
Darn stange the computer things.

[Sridhar Bhaskarla]

Hi,

Did you run /usr/contrib/bin/X11/dr_dt and see if it produced any errors?.

-Sri

[Jim Veach]

Yea
warning the /usr/lib/bindings/acorn file is not properly conffigured
the current configuration is
permissions are 775
should be 444
then rotates to each file within the dir with the same error.

[Rick Beldin]

What kind of machine is osprey? Is it a workstation or a server?

If this machine doesn't have a graphics adapter, then X will not start - and it never will.

You can prevent CDE from attempting to start the Xserver by commenting out the line that starts X in the file /etc/dt/config/Xservers.

If this machine is a workstation, try logging in to the console and trying to run X directly:

/usr/bin/X11/X :0

The result should be a gray screen over the surface of the graphics monitor and the mouse pointer should be a small X. Does this happen? If not, what are the error messages?

[Jim Veach]

The machine is a high end workstation which normally runs a cad cam system so we have plenty of power and a high end graphics card. I can start
x and get the grey screen and can even start a xterm via a telnet from another system however CDE dosn't start.

[Rick Beldin]

Great. We now know the system is a workstation and should be running graphics. We know that the Xserver *can* start so the problem is likely in the way the CDE is attempting to start it.

Can we get the contents of /var/dt/Xerrors posted here? That file is where CDE's dtlogin (the process that starts X) logs its error messages.

More than likely, if you were able to start it by hand, the problem is some sort of permissions problem. For example, CDE needs to have write access to /dev/null (you would be amazed at how many people remove permissions to this file) and
I believe to /tmp.

[V. Nyga]

Hi Jim,

do you have UX11i?

Do you have input devices configured such as tablet?

Volkmar

[V. Nyga]

Hi again,

from your rc.log I can see:
Start network tracing and logging daemon
Output from "/sbin/rc2.d/S300nettl start":
---------------------------
Initializing Network Tracing and Logging...
nettl : Failed to start console logging due to invalid configuration file. Console logging will be disabled. To correct the problem, enter the command netfmt -pc /var/adm/conslog.opts
and check the output.

and:
Configure HP Core/PCI 100BT interfaces
Output from "/sbin/rc2.d/S323hpbase100 start":
----------------------------
ERROR: invalid duplex value for lan0 interface

Have you checked this?
Volkmar

[Jim Veach]

here is the file and the mouse is attached and works in the xterm
this is a test I keep geting a fail

[Jim Veach]

here is a sample of the text the forum won't allow the file.
Fatal server error:
Couldn't open X pointer device! Is one attached?

^[gXIO: fatal IO error 232 (Connection reset by peer) on X server "osprey:0.0
"
after 0 requests (0 known processed) with 0 events remaining.

Fatal server error:
Couldn't open X pointer device! Is one attached?

^[gXIO: fatal IO error 232 (Connection reset by peer) on X server "osprey:0.0
"
after 0 requests (0 known processed) with 0 events remaining.

Fri Jan 23 03:49:25 2004
error (pid 1544): Server for display osprey:0 can't be started.

Fatal server error:
Couldn't open X pointer device! Is one attached?

[Alex Glennie]

Have you tried changing the mouse ? or recreating it's devise files ? It would appear this maybe where the problems lies given the error.

Or is the mouse connected to a kvm switch or something similar ?

[Jim Veach]

the netfmt returned nothing except to state that it failed and the file would be formated. I have two machines doing this so it's not hardware.

Thanks

[Rick Beldin]

You either have a bad mouse or a bad connection to the mouse:

Fatal server error:
Couldn't open X pointer device! Is one attached?

^[gXIO: fatal IO error 232 (Connection reset by peer) on X server "osprey:0.0
"
after 0 requests (0 known processed) with 0 events remaining.

The first message is from the Xserver, the second is probably from xterm as the Xserver died.

What kind of workstation is this? Depending on the model, you either have a USB, PS2, or if really old, an HIL connection.

If the device is Visualize EG, FX2/4/6 or FXE/5/10, then you can edit /etc/X11/X0devices and allow the Xserver to come up without a mouse by uncommenting:

#first NULL pointer # the X pointer is a null device

I doubt that this is what you want, so I would try swapping the mouse.

Since you say that the problem does NOT occur if you run Xserver as root directly, it is likely a permissions problem on the mouse device file itself.

The device file will vary depending on whether the interface is USB, PS2, or HIL. We need to know the model.

A good command to get all kinds of graphics information about a workstation is:

/opt/graphics/common/bin/graphinfo

[Jim Veach]

The machine is a hp visual c360 and I replaced the mouse
but now change in error
the screen is now rolling with
The xserver cannot be opend on display osprey:0
suspending desktop login
hit return to login in promt
log in desktop login will resume when you log out.

[Rick Beldin]

A C360 uses a PS2 interface. This means that the device file that will be used will be /dev/ps2mouse.

A working configuration should have it set up like this:

ll /dev/ps2mouse
crw-rw-rw- 1 bin bin 159 0x000001 Dec 2 2002 /dev/ps2mouse

The 'rolling' that you report is an indication that CDE (dtlogin) still could not start your Xserver. Login to the console as root and run /usr/bin/X11/X. Do you get the gray screen with the x cursor? Use ctrl-shift-break to get back to the console.

Now login to the console as an ordinary user. Do you get the gray screen? If not, what errors do you get?

[Jim Veach]

its c775 ps2mouse
the xwindow comes with the x in the center and the mouse moves the
x

[Rick Beldin]

Hmmm...

Does X work for BOTH root and an ordinary user?

What does /var/dt/Xerrors show now?