cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1524
Views
5
Helpful
1
Replies

errSystemError-ct-sensorApp.463 not responding on ASA-SSM-10

ngtransge
Level 1
Level 1

Hello,

I got following error message when login into IPS over IDM, after error is displayed IDM is closing.

errSystemError-ct-sensorApp.463 not responding, please check system processes

- The connect to the specified Io::ClientPipe failed.

SSH login works, when using CLI following health statistics are available:

sensor# show health

Overall Health Status                                               Red

Health Status for Failed Applications                         Red

Health Status for Signature Updates                         Yellow

Health Status for License Key Expiration                   Green

Health Status for Running in Bypass Mode                Red

Health Status for Interfaces Being Down                   Green

Health Status for the Inspection Load                      Green

Health Status for the Time Since Last Event Retrieval   Green

Health Status for the Number of Missed Packets          Green

Health Status for the Memory Usage                      Not Enabled

Health Status for Global Correlation                    Green

Health Status for Network Participation                 Not Enabled

Security Status for Virtual Sensor sensor-int    Green

Security Status for Virtual Sensor vs0           Green

Do you have any idea why IPS crashed ?

ASA-SSM-10 is installed into ASA 5510.

1 Reply 1

secstd
Level 1
Level 1

Hello,

I have the sem problem since sveral days, I found the following workaround on our environement. Working since 5hours.

Hope it helps.

Regards.

IDSM-2 Sensor Module - errSystemError -ct-sensorApp.XXX not responding, please check system processes - The connect to the specified Io::ClientPipe failed.

Symptom:

When attempting to access an IDSM-2 sensor via its GUI (IDM) or via IME (IPS Manager Express), an error such as the following is encountered:

"errSystemError -ct-sensorApp.XXX not responding, please check system processes - The connect to the specified Io::ClientPipe failed."

Additionally, review of the 'show version' command output indicates the AnalysisEngine (sensorApp process) to be "Not Running".

Conditions:

IDSM-2 sensor module running 7.0(x) software release. Global Correlation Inspection feature enabled (On). A 'show tech' command output includes a sensorApp process core containing lines similar to the following:

cat /usr/cids/idsRoot/core/sensorApp/core.txt

...

/usr/cids/idsRoot/bin/sensorApp(_ZN3Cid3Rep9RepIpData13ApplyIpUpdateEPKcPNS0_8RepScoreE+)

Solution:

This problem is tracked as defect CSCti79423. It can be encountered on the IDSM-2 platform when a Global Correlation Update occurs. A fix for this is currently planned for inclusion in the next 7.0 release (7.0(6)).

In the interim, the only workaround to ensure that the sensor does not re-encounter this defect is to disable Global Correlation Inspection (Updates) as such:

sensor# conf t

sensor(config)# service global-correlation

sensor(config-glo)# global-correlation-inspection off

sensor(config-glo)# exit

Apply Changes?[yes]: yes

After making the above configuration change, a reboot of the affected IDSM-2 sensor module should restore it to service:

sensor# reset

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: