Hello!
for the first, I’m not a linux guy:)
i have a script. this script copying file by rpc. last time file copied
1 month before. and now i cannot copy new file. rcp starting to copy, it
copies 540Kb and than it stuckes (connection timeout).
cannot find anything in logs about it.
(suse linux 9 on both servers)
So can you help me, where should i search the problem. What it can be?
btw network configuration never changed.
thanks in advance!
rcp is pretty old… in fact, ancient, and insecure. You really should
be using scp for any file copies as it adds security and works out of
the box on SLES (since SSH is enabled by default on SLES). Perhaps rcp
actually uses scp these days, but I’d still use scp explicitly since
sending data unencrypted across the wire is generally a bad idea. Is
this an option for you?
If not, get a LAN trace of the connection and see which side is not
continuing to send data when it should. A lack of acknowledgement from
the server could stall the client, or just leave it retrying things over
and over. A lack of continuing the stream from the client could also
stall things.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
I concur. I use scp here exclusively with no issues. Although I am
running SLES 10, but that should not make a difference.
–El
ab;2148532 Wrote:[color=blue]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
rcp is pretty old… in fact, ancient, and insecure. You really
should
be using scp for any file copies as it adds security and works out of
the box on SLES (since SSH is enabled by default on SLES). Perhaps
rcp
actually uses scp these days, but I’d still use scp explicitly since
sending data unencrypted across the wire is generally a bad idea. Is
this an option for you?
If not, get a LAN trace of the connection and see which side is not
continuing to send data when it should. A lack of acknowledgement
from
the server could stall the client, or just leave it retrying things
over
and over. A lack of continuing the stream from the client could also
stall things.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - ‘Enigmail: A simple interface for
OpenPGP email security’ (http://enigmail.mozdev.org/)
Are both source and destination on the same subnet? If not, what’s the
basic network setup (rcp through local routers vs. off-site, VPNs,
Internet, whatever else is involved)
Do pings go through between the involved nodes? Do they go through with
large block sizes?
Have you tried snooping with ethereal (“wireshark” nowadays) to see
what the last part of the traffic is?
Which “logs” have you checked?
Does invoking rsh work? Any hangs in the output when transfering larger
bits of stdout (from something like “find /”)?
Regards,
Jens
–
from the times when today’s “old school” was “new school” :eek:
