[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

521.0. "AUDIT SERVER SNDOPRERR" by TAV02::GODOVNIK (Haim Godovnik) Thu Apr 24 1997 07:37

Hi,

A cluster of 2 VAX'es OpenVMS 6.1 and 2 ALPHA's OpenVMS 6.2. They are getting
the following error messages from AUDIT SERVER :


%%%%%%%%%%%  OPCOM   20-APR-1994 16:38:08.24  %%%%%%%%%%%
Message from user AUDIT$SERVER on APPOLO
%AUDSRV-W-SNDOPRERR, error (%X000008D8) returned from $SNDOPR; alarm may not
be received on remote nodes


And in a moment later:

%%%%%%%%%%%  OPCOM   20-APR-1994 16:38:08.25  %%%%%%%%%%%
Message from user AUDIT$SERVER on APPOLO
%AUDSRV-F-INCONSTATE, internal consistancy error; please submit an SPR with
SYS$SYSROOT:[SYSEXE]AUDIT_SERVER.DMP
-AUDSRV-I-SIGNAL_PC, error occured at pc: 000074CE

No dump can be found, and the AUDIT SERVER did not crash. They have also
checked while it was happening - The OPCOM was running on all nodes.



I have seen the following article in STARS:
===============================================================================
TITLE: {Elev} AUDSRVWSNDOPRERR Error returned from OPCOM
  NOEDITORIAL_REVIEWED,FIELD_READABLE,NOFLASH,TECHNICAL_REVIEWED,NOREADY)
PRODUCT or COMPONENT:  Security

OP/SYS:  OPENVMSVAX

VERSION INFORMATION:

Operating System Version(s): OpenVMS Vax 6.1
Layered Product/Component Version(s): Cluster

SOURCE:   Digital Equipment Corporation

SYMPTOM:

%%%%%%%%%%%  OPCOM   1-AUG-1994 19:04:50.49  %%%%%%%%%%%
Message from user AUDIT$SERVER on W0DISA
%AUDSRV-W-SNDOPRERR, error (%X000008D8) returned from $SNDOPR; alarm may not
be received on remote nodes

DIGITAL RESPONSE:

This problem has been reviewed by Engineering and has been determined
to be a design failure.  It has been escalated into the Engineering
Product cycle for consideration into a future release of the product.
The appendix of the release notes will identify if the solution has
been incorporated.
===============================================================================


I could not find in the documentation anything about it being fixed.
Please advise.


Haim G.

T.R Title User Personal
Name Date Lines

521.1 Check Available OPCOM-related Patches... XDELTA::HOFFMAN Steve, OpenVMS Engineering Thu Apr 24 1997 09:46 18

T.R	Title	User	Personal Name	Date	Lines
521.1	Check Available OPCOM-related Patches...	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Thu Apr 24 1997 09:46`	18
	Consider applying VAXSHAD09_061 on the OpenVMS VAX V6.1 nodes, and ALPOPCO01_070 on the OpenVMS Alpha V6.2 nodes. Also see if you can determine what is filling the operator mailbox: $ exit %x8D8 %SYSTEM-W-MBFULL, mailbox is full $ And look for a failed or missing OPCOM process somewhere in the VMScluster. Are nodes entering and/or leaving the VMScluster? And are there large volumes of audits being generated? Also try a COMET search for OPCOM and MBFULL, and OPCOM and 8D8. And, as the error message indicates, if the customer needs the fix, submit an IPMT...

  Consider applying VAXSHAD09_061 on the OpenVMS VAX V6.1 nodes, and
  ALPOPCO01_070 on the OpenVMS Alpha V6.2 nodes.

  Also see if you can determine what is filling the operator mailbox:

   $ exit %x8D8
   %SYSTEM-W-MBFULL, mailbox is full
   $

  And look for a failed or missing OPCOM process somewhere in the
  VMScluster.  Are nodes entering and/or leaving the VMScluster?
  And are there large volumes of audits being generated?

  Also try a COMET search for OPCOM and MBFULL, and OPCOM and 8D8.

  And, as the error message indicates, if the customer needs the fix,
  submit an IPMT...