Conference turris::digital_unix

9531.0. "dupatch: /usr/lbin/patch_blt: 2245 Memory fault - core dumped" by NNTPD::"[email protected]" () Thu Apr 17 1997 02:54

G'Day,

Has anyone seen the following error, while running dupatch on DU V3.2c.

/usr/lbin/patch_blt: 2245 Memory fault - core dumped
/usr/lbin/patch_blt: 2247 Memory fault - core dumped
/usr/lbin/patch_blt: 2249 Memory fault - core dumped
/usr/lbin/patch_blt: 2251 Memory fault - core dumped

Interrupt received!  Stopping program...
Please wait...done.
dupatch: Exiting

The core file seems to be generated by "usync"

> dbx /usr/lbin/usync core
dbx version 3.11.10
Type 'help' for help.
Core file created by program "usync"

warning: /usr/lbin/usync has no symbol table -- very little is supported
without it


signal Segmentation fault at >*[printf, 0x3ff800daf40]  ldah    r3, 16(r31)
(dbx) where
>  0 printf(0x140000880, 0x120003000, 0x3ffc0004a80, 0x3, 0x104f8)
[0x3ff800daf40]


Please help, a full log of the session is below.

Thanks in advance

Lance.

_______________________________________________________________________

Tue Mar 25 21:36:15 EST 1997

Digital UNIX Patch Utility
==========================
        (This dupatch session is logged in /var/adm/patch/log/session.log)

    Main Menu:
    ---------

    1)  Patch Installation
    2)  Patch Removal
    3)  Patch Documentation
    4)  Patch Tracking
    
    5)  Patch Baseline Analysis/Adjustment
    
    q)  Quit

Enter your choice: 5

Patch Baseline Analysis and Adjustment
======================================

This section of the patch management utility does not actually install
patches. It is an enabler and need only be used to baseline your
system for routine use of setld-based patch kits. It is recommended that
you read the release notes accompanying this kit, prior to continuing.

It is specifically designed to provide continuity from an environment with
manually installed operating system patches to one that can be managed
using the standard 'setld' installation technology.

This baselining is broken into phases that assess and report the state of
your operating system files. It will only make changes to your system with
your confirmation.

    Phase 1 - System Evaluation

        Where possible, this phase determines the origin of changed operating
        system files and detects formally released official patches that were

----------------------------------------
Press <RETURN> to continue viewing: 
----------------------------------------

        manually installed.

    Phase 2 - Report patches with layered product conflicts

        Some layered products ship operating system files. If any such files
        exist on your system, they will show up during this phase.  You can 
        NOT install patches that intersect with a layered product as it would 
        corrupt the layered product operation.

    Phase 3 - Create installation records for manually installed patches

        During this phase, you will be shown a list of patches that match
        the operating system files on your system. You will be offered an
        opportunity to mark these patches as 'installed' on your system.
        This involves copying valid 'setld' database information to your
        system.

    Phase 4 - Report changed system files not included in the patch kit

        This phase provides information to help you make choices later in 
        this process. The files which appear in this phase are changed on 
        your system but their origin cannot be determined.  They are also 

----------------------------------------
Press <RETURN> to continue viewing: 
----------------------------------------

        not part of the patch kit under evaluation.  You will want to 
        consider this information when you later make decisions in phase 5.

    Phase 5 - Enable patches with file conflicts or missing system files

        This phase allows you to enable subsequent installation of patches 
        whose inventory does not match the installed system.  This occurs 
        when, 1) system files change and the origin of that change cannot 
        be deteremined, 2) the original file to be patched is missing from 
        the system.

        It is recommended that you do not enable the installation of these 
        patches, if any, until you have tracked down the origin of the 
        files that are in conflict, or you may compromise the integrity of 
        your operating system.   

        To assist you in this effort, the file list for the entire patch 
        with the known information will be displayed. You may run through 
        this phase to get the analysis without enabling the installation 
        of any of the listed patches.
    
        It is recommended that you backup your operating system prior to 

----------------------------------------
Press <RETURN> to continue viewing: 
----------------------------------------

        the actual patch installation.

Do you want to proceed with the analysis and adjustment? [y/n]: y

    - This Patch Baseline Analysis/Adjustment session is logged in:
                /var/adm/patch/log/baseline.log

    - Previous baseline.log saved to baseline.bak

Enter path to the patch kit (the directory containing ./kit and ./doc),
or enter "q" to get back to the menu: .

Phase 1 - System Evaluation
===========================

    This evaluation compares the contents of your patch kit to the
    state of files already installed on your system regardless of their
    origin.

    The amount of time needed to complete this phase can vary greatly
    depending on the size of the patch kit, the version of the Operating
    System, and the performance of the system.
/usr/lbin/patch_blt: 2245 Memory fault - core dumped
/usr/lbin/patch_blt: 2247 Memory fault - core dumped
/usr/lbin/patch_blt: 2249 Memory fault - core dumped
/usr/lbin/patch_blt: 2251 Memory fault - core dumped

Interrupt received!  Stopping program...
Please wait...done.
dupatch: Exiting


[Posted by WWW Notes gateway]

                                          <<< Note 9531.0 by NNTPD::"[email protected]" >>>
                                 -< dupatch: /usr/lbin/patch_blt: 2245 Memory fault - core dumped >-
    
    Could you please get hold of the following information:
    a) a ls -l of /usr/.smdb. (A tar file with the contents of /usr/.smdb.
    would be even better)
    b) Which patch kit ?
    c) The core dump file.
    
    	Yaacov

    Oh, and please submit a QAR against DUPATCH so that we can track it.
    
    	Yaacov

The patch kit is DUV32CAS00001-1996121

The core file along with a tar archive of /usr/.smdb/ can be
found in the default ftp area on redbck.stl.dec.com (16.153.32.4)

ie

dupatch_core
smdb.tar.Z

Thanks
Lance.
[Posted by WWW Notes gateway]

Found it, there was a corrupt ctrl file in the /usr/.smdb. directory.

Once a good copy was restored everything worked fine.

See ya

Lance.

[Posted by WWW Notes gateway]