RE: STARTUP.LOG?
- From: "Main, Kerry" <Kerry.Main@xxxxxx>
- Date: Thu, 29 Dec 2005 09:40:26 -0500
> -----Original Message-----
> From: R Boyd [mailto:bob@xxxxxxx]
> Sent: December 27, 2005 11:45 AM
> To: Info-VAX@xxxxxxxxxxxx
> Subject: Re: STARTUP.LOG?
>
> And if you try the 20000 flag and still dont get enough information,
> try 10000 -- which will generate excruciatingly detailed logging of
> everything happening before STARTUP.COM is invoked.
>
> If the system is getting to the point where it invokes STARTUP.COM,
> your best bet is the STARTUP_P2 setting mentioned by Jilly. I prefer
> to set all of my Alpha systems to boot with the 20000 flag, so that in
> the event that something does go wrong, I have the information
> available on the 1st go without having to go back and try again. The
> 20000 flag has no effect on the output generated after the transfer of
> control to STARTUP.COM (or whatever is specified by the /STARTUP
> setting in the system parameters).
>
> Robert
>
> Jilly wrote:
> > The only thing I can thik of it to edit STARTUP.COM to put
> in the SET PREFIX
> > and set STARTUP_P2 to VDC.
> >
> > "Phillip Helbig---remove CLOTHES to reply"
> <helbig@xxxxxxxxxxxxxxxxxxxxxxxx>
> > wrote in message news:dookcb$jle$3@xxxxxxxxxxxx
> > >I have an ALPHA which hangs for a couple of minutes AFTER
> it joins the
> > > cluster. This is a 21164A CPU (actually, two of them) so
> the machine is
> > > quite fast. By the time it gets to SYLOGICALS.COM, a 4000/60 has
> > > already completed booting.
> > >
> > > Is there a way to get the startup sequence before
> SYLOGICALS.COM logged
> > > somewhere, preferably with SET PREFIX turned on, so I can
> see where and
> > > perhaps why it is hanging? During the hanging, no
> messages are written
> > > to the console, so I have no idea what it is doing.
> > >
> > > Other ALPHAs don't show this behaviour.
> > >
To see what sysgen parameters you can use for startup_p1 and startup2,
enter the following:
sysgen> help sys startup
Startup_p2 options include detailed logging such as "set verify" for
most of the startup files.
I prefer to set startup_p2 "D" which logs the console type messages to
sys$system:startup.log.
To keep all the startup logs and not risk having them purged at some
point, you could then submit a batch job to start few minutes after the
startup is finished to rename startup.log to startup_date-time.log. That
same batch job could then move the log file off the system disk if need
be and it could search the log file for errors or warnings after the
system is booted and send email if it finds something.
If the system is a multi-root system disk, then the file is available
via other systems for review even if a system is hanging on boot.
P.s. do not forget to "sysgen write current" to make the startup_p2
change permanent if that is the intent.
Regards
Kerry Main
Senior Consultant
HP Services Canada
Voice: 613-592-4660
Fax: 613-591-4477
kerryDOTmainAThpDOTcom
(remove the DOT's and AT)
OpenVMS - the secure, multi-site OS that just works.
.
- Follow-Ups:
- RE: STARTUP.LOG?
- From: Larry Kilgallen
- RE: STARTUP.LOG?
- Prev by Date: Re: SSH
- Next by Date: RE: STARTUP.LOG?
- Previous by thread: Re: STARTUP.LOG?
- Next by thread: RE: STARTUP.LOG?
- Index(es):
Relevant Pages
|