Cisco IPS Error -- errsystemerror-ct-sensorapp.333 not responding

Unanswered Question
Nov 5th, 2008

Hi Team,

I am getting the below error while accessing IDM. I rebooted the device, after some times i get the same type of messages..

error connecting to sensor + failed to load sensor. errsystemerror-ct-sensorapp.333 not responding. please check system processes- the connect to the specified lo::clientpipe failed.

Will be appreciated for the quick reply on priority...



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 2.5 (2 ratings)
rhermes Wed, 11/05/2008 - 10:50

When the error message tells you to check the system processes, you should check them:

ssh to your sensor and login.

run a "sh ver"

Sec IT Wed, 11/05/2008 - 22:44


Pls find the below show version..

Looks like all the processes are running..

Application Partition:

Cisco Intrusion Prevention System, Version 5.1(5)E1


Realm Keys key1.0

Signature Definition:

Signature Update S323.0 2008-03-24

Virus Update V1.2 2005-11-24

OS Version: 2.4.26-IDS-smp-bigphys

Platform: IPS-4240-K9

Serial Number: xxxxxxxxxxxx

Licensed, expires: 01-Dec-2009 UTC

Sensor up-time is 14:55.

Using 512040960 out of 1454153728 bytes of available memory (35% usage)

system is using 17.4M out of 29.0M bytes of available disk space (60% usage)

application-data is using 44.1M out of 166.8M bytes of available disk space (28%


boot is using 35.3M out of 68.6M bytes of available disk space (54% usage)

MainApp 2007_FEB_02_15_58 (Release) 2007-02-02T16:04:00-0600 Runn


AnalysisEngine 2007_FEB_02_15_58 (Release) 2007-02-02T16:04:00-0600 Runn


CLI 2007_FEB_02_15_58 (Release) 2007-02-02T16:04:00-0600

Upgrade History:

* IPS-K9-sp-5.1-5-E1 10:28:00 UTC Fri Feb 02 2007

IPS-sig-S323-req-E1.pkg 07:26:42 UTC Tue Mar 25 2008

Recovery Partition Version 1.1 - 5.1(5)E1

Sec IT Sun, 11/09/2008 - 01:39


Pls find the logs and let me know what could be the problem...


ending a TLS warning alert close_notify, the following error occurred: socket error [3,32]05Nov2008 20:05:53.338 106.380 mainApp[272] Cid/E errSystemError AppManager::ApplicationEntry::updateProcessStatus - Application "AnalysisEngine "terminated prematurely05Nov2008 20:06:14.689 21.351 cidwebserver[320] IoPipe/E errSystemError connect timed out [ClientPipe::connect]05Nov2008 20:06:14.711 0.000 cidwebserver[320] Syslog/F ct-sensorApp.333 not responding, please check system processes - The connect to the specified Io::ClientPipe failed.05Nov2008 20:16:32.787 618.098 cidwebserver[325] tls/W errTransport while sending a TLS warning alert close_notify, the following error occurred: socket error [3,32]05Nov2008 20:17:04.090 31.303 cidwebserver[2853] IoPipe/E errSystemError connect timed out [ClientPipe::connect]05Nov2008 20:17:04.090 0.000 cidwebserver[2853] Syslog/F ct-sensorApp.333 not responding, please check system processes - The connect to the specified Io::ClientPipe failed.--------------- .logApp begin Wed 05-Nov-2008 20:18:37 GMT+05:30


adiwakar Sun, 11/09/2008 - 12:55

Hi Rajesh,

What version of the sensor are you using, if you are using the latest 6.1.1E3, try downgrading and see if that helps by using the 'downgrade' command. If you have been running this version for a while, what's changed in your environment? Open the CLI to the sensor, run the command "show events" and try another connection to the sensor via IDM, place the output here.

Sec IT Mon, 11/10/2008 - 03:22

Hi Adiwakar,

The version is 5.1-5-E1.

I am planning to upgrade the sensor to 6.x version inorder to fix this problem, because I do not find anything related to this issue.

Sec IT Thu, 11/13/2008 - 03:53


My upgrade to 6.0 and 6.1 was not successfull and had to reimage to 5.1.6. The device was rebooting frequently inspite of the fact that this has 1GB RAM.

Can anyone give me a solution on this...


mdreelan Mon, 12/01/2008 - 08:46

You can try re-installing the license. A corrupt license file can cause what you are describing.

Solobone22 Tue, 12/09/2008 - 18:58

I am getting the following error:

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

The device is a IDSM-2 running 6.1.(1)E3. Is this a E3 issue only? I rebooted the sensor and it is functioning normally again. We had this happen to an inline sensor and it caused all kinds of problems.



Sec IT Wed, 12/17/2008 - 10:33

I think reset of IPS will resolve this issues..

you need to fine tune the signatures as well..

Solobone22 Wed, 12/17/2008 - 17:19

Is there a particular reason why you say I need to fine tune signatures? TAC said to disable 2 sigs and lower the frequency of the auto-update feature. I disabled the sigs as well as the auto-update, rebooted and now it is fine. They said a software fix will be available in a week or so. I'll let you know how it goes.

Sec IT Mon, 12/22/2008 - 00:45

What are the sig ids disabled ?

Were you getting alerts in EV/IME before ??

Im not getting alerts in ime.

Sec IT Tue, 02/10/2009 - 20:09

The problem is resolved after upgrading the signatures.

Sec IT Sun, 03/22/2009 - 06:13

Actually I have upgraded the signature to the latest version.

Secondly, I monitored the outputs of the below command and disabled few of the signatures which are firing a lot of signatures...

command is --- show statistics virtual-sensor


Rajesh P


This Discussion