Conference azur::mcc

1877.0. "BMS T1.2 MMABORT problem" by MICROW::LANG () Wed Dec 04 1991 16:42

	I am running the internal field test of 1.2 on ultrix.  Sometimes
	when I run I get the following error.  I'm taking the input from
	a file.  Other times this runs successfully, with the same executable
	and can't figure out why.  Sometimes this runs and the mm aborts without
	any more information, and the process hangs.

				thanks,

				Bonnie

ERROR RUN 1:
------------

glaive.tay1.dec.com> /usr/bin/manage < $TSRC/tps_am_set_tpcontroller_i.inp
DECmcc (T1.2.1)

Killing existing MM mcc_tps_am (pid 18334)
Kill succeeded
%MCC-E-RECEIVEERROR, error trying to receive a packet
Exception in Mgt Module (id=16), CMA code = 40802c
%MCC-E-MMABORT, Target Management Module thread has aborted
Terminated


ERROR RUN 2:
------------

DECmcc (T1.2.1)

Killing existing MM mcc_tps_am (pid 19694)
Kill succeeded
 %MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replacd
%Internal error: cma__open_general: unexpected fstat error
dcethreads: Error opening message catalog "dcethreads.cat"
dcethreads: Error closing message catalog "dcethreads.cat"
Error message text not available
%MCC-E-TRANSMITERROR, error trying to transmit a packet


INPUT_FILE:
----------
	The input file $TSRC/tps_am_set_tpcontroller_i.inp
	has the following

enroll mcc_tps_am
! The following are invalid tests
set tpcontroller x username=Johnson, via path
set tpcontroller x username=Johnson, via port
set tpcontroller x username=Johnson, by pass
set tpcontroller x username=Johnson, by user
set tpcontroller x dummy_attribute=Johnson
set tpcontroller x username=Johnson

    

The ident reported by MCC in your example indicates that you
are running an older version of the DECmcc field test.
You may want to upgrade before persuing some of these problems.

>%MCC-E-RECEIVEERROR, error trying to receive a packet

on ULTRIX, each MM runs in its own process, and mcc calls use
an RPC to communicate.  This error means the target of an mcc call
crashed, and so never responded to the RPC request.

>Exception in Mgt Module (id=16), CMA code = 40802c
>%MCC-E-MMABORT, Target Management Module thread has aborted
>Terminated

The first aid in tracing this is to find out which module is running
with id=16.  If you can re-start your test, and (before it crashes)
issue the command "ps -aux | grep mcc | grep 16" and post the results,
that will indicate which module crashed.

Thread problems are often timing related, which explains why
you don't see consistant results.


>%Internal error: cma__open_general: unexpected fstat error

This is a known problem (see the release notes)  It is harmless.

>dcethreads: Error opening message catalog "dcethreads.cat"
>dcethreads: Error closing message catalog "dcethreads.cat"
>Error message text not available

This indicates that the environmental variable "NLSPATH" is not
pointing to a location with the CMA message file.
The variable is set in /usr/mcc/mcc_system/mcc_login.{sh,csh}
Could you check the value with "printenv NLSPATH"?  Then look in
/usr/mcc/mcc_system for the file dcethreads.cat

    

    
    We installed the MCC EFT kit and the hanging problems disappeared.
    Thanks for the help.
    
    		Bonnie