Skip to Content
avatar image
Former Member

'Configure Diagnostics' tries to reach P4-Port of wrong hostname (phys.)...

Hi,

when i execute 'Configure Diagnostics' in the managed systems setup,

i get the following error:

Failed to connect, P4 port=50904 User=j2ee_admin SID=PEP Instance Number=09
Connection error to SAP System sid [PEP/null], more details about the error in agent 'jipep09' log file (SMDAgentApplication.X.log).; nested exception is: 
com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances: 
affha116:50904 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 126.12.38.116 and port: 50904(cause=com.sap.engine.interfaces.cross.DestinationException Cannot establish connection with any of the available instances: 
affha116:50904 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 126.12.38.116 and port: 50904)

The SM tries to reach the physical host, but there is the p4-port locked...

From where does the SM gets this hostname ? It must connect to the virtual host...

In SMSY the virtual host is configured, and the manual added values in the 'Configure Diagnostics' are from the virtual host.

kind regards

Christoph

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

6 Answers

  • avatar image
    Former Member
    Feb 10, 2012 at 11:13 AM

    Hi,

    Please use below command to update the correct solution manager details

    as <smdagent sid> adm

    go to folder

    /usr/sap/<SID>/<Instnace number>/script

    run command

    smdsetup.sh managingconf hostname:"<fqn>" port:"<p4 port>" [optional user:"<value>" pwd:"<value>"

    Regards

    Purna

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 10, 2012 at 11:18 AM

    From where does the SM gets this hostname ? It must connect to the virtual host...

    /usr/sap/<SID>/<System number>/SMDAgent/configuration/runtime.properties

    Regards

    Purna

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 03, 2012 at 06:33 AM

    Unfortunately i have no answer from SAP since 22.02. in my opened ticket 😔 😔 😔 😔 😔

    Very annoying... 😔

    Maybe someone can help me here....!?

    The Wizard still tries to reach the physical host, and i still don't know from where the wizard gets this value...

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Jansi Rani Murugesan

      Hi Jansi,

      there is no SCS in the Agent-Path...

      I've made the smdsetup severall times since the problem occours....No change...

      I will check the hostname resolution of the system now...Maybe there is a missconfiguration...(wrong response !?)

      I've no further idea....

  • avatar image
    Former Member
    Apr 27, 2012 at 08:15 AM

    Still the same problem...

    I have found the following entry in the SMDSystem.0.log:

    Apr 26, 2012 2:22:16 PM [Thread[main,5,main]] Info       InetAddress Resolving for 'jipep09' - FQN: jipep09 SQN: jipep09 IP: xxx.xxx.240.158

    Apr 26, 2012 2:22:16 PM [Thread[main,5,main]] Info       InetAddress Resolving for localhost - FQN: affha116 SQN: affha116 IP: xxx.xxx.38.116

    Looks like the Agent knows the physical adress...

    The problem is, that the diagnostics-wizard don't try the virtual adress...

    It tries the physical adress directly...

    Does the SM remember a failed connection and avert the adress ?

    kind regards

    Christoph

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 08, 2012 at 02:23 AM

    Hi Christoph,

    If you want to make the connection using the message server HTTP port, I don't think there is a solution to the problem.  The SolMan's J2EE message server will reply to the agent with the P4 connection information for a specific app server (e.g. load balancing across several J2EE instances on your SolMan if you have them), and then the agent will attempt to connect to the instance using the P4 protocol.  

    If it's just a name resolution issue, and you really want the agent to connect to an instance using a virtual hostname, then Purnachand's suggested workaround to connect directly to the P4 port (rather than to the message server) should have worked.  You should run smdsetup and provide the virtual hostname and the P4 port.  The connection will not be load-balanced -- the agent will always connect to the instance corresponding to the virtual hostname. This technique requires avoiding the automated connection wizard and using the smdsetup script exclusively (since the automated connection wizard does not yet support direct P4 connections last time I checked).

    You also say "there is the p4-port locked" --- if you mean, firewalls prevent P4 connections regardless of the hostname (physical or virtual), you will need to take a different approach.  Your best bet would be to tunnel your diagnostics agents through a saprouter.  In this case the agents would connect to the saprouter on port 3299, and the saprouter would complete the p4 connection to the physical instance.  As far as I know this is the only supported way for diagnostics agents to traverse a firewall.

    I hope this helps and good luck!

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 25, 2012 at 12:27 PM

    Hello.

    Just to share my experience with this error message. In my case, the problem was not in the P4 port but in the Java Connect Parameters in the setup wizard. I had to enter the SCS instance server name and its message server port to make the setup working. I had the SCS instance running on different physical host then the Java AS.

    Hopefully this helps to anyone.

    Add comment
    10|10000 characters needed characters exceeded