rcp gets hung for long time


 
Thread Tools Search this Thread
Operating Systems AIX rcp gets hung for long time
# 1  
Old 01-09-2008
rcp gets hung for long time

Every evening I run a script in AIX production box, which executes below command:
rcp prod_bkup.tar prodapp@IP:/data/appl/prod

This will rcp a backup of around 11 GB from production to another machine (runs every evening so overwrites previous one). Just to keep the backup safe. Since 2-3 days, I notice that this command takes quite longer than normal days and when I go to another machine - I am allowed to login, But when I give 'ls -l /data/appl/prod' nothing comes and looks like session on both windows kinda hung state. Then I press ctrl C on production.

Then next morning 'ls -l /data/appl/prod' command also works fine on another machine and I see that backup is copied (not fully, the byte difference is there) of around 2 hours later time stamp. And I tried rcping a 0 byte from production to another machine also works fine. Only problem comes during evening when I rcp the backup.

Do you know what might be going wrong and where can I find such logs on AIX machines?

Please advice / Thank you.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

First script in a long time

I was wondering if I could get some feedback on my script to grab time from our MDM... I blocked out all of the important stuff. I really appreciate any guidance, since I am long out of practice. #!/bin/bash serial=$1 # get last seen value of ipad lastseen=$(curl -s -X "GET"... (11 Replies)
Discussion started by: andysensible
11 Replies

2. UNIX for Dummies Questions & Answers

ls is taking long time to list

Hi, All the data are kept on Netapp using NFS. some directories are so fast when doing ls but few of them are slow. After doing few times, it becomes fast. Then again after few minutes, it becomes slow again. Can you advise what's going on? This one directory I am very interested is giving... (3 Replies)
Discussion started by: samnyc
3 Replies

3. Shell Programming and Scripting

How long ago since time - Using perl

echo "1337124526" | perl -pe 's/(\d+)/easttime($1)/e' the above gives a date and time. how can i subtract the date and time given by this command, from the current present date? can this be a one liner or as close to a one-liner as possible? (1 Reply)
Discussion started by: SkySmart
1 Replies

4. 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

5. UNIX for Dummies Questions & Answers

Job is taking long time

Hi , We have 20 jobs are scheduled. In that one of our job is taking long time ,it's not completing. If we are not terminating it's running infinity time actually the job completion time is 5 minutes. The job is deleting some records from the table and two insert statements and one select... (7 Replies)
Discussion started by: ajaykumarkona
7 Replies

6. HP-UX

Strange- RCP command works every other time

This just started happening. I use the rcp command to copy a file from one server to another. Now when I use the command, every other time I execute the exact same command I get the error: remshd: login correct Example: 1. rcp testfile server2:/db/tmp (Work ok, verified file... (6 Replies)
Discussion started by: jrowland
6 Replies

7. HP-UX

ssh session getting hung (smilar to hpux telnet session is getting hung after about 15 minutes)

Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies

8. Shell Programming and Scripting

help - exec time too long

Dear everyone... thanks to this forum I am able to do everyday more and more complex scripts...but now I come up with problem with optimisation.. problem 1 - optimise: here is my code: while read number do nawk -F "|" -v... (8 Replies)
Discussion started by: abdulaziz
8 Replies

9. Solaris

ssh Long time to return prompt.

Hi All, I was installed new server M5000 on solaris10. I'am try to connect to server by ssh client (putty) after type user name and password the server take long time to return prompt to me about 30-60 second. any body can suggess me how to do it. (8 Replies)
Discussion started by: cesmk
8 Replies

10. Programming

Debug env for long time use

Hi, I'm pritty new to C, but a recent bug in a program i've been using has forced me to debug it. But I am unable to find a debugger that can act as a layer between the OS and the program to see whats going on.. The problem is that this piece of software makes a connection through localhost... (2 Replies)
Discussion started by: nephilimbe
2 Replies
Login or Register to Ask a Question
rcp(1)							      General Commands Manual							    rcp(1)

NAME
rcp - Copies files between a local and a remote host or between two remote hosts SYNOPSIS
rcp [-pr] source destination The remote copy command (rcp) is used to copy one or more files between the local host and a remote host, between two remote hosts, or between files at the same remote host. OPTIONS
Preserves the modification times and modes of the source files in the copies sent to the destination; extended file attributes (property list), including the access control list (ACL), if any, are not copied. Without this option, the umask command at the destination modifies the mode of the destination file, and the modification time of the destination file is set to the time the file is received. Copies recur- sively, for directories only, each file and subdirectory in the source directory into the destination directory. DESCRIPTION
By default, the mode and owner of an existing destination file are preserved. Normally, if a destination file does not exist, the mode of the destination file is equal to the mode of the source file as modified by the umask command at the destination host. If the -p option is set, the modification time and mode of source files are preserved at the destination host. If the file has extended file attributes (prop- erty list), including the access control list (ACL), they are not copied and rcp returns the rcp: filename: proplist not copied message. If a remote hostname is not specified for either the source or the destination, rcp is equivalent to the cp command. When copying files to or from a remote host, any remote filename or directory name must be prefixed by the name of the remote host and a : (colon). Local filenames and directory names do not need to have a host specified. However, since rcp assumes that a colon terminates a hostname, local filenames or directory names must have a (backslash) inserted before any colons embedded in the name. If you want to specify an IPv6 address for source or destination, you must prefix the address with the [ (backslash, left bracket) charac- ters and terminate the address with the ] (backslash, right bracket) characters. Because the bracket characters are shell metacharacters, you must precede them with the backslash character. The username entered for the remote host determines the file access privileges rcp uses at that host. Additionally, the username given to a destination host determines the ownership and access modes of the resulting destination file or files. If a hostname is not prefixed by user@, the local username is used at the remote host. If a username is entered, that name is used. In either case, the remote host allows access if one of the following conditions is satisfied: The local host is included in the remote host's /etc/hosts.equiv file and the remote user is not the superuser. The local host and username is included in a $HOME/.rhosts file in the home directory of the remote user account. For security reasons, any $HOME/.rhosts file must be owned by either the remote user or the root user and should have permissions set to 600 (read and write by owner only). In addition to the preceding conditions, rcp also allows access to the remote host if the remote user account does not have a password defined. However, for security reasons, use of a password on all user accounts is recommended. If the path for a file or directory on a remote host is not specified or is not fully qualified, the path is interpreted as beginning at the home directory for the remote user account. Additionally, any metacharacters that must be interpreted at a remote host must be quoted using (backslash), " " (double quotes), or ' ' (single quotes). RESTRICTIONS
The rcp command is confused by output generated by commands in a file on the remote host. In particular, the messages, where are you? and stty: Can't assign requested address can result if output is generated by the startup file. EXAMPLES
To copy a file named localfile from the local host to a remote host named host2, enter: rcp localfile host2:/u/eng/fred To copy a remote file named newplan from one remote host, host1, to another remote host, host2, enter: rcp host1:/u/eng/fred/newplan host2:/u/eng/mary To send a directory subtree report from the local host to the home directory of a user named fred at a remote host named host2, and preserve all modes and modification times, enter: rcp -p -r report fred@host2:report The remote file /u/fred/.rhosts includes an entry specifying the local host and username. FILES
Specifies remote hosts from which users can execute commands on the local host (provided these users have an account on the local host). Specifies remote users who can use a local user account. SEE ALSO
Commands: rsh(1), rlogin(1), rshd(8) Files: rhosts(4) rcp(1)