I want to recognize and handle some rsync error messages
in my log files (containing also the --itemize-changes output)
on different computers with different language/locale settings.
Can I rely on rsync to create only English error messages
to have a stable pattern to recognize?
PS: In the
Hi, folk.
I got some problem when running this command on client side:
# rsync -avPH --chown=root:wheel --chmod=D755,F644 --delete --exclude
ads --exclude backup rsync://192.168.0.100/data /mnt/DATA
receiving incremental file list
Invalid dir index: -826 (-101 - -825) [receiver]
rsync error
Hi,
Heiko Schlittermann via rsync (Mi 20 Okt 2021 10:56:51
CEST):
> Hello,
>
> we're using rsync on SLES 12 SP 5 on both sides (for detailed version
> info see below) and we're experiencing the following issue on the
> sender's side:
…
> deflate on token retur
Hello,
we're using rsync on SLES 12 SP 5 on both sides (for detailed version
info see below) and we're experiencing the following issue on the
sender's side:
```
etc/test/windows2019_x86_64_20210929.gz
deflate on token returned 0 (22199 bytes left)
rsync error: error in rsyn
On 25/06/2020 13:18, Madhurananda Pahar via rsync wrote:
> Hello everybody,
>
> I am having a funny problem while using rsync as a tool to
> back-up my files:
>
> [sender] expand file_list pointer array to 524288 bytes, did move.
>
> I am just wondering if you had this issue before an
Hello everybody,
I am having a funny problem while using rsync as a tool to back-up
my files:
[sender] expand file_list pointer array to 524288 bytes, did move.
I am just wondering if you had this issue before and if you know a way to
solve this, please share with me.
Many thanks,
Dr.
> You should not be using rsync's --checksum during routine backups.
you know that excel can change a file`s contents without changing a file`s
timestamp - do you? ;)
> Gesendet: Donnerstag, 09. April 2015 um 18:37 Uhr
> Von: "Kevin Korb"
> An: rsync@lists.samba.org
es via rsyncd, with
> enabled checksums. Whith one of the shares I get the error (in
> syslog):
> -
>
>
robbe rsyncd[2183]: ERROR: out of memory in receive_sums [sender]
> robbe rsyncd[2183]: rsync error: erro
bbe rsyncd[2183]: rsync error: error allocating core memory buffers
(code 22) at util2.c(106) [sender=3.1.2dev]
robbe rsyncd[9821]: connect from elefant.control.local (192.168.1.200)
robbe rsyncd[9821]: rsync on . from backuppc@elefant.control.local
about? I keep getting this
> message once in a while after my rsync command is run for some
> time.
>
> rsync error: unexplained error (code 255) at rsync.c(541)
> [sender=3.0.4]
>
> Regards
>
> Jerry
>
>
Does anyone know what this message is about? I keep getting this message
once in a while after my rsync command is run for some time.
rsync error: unexplained error (code 255) at rsync.c(541) [sender=3.0.4]
Regards
Jerry
HSBC Global
eSATA HDD (i.e. sender and receiver are the same host
communicating via pipes).
rsync: writefd_unbuffered failed to write 5 bytes to socket [sender]: Broken
pipe (32)
rsync: connection unexpectedly closed (209441 bytes received so far) [sender]
rsync error: error allocating core memory buffers
https://bugzilla.samba.org/show_bug.cgi?id=6183
--- Comment #5 from Dal 2011-06-01 07:58:01 UTC ---
The issue happens intermittently. Most of the time large files are sync'd fine.
I have run rsync on the failed file several times now and it hasn't failed. Is
there any debugging I can put in place
https://bugzilla.samba.org/show_bug.cgi?id=6183
Wayne Davison changed:
What|Removed |Added
Status|ASSIGNED|NEEDINFO
--- Comment #4 from Wayne Davison
https://bugzilla.samba.org/show_bug.cgi?id=7765
--- Comment #2 from nvbolh...@aimvalley.nl 2010-10-29 08:40 CST ---
aha!
I tried many things to avoid the error, but forgot to try
the rsync option --exclude messages*
thanks for the quick response!
and btw. rsync is great (we used to
https://bugzilla.samba.org/show_bug.cgi?id=7765
--- Comment #1 from m...@mattmccutchen.net 2010-10-29 08:36 CST ---
(In reply to comment #0)
> skipping daemon-excluded file "messages"
> skipping daemon-excluded file "messages.0"
Here's your error. The client wanted to push those fil
https://bugzilla.samba.org/show_bug.cgi?id=7765
Summary: rsync error 23 without any real error
Product: rsync
Version: 3.0.7
Platform: PPC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=4232
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=6461
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
Hi,
Please try this patch below, I think it’ll solve the bug…
Amir
diff -U 5 -Nuir rsync-3.0.4/cleanup.c rsync-3.0.4.new/cleanup.c
--- rsync-3.0.4/cleanup.c 2008-06-04 19:01:02.0 +0300
+++ rsync-3.0.4.new/cleanup.c 2009-03-29 09:45:04.0 +0300
@@ -98,11 +98,11 @@
https://bugzilla.samba.org/show_bug.cgi?id=6461
--- Comment #1 from james.pur...@ny.frb.org 2009-06-10 09:03 CST ---
I should mention that we are using rsync in conjunction with ssh. Please let
me know if there are additional details you would like.
--
Configure bugmail: https://b
https://bugzilla.samba.org/show_bug.cgi?id=6461
Summary: rsync occassionally issues the message "rsync error:
unexplained error (code 255) at main.c(1506)
[generator=3.0.4]"
Product: rsync
Version: 3.0.4
Hi, we have been getting this errors frequently.
ERROR: DoRsync(): rsync had errors or failed
rsync return code: 12
unexpected tag -7
rsync error: error in rsync protocol data stream (code 12) at
io.c(469)
rsync: connection unexpectedly closed (7087269 bytes read so
far
https://bugzilla.samba.org/show_bug.cgi?id=5811
mark.mathie...@concepts.co.nz changed:
What|Removed |Added
CC||mark.mathie...@concepts.co.n
24442-01_1of3.zip": File too large
(27)
rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.5]
rsync: connection unexpectedly closed (10306 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(600)
[sender=3.0.5]
real3m3
Hi I'm using rsync (ver 3.0.5) to sync a local folder with a folder on a
server using SSH and encrypted key files. It works fine on Windows
2000/XP/2003/Vista but not Windows 2008 Server.
I get an error like the following:
"ssh _cygtls::handle_exceptions Error while dumping state (probably
https://bugzilla.samba.org/show_bug.cgi?id=6183
--- Comment #2 from way...@samba.org 2009-03-13 12:11 CST ---
"File too large" is an OS error, so you need to figure out why your OS is
returning that. I'd imagine that rsync was not compiled with large-file
support. If so, let me know
https://bugzilla.samba.org/show_bug.cgi?id=6183
--- Comment #1 from bros...@gmail.com 2009-03-11 11:38 CST ---
Justed tested using rsync 3.0.2, and it works fine (same file, same servers)
so the problem occursd using rsync 3.0.4
--
Configure bugmail: https://bugzilla.samba.org/use
https://bugzilla.samba.org/show_bug.cgi?id=6183
Summary: rsync error file too large (27)
Product: rsync
Version: 3.0.4
Platform: Other
OS/Version: AIX
Status: NEW
Severity: normal
Priority: P3
Component
rsync error on two test www.dwhs.net servers
rsync error: error in rsync protocol data stream (code 12) at io.c(359)
Also both of these two servers have locked out all root access remitly. I
dont think they have been hacked, but I can seem to get access without going
in single user and adding a
On Tue, Jan 20, 2009 at 03:25:05PM +0530, Jignesh Shah wrote:
> In "rsync return code: 12" error, what 12 indicates?
The error code is pretty inconsequential compared to the errors that
come before it. See what rsync is actually complaining about, and make
sure you know if there is an issue with
On Tue, Jan 20, 2009 at 10:16:37AM +, Stuart Halliday wrote:
> I suggest that this may be caused by you using two different versions of
> Rsync? Please check that the daemon and client are running the same version.
The only known issues of cross-version incompatibility have been fixed.
If you
I'd recommend that you do a search on the failing systems for duplicate or
old copies of Rsync. It just takes a PATH variable to include another old
copy of rsync to make it fail.
I'd also check your firewall or router aren't the problem. If you need to,
temporary disable the firewall or any AV so
;>> >
>>> > This at least shows you if the connection and rsync is working.
>>> >
>>> > ie
>>> >
>>> > rsync -v metatex.org::minimals-temp/test/
>>> >
>>> > or
>>> >
>>> > rsync /cygdrive/c/
>>> >
&
ows you if the connection and rsync is working.
>> >
>> > ie
>> >
>> > rsync -v metatex.org::minimals-temp/test/
>> >
>> > or
>> >
>> > rsync /cygdrive/c/
>> >
>> >
>> > --
>> > Stuart Hallida
nc /cygdrive/c/
> >
> >
> > --
> > Stuart Halliday
> >
> >
> >
> > -Original Message-
> > From: Jignesh Shah
> > To: Stuart Halliday
> > Date: Tue, 20 Jan 2009 16:18:25 +0530
> > Subject: Re: find out the meaning of rsync
/
--
Stuart Halliday
-Original Message-
From: Jignesh Shah
To: Stuart Halliday
Date: Tue, 20 Jan 2009 16:18:25 +0530
Subject: Re: find out the meaning of rsync error code
> Thanks Sven and Stuart for reply.
>
> They both are running at the same version 2.6.0 but still
-Original Message-
From: Jignesh Shah
To: rsync@lists.samba.org
Date: Tue, 20 Jan 2009 15:25:05 +0530
Subject: find out the meaning of rsync error code
> Hi,
>
> Could anyone please tell me how to get the meaning of rsync error
> codes.
>
> In "rsync return c
Tue, 20 Jan 2009 15:25:05 +0530, jignesh.shah1980 wrote:
> Could anyone please tell me how to get the meaning of rsync error codes.
>
> In "rsync return code: 12" error, what 12 indicates?
Please use the archive:
http://www.mail-archive.com/rsync@lists.samba.org/msg22890.html
Hi,
Could anyone please tell me how to get the meaning of rsync error codes.
In "rsync return code: 12" error, what 12 indicates?
Thanks,
Jignesh
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.o
I have some general remarks about the problem; I hope Wayne will have
more specific ideas on how to debug it.
On Sun, 2009-01-11 at 13:33 +0100, Ernst J. Oud wrote:
> rsync -vrpth --stats --progress --log-file=/nslu2/rsync.log
> --log-file-format="%t %i %n%L"
> --include-from=/nslu2/rsync-files /s
L.S.
I hope someone can enlighten me on the following phenomenon.
When I run rsync (3.0.2 or 3.0.4) from a (SH) script as follows:
rsync -vrpth --stats --progress --log-file=/nslu2/rsync.log
--log-file-format="%t %i %n%L" --include-from=/nslu2/rsync-files
/share/hdd/data/public/Ernst/ 192.168.
https://bugzilla.samba.org/show_bug.cgi?id=5811
--- Comment #8 from [EMAIL PROTECTED] 2008-11-04 11:34 CST ---
btw.
the first initial run was done with rsync 3.0.4 on that debian from ext2 fs to
ntfs-3g fs, which is now residing in a windows 2003 r2 and accessed with cygwin
1.7 cygdr
https://bugzilla.samba.org/show_bug.cgi?id=5811
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
more .. it reduces to a warning in the end
rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1058) [sender=3.0.4]
and I can see all the problematic files with entries like
[receiver] cannot convert filename: /CD1/(13) Kâ
as incomplete multibyte chars are
was to rename all files that where tagged with the
rsync error message "Invalid or incomplete multibyte or wide character". As
data came from windows i assume that there was some characters that rsync was
unable to recognize.
Regards.
--
Configure bugmail: https://bugzilla
https://bugzilla.samba.org/show_bug.cgi?id=5811
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
FL-Urs Von Stockar/Intro/Sources dessins/Biotechn-Sanduhr â
copie/FINDER.DAT (Invalid or incomplete multibyte or wide character)
rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1040) [sender=3.0.4]
pc-imac-mj:~ ug$ cat error.log
building file list
https://bugzilla.samba.org/show_bug.cgi?id=5811
--- Comment #2 from [EMAIL PROTECTED] 2008-10-15 09:05 CST ---
Hello,
Sorry the error message indeed came from the 3.0.3, i actually faced the
problem with the 3.0.4. It seems that the problem is solved with using
"--delete-after" inste
of host 'myProject.cvs.sourceforge.net
> > (216.34.181.109)' can't be established.
> > RSA key fingerprint is
> > dc:a3:df:84:00:c6:65:b4:93:a6:2e:22:b1:d1:91:b8.
> > Are you sure you want to continue connecting (yes/no)?
> rsync
y fingerprint is
> dc:a3:df:84:00:c6:65:b4:93:a6:2e:22:b1:d1:91:b8.
> Are you sure you want to continue connecting (yes/no)? rsync: failed
> to connect
> to localhost: Connection refused (111)
> rsync error: error in socket IO (code 10) at clientserver.c(122)
> [sender=3.0.4]
&g
to
connect
to localhost: Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(122)
[sender=3.0.4]
Terminating secure channel ...
Thanks,
Naveen S
--
Please use reply-all for most replies to avoid omitting the mailing lis
https://bugzilla.samba.org/show_bug.cgi?id=5811
--- Comment #1 from [EMAIL PROTECTED] 2008-10-09 12:10 CST ---
I do not see how you could get that message with an rsync 3.0.4 client because
io.c line 635 is in a comment. It would make sense if the client were 3.0.3,
because in rsync
https://bugzilla.samba.org/show_bug.cgi?id=5811
Summary: rsync error: error allocating core memory buffers (code
22) at io.c(635)
Product: rsync
Version: 3.0.4
Platform: x64
OS/Version: Linux
Status: NEW
On Wed, 2008-08-27 at 10:45 -0700, [EMAIL PROTECTED] wrote:
> Thank you for your response Matt.
> On the source server, "/snapshots/fs/tce_data/pc-software/pc" is a symlink
> to the directory "/snapshots/fs/tce_data/pc".
>
> On the destination server,
> "/drp/fmttcesrv1/snapshots/fs/tce_data/pc-so
Available cc
rsync@lists.samba.org
Subject
08/
On Tue, 2008-08-26 at 16:29 -0700, [EMAIL PROTECTED] wrote:
> Regarding "rsync error code 23" could the below "delete_file: ...file
> exist" failures cause the error code 23? Or, how can I resolve this as
> these are the only errors I see in the log files.
> Thank
Regarding "rsync error code 23" could the below "delete_file: ...file
exist" failures cause the error code 23? Or, how can I resolve this as
these are the only errors I see in the log files.
Thank you!
START Tue Aug 26 11:10:12 PDT 2008
/home/filerep/bin/rsync -e /var/opens
https://bugzilla.samba.org/show_bug.cgi?id=5418
--- Comment #3 from [EMAIL PROTECTED] 2008-07-21 02:30 CST ---
Sorry, I meant to refer to bug 5541.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are
https://bugzilla.samba.org/show_bug.cgi?id=5418
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=5418
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from [EM
[5], left {60, 0})
read(5, "rsync error: timeout in data sen"..., 84) = 84
time(NULL) = 1212802417
write(2, "rsync error: timeout in data sen"..., 83) = 83
write(2, "\n", 1) = 1
select(6, [5], [], NULL, {60, 0})
On Fri, Jun 06, 2008 at 04:14:45PM -0300, Manuel Kissoyan wrote:
> This is the one from the server where we are running the rsync command
> and where we backup the other server:
That's just the client. You also need to see what the server is doing.
You should attach to all 3 rsync processes, 2 on
, 8) = 0
rt_sigaction(SIGUSR2, {SIG_IGN}, NULL, 8) = 0
waitpid(18568, 0xbff58a18, WNOHANG) = -1 ECHILD (No child processes)
getpid()= 18567
kill(18568, SIGUSR1)= -1 ESRCH (No such process)
kill(18569, SIGUSR1) = -1 ESRCH (No
advance!
Manuel
Wayne Davison wrote:
On Wed, Jun 04, 2008 at 05:25:06PM -0300, Manuel Kissoyan wrote:
rsync error: timeout in data send/receive (code 30) at io.c(233)
[sender=3.0.0pre2]
Are you using a --timeout option or a timeout parameter in a daemon
config? If so, try
On Wed, Jun 04, 2008 at 05:25:06PM -0300, Manuel Kissoyan wrote:
> rsync error: timeout in data send/receive (code 30) at io.c(233)
> [sender=3.0.0pre2]
Are you using a --timeout option or a timeout parameter in a daemon
config? If so, try increasing that value. If not, you should check
er servers
geting the files from those servers.
One of these servers crashed a week before and we restored it, since
then the rsync that connect to this server is giving the following
erro after it get some files:
rsync error: timeout in data send/receive (code 30) at io.c(233)
[sender
giving the following erro
after it get some files:
rsync error: timeout in data send/receive (code 30) at io.c(233)
[sender=3.0.0pre2]
_exit_cleanup(code=30, file=io.c, line=233): about to call exit(30)
rsync: connection unexpectedly closed (83654700 bytes received so far)
[receiver]
rsync
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
rsync://localhost:8740/
==
This has worked for quite a while on a daily cron job. We can still open
the ssh tunnel without any problem. After the tunnel is open and we run
rsync, we get the following error messages:
rsync error: timeout in data
https://bugzilla.samba.org/show_bug.cgi?id=5418
Summary: rsync error: error allocating core memory buffers (code
22)
Product: rsync
Version: 3.0.2
Platform: Other
OS/Version: AIX
Status: NEW
Severity
On Thu, Apr 17, 2008 at 12:57:27PM -0600, Kenneth Seal wrote:
> I have tried running my script in verbose mode -vv but I really don't
> want to read all 1000+ lines of output to look for the error code.
Errors should be output to stderr, and it isn't required that you have
even one -v specified to
Hi,
Is it possible to log rsync error messages and read them in console
(Mac OS 10.5 Utility), or perhaps a text file? I have tried running my
script in verbose mode -vv but I really don't want to read all 1000+
lines of output to look for the error code.
Currently my script
On Tue, 2008-04-08 at 21:27 -0600, Kenneth Seal wrote:
> In my case, rsync displays the error code "rsync error: some files
> could not be transferred (code 23)" and it kills my script. Do you
> have any advice on how would I go about writing, researching etc. a
> s
On Apr 8, 2008, at 11:27 PM, Kenneth Seal <[EMAIL PROTECTED]> wrote:
Hi Wayne,
I read your thread online at http://lists.samba.org/archive/rsync/2005-June/012847.html
and I am having a similar problem.
In my case, rsync displays the error code "rsync error: some files
c
Hi Wayne,
I read your thread online at http://lists.samba.org/archive/rsync/2005-June/012847.html
and I am having a similar problem.
In my case, rsync displays the error code "rsync error: some files
could not be transferred (code 23)" and it kills my script. Do you
have any
On Fri, 4 Apr 2008 17:11:25 +0530 "Kaushal Shriyan"
<[EMAIL PROTECTED]> wrote:
> hi steven
>
> I am getting the below error now
>
> building file list ... rsync: pop_dir "/root" failed: Permission
> denied (13) rsync error: errors selecting input/o
tebin.com/d4b062d28 and the roots cron
> > entry are as below
> >
> > 30 2 * * * su sms /usr/local/bin/testrsync_mysql.sh
> >
> > I am getting the below error
> >
> > building file list ... rsync: opendir "/var/lib/mysql/wordpress"
> > failed: P
ilding file list ... rsync: opendir "/var/lib/mysql/wordpress"
failed: Permission denied (13) done mysql/ib_logfile0
mysql/ib_logfile1
Killed by signal 2.
rsync error: unexplained error (code 255) at rsync.c(276) [sender=2.6.9]
Any clue as what is happening
===
ile0
mysql/ib_logfile1
Killed by signal 2.
rsync error: unexplained error (code 255) at rsync.c(276) [sender=2.6.9]
Any clue as what is happening
Thanks and Regards
Kaushal
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.cat
> disk. It is started with the parameters
> --iconv=. what I suggest is the solution for syncing the attached file.
>
> log output in /var/log/messages
> received request to transfer non-regular file: 1706 [sender]
> rsync error: protocol incompatibility (code 2) at rsync.c(297)
https://bugzilla.samba.org/show_bug.cgi?id=5221
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=5221
--- Comment #1 from [EMAIL PROTECTED] 2008-01-23 01:03 CST ---
Rsync prints the "code 23" message at the end of the run when at least one
non-fatal error occurred that may have affected the correctness of the run.
Rsync should have prin
https://bugzilla.samba.org/show_bug.cgi?id=5221
Summary: rsync error: partial transfer (code 23) at main.c(576)
Product: rsync
Version: 2.6.3
Platform: Sparc
OS/Version: SunOS
Status: NEW
Severity: major
Priority
starts here:
write failed on IBMIHS/logs/access.log : Error 0
Received signal 30. (no core)
rsync: writefd_unbuffered failed to write 4092 bytes: phase "unknown":
Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(515)
Error ends here.
The IBMIHS is under
On Wed, 2007-11-28 at 02:29 -0800, Johan Huysmans wrote:
> I noticed it is working with the rysnc-3.0.0-pre5, or at least the protocol
> of it. Is it possible to use that protocol for the curren stable release.
No, the protocol is new in rsync-3.0.0* .
Matt
--
To unsubscribe or change options:
client side:
> rsync: writefd_unbuffered failed to write 4092 bytes [generator]:
> Connection reset by peer (104)
> rsync error: error in rsync protocol data stream (code 12) at io.c(1122)
> [generator=2.6.9]
> rsync error: received SIGUSR1 (code 19) at main.c(1182) [receiver=2.6.9]
>
Hello,
there are problems syncing files with special charcters in the filename.
The special characters in the filename are displayed as a question mark.
During synchronization, the rsync tells the file is vanished.
Here is the standard output with level 1 verbosity. Higher verbosity
levels dont g
On Thu, 2007-11-15 at 19:37 +0100, Wesley W. Terpstra wrote:
> On Nov 15, 2007, at 10:55 AM, Morgan Read wrote:
> > Can anyone help me with the following error - is it serious; is the
> > file
> > transferred; are the other files transferred?
>
> The file is transferred as are the other files.
>
On Thu, 2007-11-15 at 11:31 +0100, Daniel Maher wrote:
> On Thu, 2007-11-15 at 22:55 +1300, Morgan Read wrote:
>
> > [EMAIL PROTECTED] ~]$ rsync -a -X -A -z -v /home/morgan/Documents
> > 192.168.1.30:/home/morgan/Documents
> > [EMAIL PROTECTED]'s password:
> > building file list ... done
> > rsyn
On Thu, 2007-11-15 at 11:31 +0100, Daniel Maher wrote:
> On Thu, 2007-11-15 at 22:55 +1300, Morgan Read wrote:
>
> > [EMAIL PROTECTED] ~]$ rsync -a -X -A -z -v /home/morgan/Documents
> > 192.168.1.30:/home/morgan/Documents
> > [EMAIL PROTECTED]'s password:
> > building file list ... done
> > rsyn
On Thu, 2007-11-15 at 19:37 +0100, Wesley W. Terpstra wrote:
> On Nov 15, 2007, at 10:55 AM, Morgan Read wrote:
> > Can anyone help me with the following error - is it serious; is the
> > file
> > transferred; are the other files transferred?
>
> The file is transferred as are the other files.
>
On Nov 15, 2007, at 10:55 AM, Morgan Read wrote:
Can anyone help me with the following error - is it serious; is the
file
transferred; are the other files transferred?
The file is transferred as are the other files.
However, rsync probably gives a non-zero exit status.
lsetxattr("Documents/P
xal_set:
lsetxattr("Documents/Projects/CBT/SH20/HearingSubmission/ManukauBridgeSubCBT_PostPatrick_3_2.doc","user.Beagle.Uid")
failed: Permission denied (13)
sent 1572135 bytes received 20 bytes 89837.43 bytes/sec
total size is 2063655599 speedup is 1312.63
rsync erro
whoops forgot to mention the error i receive ;)
This message appears on the client side:
rsync: writefd_unbuffered failed to write 4092 bytes [generator]:
Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(1122)
[generator=2.6.9]
rsync error
At 11:57 15.11.2007 +0100, you wrote:
>Hi All,
>
>I have a problem when transferring files from a rsyncd. This is my setup:
What is the error you get?
bye Fabi
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/f
On Thu, 2007-11-15 at 22:55 +1300, Morgan Read wrote:
> [EMAIL PROTECTED] ~]$ rsync -a -X -A -z -v /home/morgan/Documents
> 192.168.1.30:/home/morgan/Documents
> [EMAIL PROTECTED]'s password:
> building file list ... done
> rsync: rsync_xal_set:
> lsetxattr("Documents/Projects/CBT/SH20/HearingSu
Hi All,
I have a problem when transferring files from a rsyncd. This is my setup:
* server: runs rsyncd on port 873.
* firewall: forwarding for the 873 port from outside (using SNAT and DNAT).
* client: manually running rsync command using modules.
The problem occurs when lots of small identica
~ no space was detected and reported.
rsync error: error in file IO (code 11) at receiver.c(298)
[receiver=3.0.0pre5]
rsync: connection unexpectedly closed (27 bytes received so far)
[sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(601)
[sender=3.0.0pre5]
_exit_clean
1 - 100 of 332 matches
Mail list logo
