[Info-vax] grey screen of death

[Peter 'EPLAN' LANGSTOeGER]

In article <mjth8q$1ai1$1 at news.kjsl.com>, helbig at asclothestro.multivax.de (Phillip Helbig (undress to reply)) writes:
>In article <iur93c-aah.ln1 at news.chingola.ch>, Paul Sture
><nospam at sture.ch> writes: 
>
>> >> 	and by considering the following lines for your MODPARAMS.DAT
>> >> 	MIN_LNMSHASHTBL=512
>> >> 	MIN_MAXPROCESSCNT=128
>> >> 	MIN_PQL_DBYTLM=32768
>> >> 	MIN_RESHASHTBL=512
>> >> 	MIN_TTY_ALTYPAHD=2064
>> >> 	MIN_TTY_ALTALARM=1600
>> >> 	MIN_TTY_TYPAHDSZ=2064
>> >
>> > Have done all the suggestions.  Will see what happens after AUTOGEN and 
>> > REBOOT.
>
>OK, AUTOGEN and reboot.
>
>Problem is still the same.  

I feared so.
I have them in my MODPARAMS include files for such a long time
I only wanted you to know/consider them.
(I think, they were for C-KERMIT, SET HOST/LAT and more like upgrade problems)

>DECW$SERVER_0 is always there.  DTLOGIN appears for about a second every
>few seconds or so, and DTGREET for just a fraction of a second. 
>Something is looping. 

Something is dying (and the DECW$SERVER has an error retry)
That is not the same as DECW$SERVER is looping (at prio 6) as with
I described for the problem with OPEN3D.

With a looping prio 6 process, you get nothing from the machine
(except some infos via AVAILMAN) until you reduce the prio of
DECW$SERVER_0 process to 4 or below or kill the process.

>ACCOUNTING shows subprocesses being terminated (successfully) about 6
>times per second.  This is after the restart of DECwindows from a
>different but privileged account so I'm pretty sure the subprocesses are
>related to the restart, based on the username.  (When I've occasionally
>had to restart a running DECwindows in the past, it worked fine from
>this account.) 

Ok.

But restarting DECW$SERVER is a little bit different than starting it
(as you need a process to kill the server and recreate it with a .COM file
written on the fly) so that can add confusion to error analysis.

>MONI SYSTEM shows about 16 per cent CPU, but SHOW SYSTEM shows total CPU 
>time for all processes on the system of just a few seconds.  Nothing 
>ever shows up as the "top" process.  Also, MONI SYSTEM/TOPC shows 
>nothing.  My guess is that these subprocesses are using up the CPU, but 
>exist for too short a time for MONITOR to catch them.
>
>It really looks like something is looping.

Really? Repeating something 6 times qualifies as looping? Not in my eyes.

>ACCOUNTING/FULL is useful, but it would be more useful if it would give 
>the process name.  :-(  The huge number of subrocesses also make it 
>difficult to look through them all.  I did see some "quota exceeded" 
>messages, though.  :-|
>
>Could it be the OPEN3D problem, as Peter mentioned?

Don't know (the symptoms seems different).

But Open3D is *not* supported/working after OpenVMS Alpha V7.3-2.
And the last version was V4.9B (from 2001)

	http://h30266.www3.hp.com/XLS/AlphaUpdateHistory.xls

If you want to get rid of it you have to manually delete the files.
And I still recommend to remove Open3D...

>Is there any danger in de-installing it?  Or do I have to repeat the 
>upgrade?  :-)

No need to repeat the upgrade.

Good luck (as always)
-- 
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