Diagnostic Agents not connected after restart

[Private_Member_19084]

Hi experts,

I have a problem.

We have around 12 managed systems which had been connected (DAA was connected) to the solution manager.

And now, after a restart of the solution manager, I'am not able to connect the DAAs again to the solution manager.

What can I do?
I tried already to reconnect via solman_setup - but it is not working.

What may be the problem for this?

Thank you

[Reagan · Accepted solution]

Is the agent up and running ?

What does the trace logs in the work directory say ?

Regards

RB

[Private_Member_19084 · Accepted solution]

Hi RB,

yes agent is running.

There are the entires which I have at diagnostic agents of solman:

Jan 13, 2014 12:08:00 PM [Thread[Connector,5,main]] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)

Jan 13, 2014 12:08:00 PM [Thread[Connector,5,main]] Info       [SMDConnector.resetBroker] p4 broker closed.

Jan 13, 2014 12:08:00 PM [Thread[Connector,5,main]] Info       Local P4 port opened on port '59704'.

Jan 13, 2014 12:08:00 PM [Thread[Connector,5,main]] Info       Local P4 server configured with transport layer 'None'.

Jan 13, 2014 12:08:00 PM [Thread[Connector,5,main]] Info       [SMDConnector.resetBroker] p4 broker initialized.

Jan 13, 2014 12:08:00 PM [Thread[Connector,5,main]] Info       [p4://localhost:53004] Checking server availability...

Jan 13, 2014 12:08:00 PM [Thread[Connector,5,main]] Warning    Connecting to SMD server p4://localhost:53004 failed - error counter: 2359 - com.sap.engine.services.jndi.persistent.exceptions.NamingExc

eption: Exception while trying to get InitialContext. [Root exception i

And in managed systems I have this entries:

Jan 13, 2014 2:14:36 PM [Thread[Connector,5,main]] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Jan 13, 2014 2:14:36 PM [Thread[Connector,5,main]] Info       [SMDConnector.resetBroker] p4 broker closed.
Jan 13, 2014 2:14:36 PM [Thread[Connector,5,main]] Info       Local P4 port opened on port '59704'.
Jan 13, 2014 2:14:36 PM [Thread[Connector,5,main]] Info       Local P4 server configured with transport layer 'None'.
Jan 13, 2014 2:14:37 PM [Thread[Connector,5,main]] Info       [SMDConnector.resetBroker] p4 broker initialized.
Jan 13, 2014 2:14:37 PM [Thread[Connector,5,main]] Info       Solution Manager Java stack is not ready, the SLD registration entering in waiting mode until the SMD server is available.
Jan 13, 2014 2:14:37 PM [Thread[Connector,5,main]] Info       [p4://<servername>:53004] Checking server availability...
Jan 13, 2014 2:14:37 PM [Thread[Connector,5,main]] Warning    Connecting to SMD server p4://<servername>:53004 failed - error counter: 2579 - com.sap.engine.services.jndi.persistent.exceptions.NamingExcepti
on: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.jndi.persistent.exceptions.SecurityException: Cannot get InitialContext, operation is not allowed.]

[Private_Member_19084 · Accepted solution]

ok, one thing...

In solman_setup I have the status pending which says "connection type MS" to every managed system/DAA.

But in past I did connect via P4 port.

How can I change back to p4 port?

Kind regards

[Reagan · Accepted solution]

Hello Christian

The problem looks like the connection to the Solman system.

To connect using the P4 port please check this wiki

Diagnostics Agents - SAP Solution Manager Setup - SCN Wiki

Here is an example command.

su - daaadm

./smdsetup.sh managingconf hostname:"SOLMAN.FQDN" port:"50004" user:"SMD_ADMIN" pwd:"Password"

Regards

RB

[Private_Member_19084 · Accepted solution]

Hello RB,

I did this already and did also restart the DAA.

But it don't works and in solman_setup it still writes connection type MS.

I did execute the following commands.

smdsetup.sh sldconf hostname:"<fqn>" port:"5<instance number>00" user:"slddsuser" pwd:"****"

smdsetup.sh managingconf hostname:"<fqn>" port:"5<instance number>04" user:"smd_admin" pwd:"****"

[Reagan · Accepted solution]

Hello Christian

Could you check this SAP KBA ?

1903291 - Unable to connect to Diagnostic Agent to Solution Manager 7.10 with error "com.sap.engine...

Regards

RB

[Private_Member_19084 · Accepted solution]

One further thing I did see now.

I get also the message:

" Solution Manager Java stack is not ready"

How to check the java stack for this?
Because for me it seems, like every thing is running from java stack on solman.

[Reagan · Accepted solution]

Check whether you are able to access http://SOLMAN.FQDN:5NN00/nwa

Regards

RB

[Private_Member_19084 · Accepted solution]

Yes I can access this url.

But I guess, when I click on restart, this will restart also the abap-stack, right?

[Former Member · Accepted solution]

Check steps as per SAP KBA 1963017 - Diagnostics Agent fails to connect to Solution Manager system due to "SecurityException: C....

[Private_Member_19084 · Accepted solution]

so, the solution from RB was correct.

Open the url http://<servername of solman>:5<instance number>00

Next click on SAP Netweaver Administration->Administration->Systems and restart the JAVA processes.

[Private_Member_19084]

Also one important thing I think is, that we did update the DAA of solution manager.

I hope someone have a solution for this.