Conference share::zap

132.0. "ZAP V5.1 monitor process crash .." by UTRTSC::PEETERS (AlFa VMS runs very fast ..) Tue Jun 01 1993 05:19

	Hi ZAP friends,

With V5.1 I saw a problem that the ZAPmonitor process crashed. Perhaps somebody
saw something like this, and can give me some advice ? 

	Regards, Erwin.

----------------------------/////----------------------------------------------

The logfile shows the following crashinfo :

%ZAP-I-STATUS, Status at 23-MAY-1993 18:54:32.30 Pass = 8640 Stop = 51 Exit = 0
User = 0 Error = 2
%ZAP-I-STATUS, Status at 24-MAY-1993 06:54:31.81 Pass = 9360 Stop = 51 Exit = 0
User = 0 Error = 2
%ZAP-E-NOPRCINFO, No process information available for process index FFFF00A1
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000005, PC
=001327FB, PSL=0BC00004
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC
ZAP$COMMON      STRINGS_EQUAL                    2489      00000043  001327FB
ZAP$MONITOR     DETERMINE_RULE                    982      0000025C  001278F8
ZAP$MONITOR     DETERMINE_ACTION                 1626      000002D4  00129108
ZAP$MONITOR     ZAP$MONITOR                      1975      000006A7  001285F3
                                                           00132F84  00132F84
  SYSTEM       job terminated at 24-MAY-1993 13:03:34.09


The ZAP settings are:

%ZAP-I-VERSION, DEC ZAP for VMS Version V5.1
%ZAP-I-STARTINGON, Starting at 17-MAY-1993 18:55:23.28 on BVX02
%ZAP-I-CONFIG, VAX 6000-520                    running VMS V5.5-2
%ZAP-S-PRCCON, Processing configuration file ZAP$Config_File
%ZAP-S-PRCEXC, Processing exception file ZAP$Exception_File
%ZAP-S-PRCMSG, Processing message file ZAP$Warning_File
%ZAP-I-MSGLEN, Message is 191 characters long
%ZAP-S-PRCMSG, Processing message file ZAP$Logout_File
%ZAP-I-MSGLEN, Message is 97 characters long
%ZAP-I-SENSITIVITY, Idle process sensitivity set to 13
%ZAP-I-MIN_WARNING, Minimum warning time is 5 minutes
%ZAP-I-TRACEBCK, Process owner traceback is enabled
%ZAP-I-LENIENT, Tracebacked processes will use most lenient rule
%ZAP-I-NODEBUG, Monitor debugging is disabled
%ZAP-I-WARNTIMES, Warning messages will be sent 9 7 5 3 1 minutes before action
is taken
%ZAP-I-NOINSWAP, Swapped out processes will be ignored
%ZAP-I-IGNSUSP, Suspended processes will be ignored
%ZAP-I-GROUPDW, Related DECwindows processes will be grouped together
%ZAP-I-HISTORY, History information will be generated
%ZAP-I-STATUS, Status at 18-MAY-1993 06:54:27.79 Pass = 720 Stop = 0 Exit = 0 Us
er = 0 Error = 0

Hi,

	I have never seen a crash like that before.  Has this happened more than
once?

						Keith Maconi

	Hi Keith,

It just happened once. I thought that it maybe had something to do with the
non-existing process problem what was solved in V5.1. It looks like the monitor
has a problem when it tries to handle an action to a process that doesn't exist 
anymore at that time.

Hope you have some hints to troubleshoot this.

Regards,

	Erwin.

Could you please send me a copy of the history file showing the time before
the failure.  This may include some information as to what happened.