[Info-vax] DECwindows no longer starting on satellite

[Wilm Boerhout]

smithfarm mentioned  on 14-11-2010 14:44:
> Thanks. Now I have a different problem.
>
> My two-node cluster had been booting and running OK. However, I needed
> to execute certain node-specific commands at startup so I wrote a
> command procedure (NODE_SPECIFIC_START.COM) and put it in
> SYS$SPECIFIC:[SYSMGR]. I did this on each node separately.
>
> Then I put the following line in SYS$STARTUP:SYSTARTUP_VMS.COM:
>
> $ @SYS$SPECIFIC:[SYSMGR]NODE_SPECIFIC_START.COM
>
> So far, so good. Except this appears to have broken the last line in my
> SYSTARTUP_VMS.COM script, which starts DEC Windows:
>
> $ @SYS$STARTUP:DECEVENT$STARTUP.COM
>
> The boot server node, which doesn't have a graphics card, reacts to this
> command as it did before (i.e., it tells me "No graphics card found, not
> starting DECwindows." or something to that effect).
>
> However, on the satellite node, which had been booting into DECwindows
> just fine, I now get the following error when it runs the
> DECEVENT$STARTUP script:
>
> %DCL-E-OPENOUT, error opening DIA$:[MANAGER]DECEVENT_START.TMPCOM; as
> output
> -RMS-E-DNF, directory not found
> -SYSTEM-W-NOSUCHFILE, no such file
> %PURGE-W-SEARCHFAIL, error searching for
> DIA$:[MANAGER]DECEVENT_START.TMPCOM;
> -RMS-E-DNF, directory not found
> -SYSTEM-W-NOSUCHFILE, no such file
>
> If I'm not mistaken, DECwindows *did* start after these error messages
> were displayed. Once. But after the next reboot all I get are these
> messages and no DECwindows.
>
> I get the same error messages (and no DECwindows) when I try to run
> DECEVENT$START interactively.


Why would DECEVENT$STARTUP have anything to do with DECwindows?

For troubleshooting startup issues, it is sometimes nice to have a 
startup log.

Put a $SET VERIFY and $SET NOON in the top of your node specific procedure.

Then, on the node that fails, do the following:

$ MC SYSGEN
SYSGEN> USE CURRENT
SYSGEN> SET STARTUP_P2 "CD"
SYSGEN> WRI CURRENT
SYSGEN> EXIT

and reboot. After reboot, you will have a SYS$SYSTEM:STARTUP.LOG file 
with a report of all that happend in your startup script. Reading it 
will help you (and posting the relevant part will help us help you)

NOTE: you could/should also put STARTUP_P2="CD" in your MODPARAMS.DAT 
file and then AUTOGEN.


Wilm Boerhout         |
Zwolle,               |   'These are the times that try men's souls'
The Netherlands       |   (Thomas Paine, The Crisis)