Diagnostics agent 7.4 not working

[Former Member]

Hi Friends

I have an issue with the connectivity between Diagnostic agent installed on Satellite system and Solman 7.1.

I have installed diagnnostics agent prior to the installation of SAP System and it was successful, but I was dont have the password of SMD AGT password of solman server so I have to manually push the credentials from Solman system , but when I check under the agent framework for my ABAP system in solman_workcenter the respective agent is offline and unable to restart it and also my Diagnostic agent instance does not appear under the Non authenticated agents for me to push the credentials.

Please guide, std_smdagent.out shows the following error, unable to understand what the issue is here can someone help me resolve it..

6684]  23:34:34    ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264

   :    [6684]  23:35:12    ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264

   :    [6684]  23:35:49    ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264

   :    [6684]  23:36:26    ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264

   :    [6684]  23:37:04    ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264

   :    [6684]  23:37:41    ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264

   :    [6684]  23:38:19    ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264

   :    [6684]  23:38:56    ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264

Thanks in advance

[divyanshu_srivastava3 · Accepted solution]

Pick any one system and Goto script folder under diagnostic agent folder.

As daaadm (diagnostic agent user) run script:

smdsetup managingconf  hostname:"sapms://servername" port:"81xx" user:"SMD_USER" pwd:"xxxxxxx"

Refer  Diagnostics Agents - SAP Solution Manager Setup - SCN Wiki

Once connected share results

[Former Member · Accepted solution]

Thanks for your response.

I tried it and the script result execution was successful still the agent appears to be offline and I am unable to restart the agent from Solman Agent framework/or find the Diag agent instance under non authenticated agents.

SAP Solution Manager - Diagnostics Agent  - Copyright (c) 2012 SAP AG

_________________________________________________________________________

------- VM Properties ----------
OS                            : AIX
OS Version                    : 6.1
OS Architecture               : ppc64
OS data model                 : 64
Java Vendor                   : SAP AG
Java Home                     : /usr/sap/DAA/SMDA92/exe/sapjvm_6/jre
Java Version                  : 1.6.0_65
Java Classpath                : .:lib/patch_7.10.8.0.20131127234252/launcher/smd
agentlauncher.jar:lib/patch_7.10.8.0.20131127234252/sapxmltoolkit.jar:lib/patch_
7.10.8.0.20131127234252/smdagent.jar:lib/patch_7.10.8.0.20131127234252/tc_sec_se
cstorefs.jar:lib/patch_7.10.8.0.20131127234252/iaik_jce_export.jar:lib/patch_7.1
0.8.0.20131127234252/smdserver.jar:lib/patch_7.10.8.0.20131127234252/logging.jar
:lib/patch_7.10.8.0.20131127234252/exception.jar:lib/patch_7.10.8.0.201311272342
52/sldclient.jar:lib/patch_7.10.8.0.20131127234252/sldserv.jar:lib/patch_7.10.8.
0.20131127234252/jARM.jar:lib/patch_7.10.8.0.20131127234252/httpclient.jar:lib/p
atch_7.10.8.0.20131127234252/sapj2eeclient.jar:
Java Runtime version          : 6.1.059
Java Specfic. version         : 1.6
File Encoding                 : ISO8859-1
Console Encoding              : null
HTTP Proxy                    : null
HTTP Proxy port               : null
HTTP non Proxy hosts          : null

smd class version:            : 7.10.8.0.20131127231804
--------------------------------

Check Prerequisites:
OK.

[-] Diagnostics agent maintenance setup starting ...
----------------------------------------------------

Execute the action 'managingconf' to update connection information to connect to
Managing system.

File configuration/runtime.properties generated.
STEP  - Agent secstore file generated.

Task completed with status SUCCESS (0)

[divyanshu_srivastava3 · Accepted solution]

How did you registered the agents 1st time.

Please zip and upload agents connection logs.

[Former Member · Accepted solution]

I registered the agent first time during the installation it was succesful, but as mentioned I dont have the SMD AGENT password so unable to update during installation.

So I tried to run manually to register the return code is 0 but desired output is not generated.

What logs you mean? dev_smdagent & std_smdagent.out?

[divyanshu_srivastava3 · Accepted solution]

What was the method ?

On sld or direct on solman ?

You can you anyother user with desired authorization or reset the user from solman or remove the agent completely and re register on solman directly.

Yes the smdagent and agent connection logs.

Regards

[Former Member · Accepted solution]

Thanks for the response. Direct connection to Solman using the below method.

smdsetup managingconf

hostname:"sapms://<fqn>" port:"<MS HTTP port>"

[optional user:"<value>" pwd:"<value>" servername:"<value>"]

Okay I have not tried that I will try it.

dev_smdagent.txt.zip

std_smdagent.out.txt.zip

[divyanshu_srivastava3 · Accepted solution]

You 1st stop the agent

then register it and then restart the agent.

Run smdagent supportlogs - zip and upload it.

Also make sure the ports are open between solman and your manages system.

[Former Member · Accepted solution]

Thanks. Issue resolved after running the smdsetup script with user parameter and pasword.