Conference clarid::dasc

205.0. "Unexplained crash - any ideas?" by SNOC01::63620::GRAHAM (Russell GRAHAM) Tue May 20 1997 08:16

Hi,

A log follows of an attempt to run DASC. The results are obvious - crashed!

The node is a VAX with
OVMS 6.2,
is one of 3 nodes in a CI cluster,
has a HSJ and some HSC controllers,
lots and lots and lots of disks,
512MB memory,
FDDI LAN controller

Can anyone offer an explanation as to why it occurred?

Please ask if there is any other information you require to be able to assist.

Thanks,
Russell Graham
SNSIS, Sydney
@SNO
-------------------------------------------------------------------------------
 Unauthorised Access Prohibited

Username: SYSTEM
Password: 

#4STCV17 - Unauthorized Access Prohibited


    Last interactive login on Sunday, 18-MAY-1997 18:06
    Last non-interactive login on Tuesday, 20-MAY-1997 04:45
	    You have 292 new Mail messages.

WARNING - Your password expires on Wednesday, 21-MAY-1997 09:52

["v
[62"p F
>
.$ SET DEF SYS$SYSDEVICE:[DASC]
.$ DIR

Directory SYS$SYSDEVICE:[DASC]

AEC.COM;57          DASC$CREF.SITE;1    DASC$DEINSTAL.COM;1 DASC$HREF.LIST;1   
DASC$LAN.COM;1      DASC$LAN.EXE;1      DASC$LAN.OBJ;1      DASC$LAT.OBJ;1     
DASC$LICS.LIST;1    DASC$LIFE.EXE;1     DASC$LIFE.OBJ;1     DASC$LIFE_M.OBJ;1  
DASC$MAIN.EXE;1     DASC$MAIN.OBJ;1     DASC$NREF.LIST;1    DASC$REPORT.DUP;1  
DASC$REPORT.INV;1   DASC$REPORT.LIF;1   DASC$REPORT.TXT;1   DASC$REPORT_LAN.DUP;1
DASC$REPORT_LAN.HIS;1                   DASC$REPORT_LAN.INV;1
DASC$REPORT_LAN.TXT;2                   DASC$SOFT.LIST;1    DASC$SOFT.SITE;1   
DASC$VPAT.LIST;1    DASC.COM;1          DASC_CLUS.STCV17;1  DASC_IPA.STCV17;1  
DASC_LIFE.LIS;1     DASC_LIL.STCV17;1   DASC_LIN.STCV17;2   DASC_MEM.STCV17;1  
DASC_RAID.STCV17;1  DASC_SGN.STCV17;1   DASC_VMS.STCV17;1   LAN$CONFIG.DAT;1   
SETHOST.LOG;2       SETHOST.LOG;1       

Total of 39 files.
.$ @DASC
	-- DASC V4.1-1 --		20-MAY-1997 09:53:17.72


		CONFIDENTIAL SOFTWARE
	PROPERTY OF DIGITAL EQUIPMENT CORPORATION
  Use authorized only pursuant to a valid Right-To-Use License
  Copyright (c) 1991, 1992 by Digital Equipment Corporation


	Do you want to enter details to appear in the report headers?
	Enter your choice <NO> : 

	Enter a VAXmail address to receive the report(s)
	<CR> will mail to SYSTEM, NONE implies no mail
	Enter your choice <SYSTEM> : NONE

	Select the type of configuration information to be collected
	H(ardware)  S(oftware)  L(icense)  N(etwork)
	 ** Network data collection may consume significant amounts
	 ** of CPU resources on the node doing the collection. This
	 ** may impact system performance and user response time.
	Enter a single option (N) or a list of options (HSL)
	Enter your choice  <A>ll : HSLN

	Select the type of optional report(s) to be produced
	C(LUE Config)  D(UP)  I(nventory summary)  P(ostscript for LIFE)
	L(IFE)  H(istory for LAN collections)
	 ** If you request Postscript printer information, you
	 ** will see no printer output generated in most cases.
	 ** However any Postscript printer attached to a print
	 ** queue having job flag and/or trailer page enabled
	 ** will output a job flag and/or trailer page.
	Enter a single option (I) or a list of options (ILP)
	Enter your choice  <none> : CDILH

	You may generate a LAN configuration file listing ETHERNET devices.
	Entering 0 at next prompt will disable this function.
	Enter the number of minutes (0 to 59) <30> : 

	-- Collect ETHERNET config. --	20-MAY-1997 09:53:44.96
%DCL-S-SPAWNED, process DASC$LAN spawned

	Enter list of nodes you want to collect on
	(comma separated list of nodes being part of this cluster)
	Enter nodes <whole cluster> : STCV17

	-- Collect system info --
%SYSMAN-I-TIMEVAL, timeout value is     0 00:06:00.00
%SYSMAN-I-ENV, current command environment:
	Individual nodes: STCV17
	Username SYSTEM       will be used on nonlocal nodes
 
%SYSMAN-I-OUTPUT, command execution on node STCV17
%DASC-I-Collect     :  09:54:06.45
%DASC-I-License     :  09:54:15.21
%DASC-W-NOCLUE	CLUE utility not available...
%DASC-I-LIFE_start  :  09:55:16.41
  Improperly handled condition, bad stack or no handler specified.
	Signal arguments	      Stack contents
	Number = 00000005		 00000000
	Name   = 0000000C		 0FFC0000
		 00000001		 7FDE0EF0
		 CA9664BC		 7FFE97E4
		 000111E8		 83BFF011
		 01C00008		 00000004
					 0000F078
					 86FDC8C0
					 0000F0F0
					 7FFED188
	Register dump
	R0 = 00000000  R1 = CA9664A4  R2 = 00000000  R3 = 0000EC98
	R4 = 00000000  R5 = 00000000  R6 = 0000EC88  R7 = 86666800
	R8 = 86709540  R9 = 00000006  R10= 86723380  R11= 86709540
	AP = 00000000  FP = 7FFE97A8  SP = 7FFE97A8  PC = 000111E8
	PSL= 01C00008
	-- Produce final report --
%DASC-I-Report_start:  09:57:53.21
%DASC-I-End         :  09:58:33.49

	-- LAN collection still running --
	** Please do not logout in the next 32 minutes
	-- DASC$REPORT.TXT available --
	-- %DASC-I-Exit --		20-MAY-1997 09:58:39.95
Subprocess DASC$LAN has completed
.$ LO
  SYSTEM       logged out at 20-MAY-1997 10:40:44.82

>Note 205.0               Unexplained crash - any ideas?              No replies
	Your title had me worried for a few seconds, until I realized what
	you meant by "crash" :-)

	It looks like there is something odd while running the DASC$LIFE.EXE
	image. This image will produce 2 output files, DASC__DUP.D and
	DASC_LIFE.LIS. DASC__DUP.D will get renamed to DASC$REPORT.DUP if
	you selected the D(UP) optional report. Can I have a look at this
	file? Can you also have a look at it and see if for example you
	miss one or more DUP capable device in there (like HSJ's, HSC's or
	MTI StingRay's...)?

	You could also produce those output files by simply typing:
		$ run dasc$life
	from a suitably privileged account.
	
	Can you also try to run either normal DASC or DASC$LIFE.EXE from
	other cluster members, would that give the same error message?
		
								.Andre.