segfault error 4 in libc-2.17.so

Document ID : KB000105948
Last Modified Date : 23/07/2018
Show Technical Document Details
Issue:
After installation of product an error was encountered. The error is displayed below:

Jul 10 11:26:05 ip-10-41-37-55 kernel: csampmux[15776]: segfault at f7779000 ip 00000000f758c538 sp 00000000ffb86148 error 4 in libc-2.17.so[f7446000+1b9000]
Environment:
AWS Server
Any database
Cause:
Segfault arises when process tries to access invalid or restricted memory area and generates a core dump If ulimit is set to unlimited.
 
Resolution:
Customers who have experienced this behavior indicated that the issue resolved itself and the product was working without further incident. If a core dump was created for this issue, it can be found anywhere in the AutoSys installation path. You can perform a recursive search for it in the AutoSys install path (by default /opt/CA/WorkloadAutomationAE), but if you chose to install the product elsewhere then you will need to know that location or consult with your System Administrator to locate it.

Validate that CSAM is running on your server. This can be done one of two ways:

1. Issue the command csampmux status. This should result in a listing of 4 PID's such as: 
Listeners

PID:   15036 Port 9000 for IPv6.
PID:   15036 Port 49186 for IPv6.
PID:   15327 Port 49165 for IPv6.
PID:   15327 Port 49174 for IPv6.


2a. On UNIX, perform a process listing using the command ps -ef | grep -i csam. You should get a system response similar to below:
root     16037     1  0 Jul17 ?        00:00:30 /opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmuxf
root     54271 52501  0 09:08 pts/0    00:00:00 grep --color=auto -i csam


2b. On Windows, launch Windows Task Manager and look for process name "CA-SAM-Pmux." Ensure it has a status of running.