Conference azur::mcc

4087.0. "DECmcc Director V1.2 installation failure" by JRDV04::IWASAWA (Osamu Iwasawa/ISE @JRD 81-45-336-5515) Mon Nov 16 1992 02:03

Hello,

I have a installation failure problem.
I've installed DECmcc Director V1.2 SSB kit.
I had the process dump when the mcc director startup procedure was
automatically started ,then IVP was failed.
After this failure, many other image was stopped with the process dump,
for example, less.exe which is unix's pager, "set host/lat" command,
any other layered products. Thus, the system was running, but not available.

First, I've installed on VS3100 which is not the recommended configuration.
Second, I tested on VAX 4000-300 ,which satisfied the configuration, 
but the results was the same.

Has anyone met such failure ?


Osamu.I 	J-ACMS Engineer @JRD


---------( Failure log )------------------------------------------------
( I also posted the whole installation log. )

The MCC_STARTUP_DIR startup procedure for DECmcc V1.2.0 is now running.

%SYSTEM-F-ACCVIO, access violation, reason mask=05, virtual address=04835717,
PC
=80255075, PSL=03C00000

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                8025502E
        Name   = 0000000C                80254F42
                 00000005                00000000
                 04835717                203C0000
                 80255075                7FEC8BFC
                 03C00000                7FEC8BE8
                                         7FF74F77
                                         0000000F
                                         7FF74C89
                                         00000000


        Register dump

        R0 = 04835717  R1 = 0004EE00  R2 = 00000105  R3 = 00006800
        R4 = 0000AD7C  R5 = 00009E00  R6 = 00000000  R7 = 7FEECE00
        R8 = 7FFECA4C  R9 = 7FFECC54  R10= 7FFED7D4  R11= 7FFE2BDC
        AP = 7FEC8B7C  FP = 7FEC8B3C  SP = 7FEC8BB8  PC = 80255075
        PSL= 03C00000

%DCL-W-SKPDAT, image data (records not beginning with "$") ignored


The MCC_STARTUP_DIR startup procedure for DECmcc V1.2.0 is now ending.


   Completing DECmcc DIRECTOR Postinstallation Procedure ...


   Beginning DECmcc DIR Installation Verification Procedure ..



   The IVP for DECmcc DIRECTOR will now be run.

%SYSTEM-F-ACCVIO, access violation, reason mask=05, virtual address=04835717,
PC
=80255075, PSL=03C00000

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                8025502E
        Name   = 0000000C                80254F42
                 00000005                00000000
                 04835717                203C0000
                 80255075                7FEB5DFC
                 03C00000                7FEB5DE8
                                         7FF74F77
                                         0000000F
                                         7FF74C89
                                         00000000

        Register dump

        R0 = 04835717  R1 = 0004EE00  R2 = 00000105  R3 = 00006800
        R4 = 0000AD7C  R5 = 00009E00  R6 = 00000000  R7 = 7FEECE00
        R8 = 7FFECA4C  R9 = 7FFECC54  R10= 7FFED7D4  R11= 7FFE2BDC
        AP = 7FEB5D7C  FP = 7FEB5D3C  SP = 7FEB5DB8  PC = 80255075
        PSL= 03C00000


   The following command failed:

      "MANAGE/ENTERPRISE TEST MCC 0, TO FILE = MCCDIR$OUT.TXT"

   DECmcc DIRECTOR V1.2.0  Installation Failed


%MCC-F-FAILED, fatal DECmcc error

   *********************************************************

   Fatal DECmcc DIRECTOR V1.2.0 event occurred during installation

   *********************************************************

%VMSINSTAL-E-IVPFAIL, The IVP for MCCDIR V1.2 has failed.


        VMSINSTAL procedure done at 18:24

 


----( The following log is the whole installation log. )--------------------


SAM::SYS> @sys$update:vmsinstal mccdir012 JRDV04::USER$32:[KITS.MCC.V12_SSB]


        VAX/VMS Software Product Installation Procedure V5.5-2


It is 4-NOV-1992 at 18:03.

Enter a question mark (?) at any time for help.

%VMSINSTAL-W-ACTIVE, The following processes are still active:
        DCE$RPCD
        DCE$LDSD
* Do you want to continue anyway [NO]? y
* Are you satisfied with the backup of your system disk [YES]?


The following products will be processed:

  MCCDIR V1.2


        Beginning installation of MCCDIR V1.2 at 18:03

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.

   ************************************************************
   *                                                          *
   *                  DECmcc DIRECTOR V1.2.0                  *
   *                    Integrated Package                    *
   *                                                          *
   *                  Installation Procedure                  *
   *                                                          *
   ************************************************************



                            WARNING

   The kit to be installed contains V1.2 of the TCP/IP SNMP
   Access Module.  After you have installed this kit, you
   should not reinstall V1.1 of the TCP/IP SNMP Access Module.
   V1.1 is incompatible with this kit.

* Please press return to continue:


   DECmcc requires a directory where the DECmcc common files
   will be installed.  If the logical MCC_COMMON has been
   redefined, the new definition will be used as the default.
   If  the logical is not defined, the default is for the files
   to be installed in a  directory on the system disk called
   SYS$COMMON:[MCC].  The installer may override the default.
   The target directory for the files as it is now defined is
   shown below.

   Press RETURN to use the value shown or enter a new disk and
   directory specification.

* Target directory for DECmcc Common files [SYS$COMMON:[MCC]]:
%VMSINSTAL-I-SYSDIR, This product creates system directory [MCC].
%VMSINSTAL-I-SYSDIR, This product creates system specific directory [MCC].

   If you intend to execute this layered product on other
   nodes in your VAXcluster, and you have the appropriate
   software license, you must prepare the system-specific
   roots on the other nodes by issuing the following command
   on each node (using a suitably privileged account):

   $ CREATE/DIRECTORY SYS$SPECIFIC:[MCC]/OWNER_UIC=PARENT -
     /PROT=(S:RWE,O:RWE,G:RE,W:R)

%VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.MCC].
%VMSINSTAL-I-SYSDIR, This product creates system directory
[SYSHLP.EXAMPLES.MCC]
.


* Do you want to run the DECmcc DIRECTOR IVP after the installation [YES]?

* Do you want to purge files replaced by this installation [YES]?


   The Time Differential Factor (TDF) is the difference between
   your time zone and the international standard Coordinated
   Universal Time (UTC)

   A negative (-) TDF value means that this node is west of UTC
   A positive (+) TDF value means that this node is east of UTC

   The range is from -12:00 to +13:00. The format is +hh:mm or
   -hh:mm with hh indicating the number of hours and mm
   indicating the number of minutes. A few examples are:

   Eastern Standard Time is -5:00 hours from UTC.
   Eastern Daylight Time is -4:00 hours from UTC.
   Great Britain, Iceland, Portugal, Upper Volta are
      at UTC or 0:0.
   Great Britain, Summer Time +1:00 hour from UTC.
   Japan is +9:00 hours from UTC.

* Time Differential Factor  [-5:00]: +9:00



   DECmcc requires the use of a namespace service for the
   storage and retrieval of network entity information. You
   can select a local namespace or a distributed namespace
   (DNS). Select the local namespace, unless you have multiple
   DECmcc systems that need to share namespace information, or
   you are running DECnet/OSI and are using its distributed
   namespace.  If either of these conditions apply, select the
   DNS; otherwise, select the local namespace.  You may choose
   only one namespace.

   If you select the DNS, please see the DNS chapter in the
   DECmcc Planning and Installation for VMS manual on how to
   configure your namespace.

   If you intend to use the DECmcc Autoconfiguration
   applications with the local namespace, please see the
   Autoconfiguration and Autotopology Use manual on how to
   plan your entity name structure.

* Use DECmcc Local MIR as the DECmcc Name Service [YES]?

   Using DECmcc Local MIR as the DECmcc Name Service

* Is this correct  [YES]?


   You must specify the IDP (or network address initial domain
   part) for your  network.  This must either be the default
   value of "49::", or a value explicitly  allocated for your
   network by one of the recognized allocation authorities.

   The format is:
                        afi:idi:

   where:

   afi = The "authority and format identifier".  This is two
         decimal digits indicating the IDP allocation authority

   idi = The "initial domain identifier".  This is a string of
         decimal digits that has been allocated specifically
         for your network.

   An IDP of "49::" may be used if your network will not be
   interconnected with other OSI networks (there is no "idi"
   associated with this "afi").

* Initial Domain Part  [49::]:


        Product:      DECMCC-DIRECTOR
        Producer:     DEC
        Version:      1.2
        Release Date: 9-JUN-1992


* Does this product have an authorization key registered and loaded? yes

   VMSINSTAL asks no additional questions.



%VMSINSTAL-I-RESTORE, Restoring product save set B ...

   Applying Patch to VMS V5.5 VAXCRTL Run Time Library

%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-WRTFIL, updating image file
DKB200:[SYS0.SYSUPD.MCCDIR012]VAXCRTL.EXE;1

   Following the copying of the files, the DECmcc DIRECTOR
   start-up command procedure(s) will be invoked.  Operational
   tables will be created by this procedure.

   To automatically set up DECmcc DIRECTOR on your system,
   edit your local system start-up command procedure

             SYS$MANAGER:SYSTARTUP_V5.COM

   so that it invokes the DECmcc DIRECTOR start-up command
   procedure.  Add:

             @SYS$STARTUP:MCC_STARTUP_DIR.COM

   after the statement that invokes the DECnet start-up
   command file (STARTNET.COM).

   Following the DECmcc DIRECTOR start-up the DECmcc DIRECTOR
   IVP command procedure will be invoked.

%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

   Beginning DECmcc DIRECTOR Postinstallation Procedure ...

   Deleting obsolete DECmcc verbs...


The MCC_STARTUP_DIR startup procedure for DECmcc V1.2.0 is now running.

%SYSTEM-F-ACCVIO, access violation, reason mask=05, virtual address=04835717,
PC
=80255075, PSL=03C00000

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                8025502E
        Name   = 0000000C                80254F42
                 00000005                00000000
                 04835717                203C0000
                 80255075                7FEC8BFC
                 03C00000                7FEC8BE8
                                         7FF74F77
                                         0000000F
                                         7FF74C89
                                         00000000


        Register dump

        R0 = 04835717  R1 = 0004EE00  R2 = 00000105  R3 = 00006800
        R4 = 0000AD7C  R5 = 00009E00  R6 = 00000000  R7 = 7FEECE00
        R8 = 7FFECA4C  R9 = 7FFECC54  R10= 7FFED7D4  R11= 7FFE2BDC
        AP = 7FEC8B7C  FP = 7FEC8B3C  SP = 7FEC8BB8  PC = 80255075
        PSL= 03C00000

%DCL-W-SKPDAT, image data (records not beginning with "$") ignored


The MCC_STARTUP_DIR startup procedure for DECmcc V1.2.0 is now ending.


   Completing DECmcc DIRECTOR Postinstallation Procedure ...


   Beginning DECmcc DIR Installation Verification Procedure ..



   The IVP for DECmcc DIRECTOR will now be run.

%SYSTEM-F-ACCVIO, access violation, reason mask=05, virtual address=04835717,
PC
=80255075, PSL=03C00000

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                8025502E
        Name   = 0000000C                80254F42
                 00000005                00000000
                 04835717                203C0000
                 80255075                7FEB5DFC
                 03C00000                7FEB5DE8
                                         7FF74F77
                                         0000000F
                                         7FF74C89
                                         00000000

        Register dump

        R0 = 04835717  R1 = 0004EE00  R2 = 00000105  R3 = 00006800
        R4 = 0000AD7C  R5 = 00009E00  R6 = 00000000  R7 = 7FEECE00
        R8 = 7FFECA4C  R9 = 7FFECC54  R10= 7FFED7D4  R11= 7FFE2BDC
        AP = 7FEB5D7C  FP = 7FEB5D3C  SP = 7FEB5DB8  PC = 80255075
        PSL= 03C00000


   The following command failed:

      "MANAGE/ENTERPRISE TEST MCC 0, TO FILE = MCCDIR$OUT.TXT"

   DECmcc DIRECTOR V1.2.0  Installation Failed


%MCC-F-FAILED, fatal DECmcc error

   *********************************************************

   Fatal DECmcc DIRECTOR V1.2.0 event occurred during installation

   *********************************************************

%VMSINSTAL-E-IVPFAIL, The IVP for MCCDIR V1.2 has failed.


        VMSINSTAL procedure done at 18:24

 

Get a new copy of sys$common:[syslib]vaxcrtl.exe from some system that is
running the same VMS version or pull it off of the VMS kit of the same
version.

We currently patch the vaxcrtl depending on the system version.  This breaks
if some other product copied in some other version.  The V1.2.3 DECmcc kit
should do the correct patch.

Hi, 

Thank you for your information.
I've installed successfully, but still IVP was failed.
I installed DECmcc Director and replaced VAXCRTL.EXE , and then rebooted.
After reboot, I started DECmcc Director and ran IVP as follows.

Is there any idea ?


/Osamu.I


=============( Startup and IVP log )=====================================
SAM::SYS> @sys$startup:mcc_startup_dir.com


The MCC_STARTUP_DIR startup procedure for DECmcc V1.2.0 is now running.



The MCC_STARTUP_DIR startup procedure for DECmcc V1.2.0 is now ending.

SAM::SYS> @sys$test:mcc_dir_ivp


   The IVP for DECmcc DIRECTOR will now be run.

DECmcc (V1.2.0)


MCC 0
AT 18-NOV-1992 11:59:46

Test Successful
DECmcc (V1.2.0)

%MCC-E-NOTFOUND,  unsupported combination of verb, entity, partition
%MCC-E-NOTFOUND,  unsupported combination of verb, entity, partition

   The following command failed:

      "MANAGE/ENTERPRISE TEST MCC 0, TO FILE = MCCDIR$OUT.TXT"

   DECmcc DIRECTOR V1.2.0  Installation Failed


%MCC-F-FAILED, fatal DECmcc error
SAM::SYS>

It seems unlikely to me that your 

%MCC-E-NOTFOUND,  unsupported combination of verb, entity, partition

errors have anything to do with the VAXCRTL patches.  However, the
correct order would be:

1) Copy the correct version of VAXCRTL
2) Reboot (if needed?)
3) Install DECmcc (so it can patch the VAXCRTL)
4) Run the IVP

The order listed in .-1 would result in an un-patched VAXCRTL

=== Re .2 (to my reply) =====

This is my mistake.
After I read the Installation guide again, I executed as follows.

	$ @sys$startup:mcc_startup_dir.com enroll
					   ^^^^^^
	$ @sys$test:mcc_dir_ivp

Then IVP was successfully finished.

=== Re .3 ========

>It seems unlikely to me that your 
>
>%MCC-E-NOTFOUND,  unsupported combination of verb, entity, partition
>
>errors have anything to do with the VAXCRTL patches. 

Yes, this error had nothing with the VAXCRTL patches.

I understand your advice. This VAXCRTL is not a patched image.
But if I do the order you said, I'll have the same failure.

Because, at first, I've done the following order.

1) Install DECmcc (so it can patch the VAXCRTL)
2) Run the IVP

From .1, VAXCRTL is not patched correctly.
And Second,

1) Copy sys$library:vaxcrtl.exe to sys$login:(system account)
2) Install DECmcc (so it can patch the VAXCRTL)
3) Copy sys$login:vaxcrtl.exe to sys$library: 
   (so it is not patched VAXCRTL, return the image before the installation)
4) Run the IVP

Yes, This VAXCRTL is not a patched image. This case is successful. 

I think your order is the same as my first order.

>1) Copy the correct version of VAXCRTL
>2) Reboot (if needed?)
>3) Install DECmcc (so it can patch the VAXCRTL)
>4) Run the IVP

So if I do your order , the result will be failure.

I'm not familiar with DECmcc, but the system looks like correct actions.

Any idea ?

This is solved with V1.2.3 kit, isn't it ?

Thanks.

/Osamu.I

This makes sense; invalid VEP is usually do to an enrollment or
dictionary problem, so executing the startup enroll should fix it for you.

I misunderstood the goal of copying the VAXCRTL.
I thought Larry (in .1) suggested that you copy a VAXCRTL that
was compatible with the installation patch.

The V1.2.3 installation is much smarter about patches.

-- Erik

Thanks, Erik.

My system is JVMS Godzilla EFT1 which is JVMS for NTT ( that is MIA project ) 
and includes "C" Runtime Library for XPG4.
JVMS Engineer said that VAXCRTL.EXE only pointed DECC$SHR.EXE.
If DECmcc has to patch "C" Runtime Library, DECmcc should patch DECC$SHR.EXE.

>The V1.2.3 installation is much smarter about patches.

Does this patch correspond to "C" Runtime Library for XPG4 ?

Thanks,

Osamu.I

We only supply patches to VMS images that we run with.  It is
up to the VMS group to supply the patches for other VMS images.
Therefor we do NOT patch the VAXRTLG.EXE.

Also, we currently do not run with the DECC$SHR.  We will sooner
or later run with the CMA special kit or run on VMS 6.0  In either
case these bugs fixes should be in this version.

>Also, we currently do not run with the DECC$SHR.  We will sooner
>or later run with the CMA special kit or run on VMS 6.0  In either
>case these bugs fixes should be in this version.

It seems there are bugs in DECthreads.
What function or operation of DECmcc do these bugs infuluence ?

It seems to me that DECmcc runs on my machine without this patch, 
after I replaced with the unpatched VAXCRTL.EXE like .2 .

Can't we use DECmcc without the patch?


Osamu.I

The "C" library patch is not related to DECthreads.
Rather, I believe it has to do with a memory leak in the socket
code.  If you use an unpatched library with the bug, then some
SNMP operations will leak memory, reducing the length of time that
DECmcc will continue running.

Older versions of DECthreads (a different problem) had more dramatic
bugs that might cause DECmcc to crash.

The DECthreads and C runtime library groups are working together
to produce a new version in the near future.  Once DECmcc uses the
new version, we expect these installation problems will go away.
I believe that is what Larry was indicating in .-2

-- Erik