000012266 - Xudad crashes on a multi-processor machine when trace logging is enabled

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 22, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000012266
Applies ToRSA Certificate Manager (RCM)
Sun Solaris
Linux (all supported versions
Microsoft Windows Server 2003 SP2
IssueXudad crashes on a multi-processor machine when trace logging is enabled
Xudad crashes soon after startup and simply browsing through the RCM admin interface
CauseThe crash occurs in the xudad trace log thread (in std::basic_string) while constructing trace log messages due to a known issue with Standard Template Library (STL) std::string class on multi-processor machines.  For more details about the known issue, see Microsoft knowledgebase article 813810 at http://support.microsoft.com/kb/813810.
Resolution

This issue will be fixed in RCM at a future date.  In the mean time, the following steps can be taken to bind xudad.exe to a single processor to avoid the crash (when trace logging is enabled):

1. Select the "Processes" tab in Windows Task Manager
2. Right mouse click on xudad.exe process and select "Set Affinity..."
3. Select a single CPU you want xudad.exe to run in

Note:  When attempting to set process affinity you may get the following error message:
   
Unable to Access or Set Process Affinity
    The operation could not be completed
    Access is denied

If you get the above error, stop Task Manager, and follow these steps:

1. Open a command prompt (cmd.exe), run the following command to start Windows Task Manager
2. ntsd -c qd taskmgr
3. Right click on xudad.exe process and select "Set Affinity..."
4. Select a single CPU you want xudad.exe to run in

See solution How do you bind the RCM xudad process to a single CPU? for more information on binding RCM to single CPU

WorkaroundEnabled trace logging for RSA Certificate Manager (RCM) Secure Directory Server (Xudad) by uncommenting the line "TraceDetail all high" in xudad.conf
Legacy Article IDa49359

Attachments

    Outcomes