I was afraid of that. I'd hoped that it would show more. Next thing i'd
try would be to, on the remote end, write a rsync wrapper script, that
starts rsync inside a strace (or truss, or tusc, or whatever your OS
uses), directing it to follow forks, redirecting STDERR to a file. Do
another super-short run, using --rsync-path= to point at the wrapper, then
scan down that trace output. If you don't see a solution right away, post
that output here. If we find that the rsync process suspends itself
waiting for io, it's probably a transport thing.Rsync is known for
revealing weaknesses in TCP/IP implementations, though I wouldn't expect
to see it in small jobs.
Tim Conway
[EMAIL PROTECTED] reorder name and reverse domain
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
There are some who call me Tim?
Chad Moss [EMAIL PROTECTED]
Sent by:
[EMAIL PROTECTED]
12/18/02 03:48 PM
To: Tim Conway/LMT/SC/PHILIPS@AMEC
cc: [EMAIL PROTECTED]
Subject:RE: rsync problem behind a router
Classification:
OK...I tried with the -vvv on one file (an index.php file). I got:
stdin: is not a tty
server_sender starting pid=14373
make_file(1,index.php)
expand file_list to 4000 bytes, did move
recv_file_name(index.php)
received 1 names
recv_file_list done
get_local_name count=1 /home/backup/mercury/
recv_files(1) starting
send_file_list done
send_files starting
generator starting pid=1494 count=1
recv_generator(index.php,0)
generate_files phase=1
A couple of times, it did not even get that far...I got:
stdin: is not a tty
server_sender starting pid=14432
make_file(1,index.php)
expand file_list to 4000 bytes, did move
recv_file_name(index.php)
received 1 names
recv_file_list done
get_local_name count=1 /home/backup/mercury/
generator starting pid=1497 count=1
recv_generator(index.php,0)
generate_files phase=1
recv_files(1) starting
send_file_list done
send_files starting
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 12:08 PM
To: Chad Moss
Cc: [EMAIL PROTECTED]
Subject: Re: rsync problem behind a router
Chad: From the output you have so far, there's not much to go on. Can
you try a run with -vvv? That's more likely to reveal exactly what
it's
failing on, though (AFAIK(IIRC)) it won't tell you about stuff on the
remote side. I had to write a wrapper to start rsync in a truss -f for
part of my debugging.
Tim Conway
[EMAIL PROTECTED] reorder name and reverse domain
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
There are some who call me Tim?
Chad Moss [EMAIL PROTECTED]
Sent by:
[EMAIL PROTECTED]
12/17/02 04:57 PM
To: [EMAIL PROTECTED]
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject:rsync problem behind a router
Classification:
I have used rsync on many systems, and never had a problem. I am
stumped
on what to do with this?
I have a box behind a LinkSys router and I can not push or pull data
to or from it from anywhere?
When I try, it logs into the remote server, gets the file list and just
stops.
The remote server shows a process running until I control-c out of
it?when
I do that, I get:
rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
rsync error: received SIGUSR1 or SIGINT (code 20) at main.c(785)
The command I am using is:
rsync -avz -e ssh [EMAIL PROTECTED]:/home /home/backup/servername/
I have forwarded ports 22 and 873 to that machine, and I have tried
putting it in the DMZ.
The results do not seem to change.
Thanks.
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html