cancel
Showing results for 
Search instead for 
Did you mean: 

SMD 7.20 agent stuck in "starting the process" status after installation

Former Member
0 Kudos

I installed Diagnostics Agent  7.20 on ECC 6.0 ABAP stack.But after the installation the DAA agent is still in status “Starting the Process”.

I found that there is not dev_smdagent  file in work directory and missing of log and applications directories (/usr/sap/DAA/SMDA97/SMDAgent).

Also tried to unistall and install but still having the same issue.

Has anyone of you faced this kind of issue? Awaiting  your valuable repsonse.

dev_jstart :

F Wed Jul 11 15:40:22 2012

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

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

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

F    vendor            : SAP AG

F    version           : 1.6.0_07

F    cpu               : ppc64

F    java vm type      :

F    java vm version   : 6.1.008

F    jvm library name  : libjvm.so

F    library path      : /usr/sap/DAA/SMDA97/exe/sapjvm_6/jre/lib/ppc64/server:/usr/sap/DAA/SMDA97/exe/sapjvm_6/jre/lib/ppc64:/usr/sap/DAA/SMDA97/exe/sapjvm_

6/jre/../lib/ppc64:/usr/sap/DAA/SMDA97/exe/sapjvm_6/jre/lib/ppc64/jli:/usr/sap/DAA/SMDA97/exe/sapjvm_6/jre/../lib/ppc64/jli:/usr/sap/DAA/SMDA97/exe:/usr/sap/

DAA/SMDA97/exe:/usr/sap/DAA/SYS/exe/run:/usr/sap/DAA/SYS/exe/uc/rs6000_64:/lib:/usr/lib

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

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

F    SAP extensions    : available

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

I  [Thr 01] MtxInit: 30002 0 2

M  [Thr 01] ***LOG Q0I=> NiIBindSocket: could not delete file '/tmp/.sapstream64999' for hdl 18: unlink (1: Not owner) [nixxi.cpp 3720]

M  [Thr 01] *** ERROR => NiIBindSocket: could not delete file '/tmp/.sapstream64999' (hdl 18; errno=1) [nixxi.cpp    3725]

M  [Thr 01] *** WARNING => NiIBind: Could not bind local domain socket, only listening on internet socket [nixxi.cpp    4072]

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

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

F  [Thr 01] *** WARNING => SfCConfig::parseFile: cannot open file '/usr/sap/DAA/SMDA97/j2ee/cluster/instance.properties' for input. [sfxxlib.hpp  3189]

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

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

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

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

F  ICM process [icm] properties:

F    section name     : icm

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

F    node name        : ICM

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

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

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

F  [Thr 01] *** LOG => Waiting for ICM (pid 0) to connect.

Thanks in Advance

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

from my experience, please deinstall "SMD 7.20" and afterward install new SMD at least Version 7.30 or 7.31

This is working with SolMan 7.01 as well with SolMan 7.1

(By the way, you are using Java version 6 which is not suitable for 7.20)

Message was edited by: Walter Huber

former_member182675
Contributor
0 Kudos

HI

Try to install the new DAA Agent

its need to work

install with administrator user

Naor

Former Member
0 Kudos

Hi,

I have installed a stanadlone diagnostics agent against the solution manager in my landscape, Now the bottleneck is that I cannot interpret how to analyze the scripts on GUI for EEM. any document or guide will be helpful.

Regards,

Ankit

Former Member
0 Kudos

as the DAA is running, you need to integrate this agent to SolMan and the related System where the agent is residing on (in that special System Landscape)

If this is done, you can see the: Load Memory CPU Users and many more with WILY Introscope in improved details with EWA.

Former Member

Sorry for the delayed response.

I had raised a message with SAP on this issue and they provided the folllowing solution which worked for me.

1) Edit the profile
/usr/sap/DAA/SYS/profile/DAA_SMDA97_<hostname>
2) Check/Add the following lines:

SAPGLOBALHOST=<globalhost>
smd/agent/type=710
jstartup/instance_properties=$(DIR_INSTANCE)/SMDAgent/smdagent.
properties

Please also ensure that the OS user has read, write and execute
permissions on the SMDAgent path /usr/sap/SMD.

3) Start the SMDAgent.

Former Member
0 Kudos

What userid is the agent running under?  Was it started under another id?

Todd

Former Member
0 Kudos

Todd,

  Agent is running under daaadm user.Installation was done with root user. After the installation,smd agent was in yellow status.I tried to restart with daaadm user but still it is stuck in "starting the process".

Former Member
0 Kudos

I think that is most likely your issue...this entry in the log indicates that it can't properly initialize itself since the socket is "owned" by another id.

M  [Thr 01] ***LOG Q0I=> NiIBindSocket: could not delete file '/tmp/.sapstream64999' for hdl 18: unlink (1: Not owner) [nixxi.cpp 3720]

M  [Thr 01] *** ERROR => NiIBindSocket: could not delete file '/tmp/.sapstream64999' (hdl 18; errno=1) [nixxi.cpp    3725]

Are all the diagnostics executables and directories owned by root?  I would say having those changed to the daaadm account and then starting as that user will correct the issue. Perhaps you'll need to start and stop the agent as root to clean up all of the sockets as well.

former_member209924
Contributor
0 Kudos

Can you please explain your installation steps for SMD.

Is your host running low on memory, swap?

Ravi

Former Member
0 Kudos

Ravi,

I followed 7.20 Diagnostic installation guide.

1.Downloaded standalone Diagnostic agent 7.20 & SAP NetWeaver Composition Environment (CE) 7.2

2.set JCE_POLICY_ZIP variable

3.set ulimits

4.Provided SAP unicode Kernel 720 file

5.Input Diagnostic agent parameters.

Memory and swap space are fine in the host.

former_member209924
Contributor
0 Kudos

I see.

Did you register the Agent in the SLD and also, did you use P4 connection to Solution Manager.

I would also check to see if Port 5XX00 is open for DAA instance.

Please refer to the helpful links below.

SAP Note - 716604

SCN Link - http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents

Troubleshoot Guide - https://service.sap.com/~sapidb/002007974700000409092009E/DiagAgent_TroubleShooting.pdf

When I did this on Windows, it would not start because of low RAM/Pagefile size.  I had to increase the RAM for the Agent to start.  But in your case that shouldn't be a problem.

Ravi