similar to: error "rsync: connection unexpectedly closed (0 bytes received so far)"

Displaying 20 results from an estimated 4000 matches similar to: "error "rsync: connection unexpectedly closed (0 bytes received so far)""

2018 Dec 31
2
--partial does not "unhide" the files
Kevin Korb via rsync <rsync at lists.samba.org> (So 30 Dez 2018 23:56:44 CET): > I think --partial might be a red herring here. It only applies to what > happens when rsync is aborted in the middle of a file. What happens > without -P? Same happens w/o --partial. I append 2 logs: - a from localhost to remote server, exposing the missing "rename" - b from localhost to
2018 Dec 31
0
--partial does not "unhide" the files
I can't say I have any idea why rsync would just skip that step and I can't duplicate it myself. Your only recourse might be to use --inplace on that system. On 12/31/18 12:33 PM, Heiko Schlittermann via rsync wrote: > Kevin Korb via rsync <rsync at lists.samba.org> (So 30 Dez 2018 23:56:44 CET): >> I think --partial might be a red herring here. It only applies to what
2018 Dec 30
2
--partial does not "unhide" the files
Hi, I used --partial to transfer files from my local computer (rsync 3.1.2, Debian) to a remote computer (rsync 3.1.1 WD MyPassport Storage device) The files get transferred, but after successful transfer, the files are not renamed from .<tmpfile> to <file>. Where to go next? Here is the verbose output after transferring an empty file heiko at blade:~/Pictures$ rsync
2010 Mar 23
2
rsync: connection unexpectedly closed (0 bytes received so far)
Please forgive my digging up a two year old thread, but I've got the same problem, but the pointers there give no help. This is using versions 3.0.6 (server) and 3.0.7 (client). Unfortunately, I have to type the client stuff in by hand. ("Secured" laptop with highlighting & copying disabled.) Anyway: $ rsync -vvvvvv -a -e ssh --recursive gdoc rsync-acct at 99.99.99.99::doc
2018 Dec 30
0
--partial does not "unhide" the files
I think --partial might be a red herring here. It only applies to what happens when rsync is aborted in the middle of a file. What happens without -P? Also, it is worth trying with --inplace. On 12/30/18 5:32 PM, Heiko Schlittermann via rsync wrote: > Hi, > > I used --partial to transfer files from my local computer (rsync 3.1.2, > Debian) to a remote computer (rsync 3.1.1 WD
2020 Feb 01
1
[Bug 14260] New: leading / added to file name causing file not found when setting permissions
https://bugzilla.samba.org/show_bug.cgi?id=14260 Bug ID: 14260 Summary: leading / added to file name causing file not found when setting permissions Product: rsync Version: 3.1.3 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core
2006 Mar 30
2
DO NOT REPLY [Bug 3646] New: rsync: connection unexpectedly closed (3207118 bytes received so far) [generator]
https://bugzilla.samba.org/show_bug.cgi?id=3646 Summary: rsync: connection unexpectedly closed (3207118 bytes received so far) [generator] Product: rsync Version: 2.6.6 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:
2012 Oct 12
1
Problem rsyncing 450GB file to my NAS: 'connection unexpectedly closed'
Hi list! I'm trying to use rsync to do a regular remote backup of a 450GB sized container file located on my squeeze server onto a colocated QNap NAS device. Both use rsync 3.0.7. While this setup works for most files, it fails on this large file (see log below). I'm already trying to help rsync using "-P" to indicate that rsync should reuse the current copy and not trying
2008 Feb 16
3
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
Hi all: I am trying to transfer a file from a machine A to a machine B. I ran a rsync deamon on machine B at a given port. Because there is a firewall between these two machines, I opened the port on the firewall. Is this enough to get rsync work through firewall? When I tried the transfer, I got the following error messages. my command: rsync -a --copy-links localfile rsync:://me@<my
2005 Jul 14
1
rsync: connection unexpectedly closed (0 bytes read so far)
Hi all, in my log file (/var/log/messages) I see two error lines. I don't know their explained: Jul 14 09:12:51 vna009 rsyncd[21139]: rsync: connection unexpectedly closed (0 bytes read so far) Jul 14 09:12:51 vna009 rsyncd[21139]: rsync error: error in rsync protocol data stream (code 12) at io.c(150) My configuration file is this (/etc/rsyncd.conf): [web] path =
2006 Feb 09
2
DO NOT REPLY [Bug 3492] New: rsync: connection unexpectedly closed (24 bytes read so far)
https://bugzilla.samba.org/show_bug.cgi?id=3492 Summary: rsync: connection unexpectedly closed (24 bytes read so far) Product: rsync Version: 2.6.7 Platform: Other OS/Version: HP-UX Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org
2015 Oct 24
15
[Bug 11572] New: rsync --debug doesn't work, and gives erroneous results when taken out
https://bugzilla.samba.org/show_bug.cgi?id=11572 Bug ID: 11572 Summary: rsync --debug doesn't work, and gives erroneous results when taken out Product: rsync Version: 3.1.2 Hardware: x64 OS: Linux Status: NEW Severity: major Priority: P5 Component: core
2009 Jul 17
0
Rsync problem : stops unexpectedly
Hello. My problem is Rsync stops when I use it between 2 of my servers (2 NAS Synology) ( named "*.22*" and "*.6*" ). The problem continue... For example : _ Rsync run correctly between my server "*.22*" and ".6" ( in the 2 directions ) _ Rsync run correctly between my server ".6" and "*.8*" ( in the 2 directions ) _ Rsync *doesn't
2006 Dec 19
0
connection unexpectedly closed
Hi. I have a Windows machine (XP/SP2) which i want backup to a Linux machine (named "Pippi") using rsync. I have cwRsyncServer running on the Windows machine (10.10.10.90). When i start rsync from the Linux machine after a while rsync stops - as far as i understand it because of a network timeout. > io timeout after 60 seconds -- exiting > rsync error: timeout in data
2009 Jul 14
1
--delete not working (minimal example)
--delete option is not working for me. The following is a minimal example. $ mkdir box1 box2 $ touch box1/letter box2/extra $ rsync -a -vv box1/ box2/ sending incremental file list delta-transmission disabled for local transfer or --whole-file letter total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 92 bytes received 34 bytes 252.00 bytes/sec total size is 0 speedup is 0.00 $ tree
2002 Apr 15
2
Suddenly broken : connection unexpectedly closed
I always got this messages when I rsync to php.net here's my command line and error messages : $ rsync -avvvzC rsync.php.net::phpweb /usr/local/WWW/phpweb generator(distributions/manual/php_manual_cs.tar.bz2,1405) sending sums for 1405 rsync: connection unexpectedly closed (1954742 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150)
2002 Aug 30
1
rsync: connection unexpectedly closed; reverse lookups?
Hi. My goal is to use rsync to syncronize box1 and box2. On box2, I have a tapedrive which I write the data I syncronize from box1 every night. On box1, my /etc/rsyncd.conf looks like this: root@box1# cat /etc/rsyncd.conf max connections = 1 syslog facility = local6 [tmp] path = /tmp read only = yes comment = export of /tmp hosts allow = box2 auth users
2004 Aug 05
0
[Bug 1582] New: rsync dry run cannot find missing folders, contradicts actual run.
https://bugzilla.samba.org/show_bug.cgi?id=1582 Summary: rsync dry run cannot find missing folders, contradicts actual run. Product: rsync Version: 2.6.2 Platform: All OS/Version: IRIX Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org
2018 Jan 09
0
[Bug 13207] New: rsyncd doesn't send output of failed pre-xfer exec script to client
https://bugzilla.samba.org/show_bug.cgi?id=13207 Bug ID: 13207 Summary: rsyncd doesn't send output of failed pre-xfer exec script to client Product: rsync Version: 3.1.1 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core
2003 Jul 24
0
(no subject)
Here is a diff which should allow applying batch updates remotely ( as apposed to copying the batch files to the remote server and running rsync there ). Eg rsync --write-batch=test src dst1::dst rsync --read-batch=test dst2::dst Oli Dewdney diff -E -B -c -r rsync-2.5.6/flist.c rsync-2.5.6-remotebatch/flist.c *** rsync-2.5.6/flist.c Sat Jan 18 18:00:23 2003 ---