Sponsored Content
Top Forums Shell Programming and Scripting Transfer file from a server takes long time Post 302988972 by Peasant on Friday 6th of January 2017 01:50:07 AM
Old 01-06-2017
Try not using encryption (if you can) as a first step of debug.
Something in the fashion of FTP or simple netcat [nc] utility from both sides (one listening other sending)
Try an NFS mount if you can, and compare speeds.

Couple of questions :
Are other clients (the servers you are copying to) exhibiting the same problem or just that one ?

If all the clients you are copying to experience slow copy -->
Check the netstat command (-s -i) and look for drops, errors and re-transmissions on the server side (the machine you are copying from).

How are disk response times and queues ? Are disks on the server side saturated perhaps ?
If disk read can not give you more 5MB/s no network will achieve more (unlikely, 5mb/s is quite low for todays 'standards', but check, iostat will be your friend here).

If only one (or couple of perhaps in same network VLAN), check out the clients with above commands.

Take output of commands before and after the action and compare.
The before is important, cause those counters are not restarted since boot probably, as a baseline.

Is the copy done over internet or intranet, are firewalls and/or packet inspection/throttling active on those networks ?

This is where netcat may can come into play, for instance, you can throttle 'per app' in firewall like ssh (port 22), nfs (port 2049) but netcat can use any port, test a couple on server/client, try using high port numbers.

And yes, i love netcat Smilie
This User Gave Thanks to Peasant For This Post:
 

10 More Discussions You Might Find Interesting

1. Programming

fwrite takes extremely long time

After my previous thread, I think I found out what causes the long delays. I run this program on several Linux computers, and the sometimes (after the file with the arrays becomes big) the fwrite takes between 100 ms to 900 ms. This is very bad for me, as I want a timer to halt each 30 ms.... ... (5 Replies)
Discussion started by: inna
5 Replies

2. Shell Programming and Scripting

shell script takes long time to complete

Hi all, I wrote this shell script to validate filed numbers for input file. But it take forever to complete validation on a file. The average speed is like 9mins/MB. Can anyone tell me how to improve the performance of a shell script? Thanks (12 Replies)
Discussion started by: ozzman
12 Replies

3. AIX

How long does AIX resync the time with another server

Hi, I have NTP configured: vi /etc/ntp.conf broadcastclient server 128.127.1.3 driftfile /etc/ntp.drift tracefile /etc/ntp.trace # xntpdc xntpdc> sysinfo system peer: 128.127.1.3 system peer mode: client leap indicator: 00 stratum: 12 precision: ... (0 Replies)
Discussion started by: victorcheung
0 Replies

4. Linux

it takes long time to login on server

Hi, I am trying to login using ssh on Red Hat Linux 5 server, The password appears immediately but after I enter the password it takes about 90 seconds to login completely. Please suggest what changes require? Regards, Manoj (4 Replies)
Discussion started by: manoj.solaris
4 Replies

5. UNIX for Dummies Questions & Answers

time how long it takes to load a module

Hello, like the title says, how can i measure the time it takes to load a module in Linux, and how how can i measure the time it takes to load a statically compiled module. /Best Regards Olle ---------- Post updated at 01:13 PM ---------- Previous update was at 11:54 AM ---------- For... (0 Replies)
Discussion started by: ollebanan
0 Replies

6. UNIX for Dummies Questions & Answers

Changing Password process takes a long time

We are running unix. After a reboot of the server we have found that changing password takes a long time. if type in passwd "username" you can type in the 1st instance of the password , press enter , then it will wait for about 3 minutes before bringing up the confirm password line typing it in... (4 Replies)
Discussion started by: AIXlewis
4 Replies

7. Shell Programming and Scripting

sort takes a long time

Dear experts I have a 200MG text file in this format: text \tab number I try to sort using options -fd and it takes very long! is that normal or I can speed it up in some ways? I dont want to split the file since this one is already splitted. I use this command: sort -fd file >... (12 Replies)
Discussion started by: voolek
12 Replies

8. Red Hat

Login to server takes time

When I am trying to login to a server using Putty ssh from my windows xp machine it is taking too much time for login. My server name is http2 and when I enter this address into putty I immediately get login as: screen, but after I put my username root and enter the cursor moves downwards... (14 Replies)
Discussion started by: abhilashkrishn
14 Replies

9. UNIX and Linux Applications

database takes long time to process

Hi, we currently having a issue where when we send jobs to the server for the application lawson, it is taking a very long time to complete. here are the last few lines of the database log. 2012-09-18-10.35.55.707279-240 E244403536A576 LEVEL: Warning PID : 950492 ... (1 Reply)
Discussion started by: techy1
1 Replies

10. Shell Programming and Scripting

Wget takes a long time to complete

Hi, I wish to check the return value for wget $url. However, some urls are designed to take 45 minutes or more to return. All i need to check if the URL can be reached or not using wget. How can i get wget to return the value in a few seconds ? (8 Replies)
Discussion started by: mohtashims
8 Replies
rpc.statd(8)						      System Manager's Manual						      rpc.statd(8)

NAME
rpc.statd - NSM status monitor SYNOPSIS
rpc.statd [-FNL] [-d] [-?] [-n name ] [-o port ] [-p port ] [-H prog ] [-V] DESCRIPTION
The rpc.statd server implements the NSM (Network Status Monitor) RPC protocol. This service is somewhat misnamed, since it doesn't actu- ally provide active monitoring as one might suspect; instead, NSM implements a reboot notification service. It is used by the NFS file locking service, rpc.lockd, to implement lock recovery when the NFS server machine crashes and reboots. Operation For each NFS client or server machine to be monitored, rpc.statd creates a file in /var/lib/nfs/sm. When starting, it normally runs sm- notify to iterate through these files and notify the peer rpc.statd on those machines. OPTIONS
-F By default, rpc.statd forks and puts itself in the background when started. The -F argument tells it to remain in the foreground. This option is mainly for debugging purposes. -d By default, rpc.statd sends logging messages via syslog(3) to system log. The -d argument forces it to log verbose output to stderr instead. This option is mainly for debugging purposes, and may only be used in conjunction with the -F parameter. -n, --name name specify a name for rpc.statd to use as the local hostname. By default, rpc.statd will call gethostname(2) to get the local hostname. Specifying a local hostname may be useful for machines with more than one interfaces. -o, --outgoing-port port specify a port for rpc.statd to send outgoing status requests from. By default, rpc.statd will ask portmap(8) to assign it a port number. As of this writing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be useful when implementing a firewall. -p, --port port specify a port for rpc.statd to listen on. By default, rpc.statd will ask portmap(8) to assign it a port number. As of this writ- ing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be useful when implementing a firewall. -P, --state-directory-path directory specify a directory in which to place statd state information. If this option is not specified the default of /var/lib/nfs is used. -N Causes statd to run in the notify-only mode. When started in this mode, the statd program will check its state directory, send noti- fications to any monitored nodes, and exit once the notifications have been sent. This mode is used to enable Highly Available NFS implementations (i.e. HA-NFS). This mode is deprecated - sm-notify should be used directly instead. -L, --no-notify Inhibits the running of sm-notify. If sm-notify is run by some other script at boot time, there is no need for statd to start sm- notify itself. This can be appropriate if starting of statd needs to be delayed until it is actually need. In such cases sm-notify should still be run at boot time. -H, --ha-callout prog Specify a high availability callout program, which will receive callouts for all client monitor and unmonitor requests. This allows rpc.statd to be used in a High Availability NFS (HA-NFS) environment. The program will be run with 3 arguments: The first is either add-client or del-client depending on the reason for the callout. The second will be the name of the client. The third will be the name of the server as known to the client. -? Causes rpc.statd to print out command-line help and exit. -V Causes rpc.statd to print out version information and exit. TCP_WRAPPERS SUPPORT This rpc.statd version is protected by the tcp_wrapper library. You have to give the clients access to rpc.statd if they should be allowed to use it. To allow connects from clients of the .bar.com domain you could use the following line in /etc/hosts.allow: statd: .bar.com You have to use the daemon name statd for the daemon name (even if the binary has a different name). For further information please have a look at the tcpd(8) and hosts_access(5) manual pages. SIGNALS
SIGUSR1 causes rpc.statd to re-read the notify list from disk and send notifications to clients. This can be used in High Availability NFS (HA-NFS) environments to notify clients to reacquire file locks upon takeover of an NFS export from another server. FILES
/var/lib/nfs/state /var/lib/nfs/sm/* /var/lib/nfs/sm.bak/* SEE ALSO
rpc.nfsd(8), portmap(8) AUTHORS
Jeff Uphoff <juphoff@users.sourceforge.net> Olaf Kirch <okir@monad.swb.de> H.J. Lu <hjl@gnu.org> Lon Hohberger <hohberger@missioncriticallinux.com> Paul Clements <paul.clements@steeleye.com> 31 Aug 2004 rpc.statd(8)
All times are GMT -4. The time now is 04:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy