https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #6 from roland ---
nobody has a clue?
i think proper rsync timeout handling is important.
i have had whole nightly backup procedures hung for the whole night because
rsync got stuck and didn't get timeout, i.e. machines did no
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #5 from roland ---
apparently, this is causing the problem:
if (am_receiver) {
return;
}
if i comment out the return statement, things work again.
@wayne, what is the reason that timeout checking
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #4 from roland ---
here with debug=all
working correctly
# /root/rsync/rsync-3.2.5/rsync -avi --timeout=5 --exclude='/proc'
--exclude='/dev/' --exclude='/sys' --debug=all --msgs2stderr
root@172.20.37.
a timeout has occurred. When it is sifting through a lot of
* files looking for work, it will be sending keep-alive messages to
* the sender, and even though the receiver won't be sending/receiving
* anything (not even keep-alive messages), the successful writ
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #2 from roland ---
here is another bugreport, where timeout is not effective/working
https://bugzilla.redhat.com/show_bug.cgi?id=1944132
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use
https://bugzilla.samba.org/show_bug.cgi?id=15163
--- Comment #1 from roland ---
here is some strace from the backup host to show the difference
if i set timeout=60 , rsyncing "root@172.20.37.189:/" hangs forever:
08:25:30 select(4, [3], [], [3], {tv_sec=30, tv_usec=0}) = 1 (in
https://bugzilla.samba.org/show_bug.cgi?id=15163
Bug ID: 15163
Summary: rsync timeout non-effective
Product: rsync
Version: 3.2.0
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
apparently, it must be a bug
if i do
/root/rsync/rsync-3.2.5/rsync -avi --timeout=10 --exclude='/proc'
--exclude='/dev/' root@172.20.37.189:/ /zfspool/backup/172.20.37.189/
it hangs forever , as soon as rsync tries to traverse the
suspended/hanging /iscsipool on the remo
there is connection timeout and I/O timeout
i'm using the I/O timeout.
for "--timeout" manpage is "if no data is transferredthen rsync will
exit"
no data is being transferred for hours, but it doesn't exit.
so, what's the problem here ?
-
You are using rsync over ssh. The connection timeout (and port) options
don't matter if rsync isn't doing the networking.
On 9/1/22 08:49, Roland via rsync wrote:
hello,
i do some backup via rsync/ssh and pull data from remote machine to
local machine.
whenever on remote machin
der what's the purpose of "--timeout" then.
local machine: 3.1.2
remote machine: 3.2.3
command
rsync -avi --stats --delete --delete-excluded --inplace --numeric-ids
--out-format=%-15i %-15b %-15l %-20M %n%L --timeout=900
--rsync-path=export PATH=/usr/local/bin:$PATH;rsy
hello,
I have opened https://github.com/WayneD/rsync/issues/282
looks similar to https://github.com/WayneD/rsync/issues/164 and
https://github.com/WayneD/rsync/issues/8
roland
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https:
https://bugzilla.samba.org/show_bug.cgi?id=12527
Ben RUBSON changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
It appears that the --timeout only works when using the rsync
protocol, but not when copying between two directories. So if the
destination is on a network filesystem and the network link is
disconnected, rsync will only abort the operation once the underlying
system finally reports that the
Hey list,
My rsync(1) transfer keeps dieing. It starts sync'ing, slows down, and
then times out with no apparent reason. I have tried both with and
without --fuzzy, --inplace, and various --timeout values to no effect.
It is possible this could be an SSH issue, but it is difficult to tell.
On Mon 22 Jan 2018, Kevin Korb via rsync wrote:
> From man 2 select:
> int select(int nfds, fd_set *readfds, fd_set *writefds,
> fd_set *exceptfds, struct timeval *timeout);
>
> So, it is waiting for file descriptor #1 to become available with a 60
> second timeout which it is
LL, [1], [1], {60, 0}) = 1 (out [1], left
{59, 97})
17383 05:08:22 write(1, "\374\17\0\7", 4) = 4
17383 05:08:22 select(2, NULL, [1], [1], {60, 0}) = 0 (Timeout)
17383 05:09:22 select(2, NULL, [1], [1], {60, 0}) = 0 (Timeout)
17383 05:10:22 select(2, NULL, [1], [1], {60, 0}) = 0 (Ti
From man 2 select:
int select(int nfds, fd_set *readfds, fd_set *writefds,
fd_set *exceptfds, struct timeval *timeout);
So, it is waiting for file descriptor #1 to become available with a 60
second timeout which it is hitting.
Use lsof to find out what file descriptor #1 is.
On 01/22/2018 10:07
to interper this output.
I guess between 00:55:41 and 03:06:47 nothing is happening? And then
some timeout is generated? What does this 'select(1, [0], [], NULL, {60,
0}) = 0 (Timeout)' mean?
Commandline
===
rsync -avH --del --rsync-path=/usr/local/sbin/rsync-debug.sh
https://bugzilla.samba.org/show_bug.cgi?id=12527
--- Comment #3 from Ben RUBSON ---
So sounds like that when the generator sends too much info (too many checksums)
to the sender, the sender does not receive / see (important) messages anymore.
Perhaps we could solve this by making the generator w
https://bugzilla.samba.org/show_bug.cgi?id=12527
--- Comment #2 from Ben RUBSON ---
I'm troubleshooting and found that this happens when generate_and_send_sums()
writes too many bufs.
If I replace :
for (i = 0; i < sum.count; i++) {
by :
for (i = 0; i < 4500; i++) {
(sum.count > 15000 in this te
https://bugzilla.samba.org/show_bug.cgi?id=12527
--- Comment #1 from Ben RUBSON ---
Same issue with rsync-HEAD-20161010-1854GMT.
My quick previous test uses these local files :
-rw--- 1 root root 1177136858 Jan 10 2017 bf.iso
-rw--- 1 root root68558591 Jan 10 2017 sf2.dmg
And
https://bugzilla.samba.org/show_bug.cgi?id=12527
Bug ID: 12527
Summary: Sender waits for timeout when fuzzy basis file found
Product: rsync
Version: 3.1.2
Hardware: All
OS: All
Status: NEW
Severity
I am rsyncing to data from one machine (Server) running rsync --deamon
(from inetd) to another (client) using
/usr/bin/rsync -azq --delete --timeout=60 --contimeout=60
"10.1.1.100::data/" "/data/data/"
on the client which works well as you would expect (takes about 34s
On Sat, Nov 9, 2013 at 12:58 PM, Wayne Davison wrote:
>
> On Fri, Nov 8, 2013 at 6:47 AM, Dan McGee wrote:
>
>> $ strace -f rsync --contimeout=10 --timeout=10 rsync://
>> mirror.aarnet.edu.au/archlinux/lastsync /tmp/hanging-lastsync
>> [...]
>>
>> write
On Fri, Nov 8, 2013 at 6:47 AM, Dan McGee wrote:
> $ strace -f rsync --contimeout=10 --timeout=10 rsync://
> mirror.aarnet.edu.au/archlinux/lastsync /tmp/hanging-lastsync
> [...]
> write(3, "@RSYNCD: 31.0\n", 14) = 14
> read(3, ^CProcess 30534 detached
>
It
timeout=10 --timeout=10 rsync://
mirror.aarnet.edu.au/archlinux/lastsync /tmp/hanging-lastsync
execve("/usr/bin/rsync", ["rsync", "--contimeout=10", "--timeout=10",
"rsync://mirror.aarnet.edu.au/arc"..., "/tmp/hanging-lastsync"], [/* 25
vars *
es. Version 3.1.0 has
an improved keep-alive setup that may help you, but if not, you either need
to increase the timeout or eliminate it (most transfers don't need it).
..wayne..
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: h
>>> I have sometimes a huge amount of files to delete.
>>> Rsync daemon can take a lot of time to delete them, leading Rsync client
>>> into a timeout…
>>>
>>> Is there any way to avoid this timeout ?
>>> I would have liked not to increase
emon can take a lot of time to delete them, leading Rsync client
>> into a timeout…
>>
>> Is there any way to avoid this timeout ?
>> I would have liked not to increase timeout value on client side (which is
>> already set to 600 seconds), as I don't really know ho
pically finishes around 20:45. However, when this
> problem occurs, rsync blocks indefinitely. I have configured rsync
> to run using the "timeout" command so that it will be killed if not
> finished by 9:00 the next day: timeout -k 30s 764m rsync -av
> --modify-window=2 --link-dest=/
share3 nightly at 20:15. When this blocking problem does not occur,
the backup typically finishes around 20:45. However, when this problem occurs,
rsync blocks indefinitely. I have configured rsync to run using the "timeout"
command so that it will be killed if not finished by 9:00 the
Le 20 mai 2013 à 10:55, AZ 9901 a écrit :
> Hello,
>
> I use Rsync client (3.0.9) synchronising to a Rsync daemon (3.0.8) over SSH.
>
> I have sometimes a huge amount of files to delete.
> Rsync daemon can take a lot of time to delete them, leading Rsync client into
> a t
Hello,
I use Rsync client (3.0.9) synchronising to a Rsync daemon (3.0.8) over SSH.
I have sometimes a huge amount of files to delete.
Rsync daemon can take a lot of time to delete them, leading Rsync client into a
timeout…
Is there any way to avoid this timeout ?
I would have liked not to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No, it is the OS that determines this. Rsync issues a read request
then goes into a waiting on IO state until it either gets the data or
an error.
On 01/17/13 08:16, Nicolas Secreto wrote:
> Is there any way to tell rsync how much time it has to wait
I know the --timeout parameter, but it is intended to abort the copy when
there is an I/O error and what I'm interested in is to continue the copy.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/ma
Is there any way to tell rsync how much time it has to wait to decide that
a file has got read errors?
It takes forever when copying a lot of files with errors from failing disks.
Thanks
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options:
not happen anymore with the -W option.
I don't know if this will resolve your issue, but you can also try looking into
these options : --no-checksum --no-compress --blocking-io. These were not the
source of my problems, but the functions they're related to might rise a
network timeout.
I
Hello again,
still didn't find solution for timeout.
What exactly is happening during initial "no progress" period?
I guess, destination rsync is computing checksum of whole destination file
before transfer starts from source?
Is there any way to force rsync to start copyi
Hello,
tried to set timeout=7200 on both sides
also enabled logging in rsyncd
Here is output from server
2012/08/02 15:07:23 [2339] connect from ms-backup.xx.local (192.168.5.213)
2012/08/02 15:07:23 [2339] rsync to iSCSI-backup/ from backup-rsync@ms-
backup.xx.local (192.168.5.213)
2012/08/02 13
On Thu 02 Aug 2012, Libor Klepáč wrote:
> Ok, i'l try setting timeout, but according to documentation, default is
> timeout=0 which means no timeout.
IIRC setting the timeout explicitly on both ends (if you're using an
rsync daemon) to the same value will cause some sort of he
Ok, i'l try setting timeout, but according to documentation, default is
timeout=0 which means no timeout.
Maybe setting --contimeout to some large value should help?
Libor
Dne Thursday 02 August 2012 07:03:51, Tony Abernethy napsal(a):
--timeout=SECONDS set I/O timeo
--timeout=SECONDS set I/O timeout in seconds
I think this timeout must be set big enough so that data actually gets
transferred during the window.
Having the target verify that nothing has changed yet seems to not qualify as
resetting the timeout.
Figure on enough time so that
Just to clarify
When using rsyncd script, there is also no progress from beginning, it just
timeouts
Libor
Dne Thursday 02 August 2012 12:26:13, Libor Klepáč napsal(a):
> Hello,
> let me describe my setup.
> Source server is debian wheezy, rsync 3.0.9
> Destination is qnap TS-410, with rsyncd en
Hello,
let me describe my setup.
Source server is debian wheezy, rsync 3.0.9
Destination is qnap TS-410, with rsyncd enabled, rsync 3.0.7
I'm trying to rsync two files, which are exported from source server as iscsi
targets (windows iscsi backups). Files are on btrfs, so I use snapshots during
r
7;--ignore-times' is only to force a comparison. The real world scenario
would be the sync of a truecrypt container.
This transfer aborts with a timeout. The reason is that during the hash_search
phase no packets are sent to the peer. If I omit the --compress option,
tokens are sent regularly,
On 8/1/2011 4:30 AM, Bjorn Madsen wrote:
I thought other might benefit from this lesson learned and thought it
maybe should be added to the man-pages.
I thought my network connection was glitchy and hence set rsync up for
--timeout=120 but I found out that I was actually causing the glitch
with
I thought other might benefit from this lesson learned and thought it maybe
should be added to the man-pages.
I thought my network connection was glitchy and hence set rsync up for
--timeout=120 but I found out that I was actually causing the glitch with
this script:
#! /bin/sh -
while true; do
--server --sender -lHogDtpAXrRe.iLs --numeric-ids --inplace
it loops every 60 seconds with:
select(1, [0], [], NULL, {60, 0}) = 0 (Timeout)
the listed readfd is a unix domain socket:
$ sudo readlink /proc/`pgrep rsync`/fd/0
socket:[62052357]
$ sudo lsof | grep 62052357
rsync 45
--- Comment #1 from tim.l...@alcatel-lucent.com 2010-10-27 00:31 CST
---
These bugs seem to be related (having similar error messages:
connection unexpectedly closed, broken pipe, timeout).
bug7757
with big file, rsync times out out when it should not; the
sender is still
--- Comment #5 from tim.l...@alcatel-lucent.com 2010-10-27 00:30 CST
---
These bugs seem to be related (having similar error messages:
connection unexpectedly closed, broken pipe, timeout).
bug7757
with big file, rsync times out out when it should not; the
sender is still
||FIXED
Version|2.6.9 |3.1.0
--- Comment #6 from way...@samba.org 2010-08-21 13:12 CST ---
The timeout code in 3.1.0dev is much improved over 2.x and 3.0.x. Hopefully
this will fix the issue you were seeing.
--
Configure bugmail
Eduardo Terzella (eterze...@gmail.com) wrote on 6 March 2010 21:05:
>Is there any parameter in the rsync binary that I can finish the time the
>binary should wait to start a file transfer, otherwise close the rsync
>binary. As I read the timeout is a parameter used when the conne
Is there any parameter in the rsync binary that I can finish the time the
binary should wait to start a file transfer, otherwise close the rsync
binary. As I read the timeout is a parameter used when the connection has
already been established, and when it is not, which parameter I can use
https://bugzilla.samba.org/show_bug.cgi?id=7195
Summary: timeout reached while sending checksums for very large
files
Product: rsync
Version: 3.0.7
Platform: All
OS/Version: All
Status: NEW
Severity
The timeout value actually gets doubled in 3.1 (didn't check in 3.0).
It first happens between sender and destination, producing an error
message. However in the destination one of the processes continues to
run, and only times out and exits after another timeout interval. So
in practic
On Fri, Jan 8, 2010 at 2:45 PM, Carlos Carvalho wrote:
> It seems the latest timeout changes in 3.1 work well.
>
Great to hear! It's nice to know that a 3.1.0 receiver is indeed helping to
keep things alive that used to die, even without 3.1.0 on the sending side
(which is exactly
It seems the latest timeout changes in 3.1 work well. I was having
repeated timeout aborts in a sync of large files through a very slow
connection, which made each file transfer take very long. The latest
version no longer aborts and the sync finished successfully. The
destination used version 3.1
On Fri, Dec 18, 2009 at 4:29 AM, Fabian Cenedese wrote:
> 13:18:52 write(4,
> "\367\344\356\325UUM3\273*<17\7\256D\255\225x0\345^{\203"..., 4092) = 4092
> 13:18:52 time(NULL) = 1261138732
> 13:18:52 select(5, NULL, [4], [4], {60, 0}) = 0 (Time
rn for an extended
>amount of time, and then, when rsync finally gets control back and checks for
>the elapsed time since the last received input, it is a really long amount.
I now have a trace with a timeout case (almost 300MB). What do I need to look
for? I don't see immediate
On Tue, Dec 15, 2009 at 11:41 PM, Fabian Cenedese wrote:
> I think I know now where my confusion comes from. The reported time is not
> the actual time without action but the time since the start of the rsync
> command.
>
It shouldn't be, since it is reporting the time elapsed since the last inp
At 10:27 15.12.2009 +0100, Fabian Cenedese wrote:
>Hi
>
>I already wrote about this problem half a year ago but didn't get
>an answer: http://lists.samba.org/archive/rsync/2009-June/023412.html
>
>I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1
Hi
I already wrote about this problem half a year ago but didn't get
an answer: http://lists.samba.org/archive/rsync/2009-June/023412.html
I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1800.
But still I often have rsync stall much longer than that.
Some examp
At 09:07 15.06.2009 +0200, Fabian Cenedese wrote:
>Hi
>
>I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1800.
>However sometimes I get very big timeout times like this one:
>
>io timeout after 12220 seconds -- exiting
>rsync error: timeout in data
Hi
I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1800.
However sometimes I get very big timeout times like this one:
io timeout after 12220 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(239)
[sender=3.0.3pre1]
rsynd.conf on the rece
https://bugzilla.samba.org/show_bug.cgi?id=6175
--- Comment #4 from m...@mattmccutchen.net 2009-03-08 22:03 CST ---
(In reply to comment #3)
> 3.1.0 keeps the cursor at the end of the line, so ssh can't overwrite it. Is
> there something else to fix here?
You're right. Looking at t
https://bugzilla.samba.org/show_bug.cgi?id=6175
--- Comment #3 from way...@samba.org 2009-03-08 21:52 CST ---
3.1.0 keeps the cursor at the end of the line, so ssh can't overwrite it. Is
there something else to fix here?
--
Configure bugmail: https://bugzilla.samba.org/userprefs.c
https://bugzilla.samba.org/show_bug.cgi?id=6175
--- Comment #2 from m...@mattmccutchen.net 2009-03-08 20:05 CST ---
Rsync does leave the progress line on the screen, but ssh is printing the
"Timeout, server not responding" message that overwrites it. Rsync could
simply r
https://bugzilla.samba.org/show_bug.cgi?id=6175
--- Comment #1 from ar...@maven.pl 2009-03-08 06:14 CST ---
Ah, that was "rsync -avPc".
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA conta
https://bugzilla.samba.org/show_bug.cgi?id=6175
Summary: write last transfer status when timeout or other error
happens
Product: rsync
Version: 3.0.5
Platform: Other
OS/Version: Linux
Status: NEW
Severity
. Once I used the timeout option and once I didn't.
>
> When I don't use the timeout option I don't get any error and the
> upload to the webdav server works for all files (with 2.6.9 and with
> 3.0.5), but there's a long break (I guess about 60-90 minutes)
&g
s successful synchronizing the 50 MB file. The error message
> is always like this (also when I set the timeout to eg. 7200 seconds):
>
> io timeout after 1003 seconds -- exiting
> rsync error: timeout in data send/receive (code 30) at io.c(200)
> [sender=3.0.5]
>
> the syn
always like this (also when I set the timeout to eg. 7200 seconds):
io timeout after 1003 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(200)
[sender=3.0.5]
the sync command I used:
/usr/local/bin/rsync --size-only --human-readable --progre
ss --recursive --delete
On Sun, 2008-09-28 at 19:52 +0200, Tim Newsome wrote:
> I'm currently in Egypt, and my Internet connection goes up and down a
> lot. rsync --partial --timeout is great, especially when combined with a
> little script that checks whether it failed due to timeout, and in that
>
I'm currently in Egypt, and my Internet connection goes up and down a
lot. rsync --partial --timeout is great, especially when combined with a
little script that checks whether it failed due to timeout, and in that
case starts the transfer up again. I think it would be a good feature
for rsy
https://bugzilla.samba.org/show_bug.cgi?id=5695
--- Comment #2 from [EMAIL PROTECTED] 2008-08-18 20:26 CST ---
Thank you for your reply.
3.0.4pre2 times out at an earlier point:
strace -f /tmp/rsync/rsync-3.0.4pre2/rsync -v -a -x --timeout=300 --numeric-ids
--delete --delete
https://bugzilla.samba.org/show_bug.cgi?id=5695
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from [EM
https://bugzilla.samba.org/show_bug.cgi?id=5695
Summary: rsync local timeout
Product: rsync
Version: 3.0.3
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
On Thu, May 08, 2008 at 08:59:41AM -0700, arguellodw wrote:
> rsync error: timeout in data send/receive (code 30) at
> /home/lapo/packaging/tmp/rsync-2.6.3/io.c(153)
You are reaching your idle-time timeout. Either make it larger (e.g.
--timeout=360) or upgrade to a newer rsync version th
transferred over.
--
View this message in context:
http://www.nabble.com/rsync-error%3A-timeout-in-data-send-receive-%28code-30%29-at--home-lapo-packaging-tmp-rsync-2.6.3-io.c%28153%29-tp17127523p17151640.html
Sent from the Samba - rsync mailing list archive at Nabble.com.
--
Please use reply-all for most
We are rsync'ing from an xp box running cygwin to a redhat box, using a Perl
script that fist calls for an ssh tunnel, then calls rsync through local
host.
ssh -P -f -L 8740:remote.host.ip:873 [EMAIL PROTECTED] -p 22 sleep 25
rsync -vrtz -v --timeout=180 --exclude-from=exludefiles
https://bugzilla.samba.org/show_bug.cgi?id=5071
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=5071
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #3 from [EM
https://bugzilla.samba.org/show_bug.cgi?id=5071
--- Comment #2 from [EMAIL PROTECTED] 2007-11-11 01:00 CST ---
I'm looking for connection timeout, rather than I/O timeout. When I send a SYN
and never get an ACK, it hangs until a default timeout. For example, a netstat
only
https://bugzilla.samba.org/show_bug.cgi?id=5071
--- Comment #1 from [EMAIL PROTECTED] 2007-11-11 00:47 CST ---
Isn't timeout option what you want:
--timeout=TIME set I/O timeout in seconds
If yes, I let you to close the bugs.
--
Configure bugmail:
https://bugzilla.samba.org/show_bug.cgi?id=5071
Summary: Enhancement Request - Customizable Connection Timeout
Option
Product: rsync
Version: 2.6.9
Platform: Other
OS/Version: Other
Status: NEW
Severity
||INVALID
--- Comment #1 from [EMAIL PROTECTED] 2007-10-14 16:10 CST ---
I think you're misunderstanding the --timeout option. Its purpose is to
terminate rsync if something stalls. As long as the transfer is proceeding, it
will never timeout.
See the time-limit
s. Since about one week i got the following
error:
"timeout in data send/receive (code 30) at io.c(165)"
It also indicated that i used version 2.6.8 and ibiblio used 2.6.9.
- Upgraded to 2.6.9
- Still the same error.
I used "rsync -avHS --delete --progress remote.place local.plac
Paul, did you see my last email?
Shai
On 2/5/07, Shai <[EMAIL PROTECTED]> wrote:
rsync-HEAD-20070130-0408GMT
Shai
On 2/5/07, Paul Slootman <[EMAIL PROTECTED]> wrote:
>
> On Mon 05 Feb 2007, Shai wrote:
> >
> > When I send this command, I get a timeout almost
e grief. I am running cwRsync and invoking a remote
> > rsync daemon via a shell command:
> >
> > cmd /K "rsync.exe -avr --rsh=ssh --progress --stats --delete
> > /cygdrive/d/"My Documents" [EMAIL PROTECTED]::user_data"
> >
> > I get this error loca
rsync-HEAD-20070130-0408GMT
Shai
On 2/5/07, Paul Slootman <[EMAIL PROTECTED]> wrote:
On Mon 05 Feb 2007, Shai wrote:
>
> When I send this command, I get a timeout almost every time...
The earlier versions of 3.0.0cvs gave me timeouts, but the latest
version has been running
On Mon 05 Feb 2007, Shai wrote:
>
> When I send this command, I get a timeout almost every time...
The earlier versions of 3.0.0cvs gave me timeouts, but the latest
version has been running for me for a couple of days now without any
problems whatsoever, transferring many millions of fil
Hi,
When I send this command, I get a timeout almost every time...
--- this is the client side ---
rsync -av --timeout 120 /home/bat/20070205_0501/log/sync_dns29_log
/home/bat/20070205_0501/log/sync_dns29_serial
/home/bat/20070205_0501/log/sync_dns29_tcpdump_log.gz --port 5873
fileserver::test
On 1/29/07, Alexandros Papadopoulos <[EMAIL PROTECTED]> wrote:
Wait a minute, can one use ssh at the transport and still connect to an rsync
daemon module?
Yes indeed! Rsync logs into the remote machine and executes a remote
rsync process as in plain rsync over SSH, except it tells the remote
:
>
> cmd /K "rsync.exe -avr --rsh=ssh --progress --stats --delete
> /cygdrive/d/"My Documents" [EMAIL PROTECTED]::user_data"
>
> I get this error locally:
>
> Quote:
> Timeout, server not responding
Increase verbosity (-) and show us what happens wh
drive/d/"My
Documents" [EMAIL PROTECTED]::user_data"
I get this error locally:
Quote:
Timeout, server not responding
And on the server:
Quote:
2007/01/24 11:46:18 [59320] connect from (192.168.0.110)
2007/01/24 11:46:18 [59320] rsync: connection unexpectedly closed (0
b
https://bugzilla.samba.org/show_bug.cgi?id=4232
--- Comment #4 from [EMAIL PROTECTED] 2006-11-16 00:46 MST ---
same results
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the b
https://bugzilla.samba.org/show_bug.cgi?id=4232
--- Comment #3 from [EMAIL PROTECTED] 2006-11-16 00:37 MST ---
and just now i have tried timeout = 0 on both ends
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because
Connected to clients:873, remote version 30
Negotiated protocol version 28
Connected to module www
Sending args: --server --sender --numeric-ids --perms --owner --group -D
--links --times --recursive --ignore-times . .
i have added timeout = 600 on both the client and server and same issue
|2.6.9
--- Comment #1 from [EMAIL PROTECTED] 2006-11-15 19:00 MST ---
You haven't explained how this is not due to your configuring the timeout
wrong. You should also mention what options you're using. For instance, using
--delete-during is much better wh
1 - 100 of 233 matches
Mail list logo
