cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

DAA starts and then stops within 10 mins

Former Member

on ‎11-04-2010 9:36 PM

0 Kudos

We have installed DAA (solution Manager Diagnostics) agent in one of SAP ECC 6.0 system (only ABAP stack).

when we start DAA, it starts and we are able to see the below process.

(kgsand2)#ps -ef | grep DAA

root 3416 2449 0 13:52:55 pts/5 0:00 /usr/sap/DAA/SMDA97/exe/sapcontrol -prot NI_HTTP -nr 97 -function GetProcessList

daaadm 3339 3318 0 13:49:23 ? 0:00 jc.sapDAA_SMDA97 pf=/usr/sap/DAA/SYS/profile/DAA_SMDA97_kgsand2

daaadm 3420 3339 0 13:53:44 ? 0:00 /usr/sap/DAA/SMDA97/exe/jstart -appTrc -nodeId=1000 pf=/usr/sap/DAA/SYS/profile/DAA_SMDA97_kgsand2 -DSAPINFO=DAA_97_flightrec -

daaadm 2778 1 0 13:35:12 ? 0:00 /usr/sap/DAA/SMDA97/exe/sapstartsrv pf=/usr/sap/DAA/SYS/profile/DAA_SMDA97_kgsand2 -D -u daaadm

daaadm 3318 1 0 13:47:42 ? 0:00 sapstart pf=/usr/sap/DAA/SYS/profile/DAA_SMDA97_kgsand2

root 3425 24656 0 13:54:11 pts/4 0:00 grep DAA

But after few mins it goes down.

When checked using startsap -c we get the below error

kgsand2:daaadm 37> cat stderr0

(7409) New Child Process created.

(7409) Starting local Command:

Command: jc.sapDAA_SMDA97

pf=/usr/sap/DAA/SYS/profile/DAA_SMDA97_kgsand2

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.

jc.sapDAA_SMDA97=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/HTTP/file_access_0 (ref.by icm/HTTP/file_access_0) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_0 (ref.by icm/server_port_0) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_1 (ref.by icm/server_port_1) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_2 (ref.by icm/server_port_2) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_3 (ref.by icm/server_port_3) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_4 (ref.by icm/server_port_4) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_5 (ref.by icm/server_port_5) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_6 (ref.by icm/server_port_6) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_7 (ref.by icm/server_port_7) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_8 (ref.by icm/server_port_8) missing.

jc.sapDAA_SMDA97=>sapparam(14): icm[SMDA]/server_port_9 (ref.by icm/server_port_9) missing.

jc.sapDAA_SMDA97=>sapparam(14): ssl/pse_provider[SMDA] (ref.by ssl/pse_provider) missing.

We reinstalled SMD many times, but no luck

Has anyone faced this error and resolved?

Thanks

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
‎11-19-2010 9:24 PM
0 Kudos

Not answered

Show replies
Show replies
Former Member
‎11-08-2010 5:15 AM
0 Kudos

What is your SAP Kernel Release and patch level??

Check this... if it is usefull.

Note 1466109 - Support of system/type=SMDA in the SAP profiles

Edited by: Khaiser Khan Mohammed on Nov 8, 2010 6:21 AM

Show replies
Show replies
Former Member
‎11-08-2010 3:01 PM
0 Kudos

Thank you Mr.Reddy and Khaiser Khan.

Both the solutions doesn't work for me. I feel that could be a warning, but the real error message could be the below one.

F [Thr 01] Mon Nov 8 09:43:46 2010

F [Thr 01] *** WARNING => SfCJavaProcHandler(smdagent)::onTimer: connect from smdagent timed out (30000 ms) - stopping the process. [sfxxproc.hpp 1252]

F [Thr 01] *** LOG => Send SIGINT to SMDAgent (pid 26778).

F [Thr 01] *** LOG => Process smdagent stopping (pid 26778).

F [Thr 01] *** LOG => Signal 18 SIGCHLD.

F [Thr 01] *** WARNING => process SMDAgent (pid 26778) killed (signal 2). [sfuxlib.hpp 832]

F [Thr 01] *** LOG => Process smdagent stopped (pid 26778).

F [Thr 01] *** WARNING => Node smdagent failed: result 1, exit code 2. [sfxxnode.hpp 1016]

F ********************************************************************************

F Java process [collector] properties:

F section name : collector

F config file : /usr/sap/DAA/SMDA97/exe/startup.properties

F node name : collector

F home directory : /usr/sap/DAA/SMDA97/j2ee

F shutdown timeout : 136000 ms

F exit timeout : 7000 ms

F debuggable : false

F debugger active : false

F ********************************************************************************

F ********************************************************************************

F Starting process: /usr/sap/DAA/SMDA97/exe/jstart

F arg[ 1] = -nodeId=1000

F arg[ 2] = pf=/usr/sap/DAA/SYS/profile/DAA_SMDA97_kgsand2

F arg[ 3] = -DSAPINFO=DAA_97_collector

F arg[ 4] = -hostvm

F arg[ 5] = -nodeName=collector

F arg[ 6] = -file=/usr/sap/DAA/SMDA97/exe/startup.properties

F arg[ 7] = -jvmFile=/usr/sap/DAA/SMDA97/work/jstart.jvm

F arg[ 8] = -traceFile=/usr/sap/DAA/SMDA97/work/dev_collector

F arg[ 9] = -javaOutFile=/usr/sap/DAA/SMDA97/work/jvm_collector.out

F arg[10] = -clusterId=smdagent

F arg[11] = -exitcode

F arg[12] = 2

F env : LD_PRELOAD=libjvm.so

Have you face any such issues, I have written to SAP and also search OSS & Forums no relevant solutions

Thanks

Former Member
‎11-09-2010 2:06 AM
0 Kudos

Hi Senbala,

Did you check your services host control and host exe?

Are those in start condition, if so check the host agent trace for errors and post me those errors.

Cheers

Vanga Reddy

Former Member
‎11-16-2010 8:26 PM
0 Kudos

Hi Vanga Reddy,

Can you please let me know what & where the host services & exe needs to be checked?

F [Thr 01] *** LOG => Process smdagent started (pid 13947).

F

F [Thr 01] Tue Nov 16 13:15:22 2010

F [Thr 01] *** WARNING => SfCJavaProcHandler(smdagent)::onTimer: connect from smdagent timed out (30000 ms) - stopping the process. [sfxxproc.hpp 1252]

F [Thr 01] *** LOG => Send SIGINT to SMDAgent (pid 13947).

F [Thr 01] *** LOG => Process smdagent stopping (pid 13947).

F [Thr 01] *** LOG => Signal 18 SIGCHLD.

F [Thr 01] *** WARNING => process SMDAgent (pid 13947) killed (signal 2). [sfuxlib.hpp 832]

F [Thr 01] *** LOG => Process smdagent stopped (pid 13947).

F [Thr 01] *** WARNING => Node smdagent failed: result 1, exit code 2. [sfxxnode.hpp 1016]

F ********************************************************************************

F Starting process: /usr/sap/DAA/SMDA97/exe/jstart

F arg[ 1] = -nodeId=1000

F arg[ 2] = pf=/usr/sap/DAA/SYS/profile/DAA_SMDA97_kgsand2

F arg[ 3] = -DSAPINFO=DAA_97_collector

F arg[ 4] = -hostvm

F arg[ 5] = -nodeName=collector

F arg[ 6] = -file=/usr/sap/DAA/SMDA97/exe/startup.properties

F arg[ 7] = -jvmFile=/usr/sap/DAA/SMDA97/work/jstart.jvm

F arg[ 8] = -traceFile=/usr/sap/DAA/SMDA97/work/dev_collector

F arg[ 9] = -javaOutFile=/usr/sap/DAA/SMDA97/work/jvm_collector.out

F arg[10] = -clusterId=smdagent

F arg[11] = -exitcode

F arg[12] = 2

F env : LD_PRELOAD=libjvm.so

F exePath : PATH=/usr/sap/DAA/SMDA97/exe/sapjvm_5/bin:/usr/sap/DAA/SMDA97/exe:.:/home/daaadm:/usr/sap/DAA/SYS/exe/uc/hpia64:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/contrib/Q4/bin:/opt/perl/bin:/opt/gvsd/bin:/opt/ipf/bin:/opt/nettladm/bin:/opt/fcms/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/sas/bin:/opt/graphics/common/bin:/opt/atok/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/sec_mgmt/bastille/bin:/opt/caliper/bin:/opt/drd/bin:/opt/dsau/bin:/opt/dsau/sbin:/opt/resmon/bin:/opt/firefox:/opt/gnome/bin:/opt/perf/bin:/opt/propplus/bin:/usr/contrib/kwdb/bin:/opt/perl_32/bin:/opt/perl_64/bin:/opt/prm/bin:/opt/sfm/bin:/opt/swm/bin:/opt/sec_mgmt/spc/bin:/opt/ssh/bin:/opt/swa/bin:/opt/hpsmh/bin:/opt/thunderbird:/opt/sentinel/bin:/opt/langtools/bin:/opt/wlm/bin:/opt/gwlm/bin:/opt/ignite/bin

F libPath : LD_LIBRARY_PATH=/usr/sap/DAA/SMDA97/exe/sapjvm_5/jre/lib/ia64/server:/usr/sap/DAA/SMDA97/exe/sapjvm_5/jre/lib/ia64:/usr/sap/DAA/SMDA97/j2ee/os_libs:/usr/sap/DAA/SMDA97/exe

F stdout : /usr/sap/DAA/SMDA97/work/std_collector.out

F stderr : /usr/sap/DAA/SMDA97/work/std_collector.out

F console : no

F debugger: no

F nice : no

F ********************************************************************************

F Process collector started with pid 13956

F ********************************************************************************

F [Thr 01] *** LOG => Process collector started (pid 13956).

F

F [Thr 01] Tue Nov 16 13:15:52 2010

F [Thr 01] *** WARNING => SfCJavaProcHandler(collector)::onTimer: connect from collector timed out (30000 ms) - stopping the process. [sfxxproc.hpp 1252]

F [Thr 01] *** LOG => Send SIGINT to collector (pid 13956).

F [Thr 01] *** LOG => Process collector stopping (pid 13956).

F [Thr 01] *** LOG => Signal 18 SIGCHLD.

F [Thr 01] *** WARNING => process collector (pid 13956) killed (signal 2). [sfuxlib.hpp 832]

F [Thr 01] *** LOG => Process collector stopped (pid 13956).

F [Thr 01] *** LOG => Instance state is "Stopping the processes" (STOPPING @ 0, INACTIVE).

F [Thr 01] *** LOG => Run level 3 completed.

F [Thr 01] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).

F [Thr 01] *** LOG => exiting (exitcode 22002, retcode 1).

Thanks

Senthil

Former Member
‎11-18-2010 3:10 PM
0 Kudos

F Thu Nov 18 09:41:18 2010

F ********************************************************************************

F Java environment properties (/usr/sap/DAA/SMDA97/work/jstart.jvm)

F root directory : /usr/sap/DAA/SMDA97/exe/sapjvm_5

F vendor : SAP AG

F version : 1.5.0_17

F cpu : ia64

F java vm type : server

F java vm version : 5.1.038

F jvm library name : libjvm.so

F library path : /usr/sap/DAA/SMDA97/exe/sapjvm_5/jre/lib/ia64/server:/usr/sap/DAA/SMDA97/exe/sapjvm_5/jre/lib/ia64

F executable path : /usr/sap/DAA/SMDA97/exe/sapjvm_5/bin

F ********************************************************************************

F SAP extensions : available

F ********************************************************************************

I

I [Thr 01] Thu Nov 18 09:42:09 2010

I [Thr 01] MtxInit: 30002 0 2

F

F [Thr 01] Thu Nov 18 09:42:10 2010

F [Thr 01] *** CONFIG => Message Server client disabled.

F [Thr 01] *** CONFIG => Enqueue Server client disabled.

F [Thr 01] *** WARNING => SfCInstanceManager::newState: unknown runMode ''. [sfxxinst.hpp 1159]

F [Thr 01] *** LOG => Starting run level 3.

F [Thr 01] *** WARNING => SfCInstConfig::getInstanceId: cannot identify instance ID. [sfxxcfg.hpp 216]

F ********************************************************************************

F Java process [smdagent] properties:

F section name : smdagent

F config file : /usr/sap/DAA/SMDA97/SMDAgent/smdagent.properties

F node name : SMDAgent

F home directory : .

F shutdown timeout : 20016000 ms

F exit timeout : 7000 ms

F debuggable : true

F debugger active : false

F ********************************************************************************

F [Thr 01] *** LOG => Instance state is "Starting the processes" (STARTING @ 0, INACTIVE).

F [Thr 01] *** LOG => Starting nodes: runlevel 3.

F ********************************************************************************

Former Member
‎11-18-2010 3:13 PM
0 Kudos

I can see three warnings in dev_jstart file as shown above.

F

F [Thr 01] Thu Nov 18 09:42:10 2010

F [Thr 01] *** CONFIG => Message Server client disabled.

F [Thr 01] *** CONFIG => Enqueue Server client disabled.

F [Thr 01] *** WARNING => SfCInstanceManager::newState: unknown runMode ''. [sfxxinst.hpp 1159]

F [Thr 01] *** LOG => Starting run level 3.

F [Thr 01] *** WARNING => SfCInstConfig::getInstanceId: cannot identify instance ID. [sfxxcfg.hpp 216]

F [Thr 01] Thu Nov 18 09:42:40 2010

F [Thr 01] *** WARNING => SfCJavaProcHandler(smdagent)::onTimer: connect from smdagent timed out (30000 ms) - stopping the process. [sfxxproc.hpp 1252]

F [Thr 01] *** LOG => Send SIGINT to SMDAgent (pid 5545).

F [Thr 01] *** LOG => Process smdagent stopping (pid 5545).

F [Thr 01] *** LOG => Signal 18 SIGCHLD.

F [Thr 01] *** WARNING => process SMDAgent (pid 5545) killed (signal 2). [sfuxlib.hpp 832]

F [Thr 01] *** LOG => Process smdagent stopped (pid 5545).

F [Thr 01] *** WARNING => Node smdagent failed: result 1, exit code 2. [sfxxnode.hpp 1016]

F ********************************************************************************

We could not find a solution for the past 2 weeks, also SAP is involved for the past 1 week but no luck.

Regards

Senthil

Former Member
‎11-08-2010 4:04 AM
0 Kudos

Hi,

As per the startup log the process is trying to looking out for the parameter ssl/pse_provider, icm/HTTP/file_access_0 and icm/server_prot_x which is not available in the profile DAA_SMDA97_kgsand2.

please add this parameter in the profile and restart.

Cheers

Vanga Reddy

Show replies
Show replies
Ask a Question