Re: rsync error

2020-06-26 Thread Dave Gordon via rsync
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

Aw: Re: rsync error: error allocating core memory buffers

2015-04-09 Thread devzero
: rsync error: error allocating core memory buffers -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You should not be using rsync's --checksum during routine backups. It is only for very rare use cases not every backup run. On 04/09/2015 04:43 AM, Hans Kraus wrote: Hi, I've configured

Re: rsync error: error allocating core memory buffers

2015-04-09 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You should not be using rsync's --checksum during routine backups. It is only for very rare use cases not every backup run. On 04/09/2015 04:43 AM, Hans Kraus wrote: Hi, I've configured 'backuppc' to transfer files via rsyncd, with enabled

Re: rsync error: unexplained error (code 255) at rsync.c(541) [sender=3.0.4]

2014-08-10 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't know what that error means as it is non-specific. However 3.0.4 is very old. Try upgrading your rsync and see if the problem goes away. On 08/10/2014 07:08 AM, jerrycww...@hsbc.com.hk wrote: Does anyone know what this message is about? I

Re: Rsync error 'unexpected tag 93' when --log-file= parameter is present and run from crontab

2009-01-12 Thread Matt McCutchen
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

Re: rsync error: Error in socket IO(code 10) at clientserver.c(122)

2008-10-13 Thread Matt McCutchen
On Mon, 2008-10-13 at 11:51 -0400, Naveen Sajjan wrote: I am using cwrsync ver 2.1.5 over SSH to connect to [EMAIL PROTECTED] and facing some problems and not sure how to go about it. Below is the full text of the result when I run the batch file. Was wondering if anyone has seen any similar

Re: rsync error: Error in socket IO(code 10) at clientserver.c(122)

2008-10-13 Thread Matt McCutchen
Naveen, please CC rsync@lists.samba.org so that others can help you and your messages are archived for others' future benefit. On Mon, 2008-10-13 at 15:47 -0400, Naveen Sajjan wrote: I just used the rsync -av hostname and I was able to connect. hmm...Didn't seem to use SSH. I guess that means

Re: Rsync Error Code 23?

2008-08-27 Thread earl . j . sanchez
@lists.samba.org Subject 08/26/2008 08:02 Re: Rsync Error Code 23? PM

Re: Rsync Error Code 23?

2008-08-27 Thread Matt McCutchen
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-software is

Re: Rsync Error Code 23?

2008-08-26 Thread Matt McCutchen
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 you! START Tue Aug 26 11:10:12 PDT

Re: rsync error after server restore

2008-06-06 Thread Manuel Kissoyan
Wondering if this cpould happen if a file or a directory have a space on it? Something like Nouveau\ dossier? Thanx! Manuel Kissoyan wrote: Hi, We have this backup server running for a long time without problem, it run the rsync command from cron and connect to many other servers

Re: rsync error after server restore

2008-06-06 Thread Wayne Davison
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 to see

Re: rsync error after server restore

2008-06-06 Thread Manuel Kissoyan
Hi Wayne, Yes, im using timeout=500 in the cron/command as we were using before the crash and also as im using in the other servers. Ill do the strace to see what is happening and ill post here. btw, what exactly do you mean when you say to attach it of each of the 3 programs? Thank you in

Re: rsync error after server restore

2008-06-06 Thread Manuel Kissoyan
Hi Wayne, Here is the strace result. This is the one from the server where we are running the rsync command and where we backup the other server: --- select(4, [3], [], NULL, {47, 471000}) = 0 (Timeout) select(4, [3], [], NULL, {60, 0}) = 0 (Timeout) select(4, [3], [], NULL, {60, 0})

Re: rsync error after server restore

2008-06-06 Thread Wayne Davison
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

Re: rsync error after server restore

2008-06-06 Thread Manuel Kissoyan
ok, here are the last lines from the receiving side: - time(NULL) = 1212801884 select(6, [5], [], NULL, {60, 0}) = 0 (Timeout) time(NULL) = 1212801944 select(6, [5], [], NULL, {60, 0}) = 0 (Timeout) time(NULL)

Re: rsync error: timeout in data send/receive (code 30) at /home/lapo/packaging/tmp/rsync-2.6.3/io.c(153)

2008-05-10 Thread Wayne Davison
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 that has

Re: rsync error: timeout in data send/receive (code 30) at /home/lapo/packaging/tmp/rsync-2.6.3/io.c(153)

2008-05-09 Thread arguellodw
As an update to this problem, it seems that rsync has no problem updating/transferring the directory tree (every day, new data is added in a date directory structure at the remote site). So when I rsync, I get the new folders, but the error message always pops up before data files are

Re: Rsync Error Code 23

2008-04-18 Thread Wayne Davison
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

Re: rsync error: some files could not be transferred -- How to ignore

2008-04-10 Thread Matt McCutchen
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 script to tell rsync to ignore

Re: rsync error: some files could not be transferred -- How to ignore

2008-04-09 Thread Kyle Crawford
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 could not be

Re: rsync error

2008-04-04 Thread Steven Hartland
Log file is likely locked. - Original Message - From: Kaushal Shriyan [EMAIL PROTECTED] hi I have the script http://pastebin.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 ...

Re: rsync error

2008-04-04 Thread Kaushal Shriyan
On Fri, Apr 4, 2008 at 4:51 PM, Steven Hartland [EMAIL PROTECTED] wrote: Log file is likely locked. - Original Message - From: Kaushal Shriyan [EMAIL PROTECTED] hi I have the script http://pastebin.com/d4b062d28 and the roots cron entry are as below 30 2 * * * su sms

Re: rsync error

2008-04-04 Thread Daniel Maher
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/output files, dirs (code 3) at flist.c(1356) [sender=2.6.9]

Re: rsync error: protocol incompatibility (code 2) at rsync.c, using --iconv=. and (code 2) and rsync-3.0.0pre8

2008-02-10 Thread Matt McCutchen
On Thu, 2008-02-07 at 20:09 +0100, Edmond Dantes wrote: Running rsync on our intradisk Xscale Arm BigEndian MiniServer (NAS) System is causing some problems running on special character files and crashing. Rsync is syncing running on a mounted samba share, syncing to the local disk. It is

Re: rsync error when sending lot's of small files

2007-11-28 Thread Johan Huysmans
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. Greetings Johan Johan Huysmans wrote: whoops forgot to mention the error i receive ;) This message appears on the client side: rsync:

Re: rsync error when sending lot's of small files

2007-11-28 Thread Matt McCutchen
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:

Re: rsync error?

2007-11-16 Thread Morgan Read
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 rsync:

Re: rsync error?

2007-11-16 Thread Morgan Read
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. However,

Re: rsync error when sending lot's of small files

2007-11-15 Thread Fabian Cenedese
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:

Re: rsync error when sending lot's of small files

2007-11-15 Thread Johan Huysmans
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:

Re: rsync error?

2007-11-15 Thread Wesley W. Terpstra
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.

Re: rsync error?

2007-11-15 Thread Morgan Read
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. However,

Re: rsync error?

2007-11-15 Thread Morgan Read
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 rsync:

Re: rsync error: STATUS_ACCESS_VIOLATION

2007-10-25 Thread Matt McCutchen
On Thu, 2007-10-25 at 18:55 -0600, Rob Bosch wrote: I received the following error on the client when testing the pre2 release. 4 [main] rsync 8728 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION This might be the same crash that Erik Jan Tromp reported here:

RE: rsync error: STATUS_ACCESS_VIOLATION

2007-10-25 Thread Rob Bosch
Sent: Thursday, October 25, 2007 7:03 PM To: Rob Bosch Cc: rsync@lists.samba.org Subject: Re: rsync error: STATUS_ACCESS_VIOLATION On Thu, 2007-10-25 at 18:55 -0600, Rob Bosch wrote: I received the following error on the client when testing the pre2 release. 4 [main] rsync 8728 _cygtls

Re: rsync error: protocol incompatibility (code 2) at main.c(1385)

2007-10-15 Thread Matt McCutchen
Please CC the list so people other than me can help you and so your messages will be available to future users. On 10/15/07, Mario Domgörgen [EMAIL PROTECTED] wrote: No, i don't run the client side command myself. The backup should start from the server, so i use the the second command to

Re: rsync error: protocol incompatibility (code 2) at main.c(1385)

2007-10-11 Thread Matt McCutchen
On 10/8/07, Mario Domgörgen [EMAIL PROTECTED] wrote: i'm trying to backup one of my hosts with a two rsync-scripts, which are mainly just calling on the client side /usr/bin/rsync --server --sender -vlogDtprz --delete-excluded --numeric-ids --exclude-from=/etc/sm-backup/rsync.exclude / and

RE: rsync error

2007-10-07 Thread Stephen Zemlicka
Zemlicka Cc: rsync@lists.samba.org Subject: Re: rsync error On 10/7/07, Stephen Zemlicka [EMAIL PROTECTED] wrote: I'm getting the attached error suddenly. I am using deltacopy for the ease of setup and e-mail notifications. It is from a local disk to a USB drive. I believe it's using rsync 2.6.6

Re: rsync error

2007-10-07 Thread Matt McCutchen
On 10/7/07, Stephen Zemlicka [EMAIL PROTECTED] wrote: Additionally, this backup contains about 100GB of photos. It seems to backup each file every backup. Any ideas? Try --modify-window=1 . Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before

RE: rsync error

2007-10-07 Thread Stephen Zemlicka
PROTECTED] On Behalf Of Matt McCutchen Sent: Sunday, October 07, 2007 8:25 PM To: Stephen Zemlicka Cc: rsync@lists.samba.org Subject: Re: rsync error On 10/7/07, Stephen Zemlicka [EMAIL PROTECTED] wrote: Additionally, this backup contains about 100GB of photos. It seems to backup each file every backup

Re: rsync error

2007-10-07 Thread Matt McCutchen
On 10/7/07, Stephen Zemlicka [EMAIL PROTECTED] wrote: Still seems to transfer all files. Funny thing is it seems to only do it for the pictures folder. Please run rsync with -i and look at the output to see why it is transferring the files. Matt -- To unsubscribe or change options:

Re: rsync error: some files could not be transferred (code 23)

2007-07-05 Thread rsync-mail-gateway
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 So, it

Re: rsync error: some files could not be transferred (code 23)

2007-07-04 Thread Wayne Davison
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 strangely

Re: rsync error: some files could not be transferred (code 23)

2007-07-04 Thread Matt McCutchen
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\Desktop

RE: rsync error: error starting client-server protocol

2006-12-07 Thread rsync . 20 . maillinglist
-Original Message- From: Wayne Davison - [EMAIL PROTECTED] Sent: Friday, December 01, 2006 7:05 PM To: [EMAIL PROTECTED] Subject: Re: rsync error: error starting client-server protocol On Tue, Nov 28, 2006 at 03:00:03PM +0100, [EMAIL PROTECTED] wrote: 2006/11/28 14:52:36 [26584

Re: rsync error: error starting client-server protocol

2006-12-01 Thread Wayne Davison
On Tue, Nov 28, 2006 at 03:00:03PM +0100, [EMAIL PROTECTED] wrote: 2006/11/28 14:52:36 [26584] rsync denied on module home from localhost (127.0.0.1) This means that the host was not authorized (2.6.6 would have displayed an auth error if the authentication had failed). I'd suggest editing

RE: rsync error: error starting client-server protocol

2006-11-30 Thread rsync . 20 . maillinglist
-Original Message- From: Wayne Davison - [EMAIL PROTECTED] Sent: Monday, November 20, 2006 5:44 PM To: [EMAIL PROTECTED] Cc: rsync@lists.samba.org Subject: Re: rsync error: error starting client-server protocol On Fri, Nov 17, 2006 at 11:49:27AM +0100, [EMAIL PROTECTED] wrote

RE: rsync error: error starting client-server protocol

2006-11-17 Thread rsync . 20 . maillinglist
-Original Message- From: Wayne Davison Sent: Thursday, November 09, 2006 2:41 AM To: rsync@lists.samba.org Subject: Re: rsync error: error starting client-server protocol On Wed, Nov 08, 2006 at 04:12:15PM +0100, rsync.20.maillinglist @ spamgourmet.com wrote: @ERROR: access

RE: rsync error: error starting client-server protocol

2006-11-08 Thread rsync . 20 . maillinglist
-Original Message- From: Wayne Davison Subject: Re: rsync error: error starting client-server protocol On Mon, Oct 30, 2006 at 12:02:02PM +0100, you wrote: I get now the error you can read in the subject. Any hint to get it run again would be fine. Please be more explicit

Re: rsync error: error starting client-server protocol

2006-11-08 Thread Wayne Davison
On Wed, Nov 08, 2006 at 04:12:15PM +0100, [EMAIL PROTECTED] wrote: @ERROR: access denied to home from localhost (127.0.0.1) This is the important bit. This means that you got through to the rsync daemon and it rejected your access. The log file for the daemon will have more explicit

Re: Rsync error on client end: unexpected tag 3 [sender]

2006-07-21 Thread Julian Pace Ross
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

Re: Rsync error on client end: unexpected tag 3 [sender]

2006-07-21 Thread Wayne Davison
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

Re: Rsync error on client end: unexpected tag 3 [sender]

2006-05-18 Thread Wayne Davison
On Tue, May 02, 2006 at 10:30:39PM -0700, Wayne Davison wrote: The attached patch should fix the problem. I've also checked the fix into CVS (and it will appear in the next nightly tar file that gets generated). The patch I posted earlier works fine to fix this problem, but I ended up with a

Re: Rsync error on client end: unexpected tag 3 [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(843) [sender]

2006-05-03 Thread Wayne Davison
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

RE: Rsync error on client end: unexpected tag 3 [sender] rsyncerror: error in rsync protocol data stream (code 12) atio.c(843) [sender]

2006-05-03 Thread Anthony Sadler
backups not working :P Anthony Sadler Far Edge Technology w: (02) 8425 1400 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne Davison Sent: Wednesday, 3 May 2006 16:15 To: Anthony Sadler Cc: rsync@lists.samba.org Subject: Re: Rsync error on client end

Re: Rsync error on client end: unexpected tag 3 [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(843) [sender]

2006-05-02 Thread Wayne Davison
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()

Re: rsync error help required

2006-01-24 Thread gg gg234
Hi, Most of the rsync users love to have web interface or GUI list to rsync resources list.It is very useful and nice to have this. http://www.debianhelp.co.uk/rsyncweb.htm Hope who is responsible for this they will add this one Thanks On 05/01/06, John Van Essen [EMAIL PROTECTED] wrote: On

Re: rsync error code 12 on Mac OS X 10.4.4

2006-01-13 Thread Patrick M McNeal
On Jan 12, 2006, at 6:28 PM, Sean Peisert wrote: Any advice on how to resolve this? File a bug report with Apple. They have modified the version of rsync that ships with OS X 10.4.x, so they are the people who can ( should? ) fix it. FYI - There have been problems with their version of

Re: rsync error help required

2006-01-05 Thread John Van Essen
On Thu, 5 Jan 2006, gg gg234 [EMAIL PROTECTED] wrote: protocol version mismatch -- is your shell clean? (see the rsync man page for an explanation) So... Did you look at the man page? Searching for clean brings you to the DIAGNOSTICS section, which explains what the problem is and how to

Re: rsync error help required

2006-01-05 Thread John Van Essen
On Thu, 5 Jan 2006, gg gg234 [EMAIL PROTECTED] wrote: Hi John, Thanks for your reply I have check that and i try to run ssh 172.29.5.130 /bin/true out.dat and i got the out.dat file with only text inside is Rejected If rsync is seeing that Rejected that explains the error. This is a

Re: rsync error - error in rsync protocol data stream (code 12) at io.c(420)

2005-12-09 Thread gg gg234
thanks for your reply.I have tried that also but still getting the same error On 09/12/05, Paul Slootman [EMAIL PROTECTED] wrote: 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]

Re: rsync error at the end of a transfer

2005-11-08 Thread Wayne Davison
On Tue, Nov 08, 2005 at 09:33:36AM -0500, James W. Beauchamp wrote: 2005-11-08 04:14:42: inflate returned -3 (0 bytes)2005-11-08 04:14:42: rsync error: error in rsync protocol data stream (code 12) at token.c(416) Sounds like you're using an older version of rsync -- I fixed a compression bug

Re: rsync error at the end of a transfer

2005-11-08 Thread James W. Beauchamp
Wayne; Thanks - yep its an old version: rsync-2.5.7-2.legacy.9 on RedHat 9. I guess I'm going to have to try to find an updated package or compile from source unless you have another idea. Thanks! James Wayne Davison wrote: On Tue, Nov 08, 2005 at 09:33:36AM -0500, James W. Beauchamp

Re: rsync error ?

2005-07-06 Thread Paul Slootman
On Wed 06 Jul 2005, [EMAIL PROTECTED] wrote: Thanks for the reply, this version of rsync is going to be used by a group of people, I need to convince them that this is not a real error, do you have any document which talks about this rsync behavior ? Let's put it another way: where in the

Re: rsync error ?

2005-07-05 Thread Wayne Davison
On Tue, Jul 05, 2005 at 04:33:36PM -0400, [EMAIL PROTECTED] wrote: rsync error: syntax or usage error (code 1) at main.c(1097) Running rsync without any options *is* a syntax error. If all you want to see is the help, use the --help option. ..wayne.. -- To unsubscribe or change options:

RE: rsync error: some files could not be transferred -- How to ignore

2005-06-17 Thread sanalkumar.siva
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

Re: rsync error: some files could not be transferred -- How to ignore

2005-06-16 Thread Wayne Davison
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

Re: rsync error: protocol incompatibility (code 2) at main.c(451)

2005-03-15 Thread Wayne Davison
On Tue, Mar 15, 2005 at 06:54:16AM +0100, Dag Wieers wrote: Another update. Only some of the hardlinks seem to be actually missing. Does this make any sense ? Yes, that gives me something to go on for testing. I should hopefully be able to reproduce what is going on. ..wayne.. -- To

Re: rsync error: protocol incompatibility (code 2) at main.c(451)

2005-03-15 Thread Wayne Davison
On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote: Invalid packet at end of run [sender] OK, this was a combination of --delay-updates and --hard-links that was causing a problem at the end of the run. I've checked in a fix to CVS, and the latest nightly tar file has this fix

Re: rsync error: protocol incompatibility (code 2) at main.c(451)

2005-03-15 Thread Dag Wieers
On Tue, 15 Mar 2005, Wayne Davison wrote: On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote: Invalid packet at end of run [sender] OK, this was a combination of --delay-updates and --hard-links that was causing a problem at the end of the run. I've checked in a fix to CVS,

RE: rsync error: protocol incompatibility (code 2) at main.c(451)

2005-03-15 Thread Tony
:[EMAIL PROTECTED] Behalf Of Wayne Davison Sent: Tuesday, March 15, 2005 11:37 AM To: Dag Wieers Cc: rsync@lists.samba.org Subject: Re: rsync error: protocol incompatibility (code 2) at main.c(451) On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote: Invalid packet at end of run [sender

Re: rsync error: protocol incompatibility (code 2) at main.c(451)

2005-03-15 Thread Wayne Davison
On Tue, Mar 15, 2005 at 12:39:54PM -0600, [EMAIL PROTECTED] wrote: Dunno if this has any relationship (or even if this is the right place to break in) Seems like a decent place to jump in to me... Welcome! SERVER: rsync-HEAD-20050314-2227GMT rsync error: protocol incompatibility (code 2) at

Re: rsync error: protocol incompatibility (code 2) at main.c(451)

2005-03-14 Thread Wayne Davison
On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote: Invalid packet at end of run [sender] It would help to know what options you had enabled. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read:

Re: rsync error: protocol incompatibility (code 2) at main.c(451)

2005-03-14 Thread Dag Wieers
On Mon, 14 Mar 2005, Wayne Davison wrote: On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote: Invalid packet at end of run [sender] It would help to know what options you had enabled. Damn, I was planning to include those. Here they are: -avHl --progress --delete-after

Re: rsync error: protocol incompatibility (code 2) at main.c(451)

2005-03-14 Thread Dag Wieers
On Mon, 14 Mar 2005, Wayne Davison wrote: On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote: Invalid packet at end of run [sender] It would help to know what options you had enabled. An update. I noticed that the files being transfered or not updated at the end of the run

Re: rsync error: protocol incompatibility (code 2) at main.c(451)

2005-03-14 Thread Dag Wieers
On Tue, 15 Mar 2005, Dag Wieers wrote: On Mon, 14 Mar 2005, Wayne Davison wrote: On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote: Invalid packet at end of run [sender] It would help to know what options you had enabled. An update. I noticed that the files being

Re: rsync error: syntax or usage error (code 1) at /home/lapo/packaging/tmp/rsync-2., 6.3/main.c(1073)

2005-02-01 Thread Wayne Davison
On Tue, Feb 01, 2005 at 10:28:47AM -0800, Jeff Yana wrote: rsync error: syntax or usage error (code 1) at /home/lapo/packaging/tmp/rsync-2.6.3/main.c(1073) You'll have to tell us the command you're trying to run or we won't be able to figure out what you're doing wrong. ..wayne.. -- To

Re: rsync error: syntax or usage error (code 1) at /home/lapo/packaging/tmp/rsync-2., 6.3/main.c(1073)

2005-02-01 Thread Jeff Yana
Wayne Davison wrote: On Tue, Feb 01, 2005 at 10:28:47AM -0800, Jeff Yana wrote: rsync error: syntax or usage error (code 1) at /home/lapo/packaging/tmp/rsync-2.6.3/main.c(1073) You'll have to tell us the command you're trying to run or we won't be able to figure out what you're doing

Re: rsync error: syntax or usage error (code 1) at /home/lapo/packaging/tmp/rsync-2., 6.3/main.c(1073)

2005-02-01 Thread Wayne Davison
On Tue, Feb 01, 2005 at 01:47:19PM -0800, Jeff Yana wrote: In this case, I was just inputting rsync with no flags or args. In that case, in addition to the above error, rsync should have also output a big, long usage message (on stderr). You can get the usage message on stdout via rsync --help.

Re: rsync error: syntax or usage error (code 1) at /home/lapo/packaging/tmp/rsync-2., 6.3/main.c(1073)

2005-02-01 Thread Jeff Yana
Wayne Davison wrote: On Tue, Feb 01, 2005 at 01:47:19PM -0800, Jeff Yana wrote: In this case, I was just inputting rsync with no flags or args. You are right, I just did not include it as I thought it would be implicit to all. Sorry about the confusion. In that case, in addition to

Re: Rsync Error Code 23?

2005-01-27 Thread Wayne Davison
On Wed, Jan 26, 2005 at 06:47:31PM -0500, Tristan Fiedler wrote: I have an error code 23 (shown below) which I can't debug: Mixed into the verbose output should be one or more warnings about either a file-access or a file-writing problem that prevented a file from being updated. Typically the

Re: rsync error: error in rsync protocol data stream (code 12) at io.c(189)

2004-05-03 Thread Tim Conway
Standard newbie issue. rsh host command (or ssh host command in your case) does so in a fairly stripped environment, for instance, a small $PATH, which is your issue (unless rsync isn't even installed on smmk39). rsync has aneasy workaround for it. add

Re: Rsync Error..

2004-04-26 Thread Tim Conway
Jim: first - glad to see you're able to reach the group again. Second: In later messages, he'd found and fixed true rsh - to where rsh remotehost which rsync returned /usr/local/bin/rsync, and still got the timeout on actual rsyncs. I sent an enormous number of possible outputs he could get

Re: Rsync Error..

2004-04-26 Thread Naveen Babu
Hello Tim, Sorry for the late response. I was out of town for weekend. Ok, first I tried rsync -e rsh --rsync-path=/usr/local/bin/rsync hostwithrsync:/etc/services I got the following the output: -rw-r--r-- 73490 2003/10/27 09.26.50 services

Re: Rsync Error..

2004-04-26 Thread Tim Conway
Services desk:3032734776 [EMAIL PROTECTED] Naveen Babu [EMAIL PROTECTED] 04/26/2004 09:05 AM To Tim Conway/Denver/Contr/[EMAIL PROTECTED] cc [EMAIL PROTECTED] Subject Re: Rsync Error.. Hello Tim, Sorry for the late response. I was out of town for weekend. Ok, first I tried rsync -e rsh

Re: Rsync Error..

2004-04-26 Thread Naveen Babu
the directory that the binary is in. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] Naveen Babu 04/26/2004 11:41 AM To Tim Conway/Denver/Contr/[EMAIL PROTECTED] cc [EMAIL PROTECTED] Subject Re: Rsync Error.. Tim Conway wrote

Re: Rsync Error..

2004-04-23 Thread Tim Conway
rsh 66.123.34.123 which rsync I expect you'll get something like no rsync in /usr/bin /usr/ccs/bin /usr/bin/X11 /usr/contrib/bin /usr/local/bin . Some systems don't report the remote shell connection open until the called remote program comes up, so one missing from the path can look like a

Re: Rsync Error..

2004-04-23 Thread Naveen Babu
Hello, when i gave rsh 66.123.34.123 which rsync at the source system i got the following error 66.123.34.123: Connection refused rsh 66.123.34.123 works perfectly fine. What could be the problem..? Thanks, Naveen. Tim Conway [EMAIL PROTECTED] wrote: rsh 66.123.34.123 which rsync I expect

Re: Rsync Error..

2004-04-23 Thread Tim Conway
Ah! Now I've got you. rsh without parameters does an rlogin, which uses the service commonly called login, on port 513. With parameters, it does a plain rsh, using the service commonly called shell, on port 514. Here's a system with both holes open (deep inside a well-protected intranet, host

Re: Rsync Error..

2004-04-23 Thread Naveen Babu
However when I first give rsh 66.123.34.123 and after remote login when i give which rsync ; i get the following output /usr/local/bin/rsync. Jim Salter [EMAIL PROTECTED] wrote: Clearly, if you can't execute the which command remotely, rsh is _not_ working perfectly fine. If you can't use

Re: Rsync Error..

2004-04-23 Thread Naveen Babu
Hello, I uncommented shell in inetd.conf on the destination system. The command rsh 66.123.34.123 which rsync is working fine now . I get the output /usr/local/bin/rsync. But the command: rsync -avvznrbe rsh /sourcepath 66.123.34.123:/destinationpath Still does not work. I get the

Re: Rsync Error..

2004-04-23 Thread Tim Conway
Ok, I'd expected it to go once you could rsh host which rsync. Since you're not getting a + [EMAIL PROTECTED] /usr/local/admin/binrsync -e rsh --rsync-path=/usr/local/bin/rsync hostwithoutrsync:/etc/services sh: /usr/local/bin/rsync:

Re: Rsync Error..

2004-04-23 Thread Jim Salter
Tim already answered your question for you. Your remote system is not answering on port 514, only on port 513. See your OS's rsh man page for further details - this isn't really an rsync question, it's an rsh question. However when I first give rsh 66.123.34.123 and after remote login when i

Re: rsync error: some files could not be transferred (code 23) at main.c

2004-02-27 Thread Jonathan Hurley
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

Re: rsync error using ssh : @ERROR: access denied to server.domain.com from unknown (0.0.0.0) {Scanned By MailScanner}

2004-01-27 Thread jw schultz
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 allow =

Re: rsync error using ssh : @ERROR: access denied toserver.domain.com from unknown (0.0.0.0) {Scanned By MailScanner}

2004-01-27 Thread tallen
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

Re: rsync error using ssh : @ERROR: access denied toserver.domain.com from unknown (0.0.0.0) {Scanned By MailScanner}

2004-01-27 Thread jw schultz
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, and

Re: rsync error: some files could not be transferred (code 23) at main.c(1045)

2003-12-23 Thread Wayne Davison
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

Re: rsync error: some files could not be transferred (code 23) at main.c(1045)

2003-12-23 Thread Jim Salter
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

  1   2   >