Linux rsync password prompt slow to appear - result in timeout

I am having a weird problem rsync'ing between two CentOS 5 linux servers.  This results in what appears to be a timeout.

[root@machineA ~]# rsync -vt root@machineBip:/root/somefile.txt ./

------long pause occurs here, about 30 seconds

root@machineBip's password:
Connection closed by machinebip
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: unexplained error (code 255) at io.c(600) [receiver=3.0.6]
[root@machineA ~]#

What could be causing this problem?

Thank you,

Brian
LVL 1
VSEAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

nociSoftware EngineerCommented:
Did you check that any forward & reverse DNS name lookups work, and do it fast.
same for validation of passwords acros a network in case NIS/LDAP is used?

And did you check for packet loss, which can create a lot of timeout's.
(Also look for automatic switch port setup of below 1Gbps links, they might miscommunicate half/full duplex creating this kind of packet loss.
Adrian DobrotaNetworking EngineerCommented:
VSE, if I were you I would try the following:
1. ping machineB from machineA and check for losses
2. after a failed rsync attemp do a "tail /var/log/secure" on machineB and see if you get any error
3. check the /root/.ssh/authorized_keys on machineB. Do not post its content here, but see if it contains machineA public key
4. if it does not, you could try and paste the contents of /root/.ssh/id_dsa.pub from machineA into /root/.ssh/authorized_keys on machineB. If machineA does not have a public key generated, you can generate it with ssh-keygen

anyway, I guess /var/log/secure will show us what the actual problem is

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Adrian DobrotaNetworking EngineerCommented:
VSE, thanks for accepting my answer.
Could you please give us some feedback about what worked/what didn't/what the problem was? This way, others with similar problems browsing this forum will find it easier to diagnose.
Thank you
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.