Slow sftp on one node of RAC cluster

 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Slow sftp on one node of RAC cluster
# 1  
Old 10-28-2009
Slow sftp on one node of RAC cluster

I have a three node Oracle RAC cluster on RHEL4u7. User is using sftp to move files and the process works well on 2 of the three nodes. The other remaining node takes forever. I have gone through the /etc/sysconfig/network-scripts/ifcfg files and everything seems to be configured correctly.

Has anyone seen a similar problem and I wouuld appreciate help in solving this.
Thanks

---------- Post updated at 02:53 PM ---------- Previous update was at 02:48 PM ----------

sftp not dftp - Sorry for the confusion. I will learn to type and proof read.

Last edited by DukeNuke2; 10-28-2009 at 06:57 PM.. Reason: fixed typo
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. AIX

Cluster node not starting

Setting up HACMP 6.1 on a two node cluster. The other node works fine and can start properly on STABLE state (VGs varied, FS mounted, Service IP aliased). However, the other node is always stuck on ST_JOINING state. Its taking forever and you can't stop the cluster as well or recover from script... (2 Replies)
Discussion started by: depam
2 Replies

2. Solaris

SVM metaset on 2 node Solaris cluster storage replicated to non-clustered Solaris node

Hi, Is it possible to have a Solaris cluster of 2 nodes at SITE-A using SVM and creating metaset using say 2 LUNs (on SAN). Then replicating these 2 LUNs to remote site SITE-B via storage based replication and then using these LUNs by importing them as a metaset on a server at SITE-B which is... (0 Replies)
Discussion started by: dn2011
0 Replies

3. UNIX for Advanced & Expert Users

Oracle RAC Cluster on RedHat Linux, Node eviction

We have 2 node Oracle RAC Cluster. It is running RHEL 5 (2.6.18-92.1.10.el5PAE) Hardware is HP DL360 We have node eviction issue, Oracle evicts node. It is not very consistent. Oracle has looked all log files and said this is not Oracle issue but rather system or os issue. Server does not... (7 Replies)
Discussion started by: sanjay92
7 Replies

4. HP-UX

Node can't join cluster

Need help guys! when running cmrunnode batch i'm getting this error cmrunnode : Waiting for cluster to... (1 Reply)
Discussion started by: Tris
1 Replies

5. Shell Programming and Scripting

The other node name of a SUN cluster

Hello, Under ksh I have to run a script on one of the nodes of a Solaris 8 cluster which at some time must execute a command on the alternate node: # rsh <name> "command" I have to implement this script on all the clusters of my company (a lot of...). Fortunately, the names of the two nodes... (11 Replies)
Discussion started by: heartwork
11 Replies
Login or Register to Ask a Question
cmdo(1m)																  cmdo(1m)

NAME
cmdo - Execute process on multiple remote Serviceguard nodes. SYNOPSIS
cmdo [[-n node_name]...] [-t timeout] command DESCRIPTION
cmdo will execute a process on a multiple remote Serviceguard nodes and return any output or return value. cmdo is limited in several ways. cmdo is best suited for situations where other remote execution facilities are not available. For a more full featured tool for remote execution within a cluster, see cexec(1m) provided by Distributed Systems Administration Utilities. To use this command, the local user must have the root access role on each of the involved nodes. For more information on Serviceguard access control policies, see the manual, Managing Serviceguard. To use the cmdo command without specifying -n options, the local node must be configured into a Serviceguard cluster. If no -n options are specified, the command will be executed on all available nodes in the cluster. The command will be executed in an environment which matches the local node. All environment variables defined locally will be available on the remote node. Output from stderr and stdout for the remote process will be combined and delivered in one transmission. This command should not be used for interactive commands or commands which will return large quantities of output. Output from each node will be displayed sequentially as the operation is executed on each remote node. Input via stdin is not supported. Killing the cmdo process does not stop any remote executions of the command. cmdo should not be used on any command which may hang without specifying a timeout value. Options And Arguments -t timeout Kill the executed command if it does not exit within the specified timeout (in seconds) -n node_name Serviceguard node to execute command on. If no -n options are specified, all the nodes configured in the cluster are used. command Command to execute on remote node. May be quoted. RETURN VALUE
cmdo returns the following values: 0 Successful completed on all nodes. >0 Command failed on one or more nodes with the specified exit value. EXAMPLES
Execute an 'ls' in a remote directory on all nodes within the cluster. cmdo ls /tmp Execute an 'ls' in a remote directory on two nodes not configured within a Serviceguard cluster. cmdo -n node1 -n node2 ls /tmp AUTHOR
cmdo was developed by HP. SEE ALSO
cexec(1m), cmcp(1m), cmexec(1m), cmsync(1m), cmquerycl(1m), cmviewcl(1m) Requires Optional Serviceguard Software cmdo(1m)