Analysis Enginer showing not running

Analysis Engine is not running and giving Error:
Error: getAnalysisEngineStatistics : ct-sensorApp.598 not responding, please check system processes - The connect to the specified Io::ClientPipe failed

I fixed this issue once using the following procedure:
https://supportforums.cisco.com/docs/DOC-3589
If the above procedure or reload does not fix the issue as suggested on the following link:
https://supportforums.cisco.com/docs/DOC-5121/diff;jsessionid=82FA4EB3696EC0C97B6394F996EEAA5E.node0?secondVersionNumber=2
You have to contact TAC, as mentioned below:
http://www.cisco.com/en/US/docs/security/ips/6.0/installation/guide/hwTS.html#wp1122031
Regards
Farrukh
Message was edited by: Farrukh Haroon

Similar Messages

Analysis Engine is Not Running

Hi Guys!
I´m looking for your help about an issue with an Cisco IPS (B-BEAU) that is showing the Analysis Engine=NotRunning
These are the SO and Version of my IPS:
Version: 7.0(6)E4
OS Version: 2.4.30-IDS-smp-bigphys
If I execute the show events command I get the following lines:
ct-sensorApp.650 not responding
evStatus: eventId=1326914865100530240 vendor=Cisco
originator:
    hostId: XXXXXXXX
    appName: modprobe
    appInstanceId:
time: 2013/07/13 02:11:05 2013/07/12 20:11:05 CST
syslogMessage:
    description: Note: /etc/modules.conf is more recent than /lib/modules/2.4.30-IDS-smp-bigphys/modules.dep
The following lines show the result for the show status command:
XXXXXX# show health
Overall Health Status                                   Red
Health Status for Failed Applications                   Red
Health Status for Signature Updates                     Not Enabled
Health Status for License Key Expiration                Red
Health Status for Running in Bypass Mode                Red
Health Status for Interfaces Being Down                 Red
Health Status for the Inspection Load                   Green
Health Status for the Time Since Last Event Retrieval   Not Enabled
Health Status for the Number of Missed Packets          Green
Health Status for the Memory Usage                      Not Enabled
Health Status for Global Correlation                    Not Enabled
Health Status for Network Participation                 Not Enabled
Security Status for Virtual Sensor vs0   Green
Security Status for Virtual Sensor vs1   Green
Do you have any idea what's wrong here?
I'll appreciate any help about it,
Thanks folks!!!

Hi Manuel,
Pre-7.0.8 versions have issues with the latest signature updates, so most likely you will face this issue after every signature upgrade. So I suggest you to upgrade at least to 7.0.8 or 7.1.7.
HTH
Luis Silva
"If you need PDI (Planning, Design, Implement) assistance feel free to reach"
http://www.cisco.com/web/partners/tools/pdihd.html

SAP j2ee engine is not running error while applying patches.

Hi all,
Iam in the process of aplpying patches using JSPM tool , for some of them iam getting the error messages , when i checked the log file for this tool it says:
SAP J2ee engine is not running , unable to login to <HOST name> with id <Login id>.
Iam very new to this activity ,can anybody help me in this regard , i wil be very thankful.
Thanks and Regards.
Niyati.

Hi,
What exactly do you see when you say that the status in the MMC is OK? I don't think it can be green if you say that you get a message saying "Service Unavailable" when you try to login. If you get that message, it means that the service hasn't either been started or could not be started in case of an error. In this case the server status in the MMC should be yellow (or gray in case none of the services could be started)...
Could you perhaps check it again? Another point to check would be if the connection to the database is OK. If you are using MySQL MaxDB, you could use the Database Manager tool to check this. Sometimes the log files fill up the database and the server cannot start because the database is full. In such cases you will need to clear the logs and then restart the entire cluster.
Sameer

J2EE Engine is not Running

Hi All:
I start my XI server and found the J2EE Engine is not running what will be the main cause of this?? I tried to open the Visula Admin but it is throwing an Error <i>Defult user parametes not find</i>
What can be the cause of it??
Thanks
Farooq.

Hi Farooq,
For queries regarding user name and password, Please refer the page no 16 of the following pdf:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0e1ba1a-e86e-2910-ee83-b73b54abc7d4
I hope this helps.
Regards,
Shibani
*Reward with points if helpful*

Reporting & Analysis workspace9 server not running on server at port 6800

Hi all,
i installed hyperion 9 system them with reporting and essbase ..
after configured all .. configure shows sucess but after shared services configuration failed in BI
unable to open workspace
when i tried to open Workspace
"Could not find a Hyperion Reporting and Analysis in workspace9 server running on server at port 6800. Please verify your server connect string and confirm that the server is up."
Please help...

Restart order all serives in the below mentioned order:
Hyperion S9 Shared Services
Hyperion S9 OpenLDAP
Hyperion S9 BI+ Analytic Services 9.3.1 - hypservice
HyperionRMIRegistry
Hyperion S9 Planning
Hyperion S9 Administration Services ATS5
Hyperion S9 Apache 2.0
Hyperion S9 BI+ 9.3 Core Services 1
Hyperion S9 BI+ 9.3 Financial Reporting Print Server
Hyperion S9 BI+ 9.3 Financial Reporting Report Server
Hyperion S9 BI+ 9.3 Financial Reporting Scheduler Server
Hyperion S9 BI+ 9.3 Financial Reporting Java RMI Registry
"Hyperion S9 BI+ 9.3 Financial Reporting Web application
Hyperion S9 BI+ 9.3 Web Analysis
Hyperion S9 Financial Management DME Listener
Hyperion S9 BI+ 9.3 Workspace
-Sasi

WAS SP9 SR1 ABAP+Java Add in installation , j2EE engine is not running

I have completely installed SAP Netweaver SP9 SR1 WAS ABAP+JAVA addin and Installed XI completely. After few days j2EE engine stops running. I have applied the license after requesting from SAP Mareketplace and applied in WAS ABAP using SLICENSE transaction.
Issue faced
1. Tried to connect j2ee engine home page which is showing.
Dispatcher is running but no server connected.
Now I have removed the WAS J2EE installation and removed the client on which WAS j2EE engine installed. After doing this I tested the WAS ABAP which is running fine. Now I am again installing WAS Java addin. Which installed success fully and have seen the j2ee engine server page running. But proceeding further to install JAVA Dialog instance I am facing folloing issues
2. while installation step 8 and 9 as per SAP INSTANCE GUI .
3. And J2EE engine is again stopping.
Can any one help me to install J2ee dialog installation and resolving these issues.
Anand Verma
HCL technologies

Hi Anand,
J2EE Engine has a separate licensing mechanism. If the temporary license expires, the server will shut down every 30 minutes. You install a permanent license using Visual Administrator in service "Licensing Adapter".
In any case, a look into the log files of the engine can provide further information. They are found at
.../<SID>/<INSTANCE>/j2ee/cluster/server<n>/log
Kind regards,
Juergen Kremp

PBS Kids Show not running on Apple TV, why not?

I am not able to get PBS Kid shows to run on my Apple TV, I can get other programming. What is happening, I've waited for about a week now, with no change.

Try setting the Dolby digital option to "off" on the Apple TV settings.

FR and Web Analysis reports will not run in workspace

I have configured both FR and Web Analysis and then re-configured workspace to pick them up. 'Reporting and Analysis shows up in my foundation metadata under workspace. All my related ports are enabled.
Database connection manager, import financial reporting reports, preferences financial reporting, tools/link to web analysis, do not appear in workspace.
get 'required application context analyzer is missing. please contact your adminstrator.' error when try to run a web analysis or financial reporting report from workspace.
Web analysis as a client with reports is working fine.
Financial reporting allows me to create a database connection, create a report, pdf preview from the client but web preview breaks with generic page not found error.
Any suggestions would be most appreciated.

Hi,
You can use panel while creating reports and put all the graphs on it .
Panels color can be changed.
Thanks
Yashwant

Full Synch risk analysis job is not running good

Hi
Recently we have started user_full_synch_risk_analsysis job is running but with many error..
I have checked the SLD it is running, JCO also tested good..checked in debugger...tried to look the data..working good..
but the log saying "can not extract the data from DEV system"
it is skipping each userid risk analysis saying the above error and it continuing with other userIDs.. Please help
INFO: Job ID:18 : Exec Risk Analysis
Sep 27, 2010 7:51:38 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Job ID:18 : Analysis starts: XRPM_PM2
Sep 27, 2010 7:53:04 AM com.virsa.cc.comp.BgJobInvokerView onActionsearchObj
INFO: Number of users matched:132
Sep 27, 2010 7:58:30 AM com.virsa.cc.xsys.meng.MatchingEngine matchActRisks
WARNING: Error :
com.virsa.cc.dataextractor.dao.DataExtractorException: Cannot extract data from system (DEV); for more details, refer to ccappcomp.n.log
     at com.virsa.cc.dataextractor.bo.DataExtractorSAP.searchUser(DataExtractorSAP.java:551)
     at com.virsa.cc.dataextractor.bo.DataExtractorSAP.userIsIgnored(DataExtractorSAP.java:529)
     at com.virsa.cc.xsys.meng.MatchingEngine.getObjActions(MatchingEngine.java:682)
     at com.virsa.cc.xsys.meng.MatchingEngine.matchActRisks(MatchingEngine.java:112)
     at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1104)
     at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:297)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1047)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1331)
     at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:402)
     at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:264)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:240)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:80)
     at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:436)
     at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1225)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
     at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Sep 27, 2010 7:58:30 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
WARNING: Job ID:18 : Failed to run Risk Analysis
java.lang.Exception: Cannot extract data from system (DEV); for more details, refer to ccappcomp.n.log
     at com.virsa.cc.xsys.meng.MatchingEngine.matchActRisks(MatchingEngine.java:118)
     at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1104)
     at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:297)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1047)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1331)
     at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:402)
     at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:264)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:240)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:80)
     at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:436)
     at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1225)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
     at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Sep 27, 2010 7:58:30 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
WARNING: Error: while executing BatchRiskAnalysis for JobId=18 and object(s):XRPM_PM2: Skipping error to continue with next object: Cannot extract data from system (DEV); for more details, refer to ccappcomp.n.log
Sep 27, 2010 7:58:30 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
2@@Msg is Error while executing the Job for Object(s) :XRPM_PM2:Cannot extract data from system (DEV); for more details, refer to ccappcomp.n.log
Sep 27, 2010 7:58:30 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO: -
Background Job History: job id=18, status=2, message=Error while executing the Job for Object(s) :XRPM_PM2:Cannot extract data from system (DEV); for more details, refer to ccappcomp.n.log
Sep 27, 2010 7:58:30 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis

Dear Harikrishna,
Please mention what is your Support pack. This is an identified bug for SP12 especially synchronizing the users from the backend and doing the risk analysis at the user level. We had the same problem. But for some reason we are now able to do the synchronization from the backend but the management reports are getting updated.

Critical Action and Role/Profile Analysis job in not running in GRC 5.3

Hi Team,
I am working for a client where GRC 5.3 is installed( support pack 4 and patch 1).
The installation is complete and also the post processing is done.
We have scheduled a periodic ( weekly ) incremental background job for Critical Action and Role/Profile.
Following are the parameter setting used:
Task: Risk Analysis -Batch
Batch Mode : Incremental
First time it run successfully on 28th June'09 and it is completed with spool also. But next time it is supposed to run on 4th of July'09 . But it does not. And since then it is in same state.
I am not able to find any reason that why it is behaving this way where other incremental jobs are running successfully.
It will be helpfull if any one can guide me providing the solution.
Regards,
Kakali

Hi Varun,
I go to the Job History Button. It shows the following data only :
2009-06-28 00:00:59 Done Job Completed successfully
2009-06-27 23:45:00 Started RAR_PE1CLNT100_Critical Action and Role/Profile Analysis started :threadid: 0
Under the Last Run Colomn it shows 28th June ( Status -completed)
Under Next Run Date it is showing 4th July
Follwoing are the list of Updates available From SP05
When executing the critical roles/profile jobs in background, a message
"error while executing the Job: null" comes up. ---( this one is for which come under Informer Tab)
Background job spools are not available after upgrade from 5.2 to 5.3.
Critical action and critical role/profile analysis cannot be run in
background by system. --- ( But in my case It ran for once )
Selection parameters (System, User and User Group) have been provided for
"Critical Action and Role/Profile Analysis" in Configuration->Background
Job->Schedule Job. --- ( it means it run usually)
Critical Actions report in detail view shows no results after executing the
Risk Analysis Job in the background. The same report shows data when
executed in the foreground. ( this one is for which come under Informer Tab )
When there is only one periodic job configured in RAR, this job fails to
start after the first time in the specified time. ( this is not true, becoz there other periodic jobs running successfuly)
Unable to run Informer - audit reports - critical role and profiles with
logical systems. ( this is again under Informer Tab )
I had gone through this earlier also, but not able to match any update with my problem. If if have any other suggestion you can provide me the same.
Is there any way to check for job log so that I can check what is the problem. View Log option is also greyed out as we have sap logger set up as a default logger Parameter. I have made it enable just to check but there is nothing.
Please Guide.
Regards,
Kakali

H E A P   C O R R U P T E D - and smd agent shows not running

Hello Gurus,
My SMD agent is goes down every day when i check the status:
I found the heap corroupted everyday with the below warnings:
nbcsaplpa018:nedadm 19> tail hs_err_pid1888352.log
H E A P   C H E C K -
Suspension of other threads succeeded.
Heap corruption found in object at address 0x070000004ac38268. Class of object is not in the reserved heap memory area (0x002e006e006f0072).
H E A P   C O R R U P T E D -
Please suggest
Regards,
Munish

Please fine the file SMDAgentApplication.0.log for logs again : other file in next reply.
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[SMDAgentAppLog]/>
<!PATTERN[SMDAgentApplication.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%t] %10s %m)]/>
<!ENCODING[ISO8859_1]/>
<!FILESET[0, 10, 1000000]/>
<!PREVIOUSFILE[SMDAgentApplication.9.log]/>
<!NEXTFILE[SMDAgentApplication.1.log]/>
<!LOGHEADER[END]/>
Mar 24, 2010 1:53:17 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Mar 29, 2010 10:57:12 AM [Thread[Thread-174,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Mar 30, 2010 12:18:05 PM [Thread[Thread-229,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Apr 1, 2010 1:59:00 PM [Thread[Thread-311,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Apr 1, 2010 2:00:32 PM [Thread[Thread-340,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Apr 9, 2010 5:41:47 PM [Thread[Thread-546,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 28, 2010 5:44:24 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 29, 2010 3:26:39 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 29, 2010 9:09:56 AM [Thread[Thread-6,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 30, 2010 10:13:43 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
May 31, 2010 4:00:07 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jun 1, 2010 3:04:42 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jun 2, 2010 4:09:21 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jun 2, 2010 9:02:55 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 20, 2010 3:07:02 PM [Thread[Thread-6,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 21, 2010 5:32:08 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 22, 2010 12:46:11 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 22, 2010 8:28:13 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 22, 2010 3:30:13 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 22, 2010 9:15:34 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 26, 2010 7:00:11 AM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 26, 2010 2:56:56 PM [Thread[Thread-6,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found
Jul 26, 2010 11:25:29 PM [Thread[Thread-5,5,main]] Warning    com.sap.smd.eem.agelet.ext.ExtManager - init: no executor libs found

Analysis Engine Not running for IPS in AIPSSM Module

Hi all,
The Analysis Engine is not running for IPS module in AIPSSM Module. Please let me know how can i resolve this issue and get the analysis engine of IPS to running status.
Regards
Kiran

Hi Kiran,
Ideally, what you can do is to remove the configuration on the ASA that sends traffic to IPS.
The crash in sensorapp or analysis engine might be traffic, configuration related.
We can try to reboot the IPS with no load on it by stopping sending traffic to it.
You can remove the IPS policy from the ASA configuration.
http://tools.cisco.com/squish/2f7A3
What this will do is stop ASA from sending any traffic to IPS.
Now do the hw-module module 1 reset command.
See if the IPS module comes back up.
If that also fails, then you can re-image the module.
This will however erase the configuration on the module.
The re-image procedure for SSM module:
http://tools.cisco.com/squish/ee66a
Hope this helps.
Sid

Analysis Engine

The sensor IDS 4250XL 5.1 reports that the daemon AnalysisEngine has a status of not Runnnig. What does it mean? What i have to do? It is probably this is the source of the problem i have with the deployment of this sensor from the IPS Manager??
Thank you

If the Analysis Engine is not running, the sensor will not analyze traffic and will therefore be useless (won't generate alerts..). To restart the analysis engine, make a service account then log into the service account and run the command below (you must su to root first).
/etc/init.d/cids restart
Hope this helps.

Analysis Engine Not running

When i do "sh ver" over an IDS 4250XL 5.1(1)S243.0 it appears:
AnalysisEngine 2006_Feb_08_13.09 (Release) 2006-02-08T13:52:38-0600 NotRunning
What does it imply? How can i start it?
Thanks,

If the ananlysis engine is not running, your sensor is not analyzing dumped traffic (and is therefore useless).... To get it started, follow the steps below.
1. Create a service account user in CLI or IDM
2. Login using service account in CLI
3. Switch to root user by typing su and service account pwd
4. Type the following command at bash-2.05b# prompt: /etc/init.d/cids restart
5. To check if the sensor is "up" again, type su cisco. Then do a show version.
6. If you still experience issues, exit back to the service account and type reboot.
If the helps, please rate me..
Cheers,
Jay Walker

Svrcfg show Job Server not running

Hi,
I am currently running Data Services 12.1.1.0 on Linux RH AS 4.6. I have noticed an issue and wondering whether there is something I am doing wrong.
I installed DS and configured the JS. I have successfully started, stopped and started this again, via the svrcfg utility and it clearly states "running". Then I log out of Putty and log back into the into server hosting DS. When I go to the svrcfg utility again, go to control job server it reports a status of not running. If I exit the tool and type ps -fu <username> I can see my Job Servive/Engine as I would expect and jobs still run fine?
Does anyone know what might be causing this?
Thanks
Chris

Hi,
I am also getting the same issue. If you login into putty and check the status by which terminal you have started shows "RUNNING", if you login through another session with same user it shows "NOT RUNNING".
Output of ps -o user,fname |grep -v grep|grep AL_JobSe is
bodi AL_JobSe
I am running the . .al_env.sh manually (not from profile!).
Thanks
Maran

Analysis Enginer showing not running

Similar Messages

Maybe you are looking for