[Info-vax] grey screen of death

[Peter 'EPLAN' LANGSTOeGER]

In article <mjse36$10jn$2 at news.kjsl.com>, helbig at asclothestro.multivax.de (Phillip Helbig (undress to reply)) writes:
>If I try to launch an application to display on the graphics monitor 

What appl: DECW$EXAMPLES:ICO.EXE perhaps?

>connected to the 8.4 node, I get:
>
>Xlib: connection to "_WSA16:" refused by server
>Xlib: Client is not authorized to connect to Server
>X Toolkit Error: Can't Open display
>%DWT-F-NOMSG, Message number 03AB8204

How did you do this?
I thought your DECW$SERVER process is dying?

To fix an X11 server security problem, you need
*) a running X11 server (DECW$SERVER_0 process)
*) ways to affect its security
-) by defining access for the initial phase of the X11 server
via the files SYS$STARTUP:DECW$SERVER_ACCESS_ALLOWED.DAT (and another one
I can't remember now - something with TRUST or so) when there is no session
-) by defining access for the current session (via DECW$SESSIONMGR and
its saved settings via SYS$LOGIN:[.DT.SESSIONS.CURRENT]DT.RESOURCES file)

>I suspect that the message doesn't indicate the real problem.

I second this. Although I think, if you have an X11 server running
for some seconds (during them you got this error message above)
and then the server is dying (but before DECW$GREET/DTLOGIN is starting
it could well be a resource/quota problem.

The fact, that the server ran after the VMS upgrade, doesn't mean it gets
enough resources now (now that you finished some more upgrade tasks ;-).

After your DECW$SERVER_0 process died, how does the error message
(for accessing it from remote) look like then? Have you checked it?
(I expect a "Xlib: ... Network error: Connection refused" message then)


btw: Have you run SYS$UPDATE:LIBDECOMP already?
-- 
Peter "EPLAN" LANGSTÖGER
Network and OpenVMS system specialist
E-mail  Peter at LANGSTOeGER.at
A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist