home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!paladin.american.edu!howland.reston.ans.net!usc!news.service.uci.edu!network.ucsd.edu!mvb.saic.com!mx-list
- From: pat@che.phys.Virginia.EDU
- Newsgroups: vmsnet.mail.mx
- Subject: "opcode reserved to DIGITAL fault" still killing SMTP
- Message-ID: <009664cc.6323e080.4879@gomez.phys.virginia.edu>
- Date: Fri, 08 Jan 1993 10:59:09 EST
- Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
- X-Gateway-Source-Info: Mailing List
- Lines: 27
-
- A few days ago I wrote (in part):
-
- >Now I have a new question: my SMTP process is dying on me as soon as I try
- >to SEND. The appropriate *.HDR_INFO, *.MSG_TEXT, *.SRC_INFO and *.SMTP_INFO
- >files are being created in the (now correctly-defined) FLQ_DIR directory,
- >but they all end up stranded there because SMTP has died. The VMS accounting
- >utility tells me that SMTP is dying with status code 1000043C,
-
- >%SYSTEM-F-OPCDEC, opcode reserved to DIGITAL fault at PC=!XL
-
- >Does this ring a bell with anyone? A bug in MX 3.1 (i.e., "Try 3.1C, dummy!),
- >or am I still doing something wrong?
-
- >(A review of my MX environment: 7-node Vaxcluster, all nodes running VMS 5.5
- > and CMU-TEK 6.6-5. MX 2.0 currently running successfully on all nodes with
- > the exception of occasional failures to deliver, particularly to CERN in
- > Europe (addresses ending in .CH). ROUTER, LOCAL and MLF run on 3 of the
- > 7 nodes; SMTP runs on these 3 plus 1 other node, and all 7 nodes run
- > SMTP Server.)
-
- Well, I've just tried reinstalling MX 3.1 from scratch, creating a new
- CONFIG.MCP, etc., and I'm getting the same "opcode reserved to DIGITAL fault"
- error. Any ideas? Any more information I can supply? Thanks.
-
- - Patrick Walsh
- University of Virginia Department of Physics
- pw@virginia.bitnet, pw@virginia.edu, pat@gomez.phys.virginia.edu
-