Hi All,

We are facing issues with our soap port in our environment. Below is the error when I try to run the wsadmin script.

replaced actual servername in below error :)

./wsadmin.sh -port 8892
WASX7023E: Error creating "SOAP" connection to host "abc.xyz.com"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Unable to find a valid IP for host abc.xyz.com]
WASX7213I: This scripting client is not connected to a server process; please refer to the log file /profiles/Dmgr01/logs/wsadmin.traceout for additional information.
WASX8011W: AdminTask object is not available.
WASX7029I: For help, enter: "$Help help".

Few observations.

1. Able to start DMGR
2. Able to start Node
3. telnet to soap port getting timedout
4. telnet to RMI port is happening

Its WAS 8.5.5.1 running on Linux.

Kindly let me know your inputs.

Thanks in advance.

Regards, 
Pavan 

Hi Please check the hostname in the wsadmin.properties file under DMGR_HOME/properties.
Confirm that hostname is correct in etc/hosts file and resolves to ip.

Also confirm hostname specified for SOAP port under serverindex.xml for DMGR ie DMGR_HOME/config/cells//nodes//serverindex.xml

Hey,

Checked the DMGR soap port in serverindex.xml and looks good. I am facing the same issue while doing the manual synch from node.

Its not a new setup.. it is happening on the env which is already being up and running.

Regards,
pavan

Hi Pavan,

  As Archie882 have pointed have you reviewed DMGR_HOME/properties/wsadmin.properties file specifically the line

  com.ibm.ws.scripting.host

   The error says "Unable to find a valid IP for host abc.xyz.com]" have you review if the server "abc.xyz.com" can be resolved?

  try doing a nslookup abc.xyz.com (and review /etc/hosts file too) to check if abc.xyz.com can be resolved
 
  Try
 
    wsadmin.sh -conntype SOAP -host IP_DMGR -port 8892

  Hope this helps.  Tell us if you need more support
 
Regards

Hi Gabriel,

I did verify the soap port and also pinged and did a nslookup.. all look good.

we have fixed the issue with some support and eventually the issue was with iptables.

Now the issue is fixed.

Thanks for support.

Regards,
Pavan 

Hi Pavan,

  Good to know that the problem is solved

  You have say in your first question

   3. telnet to soap port getting timedout

    For the next time, with netstat -na you can find if some port is in SYN_SENT that indicates a firewall issue.

  Thanks for sharing the solution.

Regards

Hi Gabriel,

Sure, will make a note of this.. I did do a netstat -an during issue but couldn't align it to firewall.

Thanks,
Pavan