SDServer and/or cserver hang on Scalability servers

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

sdserver and/or cserver plugins are hanging or crashing.

 

Example of cserver crash :

Faulting application name: cserver.exe, version: 14.5.0.153, time stamp: 0x60073e55
Faulting module name: ntdll.dll, version: 10.0.14393.5427, time stamp: 0x63368a30
Exception code: 0xc0000374
Fault offset: 0x000d8fb1
Faulting process id: 0x1160
Faulting application start time: 0x01d9892d89524812
Faulting application path: D:\CA\DSM\Bin\cserver.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Stack trace:
Stack trace at 0x7789c908
    777d6a9c: ntdll!RtlFreeHeap+0xac
    7c34218a: msvcr71!free+0xc3
    059d4d43: awmsq!AWMsq_quitselect+0x173
    736f1b7c: cfmspi!MspiIoctlEx+0x4c
    7376707b: cfsmcapi!CFCreateInstance+0x5e0b
    7376bde3: cfsmcapi!SmIoctl+0xd3
    00efea9b: cserver+0xea9b
    00f043f3: cserver+0x143f3
    00f048e9: cserver+0x148e9
    73768a9d: cfsmcapi!CFCreateInstance+0x782d
    73768925: cfsmcapi!CFCreateInstance+0x76b5
    7377e24b: cfsmcapi!SmSecSetCallback+0x12eb
    737685ce: cfsmcapi!CFCreateInstance+0x735e
    73768db3: cfsmcapi!CFCreateInstance+0x7b43
    736f2ae8: cfmspi!MspiQueryFacility+0x518
    72c421f2: cfMessenger+0x21f2

 

And last lines of crashing thread in TRC_CSERVER*.log are :

260623-08:20:12.4147396L|004184|000010f8|cserver   |server.cpp      |                    |000000|INFO   | === executing request: req_get_mgmt_info from host: 1.2.3.4 (1.2.3.4) ===
260623-08:20:12.4149952L|004184|000010f8|cserver   |get_mgmt_info   |                    |000000|DETAIL | Calling SmIoctl on 1.2.3.4
260623-08:20:12.4150346L|004184|000010f8|cserver   |CFSMCAPI        |CFSMCAPI            |000000|DETAIL | endpoint::ioctl : Action ioctl 14

Environment

Client Automation 14.5 with or without CU patch.

Cause

Code is calling cam api which needs to fetch the proxy list of a network queue even though the earlier api is failing (the api for proxy list should be called only upon successful return of the earlier api).

Resolution

Open a case at CA Broadcom Technical Support and request the fix T437407