Hi Wayne,I am getting the "unexpected tag 3" error quite often when pushing using 2.6.8CVS on cygwin /WinXP to 2.6.8CVS on Linux over SSH (no daemon).The CVS version is pre tag-3.patch that you had posted.
I can compile with this patch on both sides (using cygwin on the client).However from the pre
On Fri, Jul 21, 2006 at 12:22:24PM +0200, Julian Pace Ross wrote:
> However from the previous mails it is not clear what is causing this and
> whether the patch is required on the server, client or both.
It is the receiving side that causes the tag-3 error (the generator,
to be specific). So, if
gument (22)
*** Skipping everything below this failed directory ***
sent 66340 bytes received 22 bytes 574.56 bytes/sec
total size is 5531245572 speedup is 83349.59
rsync error: some files could not be transferred (code 23) at main.c(791)
and it doesn't backup all "Document and Settings&
On Wed, May 03, 2006 at 11:58:07AM +1000, Anthony Sadler wrote:
> unexpected tag 3 [sender]
My analysis shows that some deferred messages (which are those that
arrive in the generator when the generator is already trying to flush a
partial message down the socket) are not being handled by rwrite()
On Wed, May 03, 2006 at 11:58:07AM +1000, Anthony Sadler wrote:
> Notice /etc/localtime not being able to open?
That happens because you're using "use chroot = yes". When rsync is
running inside a chroot jail, it cannot access files that exist outside
the rsync module's path.
Rsync attempts to
Trying to rsync between win2k machines.
rsync version is 2.5.3pre (downloaded today)
This is the message after 368100 files have been checked:
rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
My cmdline is :
c:\sbin\rsync\rsync -az /cygdrive/d/Home
[EMAIL PROTECTED
Hi
there!
I am having a
problem having a Solaris 9 box retrieveing files from a OpenBSD 2.9 box. The
both have rsync 2.5.5 protocol version 26. They were compiled using gcc 2.95.3.
Everythings goes until it tries to disconnect:
receiving file list
... donewrote 16 bytes read 28412 by
shing local data to a remote rsync backup server:
>
> ---[snip]---
> # rsync -a -v --modify-window=2 /backup/Source/Dir/
> [EMAIL PROTECTED]::backup/dest
> Password:
> building file list ... rsync: writefd_unbuffered failed to write 4092
> bytes: phase "send_file_entry&quo
On Mon, 16 Jun 2003 at 16:24:25 -0700, jw schultz wrote:
>
> > After looking at io.c, it seems like the problem (rather, the symptom)
> > for
> > this error message is a failed write() call (which explains the Broken
> > Pipe message to stderr). I thought maybe --blocking-io would avoid this
> > i
On Tue, Jun 17, 2003 at 09:10:38AM -0500, Nathaniel Case wrote:
> On Mon, 16 Jun 2003 at 16:24:25 -0700, jw schultz wrote:
> >
> > > After looking at io.c, it seems like the problem (rather, the symptom)
> > > for
> > > this error message is a failed write() call (which explains the Broken
> > > Pi
8:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] inflate returned -3 (0
bytes)
Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] rsync error: error in
rsync protocol data stream (code 12) at ../token.c(416)
Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] rsync: conn
ckup server using rsyncd. Almost every night I see the following errors
> logged on the rsyncd server:
>
> Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] inflate returned -3
> (0 bytes)
> Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] rsync error: er
Just for the record, the patch to token.c for the -z bug that was
discovered by Yasuoka Masahiko and patched by him and Wayne Davison
has fixed the problem that I reported here:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg07289.html
Thanks guys, this bug has been biting me for the past 6
fd = 103
(1013) rsync error: error in socket IO (code 10) at io.c(423)
Trying to sync a directory between two NW 5.1 Sp6 server.
Any suggestions are welcome
thanks a lot
Marcus
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http
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
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=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
--- 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
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
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
Settings_Administrator_Local Settings_Application Data_Microsoft_Windows):
Device or resource busy (16)
rsync: send_files failed to open "ion
Data/Microsoft/Windows/UsrClass.dat.LOG" (in C:_Documents And
Settings_Administrator_Local Settings_Application Data_Microsoft_Windows):
Device or resource busy (
Hi there
I am running rsync-2.6.9rc2 and am having difficulty getting rsync to
report an error when I think it should
I mounted (via "mount -t cifs") a remote Win2K3 server and on a XP
client opened a Word document. Then from Linux (FC5) I attempted a
bash$ cp /tmp/other.txt file.doc
cp: cannot
Hi there
I just reported a problem to the rsync list, and a minute later realised
a further test I should have tried first.
Basically it appears that "mount -t cifs" SMB shares under Linux don't
properly report low-level rename failures.
i.e. if I use rsync to overwrite a locked file rsync thin
Hi,
I am encountering a error saying-rsync error: received SIGUSR1 or SIGINT
(code 20) at rsync.c(229).
This error was encountered after 2.5hrs of rsync. What does this exactly
mean?
I am pretty new the whole concept so not able to figure it out.
Regards,
Madhavan Chari
--
To unsubscribe or
On Wed, Jul 04, 2007 at 03:36:35PM +0200, Peppe La Rosa wrote:
> and it doesn't backup all "Document and Settings" directory !!!
That's not what it said. The name of the directory is apparently this:
Documents and Settings\Amministratore\Desktop
So, it looks like you've got at least one strange
On 7/4/07, Wayne Davison <[EMAIL PROTECTED]> wrote:
On Wed, Jul 04, 2007 at 03:36:35PM +0200, Peppe La Rosa wrote:
> and it doesn't backup all "Document and Settings" directory !!!
That's not what it said. The name of the directory is apparently this:
Documents and Settings\Amministratore\Desk
wayned at samba.org wrote:
> On Wed, Jul 04, 2007 at 03:36:35PM +0200, Peppe La Rosa wrote:
>
> > and it doesn't backup all "Document and Settings" directory !!!
> >
>
> That's not what it said. The name of the directory is apparently this:
>
> Documents and Settings\Amministratore\Desktop
>
On Tue, Feb 12, 2002 at 01:18:49PM +0100, Rönnblom Janåke /Teknous wrote:
>
> Trying to rsync between win2k machines.
>
> rsync version is 2.5.3pre (downloaded today)
>
> This is the message after 368100 files have been checked:
> rsync error: received SIGUSR1 or SIGINT
"Known to have problems" list.
-Forwarded Message-
From: Bill Geddes <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: rsync: error writing unbuffered bytes - exiting:Connection reset by peer
Date: 13 Jun 2002 09:38:56 -0600
Has anyone figured out what is happening
fer overflow in receive_file_entry
rsync error: error allocating core memory buffers (code 22) at util.c(238)
ns1: /acct/peter>
How can I trace what is causing the problem? The filesystem I am trying to
copy has about 6000+ file in it.
Thanks
--
Peter Dominguez
72 Belvedere Dr
Yonkers, NY 10705-28
;==cut==>>
Password:
building file list ...
1 file to consider
110mb_file.mov
rsync: error writing 4 unbuffered bytes - exiting: Connection reset by peer
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
<<==cut==>>
after starting the transfer I monitored it wi
2003 Andrew Tridgell, Paul Mackerras, Martin Pool
>(1013) read_timeout: Error peer socket closed fd = 103
> (1013) rsync error: error in socket IO (code 10) at io.c(423)
>
> Trying to sync a directory between two NW 5.1 Sp6 server.
> Any suggestions are welcome
> thanks
I am using rsync to backup a machine with a large number of files, and I
am getting this error.
It would be helpful to know which files this is occuring with, to diagnose
the problem.
Is there a configuration option to rsync (that I may have missed) that
will reveal this info.
Alternatively, is
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
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
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
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
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
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
--- 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
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
>
>
On Thu, Jun 16, 2005 at 08:49:54PM +0530, [EMAIL PROTECTED] wrote:
> Is there any way to ignore these errors when i do file transfer using
> rsync?
What do you mean by ignore? They're just warnings, so rsync ignores
them already for most things, just not deletions that happen after the
warnings (
Thanks Wayne.. Your mail answered my query perfectly..
-sanal
On Thu, Jun 16, 2005 at 08:49:54PM +0530, [EMAIL PROTECTED]
wrote:
> Is there any way to ignore these errors when i do file transfer using
> rsync?
What do you mean by ignore? They're just warnings, so rsync ignores
them already for
On Thu, Oct 19, 2006 at 03:28:56PM +1300, Jason Haar wrote:
> bash$ rsync /tmp/other.txt file.doc
> bash$ echo $?
> 0
Re-run the same command under strace:
strace rsync -av /tmp/other.txt file.doc
That will show you the rename() call that rsync is making and what the
return value is. If it is
Wayne Davison wrote:
> On Thu, Oct 19, 2006 at 03:28:56PM +1300, Jason Haar wrote:
>
>> bash$ rsync /tmp/other.txt file.doc
>> bash$ echo $?
>> 0
>>
>
> Re-run the same command under strace:
>
> strace rsync -av /tmp/other.txt file.doc
>
>
Too late - I bet you to it :-) I just replied
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
rashing
and the machine has 256MB and does nothing besides being subject to my
rsync testing.
However I did another test with 2.5.3pre and this is what i got on the
client:
rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
and on the server:
select(4, [3], NULL,
[EMAIL PROTECTED] skriver:
>
>
>Ah, that strace was quite helpful and showed a real error message which is
>somehow getting lost. The overflow message comes from
>receive_file_entry()
>in flist.c and appears to be because the filename that's coming next is
>too
>long, greater than around MAXPATHL
Hello,
I am getting the following error:
| rsync: open connection using rsh conn /usr/bin/rsync --server --sender
-v . "/home/andrewm/test-rsync/tree/*"
| large_file2
| write failed on large_file2 : Success:06
| rsync error: error in file IO (code 11) at receiver.c(271)
| rsync:
t asks for password, starts to transfer the file, and at about 80% gives me
> this error message:
>
> <<==cut==>>
> Password:
> building file list ...
> 1 file to consider
> 110mb_file.mov
> rsync: error writing 4 unbuffered bytes - exiting: Connection reset b
.rh90.i386.rpm
rsync: error writing 4 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
I'm using rsync-2.5.5-4 (the rsync shipped with RH9). The first time rsync
halted (indefinitely), every other run gives the a
r /mnt/dar : No such file or directory
rsync error: errors selecting input/output files, dirs (code 3) at flist.c(980)
I guess it is caused because the current directory (pwd) has been deleted,
nevertheless I guess rsync should handle this situation (as any other
command can handle it).
The
I am using rsync to backup Maildir directories. Since it is very active,
some files are deleted (and some are added as new mail arrive) from the
time that the list of files are collected and the time of the actual
operation.
I have check the mailing list archive and I did not see a clear answer to
Hi!
How can I find out what files wheren't transferred If I have error:
rsync error: some files could not be transferred (code 23) at
main.c(1045)
running rsync?
I've tried "rsync -v[v][v]" but had no success. It wasn't possible to make
sure what where the files
Follow up to my own posting.
I was running rsync with -v and rsync was having problems chowning (not
transferring) files. I realise now that the error message applied to this
problem. I found the error message a little confusing, as I was trying to
track down the non-transferred files, while k
Rsync Issue Solaris8
When performing a simple rsync between servers I was getting the
following error:
root:#> rsync -e ssh -va /export/home/a078479/bob
smmk39:/export/home/a078479/
ksh: rsync: not found
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rs
This is an extrememly old post, so it might not be of any use anymore.
I encountered this same error, and the problem ended up being a full
filesystem (my destination filled up before completion).
rsync error: error in rsync protocol data stream (code 12) at io.c(140)
Dave Dykstra dwd at bell
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
Hi sir,
While I am trying to run
rsync -rvzl . rsync-destination
it is giving the above error after copying few files.
If I run it again then its copying some more files and again
exiting with the above problem.
Thanks
srinivas
--
To unsubscribe or change option
hostrsync: connection unexpectedly closed (0 bytes received so far) [sender]rsync error: error in rsync protocol data stream (code 12) at io.c(420)
this is related to ssh i believe.But when i try to use from the command prompt it is working without any problem through ssh
Please some one help me how
gument (22)
*** Skipping everything below this failed directory ***
sent 66340 bytes received 22 bytes 574.56 bytes/sec
total size is 5531245572 speedup is 83349.59
rsync error: some files could not be transferred (code 23) at main.c(791)
and it doesn't backup all "Document and Settings&
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
in, it's possible you're running out of memory with that many files.
> >
> Checked the unixbox and the process is using about 50M (according to top)
> before crashing and the machine has 256MB and does nothing besides being
> subject to my rsync testing.
>
>
er
> -v . "/home/andrewm/test-rsync/tree/*"
> | large_file2
> | write failed on large_file2 : Success:06
> | rsync error: error in file IO (code 11) at receiver.c(271)
> | rsync: connection unexpectedly closed (201 bytes read so far)
> | rsync error: error in rsync protocol data
Hi,
I have installed 2.5.3pre1 but have (virtually) the same error:
| write failed on large_file2 : Success:12
| rsync error: error in file IO (code 11) at receiver.c(271)
| rsync: connection unexpectedly closed (201 bytes read so far)
| rsync error: error in rsync protocol data stream (code 12
> | write failed on large_file2 : Success:12
> | rsync error: error in file IO (code 11) at receiver.c(271)
> | rsync: connection unexpectedly closed (201 bytes read so far)
> | rsync error: error in rsync protocol data stream (code 12) at io.c(151)
Hi,
I would like to humbly apolo
7, 2002 at 11:29:44AM +, Andrew McGregor wrote:
> Hi,
>
> I have installed 2.5.3pre1 but have (virtually) the same error:
>
> | write failed on large_file2 : Success:12
> | rsync error: error in file IO (code 11) at receiver.c(271)
> | rsync: connection unexpectedly closed
On Wed, Feb 27, 2002 at 02:57:59PM +, Andrew McGregor wrote:
> > | write failed on large_file2 : Success:12
> > | rsync error: error in file IO (code 11) at receiver.c(271)
> > | rsync: connection unexpectedly closed (201 bytes read so far)
> > | rsync error: erro
Dave Dykstra wrote:
>
> The rsync code that prints that error on line 270 of receiver.c is printing
> strerror(errno), and that error message "Success:12" looks very strange to
> me. If the 12 indicates errno, that's an ENOMEM error. Is your system out
> of virtual address space? Maybe it is s
Dave Dykstra wrote:
>
> The rsync code that prints that error on line 270 of receiver.c is printing
> strerror(errno), and that error message "Success:12" looks very strange to
> me. If the 12 indicates errno, that's an ENOMEM error. Is your system out
> of virtual address space? Maybe it is s
es/avifile/
> apt/packages/avifile/avifile-0.7.34-1.dag.rh90.i386.rpm
> rsync: error writing 4 unbuffered bytes - exiting: Broken pipe
> rsync error: error in rsync protocol data stream (code 12) at io.c(463)
>
> I'm using rsync-2.5.5-4 (the rsync shippe
386.rpm
> rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe
> rsync error: error in rsync protocol data stream (code 12) at io.c(515)
>
> I'm now going to test with an unpatched rsync, although looking at the Red
> Hat patches I don't
> The remote disk is full. Is there a chance that
> rsync could give a more descriptive error ?
I sent a suggested patch for rsync 2.5.6 back in May:
http://lists.samba.org/pipermail/rsync/2003-May/010757.html
http://lists.samba.org/pipermail/rsync/2003-May/010763.html
John
--
To unsubscribe
On Sat, Nov 22, 2003 at 05:44:54PM -0500, [EMAIL PROTECTED] wrote:
> I am using rsync to backup Maildir directories. Since it is very active,
> some files are deleted (and some are added as new mail arrive) from the
> time that the list of files are collected and the time of the actual
> operation.
On Tue, Dec 23, 2003 at 04:00:24AM +0100, [EMAIL PROTECTED] wrote:
> Hi!
>
> How can I find out what files wheren't transferred If I have error:
>
>rsync error: some files could not be transferred (code 23) at
> main.c(1045)
>
> running rsync?
>
> I&#
> On Tue, Dec 23, 2003 at 04:00:24AM +0100, [EMAIL PROTECTED]
wrote:
>> Hi!
>>
>> How can I find out what files wheren't transferred If I
>> have error:
>>
>>rsync error: some files could not be transferred
>>(code 23) at main.c(1045)
&g
On Tue, Dec 23, 2003 at 04:59:20AM +0100, [EMAIL PROTECTED] wrote:
> rsync -avv --delete --delete-excluded server::public/$i dest/
Look in the server's log file -- rsync puts some of the messages there
out of paranoia about exposing too much about the server's setup to the
end user. It may well
Look in the server's log file -- rsync puts
some of the messages there out of paranoia
about exposing too much about the server's
setup to the end user. It may well be that
rsync is being too paranoid in this instance.
..wayne..
Is there any way to *change* that behavior, particularly if rsyn
[EMAIL PROTECTED] wrote:
On Tue, Dec 23, 2003 at 04:00:24AM +0100, [EMAIL PROTECTED]
May the file-list is getting a bit to big for rsync?
If I splitt the transfer using
for i in *; do
rsync -avv --delete --delete-excluded server::public/$i dest/
done
it works seamlessly. The file list is about
ing the
following error:
root:#> rsync -e ssh -va /export/home/a078479/bob
smmk39:/export/home/a078479/
ksh: rsync: not found
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(189)
root:#>
--
To unsubscribe or ch
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
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=5418
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from [EM
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
--- 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
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
On Fri 09 Dec 2005, gg gg234 wrote:
>
> ssh: connect to host x.x.x.x port 22: No route to host
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(420)
>
> this is related to ssh i beli
so far) [sender]> rsync error: error in rsync protocol data stream (code 12) at io.c(420)>> this is related to ssh i believe.But when i try to use from the command
> prompt it is working without any problem through sshPerhaps you have some host-specific options in ~/.ssh/config that a
I use rsync to mirror several servers.
I run RH7.3
My rsyncd.conf file is:
motd file = /etc/rsync.d/rsync.motd
log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
lock file = /var/run/rsync.lock
hosts allow = 10.1.2.200 10.1.2.201
hosts deny = 0.0.0.0/0.0.0.0
use chroot = yes
max conne
I've encountered a similar situation, and tracked it down. It seems that
if the shell for your user is set to bash2 versions 2.0 -> 2.05.0, it
causes your IP to appear as 0.0.0.0 . However, this has been fixed in
2.05b.0, and also works as normal in every other shell I've tested (zsh,
csh, bash v
On Tue, Jan 27, 2004 at 09:55:41PM -0500, [EMAIL PROTECTED] wrote:
> I've encountered a similar situation, and tracked it down. It seems that
> if the shell for your user is set to bash2 versions 2.0 -> 2.05.0, it
> causes your IP to appear as 0.0.0.0 . However, this has been fixed in
> 2.05b.0,
https://bugzilla.samba.org/show_bug.cgi?id=1502
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
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
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
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.
On Tue, Jan 27, 2004 at 04:31:53PM -0800, AI Connex wrote:
> I use rsync to mirror several servers.
>
> I run RH7.3
>
> My rsyncd.conf file is:
>
> motd file = /etc/rsync.d/rsync.motd
> log file = /var/log/rsyncd.log
> pid file = /var/run/rsyncd.pid
> lock file = /var/run/rsync.lock
> hosts allo
https://bugzilla.samba.org/show_bug.cgi?id=1502
Summary: rsync error: error in rsync protocol data stream (code
12) at io.c(836)
Product: rsync
Version: 2.6.2
Platform: x86
OS/Version: Linux
Status: NEW
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
> 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=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
201 - 300 of 332 matches
Mail list logo
