Error while configuring the Introscope Agent within SMD

[Former Member]

Hi,

we are setting up SMD - E2E with our solution manager on SP15.

Everthing seems to be fine, all managed setups ended with success.

Now we want to rollout the introscope agent to the monitored system. Up to now there is only one system in one solution connect via SMD agent. And this is the solman itself.

When we start the introscope agent set up, we get the error:

J2EE Node Settings Rerieval - Remote Operation Failed

Detailed Information - Failed to connect via P4 channel - com.sap.smdagent.plugins.connectors.p4.exceptions.P4ConnectionException: Error to established the p4 connection for sid [SMA]; nested exception is:

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.io.IOException: Can't get Socket. Reason:Connection refused: connect]

What can we do?

Kind regards

Timm

[Former Member]

52004 is the P4 port and this is also the port we have entered

[raguraman_c]

Hi,

your instance number is 20?

P4 Port is 5XX04

XX is instance number.

Feel free to revert back.

--Ragu

[Former Member]

Hi Timm,

I am suffering for the same issue, when running setup wizard in Solution Manager Diagnostics.

My log says:

Failed to connect, P4 port=50004 User=Administrator SID=VD1 Instance Number=null

Error to established the p4 connection for sid [VD1]; nested exception is:

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.io.IOException: Can't get Socket. Reason:Connection refused (errno:239)](cause=com.sap.engine.services.jndi.persistent.exceptions.NamingException Exception while trying to get InitialContext.)

Open/Close Exception stack trace Exceptions

com.sap.smdagent.plugins.connectors.p4.exceptions.P4ConnectionException: Error to established the p4 connection for sid [VD1]; nested exception is:

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.io.IOException: Can't get Socket. Reason:Connection refused (errno:239)]

at com.sap.smd.agent.plugin.connectors.p4.P4ConnectionService.getP4Connection(P4ConnectionService.java:71)

at com.sap.smd.agent.plugins.remotesetup.SetupManager.newP4ctx(SetupManager.java:119)

at com.sap.smd.agent.plugins.remotesetup.RemoteSetupService._setup(RemoteSetupService.java:123)

at com.sap.smd.agent.plugins.remotesetup.RemoteSetupService.setup(RemoteSetupService.java:85)

at com.sap.smd.agent.plugins.remotesetup.RemoteSetupServicep4_Skel.dispatch(RemoteSetupServicep4_Skel.java:112)

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

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

at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)

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

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.io.IOException: Can't get Socket. Reason:Connection refused (errno:239)]

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

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

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

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

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

at com.sap.smd.agent.plugin.connectors.p4.P4ConnectionService.getP4Connection(P4ConnectionService.java:50)

... 8 more

Caused by: java.io.IOException: Can't get Socket. Reason:Connection refused (errno:239)

at com.sap.engine.transport.ClientPortsManager.getRealSocket(ClientPortsManager.java:150)

at com.sap.engine.services.rmi_p4.LoadBalancerImpl.getAllAccessPoints(LoadBalancerImpl.java:76)

at com.sap.engine.interfaces.cross.CrossObjectBroker.getDestination(CrossObjectBroker.java:92)

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

... 13 more

Any idea??

I ve tested connection via Visual admin and P4 port looks like it s working fine.

[raguraman_c]

Post a separate thread, read rules before posting.

Feel free to revert back.

--Ragu

[Former Member]

Hi Ragu,

the P4 Port is entered the right way. Of course I can connect to this port. For example with the Visual Admin tool.

Any more suggestions?

Thank you

[raguraman_c]

Hi,

This is definitely a P4 port problem, what is the port number that you have maintained.

Feel free to revert back.

--Ragu

[Former Member]

Hello

Inorder to suggest you. Please check the following lines in the log:

-

---

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. Root exception is java.io.IOException: Can't get Socket. Reason:Connection refused: connect

-

---

Please paste this log file completely so that we can identifiy the error exactly.

Thanks

Mona

[Former Member]

Any Idea which log file?

the default trace has only one entry after starting the setup:

#1.5 #00110A5B40BE005A00000025000016C0000452861D21DC75#1216635874691#com.sap.sup.admin.audit.smdnavigation.smdnavigation#sap.com/tc_wddispwda#com.sap.sup.admin.audit.smdnavigation.smdnavigation#V580351#337##lddst101_SMA_207975050#V580351#30f4f9f0570f11dd9c7c00110a5b40be#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#/Applications/AdminConsole/Audit/SmdNavigation/SmdNavigation#Plain#Starting Introscope Agent###

no entry in the application log concerning the setup.

Kind regards

Timm

[raguraman_c]

Hi,

I would suggest you to add one satellite system apart from solman.

Coming to your P4 Port problem, go to

http://<hostname>:<port>/sld

click on Technical System, select java systems --> click on your solman system.

Select the instances TAB below systems. In that expand your instance node --> Expand dispatcher node...

here you will find P4 Port. Check if you are entering the same port while running SMD Wizard.

This will solve your problem.

Feel free to revert back.

--Ragu