IBM Support

PM44878: albd_server registry files stop writing to the permanent registr y files when a child process terminates and journaling stops

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • albd_server registry files stop writing to the permanent
    registry files when a child process terminates and interrupts
    the journaling process
    
    
    RedHat Enterprise 5
    
    ClearCase 7.1.2.x
    
    
    When reviewing the registry files within the
    /var/adm/rational/clearcase/rgy/ directory on a ClearCase
    Registry Server, the following is seen:
    
    -rw-rw-r--  1 root    root      2078494 Jul 29 08:02
    view_object_journal
    -rw-r--r--  1 root    root      2351104 Jul 22 14:05
    view_object.new
    -rw-r--r--  1 root    root     40172374 Jul 22 14:03 view_tag
    
    -rw-rw-r--  1 root    root      5677681 Jul 29 08:02
    view_tag_journal
    -rw-r--r--  1 root    root      1933312 Jul 22 14:05
    view_tag.new
    -rw-r--r--  1 root    root       225363 Jul 29 05:21 vob_object
    
    -rw-r--r--  1 root    root      2729038 Jul 26 11:02 vob_tag
    
    -rw-rw-r--  1 root    root        54803 Jul 29 05:20
    vob_tag_journal
    
    
    As noted above, the view_object does not exist and the
    view_object, view_tag and vob_tag are al journaling their
    entries and not updating the permanent files.
    
       NOTE:  The nature and combination of which registry files are
    affected may differ from site to site that experience the update
    problem.
    
    When reviewing the last update times from above, the following
    logs correspond to the same time:
    
    System Messages file:
    Jul 22 14:05:07 rgyhost  kernel: credmap_server[7216]: segfault
    at 0000000000000030 rip 00000000f7b2366a rsp 00000000ffa5f868
    error 6
    
    albd_log:
    2011-07-22T14:05:26-04:00 albd_server(3372): Ok: Server
    credmap_server(7216) exited due to signal 11
    
       NOTE:  The nature of which forked child process from the
    albd_server that terminates is not specific:  The above is
    simply an example of one case where the journaling stopped
    writing to the permanent registry files.
    
    As seen above, the child process which terminated had ultimately
    interrupted the albd_server registry journaling process which
    never recovers.  Thus, all of the changes are within the memory
    of the albd_server process and are no longer written to disk.
    
    
    Days later, the following error may be seen within the albd_log:
    
    2011-07-26T11:07:39-04:00 albd_server(3372): Error: Unable to
    write to registry file
    '/var/adm/rational/clearcase/rgy/vob_tag.new': Input/output
    error.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    albd_server registry files stop writing to the permanent
    registry files when a child process terminates and
    interrupts the journaling process
    
    
    RedHat Enterprise 5
    
    ClearCase 7.1.2.x
    
    
    When reviewing the registry files within the
    /var/adm/rational/clearcase/rgy/ directory on a ClearCase
    Registry Server, the following is seen:
    
    -rw-rw-r--  1 root    root 2078494 Jul 29 08:02
    view_object_journal
    -rw-r--r--  1 root    root 2351104 Jul 22 14:05
    view_object.new
    -rw-r--r--  1 root    root     40172374 Jul 22 14:03
    view_tag
    -rw-rw-r--  1 root    root 5677681 Jul 29 08:02
    view_tag_journal
    -rw-r--r--  1 root    root 1933312 Jul 22 14:05
    view_tag.new
    -rw-r--r--  1 root    root  225363 Jul 29 05:21
    vob_object
    -rw-r--r--  1 root    root 2729038 Jul 26 11:02 vob_tag
    
    -rw-rw-r--  1 root    root   54803 Jul 29 05:20
    vob_tag_journal
    
    
    As noted above, the view_object does not exist and the
    view_object, view_tag and vob_tag are al journaling their
    entries and not updating the permanent files.
    
       NOTE:  The nature and combination of which registry files
    are affected may differ from site to site that experience
    the update problem.
    
    When reviewing the last update times from above, the
    following logs correspond to the same time:
    
    System Messages file:
    Jul 22 14:05:07 rgyhost  kernel: credmap_server[7216]:
    segfault at 0000000000000030 rip 00000000f7b2366a rsp
    00000000ffa5f868 error 6
    
    albd_log:
    2011-07-22T14:05:26-04:00 albd_server(3372): Ok: Server
    credmap_server(7216) exited due to signal 11
    
       NOTE:  The nature of which forked child process from the
    albd_server that terminates is not specific:  The above is
    simply an example of one case where the journaling stopped
    writing to the permanent registry files.
    
    As seen above, the child process which terminated had
    ultimately interrupted the albd_server registry journaling
    process which never recovers.  Thus, all of the changes are
    within the memory of the albd_server process and are no
    longer written to disk.
    
    
    Days later, the following error may be seen within the
    albd_log:
    
    2011-07-26T11:07:39-04:00 albd_server(3372): Error: Unable
    to write to registry file
    "/var/adm/rational/clearcase/rgy/vob_tag.new": Input/output
    error.
    

Problem conclusion

  • A fix is available in ClearCase versions 7.1.1.8, 7.1.2.5
    and 8.0.0.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM44878

  • Reported component name

    CLEARCASE UNIX

  • Reported component ID

    5724G2901

  • Reported release

    712

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-08-01

  • Closed date

    2011-12-16

  • Last modified date

    2011-12-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    CLEARCASE UNIX

  • Fixed component ID

    5724G2901

Applicable component levels

  • R712 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.2","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
16 December 2011