000025781 - Enabling trace logging in RSA Certificate Manager causes xudad process to abort

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000025781
Applies ToRSA Certificate Manager 6.6
Sun Solaris 2.9
IssueEnabling trace logging in RSA Certificate Manager causes xudad process to abort
Shortly after starting RSA Certificate Manager (RSA CM) services and accessing the RSA CM administrative interface, xudad process (RSA CM Secure Directory Server) aborts and generates a core dump
CauseIf trace logging is enabled and RSA Certificate Manager is running on a Sun Solaris machine with multiple processors, xudad crashes. This issue does not apply to Certificate Manager installed on Microsoft Windows or single processor Solaris machines.
ResolutionThis issue has been fixed in Build 302 for RSA Certificate Manager 6.6. Contact RSA Security Customer Support to request Build 302, or request the latest fix level (which is cumulative, and includes fixes from all previous fix levels).
WorkaroundApplied RSA Certificate Manager 6.6 Build 301
Enabled trace logging by un-commenting the line "TraceDetail all high" in <RSACM_install-dir>\Xudad\conf\xudad.conf
NotesUse "psrinfo -v" command on Solaris to determine whether the system has multiple processors.  An example output of psrinfo command is listed below:

# psrinfo -v
Status of processor 0 as of: 01/18/06 00:38:50
  Processor has been on-line since 01/09/06 17:27:35.
  The sparcv9 processor operates at 296 MHz,
        and has a sparcv9 floating point processor.
Status of processor 1 as of: 01/18/06 00:38:50
  Processor has been on-line since 01/09/06 17:27:38.
  The sparcv9 processor operates at 296 MHz,
        and has a sparcv9 floating point processor.
Legacy Article IDa30809

Attachments

    Outcomes