cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1709
Views
0
Helpful
9
Replies

Error: getAnalysisEngineStatistics:ct-sensorApp.26277 not responding

ahmed.gadi
Level 1
Level 1

One of my customers has  IPS-4240-K9   and facing issue with follwing error

Output from show statistics analysis-engine

Error: getAnalysisEngineStatistics : ct-sensorApp.26277 not responding, please check system processes - The connect to the specified Io::ClientPipe failed.


Output from show statistics anomaly-detection

Error: getAnomalyDetectionStatistics : ct-sensorApp.26277 not responding, please check system processes - The connect to the specified Io::ClientPipe failed.

Analysis Engine is working fine as you can see under show version

MainApp            B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   2009-10-15T08:09:06-0500   Running 

AnalysisEngine     BE-BEAU_E4_2010_MAR_25_02_09_7_0_2   (Ipsbuild)   2010-03-25T02:11:05-0500   Running 

CollaborationApp   B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   2009-10-15T08:09:06-0500   Running 

CLI                B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   2009-10-15T08:09:06-0500         

Can please someone help me to analysis the error.

Look forward for response.

Reagrds 

1 Accepted Solution

Accepted Solutions

  I don't think a signature update will resolve the issue. But you can give it a shot.

Thanks.

View solution in original post

9 Replies 9

sbagavat
Cisco Employee
Cisco Employee

What version are you running?

Do you have a core.txt in your sh tech? If so, can you paste that info?

Thanks.

Please find attached core.txt and version is

Output from show version

Application Partition:

Cisco Intrusion Prevention System, Version 7.0(2)E4

Host:                                                       

OS Version:             2.4.30-IDS-smp-bigphys               

Platform:               IPS-4240-K9                         

Sensor up-time is 355 days.

Using 1482727424 out of 1984548864 bytes of available memory (74% usage)

Upgrade History:

  IPS-sig-S492-req-E4.pkg   00:01:02 UTC Sun Jun 06 2010 

Recovery Partition Version 1.1 - 7.0(2)E3


Look forward for your quick response.

Thanks Ahmed for the core file.

I see the following in your core file:

0x0x8316ea9   +/usr/cids/idsRoot/bin/sensorApp(_ZN3Cid6Sensor4Proc11SignatureDB11TcpRootNode9expireNowEv+0x19) [0x8316ea9];0x0x406328f0   +/lib/libc.so.6 [0x406328f0];0x0x8318be3   +/usr/cids/idsRoot/bin/sensorApp(_ZN3Cid6Sensor4Proc11SignatureDB5purgeEhNS2_9PurgeTypeE+0x243)

You might be hitting the following bug:

Bug ID: CSCtb39179

Bug Tool Kit: http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs

The bug is fixed in 7.0.4 E4 and 6.2.3 E4.

Thanks.

Thanks for your quick response :-) Glade to get reply now only...

So do you think upgrading from 7.0(2)E4  to 7.0.4 E4  will solve my problem ?

Let me schedule with my client for upgrade and will update my feedback  once i will do the upgrade 

Regrads

Ahmed

Sure. Please keep me posted.

Thanks.

oh sorry,,, i forgot to mentioned that the signature update has been expired since 2010, so client is in process to renew it.

Do you think after updating signature license, will solve the issue without upgrading OS ?

I can see this error related to signature update in bug toolkit.

Regards

Ahmed...

  I don't think a signature update will resolve the issue. But you can give it a shot.

Thanks.

Thanks i will update you ...

Hi sbagavat,

                  Today i upgrade its license and update all signature uptodate and everything started working normal, Now i can access IPS through IDM normally.

Thanks for your support, I will do upgrade to 7.0.4 if i will face further problem.

Regards

Ahmed...

Review Cisco Networking for a $25 gift card