thanks Sharon, got it working.
~Praveen. On Mon, Nov 8, 2010 at 9:51 PM, Sharon Lucas <luc...@us.ibm.com> wrote: > > Make sure that a regular "ping" to the IP address works. e.g. > ping 192.168.126.128 > > If a regular ping (one that doesn't use STAF) fails, then there's a problem > in your TCP/IP configuration. If a regular ping doesn't work, then of > course a STAF ping will also fail. > > If a regular "ping" to the IP address works, then another common cause for > RC 16 on Linux machines is talked about in section "3.1.5 Why aren't my > entries in /etc/hosts being using for STAF communication" in the STAF FAQ > at http://staf.sourceforge.net/current/STAFFAQ.htm#d0e1086. It says: > > 3.1.5 Why aren't my entries in /etc/hosts being used for STAF communication > (particularly on Linux SLES)? > > > On Linux, if you are using /etc/hosts to specify hostnames/IPs, and a > regular "ping" to the hostname works, but a STAF ping fails with RC 16, it > is likely that your /etc/hosts file is not being used. > > > Ensure that your /etc/host.conf file looks contains > > > order hosts, bind > > > Also verify that the /etc/nsswitch.conf file contains: > > > hosts: files dns > > -------------------------------------------------------------- > Sharon Lucas > IBM Austin, luc...@us.ibm.com > (512) 286-7313 or Tieline 363-7313 > > ----- Forwarded by Sharon Lucas/Austin/IBM on 11/08/2010 10:15 AM ----- > > From: Sharon Lucas/Austin/IBM > To: praveen b <praveenkumar...@gmail.com> > Cc: staf-users@lists.sourceforge.net > Date: 11/08/2010 10:10 AM > Subject: Re: [staf-users] Run STAF remotely > > > There are several possible causes for RC 16. You can get help for RC 16 > (or any STAF error code as follows): > > # STAF local HELP ERROR 16 > Response > -------- > Description: No path to endpoint > Details : This indicates that STAFProc was not able to submit the > request > to the requested endpoint (i.e. target machine). This error usually > indicates one or more of the following: > > 1. STAFProc is not running on the target machine. > 2. The requested endpoint is not valid. > 3. The network interface or port for the requested endpoint is not > supported. > 4. A firewall is blocking communication via the port for the requested > endpoint. > 5. A secure network interface is being used to communicate to a machine > that > doesn't have a secure network interface configured with the same > certificate. > > Alternatively, you may need to increase your CONNECTTIMEOUT value for the > network interface and/or increase your CONNECTATTEMPTS value in your > STAF.cfg file. > > Assuming STAFProc is running on the target machine, the most common reason > for this error is that there is a firewall blocking communication via the > port that STAF is using for the tcp/ssl interface when trying to connect to > the remote machine. By default, STAF uses port 6550 to communicate using > its ssl interface (or port 6500 to communicate using its tcp interface), > unless you've changed these ports in the STAF.cfg file. > > The STAF FAQ provides more information about this issue in section "3.1.4 > Why can't my STAF machines communicate?" at > http://staf.sourceforge.net/current/STAFFAQ.htm#STAF%20machines%20can%27t%20communicate%20due%20to%20DNS%20issues > . In particular, since it appears your machines are Linux, see the > following note in the STAF FAQ: > > Note: > Certain versions of Linux set up a high level of security access for > incoming requests on specific ports (including STAF requests, which, by > default, come in through port 6550 for the ssl interface or 6500 for the > tcp interface). From a Linux machine, if you are able to successfully send > a staf ping to another machine, but the other machine cannot do a staf ping > to the Linux machine (and you have verified that the DNS information is set > up correctly on both machines), try the following (note that you may need > to customize these commands depending on the Linux distribution): > > 1. On RedHat 8.0, edit the /etc/sysconfig/iptables file and add the > following lines: > -A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 6500 --syn -j ACCEPT > -A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 6550 --syn -j ACCEPT > > Be sure to add these ACCEPT lines to accept traffic via the tcp ports > you've configured for STAF before the REJECT or DROP line in the > iptables file which rejects/drops all other traffic. > > 2. On RHEL4 and RHEL5, edit the /etc/sysconfig/iptables file and add the > following lines: > -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport > 6500 -j ACCEPT > -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport > 6550 -j ACCEPT > > Be sure to add these ACCEPT lines to accept traffic via the tcp ports > you've configured for STAF before the REJECT or DROP line in the > iptables file which rejects/drops all other traffic. > > 3. Then execute: > /etc/rc.d/init.d/iptables restart > > > -------------------------------------------------------------- > Sharon Lucas > IBM Austin, luc...@us.ibm.com > (512) 286-7313 or Tieline 363-7313 > > > > > From: praveen b <praveenkumar...@gmail.com> > To: Sharon Lucas/Austin/i...@ibmus > Cc: staf-users@lists.sourceforge.net > Date: 11/08/2010 09:54 AM > Subject: Re: [staf-users] Run STAF remotely > > > > thanks for reply, > > yea I understand that we need to have TCP/IP network between two machines > sorry actually earlier i pasted wrong error message, the correct one is > here > > [r...@localhost ~]# STAF 192.168.126.128 PING PING > Error submitting request, RC: 16 > Additional info > --------------- > STAFConnectionProviderConnect: Error performing test read on connected > endpoint: > recv() RC=113: 22, Endpoint: > ssl://192.168.126.128 > [r...@localhost ~]# STAF local PING PING > Response > -------- > PONG > [r...@localhost ~]# > > > > > > > > > On Thu, Nov 4, 2010 at 9:06 PM, Sharon Lucas <luc...@us.ibm.com> wrote: >> The IP address you specified is invalid (as the message tells you). An > IP >> address is made up of four bytes of information (totaling 32 bits) >> expressed as four numbers between 0 and 255 shown separated by periods. > For >> example, 192.17.168.130. >> >> Note: You have to have TCP/IP configured on your machine (as that's what >> STAF uses to communicate to remote machines). >> >> -------------------------------------------------------------- >> Sharon Lucas >> IBM Austin, luc...@us.ibm.com >> (512) 286-7313 or Tieline 363-7313 >> >> >> >> >> From: praveen b <praveenkumar...@gmail.com> >> To: Sharon Lucas/Austin/i...@ibmus >> Date: 11/04/2010 12:00 AM >> Subject: Re: [staf-users] Run STAF remotely >> >> >> >> Hi >> >> even though STAF is running on remote machine I am not able to ping >> the remote machine and getting following error message >> >> [r...@localhost ~]# STAF 192.168.130 ping ping >> Error submitting request, RC: 16 >> Additional info >> --------------- >> STAFConnectionProviderConnect: Invalid IP Address: 192.168.130: 22, >> Endpoint: ssl://192.168.130 >> [r...@localhost ~]# >> >> >> but it is working fine with local machine >> >> [r...@localhost ~]# STAF local ping ping >> Response >> -------- >> PONG >> >> >> can some one please let me know how to mke ping work for remote server. >> >> > > > ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ staf-users mailing list staf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/staf-users
