cancel
Showing results for 
Search instead for 
Did you mean: 

Diagnostic agent not starting

Former Member
0 Kudos

Hi all ,

We are trying to register the diagnostic agent to our solman system and after executing the command ./smdsetup.sh managingconf hostname:"sapms://<solman host name" port:"81xx" user:"<admin user of diagnostic agent>" pwd:"******"

the diagnostic agent went offline.

We tried bringing it up by startsap SMDA98 , since we are at higher version we dont have smdstart command.

kindly let me know how can i bring SMD agent online.

Thanks,

Gaurav

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Divyanshu,

I have one doubt :

why its connecting to P4 when it has to be ms?

Establishing P4 connection to server 'ms:///<solman host>:81xx/P4


in the above logs.


Regards,

Gaurav

divyanshu_srivastava3
Active Contributor
0 Kudos

Connecting to SMD server ms:///<solman host>:81xx/P4 failed

[EXCEPTION]

com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exc

You can see, the above was the issue.

Now, the connection is getting failed.

Check the P4 port

http://msgserver:81xx/msgserver/text/logon

Do telnet and check the port is open.

Also check user and password are correct.

If this is not working.

Then use below to register agent to solman.

smdsetup managingconf hostname:"<fqn>" port:"<p4 port>" user:"<value>" pwd:"<value>"

Regards,

Divyanshu

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Gaurav,

There are two possible connections to solman:

  • Connection through the Solution Manager Java Message server.
  • Direct connection to Solution Manager Java P4 dispatcher.

In both cases, P4 port is used for final connection.

In your case, 1st the call goes to SCS, then j2ee entry ports, then P4 is selected and then connected.

Have a look at http://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents

Regards,

Divyanshu

divyanshu_srivastava3
Active Contributor
0 Kudos

Any update ?

Former Member
0 Kudos

Hi Divyanshu,

Followed your steps.

gave this command:

smdsetup managingconf hostname:"<fqn>" port:"<p4 port>" user:"<value>" pwd:"<value>"


this time i could find logs written, nither the agent has come up.

If i am not worng is this user for login into solman at telnet port.

At OS level of solman telnet command is working

How can i check for the credentials of the users .

I can login to my solman system OS level through the user daaadm and i am using that credentials here.


Regards,

Gaurav

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Gaurav,

You have to give solution manager user. This is generally SMD_ADMIN created in system preparation from solman_setup. You can also check with J2ee_admin(just for check)

For eg.

If your solman hostname is - xyv.domain.com

SCS instance number is 01

User - SMD_ADMIN

Password - 123456

then the script would be


smdsetup managingconf hostname:"xyv.domain.com" port:"8101" user:"SMD_ADMIN" pwd:"123456"


and also try this.

smdsetup managingconf hostname:"sapms://xyv.domain.com" port:"8101" user:"SMD_ADMIN" pwd:"123456"

Make sure your host file is updated with solman hostname and FQDN.

Regards,

Divyanshu

Former Member
0 Kudos

Hi Divyanshu,

Finally Diagnostic agent is running now.

I just restarted the agent after giving smdsetup managingconf hostname:"<fqn>" port:"<p4 port>" user:"<value>" pwd:"<value>" command

still error in connecting to solman :

Failed to connect to SMD server - user: j2ee_admin

Jul 25, 2014 10:17:08 PM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server p4://<hostname>:81xx failed - error cou

nter: 18 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interface

s.cross.DestinationException: Cannot establish connection with any of the available instances:

<hostname>:81xx Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: <ip address> and port: 81xx]

Thanks,

Gaurav.

divyanshu_srivastava3
Active Contributor
0 Kudos

.DestinationException: Cannot establish connection with any of the available instances:

<hostname>:81xx Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: <ip address> and port: 81xx]

So, now if you see this, there is a connection issue with this port.

Check with for P4 for, the value should come

http://msgserver:81xx/msgserver/text/logon.

Try to ping and do telnet to solman 81xx

Refer a similar thread

Regards,

Divyanshu

divyanshu_srivastava3
Active Contributor
0 Kudos

Also, try the other MS connection.

Check ports are opens

Former Member
0 Kudos

Hi Divyanshu,

I think its fine now.As per logs

[p4://<solman fqn>:500xx] Registration done.

Jul 25, 2014 10:38:47 PM [Thread[Connector,5,main]                     ] Info       [p4://<solman fqn>:500xx] Agent ready.

Jul 25, 2014 10:38:47 PM [Thread[Thread-6,5,main]                      ] Info       Found application : 'com.sap.smd.agent.application.wily4java' in folder 'com.sap.smd

.agent.application.wily4java_8.2.4.0.20120626135042'.

Jul 25, 2014 10:38:47 PM [Thread[Thread-6,5,main]                      ] Info       Found application : 'com.sap.smd.agent.application.e2edcc' in folder 'com.sap.smd.ag

ent.application.e2edcc_7.10.8.6.20140218052400'.

Jul 25, 2014 10:38:47 PM [Thread[Thread-6,5,main]                      ] Info       Found application : 'com.sap.smd.agent.application.database' in folder 'com.sap.smd.

agent.application.database_7.10.8.6.20140218052400'.

Jul 25, 2014 10:38:47 PM [Thread[Thread-6,5,main]                      ] Info       Found application : 'com.sap.smd.agent.application.e2emai.bobj' in folder 'com.sap.s

md.agent.application.e2emai.bobj_7.10.8.6.20140218052400'.

Jul 25, 2014 10:38:51 PM [Thread[Thread-6,5,main]                      ] Info       Create an Execution Manager agelet_WilyEM @ 1635668937

Jul 25, 2014 10:38:51 PM [Thread[Thread-6,5,main]                      ] Info       [WHS] Initializing Wily Handler Service

Jul 25, 2014 10:38:51 PM [Thread[Thread-6,5,main]                      ] Info       Create an Execution Manager dpc:job @ 1178041898

Jul 25, 2014 10:38:51 PM [Thread[Thread-6,5,main]                      ] Info       Create an Execution Manager selfd:filter @ 583242657

Jul 25, 2014 10:38:51 PM [Thread[Thread-6,5,main]                      ] Info       Create an Execution Manager OutsideDiscovery @ 1475697838

Jul 25, 2014 10:38:52 PM [Thread[Thread-6,5,main]                      ] Info       Create an Execution Manager com.sap.maimgr @ 1198376393

Jul 25, 2014 10:38:52 PM [Thread[Thread-6,5,main]                      ] Info       Create an Execution Manager e2emai:jobmgr @ 966542180

Jul 25, 2014 10:38:52 PM [Thread[Thread-6,5,main]                      ] Info       Initialization done.

Jul 25, 2014 10:38:52 PM [Thread[Thread-6,5,main]                      ] Info       Service provider initialized.

Jul 25, 2014 10:38:52 PM [Thread[Thread-6,5,main]                      ] Info       [AgentContext.startApplications] Agent Applications started.

Jul 25, 2014 10:39:09 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideD...] Info       Reading JStartup environment...

Jul 25, 2014 10:39:09 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideD...] Info       'SAPLOCALHOST' found, The value '<managed system hostname>' will be used to determine the Agent name.

Jul 25, 2014 10:39:09 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideD...] Info       InetAddress Resolving for '<managed system hostname>' - FQN: <managed system fqn> SQN: <managed system hostname> I

P: 155.66.173.104

Jul 25, 2014 10:39:09 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideD...] Info       InetAddress Resolving for localhost - FQN: <solman hostname> SQN: <solman hostname> IP: <solman ip>

I gave the command with telnet port instead of mshttp port.

Thanks a lot

Gaurav.

divyanshu_srivastava3
Active Contributor
0 Kudos

Welcome

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Divyanshu,

1) i tried connecting to sld by command as above but  missed ":" between sapms and //

2) when i saw the logs it showed error

3) i corrected the command and agent went unavailable.

Regards,

Gaurav

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Gaurav,

You don;t have to do like this.

1st. give - stopsap SMDA98

2st, kill all processes running under DAAADM

3rd. startsap SMDA98.

./smdsetup.sh managingconf hostname:"sapms://<solman host name" port:"81xx" user:"<admin user of diagnostic agent>" pwd:"******"

The above command is registering on MS of solman.

Share the logs in agent work and log directory if it's not coming up.

Regards,

Divyanshu

Former Member
0 Kudos

Hi Divyanshu,

I stopped SMDA98 killed the processes under daaadm

while stating it failed:

startsap SMDA98

Starting Startup Agent sapstartsrv

FAIL: Timeout

Startup of Instance Service failed

See /users/p80adm/startsap_SMDA98.log for details

-------------------------------------------

19:24:39

Starting Startup Agent sapstartsrv

-------------------------------------------

19:26:41

Startup of Instance Service failed

-------------------------------------------

Regards,

Gaurav

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Gaurav,

I was not asking for start stop logs.

Please goto /usr/sap/DAA/ directory and share logs from work directory and log directory.

Divyanshu

divyanshu_srivastava3
Active Contributor
0 Kudos

If I am not wrong, you have not started agent from daaadm this time.

Former Member
0 Kudos

Hello Divyanshu,

I was trying with daaadm , now it came up but the diagnostic agent is still unavailabe.

log from dev_jstart

Process collector started with pid 14962

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

F  [Thr 140255350110048] *** LOG => Process flightrec started (pid 14962).

F

F [Thr 140255350110048] Fri Jul 25 20:35:23 2014

F  [Thr 140255350110048] *** LOG => Signal 17 SIGCHLD.

F  [Thr 140255350110048] *** WARNING => process collector (pid 14962) exited (exit code 2). [sfuxlib.hpp  831]

F  [Thr 140255350110048] *** LOG => Process flightrec stopped (pid 14962).

log from SMDSystem.0.log:

Jul 25, 2014 8:35:14 PM [Thread[main,5,main]                          ] Info       _______ Starting SMDAgent ..._______

Jul 25, 2014 8:35:17 PM [Thread[main,5,main]                          ] Info       Agent path: /usr/sap/DAA/SMDA98/SMDAgent

Jul 25, 2014 8:35:17 PM [Thread[main,5,main]                          ] Info       Agelets path: /usr/sap/DAA/SMDA98/SMDAgent/applications

Jul 25, 2014 8:35:17 PM [Thread[main,5,main]                          ] Info       Agelets configuration path: /usr/sap/DAA/SMDA98/SMDAgent/applications.config

Jul 25, 2014 8:35:17 PM [Thread[main,5,main]                          ] Info       Create an Execution Manager default @ 59584763

Jul 25, 2014 8:35:17 PM [Thread[main,5,main]                          ] Info       SLD configuration not found to register the agent, SLD Agent Registration is skipped.

Jul 25, 2014 8:35:17 PM [Thread[main,5,main]                          ] Info       Reading JStartup environment...

Jul 25, 2014 8:35:17 PM [Thread[main,5,main]                          ] Info       'SAPLOCALHOST' found, The value '<hostname>' will be used to determine the Agent name.

Jul 25, 2014 8:35:17 PM [Thread[main,5,main]                          ] Info       InetAddress Resolving for '<hostname>' - FQN: <managed system host> SQN: p8000 IP

: 155.66.173.104

Jul 25, 2014 8:35:17 PM [Thread[main,5,main]                          ] Info       InetAddress Resolving for localhost - FQN: <managed system hostname> SQN: gva6

704 IP: 155.66.173.103

Jul 25, 2014 8:35:17 PM [Thread[main,5,main]                          ] Info       [SMDAgent.locateSolManServer]===> Establishing P4 connection to server 'ms:///<solman host>:81xx/P4

Jul 25, 2014 8:35:18 PM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)

Jul 25, 2014 8:35:18 PM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59804'.

Jul 25, 2014 8:35:18 PM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.

Jul 25, 2014 8:35:18 PM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.age

nt.AgentHandle@62114b17) is available in P4 Object Broker.

Jul 25, 2014 8:35:18 PM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.

Jul 25, 2014 8:35:18 PM [Thread[Connector,5,main]                     ] Info       [ms://<solman host>:81xx/P4] Checking server availability...

Jul 25, 2014 8:35:18 PM [Thread[Connector,5,main]                     ] Info       [ms://v/P4] Authentication in progress ... (method:

yes)

Jul 25, 2014 8:35:18 PM [Thread[Connector,5,main]                     ] Error      Failed to connect to SMD server - user: daaadm

Jul 25, 2014 8:35:18 PM [Thread[Connector,5,main]                     ] Error      Connecting to SMD server ms:///<solman host>:81xx/P4 failed

[EXCEPTION]

com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. [Root exc

eption is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]

        at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleUserProblem(InitialContextFactoryImpl.java:512)

        at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:366)

        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)

        at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)

        at javax.naming.InitialContext.init(InitialContext.java:223)

        at javax.naming.InitialContext.<init>(InitialContext.java:197)

        at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.getNewSMDInitialContext(SMDConnector.java:415)

        at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.internalAttemptConnection(SMDConnector.java:565)

        at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.attemptConnection(SMDConnector.java:95)

        at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.run(SMDConnector.java:1097)

        at java.lang.Thread.run(Thread.java:722)

Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.

        at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:178)

        at java.security.AccessController.doPrivileged(Native Method)

        at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:187)

        at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:72)

        at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_Skel.java:64)

        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)

        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)

        at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)

        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:104)

        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.

        at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:175)

        ... 13 more

Jul 25, 2014 8:35:19 PM [Thread[Connector,5,main]                     ] Info       [AgentAppStartupManager.offlineStartAppsIfNeeded] start agent applications.

Jul 25, 2014 8:35:19 PM [Thread[Connector,5,main]                     ] Warning    Encryption will be disabled because property smd.server.encryption.definition was not

found on the server

Jul 25, 2014 8:35:19 PM [Thread[Connector,5,main]                     ] Info       [AgentContext.startApplications] Starting Agent Applications...

Jul 25, 2014 8:35:19 PM [Thread[Connector,5,main]                     ] Info       Found application : 'com.sap.smd.agent.application.runtime' in folder 'com.sap.smd.ag

ent.application.runtime_7.10.1.0.20110706111553'.

Jul 25, 2014 8:35:22 PM [Thread[Connector,5,main]                     ] Info       SMD Patch Installer: Nothing to do ... already patched at: /usr/sap/DAA/SMDA98/SMDAge

nt/lib/patch_7.10.1.0.20110706111553

Jul 25, 2014 8:35:22 PM [Thread[Connector,5,main]                     ] Info       Initialization done.

Jul 25, 2014 8:35:22 PM [Thread[Connector,5,main]                     ] Info       Service provider initialized.

Jul 25, 2014 8:35:22 PM [Thread[Connector,5,main]                     ] Info       [AgentContext.startApplications] Agent Applications started.

Jul 25, 2014 8:35:22 PM [Thread[SMDAgentShutdownHook,5,main]          ] Info       [ShutdownHook.run] hook received ...

Jul 25, 2014 8:35:22 PM [Thread[SMDAgentShutdownHook,5,main]          ] Info       [ShutdownHook.run] Shutting down SMDAgent ...

Jul 25, 2014 8:35:22 PM [Thread[SMDAgentShutdownHook,5,main]          ] Info       Execution manager shutdown

Jul 25, 2014 8:35:22 PM [Thread[SMDAgentShutdownHook,5,main]          ] Info       the thread group default is already closed.

Jul 25, 2014 8:35:22 PM [Thread[SMDAgentShutdownHook,5,main]          ] Info       [AgentContext.stopApplications] Stopping Agent applications ...

Jul 25, 2014 8:35:22 PM [Thread[SMDAgentShutdownHook,5,main]          ] Info       [AgentContext.stopApplications] Agent Applications stopped.

Jul 25, 2014 8:35:22 PM [Thread[SMDAgentShutdownHook,5,main]          ] Info       [SMDAgent.shutdown] SMDAgent is shut down.

Regards,

Gaurav

divyanshu_srivastava3
Active Contributor
0 Kudos

switchto user daaadm

give command startsap SMDA98

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Gaurav,

In short, you have to goto DAAADM user env i.e. diag agent admin and give startsap command.

If even after giving it's not working, then share the logs.

Cheers,

Divyanshu

Former Member
0 Kudos

Hello Divyanshu,

I already tried that command

daaadm 213> ps -ef|grep daa

daaadm     449     1  0 17:02 ?        00:00:00 /usr/sap/DAA/SMDA98/exe/sapstartsrv pf=/usr/sap/DAA/SYS/profile/DAA_SMDA98_p8000.2 -D

daaadm    4136  6852  0 18:02 ?        00:00:00 sapstart pf=/usr/sap/DAA/SYS/profile/DAA_SMDA98_p8000

daaadm    4570 27222  0 18:03 pts/0    00:00:00 ps -ef

daaadm    4571 27222  0 18:03 pts/0    00:00:00 grep daa

daaadm    6852     1  0 May14 ?        00:01:36 /usr/sap/DAA/SMDA98/exe/sapstartsrv pf=/usr/sap/DAA/SYS/profile/DAA_SMDA98_p8000 -D -u daaadm

daaadm    6986     1  0 May14 ?        00:00:00 sapstart pf=/usr/sap/DAA/SYS/profile/DAA_SMDA98_p8000

daaadm    7170  6986  0 May14 ?        00:00:01 jc.sapDAA_SMDA98 pf=/usr/sap/DAA/SYS/profile/DAA_SMDA98_p8000

root     27216 26618  0 16:05 pts/0    00:00:00 su - daaadm

daaadm   27222 27216  0 16:05 pts/0    00:00:00 -csh

the logs are:

-------------------------------------------

18:02:28

Starting Startup Agent sapstartsrv

-------------------------------------------

18:02:29

Instance Service on host ***** started

-------------------------------------------

18:02:29

starting SAP Instance SMDA98

-------------------------------------------

18:02:29

Startup-Log is written to /users/daaadm/startsap_SMDA98.log

-------------------------------------------

18:02:29

/usr/sap/DAA/SMDA98/exe/sapcontrol -prot NI_HTTP -nr 98 -function Start

25.07.2014 18:02:29

Start

OK