Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!brutus.cs.uiuc.edu!psuvax1!psuvm!HMCVAX!NED From: NED@HMCVAX.CLAREMONT.EDU (Ned Freed, Postmaster) Newsgroups: bit.listserv.pmdf-l Subject: RE: Unexpected death of BN_SLAVE Message-ID: Date: 4 Feb 90 00:54:00 GMT Sender: PMDF Distribution List Reply-To: PMDF Distribution List Lines: 40 Approved: NETNEWS@PSUVM Gateway Errors-to: postmast@YMIR.BITNET X-PS-Qualifiers: /DOOF X-Envelope-to: PMDF-L@IRLEARN.BITNET X-VMS-To: IN%"OWEN@AUDUCVAX.BITNET" X-VMS-Cc: IPMDF X-To: OWEN@AUDUCVAX, INFO-PMDF@YMIR Larry Owen writes: > Below is the relevant portion of LMD.LOG. BN_SLAVE dies badly here, > causing the old (Joiner-supplied) local mail delivery daemon to run > (and junking up everyone's mailboxes with a bunch of un-replyable > addresses). However, when jnet was restarted, BN_SLAVE ran just fine! > Does anyone know what could cause this? > ... >%PAS-F-VARINDVAL, varying index value is greater than current length >%TRACE-F-TRACEBACK, symbolic stack dump follows >module name routine name line rel PC abs PC >BN_SLAVE STRIP 1101 0000005C 00004EEC >BN_SLAVE MUNGED 1148 0000019F 00003E8B >BN_SLAVE BN_SLAVE 1323 000005B4 000047BC The fact that BN_SLAVE is dying in STRIP means that you're running a PMDF prior to 3.0-20. STRIP was eliminated entirely in that patch. It also probably means that you're running a PMDF prior to 3.0-6, since 3.0-6 fixed a problem like this specifically in STRIP. A number of problems in BN_MUNGE have been found at one time or another. They are, as a rule, triggered by some funniness in one or more header lines. Problem is, BN_SLAVE dies and JNET picks up and processes the message causing the problem, leaving no clue as to what specifically caused the trouble... You have three options: (1) Install 3.0-6 and hope it fixes it. (2) Install 3.0-20 (which totally supercedes 3.0-6) and eliminate this problem for sure. (3) Upgrade to 3.1, also eliminating the problem for sure. Hope this helps. Ned