Re: rsync error
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 and if you know a way
> to solve this, please share with me.
>
> Many thanks,
> Dr. Madhurananda Pahar.
That's just a debug message, letting the developers know when the file
list had to be expanded, and whether it had to be moved (by realloc(3))
as a result -- because that case introduces the particular hazard that
some other code might have kept a pointer to the old array. So this
message would be useful if one were debugging a random crash, to know
whether it only happened when the file list grew to a certain size, or
when it was relocated during expansion.
> if (DEBUG_GTE(FLIST, 1) && flist->malloced != FLIST_START) {
> rprintf(FCLIENT, "[%s] expand file_list pointer array to %s
> bytes, did%s move\n",
> who_am_i(),
> big_num(sizeof flist->files[0] * flist->malloced),
> (new_ptr == flist->files) ? " not" : "");
> }
>
It's not an error of any sort, and you're only seeing it because you've
enabled DEBUG_GTE. Is there some other problem that you're trying to debug?
.Dave.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Aw: Re: rsync error: error allocating core memory buffers
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 k...@sanitarium.net An: rsync@lists.samba.org Betreff: Re: 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 'backuppc' to transfer files 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: 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 (192.168.1.200) - I read that the memory overflow comes from bulding the checksums list. Is there a way to find out where in the file tree that overflow occurs for determine splitting points? The OS is Debian 7.4 amd, 24 GB RAM, 32 GB swap. Kind regards, Hans - -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: http://www.sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlUmqrAACgkQVKC1jlbQAQdYnQCfSDNBGlPPbi1T0ATUlNngj3tz fTsAn1OwEGeDdkOKf+lCaDTZEBJoS/jg =TJEs -END PGP SIGNATURE- -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: 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 'backuppc' to transfer files 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: 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 (192.168.1.200) - I read that the memory overflow comes from bulding the checksums list. Is there a way to find out where in the file tree that overflow occurs for determine splitting points? The OS is Debian 7.4 amd, 24 GB RAM, 32 GB swap. Kind regards, Hans - -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: http://www.sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlUmqrAACgkQVKC1jlbQAQdYnQCfSDNBGlPPbi1T0ATUlNngj3tz fTsAn1OwEGeDdkOKf+lCaDTZEBJoS/jg =TJEs -END PGP SIGNATURE- -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: unexplained error (code 255) at rsync.c(541) [sender=3.0.4]
-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 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 Asset Management (Hong Kong) Limited whose registered address is HSBC Main Building, 1 Queen's Road Central, Hong Kong - *** This e-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return e-mail. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. *** SAVE PAPER - THINK BEFORE YOU PRINT! - -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: http://www.sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlPnyv4ACgkQVKC1jlbQAQeG0QCguzqAUb0p/VMkAUsc6jDTKuMC yL4An3M1l74sZOm+U45geklV0gNb0XCw =pHqD -END PGP SIGNATURE- -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync error 'unexpected tag 93' when --log-file= parameter is present and run from crontab
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 /share/hdd/data/public/Ernst/ 192.168.1.69::rsync-nslu2 However, if I include the same line in crontab, when executed the server reports an unexpected tag 93 and protocol errors in io.c at line 1169, which is the default handler for communication errors. This *only* happens when the --log-file=/nslu2/rsync.log line is present. BTW; how can an error such as this be 'unexpected'? The tag '93' must mean something? Why can't the error handler be more specific about what caused this? At least some information in a client-server environment on which side generated the protocol error would help enormously! The rsync protocol consists of messages of different types, and each type is identified by a tag number. The error means that an rsync got a message with tag number 93, which is not one of the valid tags whose meaning is defined by the protocol. This is generally a result of the protocol somehow getting out of sync. It is hard to tell which side generates the error though. The error message appears in /var/log/messages at the server's end. The client's syslog does not report an error, it only reports that cron has started rsync. The error should have a [client] or [server] prefix that tells you which side detected the error. That doesn't, however, reveal which side is at fault for the protocol getting out of sync. I can live with the latter option since it also generates a log file by redirection of rsync's output but I prefer the --log-file= version since that allows me to change the log format. You should be able to change the stdout format with --out-format. -- Matt -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: Error in socket IO(code 10) at clientserver.c(122)
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 issue. Any thoughts/help is much appreciated. Tunnel: ssh Command to run: C:\Program Files\cwRsync\bin\rsync.exe -av /cygdrive/c/backup/ rsync://[EMAIL PROTECTED]:9119/cvsroot/myproject Tunnel command: ssh -i E:\BTP\PuTTY\myPrivateKey_SSH2DSA.ppk -L 9119:127.0.0.1:873 [EMAIL PROTECTED] -T -N Establishing secure channel ... The authenticity 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: failed 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 ... It looks like the ssh host key check is interfering with the creation of the tunnel. If you ssh to [EMAIL PROTECTED] once manually and accept the host key warning, you should then be able to use the batch file. Matt -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: Error in socket IO(code 10) at clientserver.c(122)
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 an SSH tunnel is not required to access the rsync daemon holding the CVS repositories. You could continue using the SSH-less command that worked, or you could use the SSH tunnel anyway if you wish to have your data protected in transit. I am very new to this so please bear with me. Could you please tell me how to manully do the ssh? Would that be using putty? Just run the Tunnel command shown by the batch file and kill it with Ctrl-C once it connects successfully: ssh -i E:\BTP\PuTTY\myPrivateKey_SSH2DSA.ppk -L 9119:127.0.0.1:873 [EMAIL PROTECTED] -T -N Matt On Mon, Oct 13, 2008 at 1:30 PM, Matt McCutchen [EMAIL PROTECTED] wrote: 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 issue. Any thoughts/help is much appreciated. Tunnel: ssh Command to run: C:\Program Files\cwRsync\bin\rsync.exe -av /cygdrive/c/backup/ rsync://[EMAIL PROTECTED]:9119/cvsroot/myproject Tunnel command: ssh -i E:\BTP\PuTTY \myPrivateKey_SSH2DSA.ppk -L 9119:127.0.0.1:873 [EMAIL PROTECTED] -T -N Establishing secure channel ... The authenticity 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: failed 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 ... It looks like the ssh host key check is interfering with the creation of the tunnel. If you ssh to [EMAIL PROTECTED] once manually and accept the host key warning, you should then be able to use the batch file. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error Code 23?
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 a directory which contains the partial content of /drp/fmttcesrv1/snapshots/fs/tce_data/pc. rmdir cannot remove /drp/fmttcesrv1/snapshots/fs/tce_data/pc-software which is not empty as it contains partial content from /drp/fmttcesrv1/snapshots/fs/tce_data/pc. See below directory structure. drpvault# pwd /drp/fmttcesrv1/snapshots/fs/tce_data drpvault# ls client_logs ItemValRequest pc-software tcdata_unx trans_9135 fmtprd lost+found pc-software.README tcdata_win imandata_unxmcadPdfCreateRequestteam imandata_winpc softwaretrans drpvault# ls -l pc-software total 4 drwxr-xr-x 3 ideasadm ideasadm 512 Jun 14 2006 pc-software lrwxrwxrwx 1 ideasadm ideasadm 14 Nov 5 2007 team - /tce_data/team drpvault# ls -l pc total 6 lrwxrwxrwx 1 ideasadm ideasadm 7 Nov 5 2007 mcad - ../mcad drwxrwxrwx 11 ideasadm ideasadm 512 Apr 4 16:27 pc-software lrwxrwxrwx 1 ideasadm ideasadm 7 Nov 5 2007 team - ../team drpvault# Matt McCutchen [EMAIL PROTECTED] en.netTo No Phone Info [EMAIL PROTECTED] Available cc rsync@lists.samba.org Subject 08/26/2008 08:02 Re: Rsync Error Code 23? PM 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 2008 /home/filerep/bin/rsync -e /var/openssh/bin/ssh --archive --stats --timeout 3600 fmttcesrv1::tce_data /drp/fmttcesrv1/snapshots/fs/tce_data --bwlimit=900 delete_file: rmdir /drp/fmttcesrv1/snapshots/fs/tce_data/pc-software failed: F ile exists symlink /drp/fmttcesrv1/snapshots/fs/tce_data/pc-software - pc failed: File exists In this case I think it's actually the symlink failure causing the code 23. delete_file failures currently don't cause code 23, but they probably should because they result in an incorrect transfer. Rsync appears to be trying to delete what it believes is a directory from the destination and make a symlink there instead. However, its rmdir call fails with EEXIST (File exists), which isn't even listed as a possible error in my rmdir(2) man page. What is at the path /drp/fmttcesrv1/snapshots/fs/tce_data/pc-software ? Is it a directory, as rsync believes? Can you remove the directory manually with rmdir(1)? If you can't, you have a non-rsync-specific filesystem problem, while if you can, we'll have to investigate further why rsync is failing. Matt (See attached file: signature.asc) signature.asc Description: Binary data -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error Code 23?
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 a directory which contains the partial content of /drp/fmttcesrv1/snapshots/fs/tce_data/pc. rmdir cannot remove /drp/fmttcesrv1/snapshots/fs/tce_data/pc-software which is not empty as it contains partial content from /drp/fmttcesrv1/snapshots/fs/tce_data/pc. Ah. If you want rsync to recursively delete a destination directory that is to be replaced with a non-directory, you just need to use --force. (I was thrown off by the File exists error; I would have expected Directory not empty.) Matt signature.asc Description: This is a digitally signed message part -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error Code 23?
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 2008 /home/filerep/bin/rsync -e /var/openssh/bin/ssh --archive --stats --timeout 3600 fmttcesrv1::tce_data /drp/fmttcesrv1/snapshots/fs/tce_data --bwlimit=900 delete_file: rmdir /drp/fmttcesrv1/snapshots/fs/tce_data/pc-software failed: F ile exists symlink /drp/fmttcesrv1/snapshots/fs/tce_data/pc-software - pc failed: File exists In this case I think it's actually the symlink failure causing the code 23. delete_file failures currently don't cause code 23, but they probably should because they result in an incorrect transfer. Rsync appears to be trying to delete what it believes is a directory from the destination and make a symlink there instead. However, its rmdir call fails with EEXIST (File exists), which isn't even listed as a possible error in my rmdir(2) man page. What is at the path /drp/fmttcesrv1/snapshots/fs/tce_data/pc-software ? Is it a directory, as rsync believes? Can you remove the directory manually with rmdir(1)? If you can't, you have a non-rsync-specific filesystem problem, while if you can, we'll have to investigate further why rsync is failing. Matt signature.asc Description: This is a digitally signed message part -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error after server restore
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 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=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 error: error in rsync protocol data stream (code 12) at io.c(596) [receiver=3.0.0pre2] _exit_cleanup(code=12, file=io.c, line=596): about to call exit(12) rsync: connection unexpectedly closed (14185 bytes received so far) [generator] rsync error: timeout in data send/receive (code 30) at io.c(596) [generator=3.0.0pre2] _exit_cleanup(code=12, file=io.c, line=596): about to call exit(30) We have installed the same version as we had before the crash, is a Centos 5 64 bit. and the rsync version is rsync version 3.0.0pre2 protocol version 30.PR10 Wondering what could cause the error. Thank you in advance! Manuel -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error after server restore
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 if both sides are reporting a connection-closed error, or if one side is dying/crashing. One way to do that by attaching an strace to each of the 3 programs (e.g. use strace -o FILE -p PID after it is running if you don't want to tweak the way you start the copy going). ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error after server restore
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 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 increasing that value. If not, you should check to see if both sides are reporting a connection-closed error, or if one side is dying/crashing. One way to do that by attaching an strace to each of the 3 programs (e.g. use strace -o FILE -p PID after it is running if you don't want to tweak the way you start the copy going). ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error after server restore
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}) = 0 (Timeout)
select(4, [3], [], NULL, {60, 0}) = 0 (Timeout)
select(4, [3], [], NULL, {60, 0}) = 0 (Timeout)
select(4, [3], [], NULL, {60, 0}) = 0 (Timeout)
select(4, [3], [], NULL, {60, 0}) = 0 (Timeout)
select(4, [3], [], NULL, {60, 0}) = 0 (Timeout)
select(4, [3], [], NULL, {60, 0}) = 1 (in [3], left {0, 0})
--- SIGCHLD (Child exited) @ 0 (0) ---
waitpid(-1, [{WIFSIGNALED(s) WTERMSIG(s) == SIGUSR1}], WNOHANG) = 18568
waitpid(-1, [{WIFEXITED(s) WEXITSTATUS(s) == 30}], WNOHANG) = 18569
waitpid(-1, 0xbff58724, WNOHANG)= -1 ECHILD (No child processes)
sigreturn() = ? (mask now [])
read(3, , 8184) = 0
write(2, rsync: connection unexpectedly c..., 79) = 79
write(2, \n, 1) = 1
rt_sigaction(SIGUSR1, {SIG_IGN}, NULL, 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 such process)
write(2, rsync error: error in rsync prot..., 93) = 93
write(2, \n, 1) = 1
exit_group(12) = ?
Process 18567 detached
---
And this is from the server that we are backing up:
--
Process 19247 attached - interrupt to quit
select(1, [0], [], NULL, {6, 227000}) = 0 (Timeout)
select(1, [0], [], NULL, {60, 0}) = 0 (Timeout)
select(1, [0], [], NULL, {60, 0}) = 0 (Timeout)
select(1, [0], [], NULL, {60, 0}) = 0 (Timeout)
select(1, [0], [], NULL, {60, 0}) = 0 (Timeout)
select(1, [0], [], NULL, {60, 0}) = 0 (Timeout)
select(1, [0], [], NULL, {60, 0}) = 0 (Timeout)
select(1, [0], [], NULL, {60, 0}) = 0 (Timeout)
select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {0, 31000})
read(0, , 4) = 0
select(2, NULL, [1], [1], {60, 0}) = 1 (out [1], left {60, 0})
write(1, M\0\0\10rsync: connection unexpected..., 81) = -1 EPIPE
(Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(2, rsync: writefd_unbuffered failed..., 77) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
rt_sigaction(SIGUSR1, {SIG_IGN}, NULL, 8) = 0
rt_sigaction(SIGUSR2, {SIG_IGN}, NULL, 8) = 0
write(2, rsync error: errors with program..., 87) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
rt_sigaction(SIGUSR1, {SIG_IGN}, NULL, 8) = 0
rt_sigaction(SIGUSR2, {SIG_IGN}, NULL, 8) = 0
select(0, NULL, NULL, NULL, {0, 10}) = 0 (Timeout)
exit_group(13) = ?
Process 19247 detached
-
Thank you!
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 increasing that value. If not, you should check to
see if both sides are reporting a connection-closed error, or if one
side is dying/crashing. One way to do that by attaching an strace to
each of the 3 programs (e.g. use strace -o FILE -p PID after it is
running if you don't want to tweak the way you start the copy going).
..wayne..
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error after server restore
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 the receiving side, and 1 on the sending side. ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error after server restore
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) = 1212802004
select(6, [5], [], NULL, {60, 0}) = 0 (Timeout)
time(NULL) = 1212802064
select(6, [5], [], NULL, {60, 0}) = 0 (Timeout)
time(NULL) = 1212802124
select(6, [5], [], NULL, {60, 0}) = 0 (Timeout)
time(NULL) = 1212802184
select(6, [5], [], NULL, {60, 0}) = 0 (Timeout)
time(NULL) = 1212802244
select(6, [5], [], NULL, {60, 0}) = 0 (Timeout)
time(NULL) = 1212802304
select(6, [5], [], NULL, {60, 0}) = 0 (Timeout)
time(NULL) = 1212802364
select(6, [5], [], NULL, {60, 0}) = 1 (in [5], left {6, 938000})
read(5, T\0\0\10, 4) = 4
time(NULL) = 1212802417
select(6, [5], [], NULL, {60, 0}) = 1 (in [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}) = 1 (in [5], left {59, 895000})
read(5, , 4) = 0
write(2, rsync: connection unexpectedly c..., 81) = 81
write(2, \n, 1) = 1
rt_sigaction(SIGUSR1, {SIG_IGN}, NULL, 8) = 0
rt_sigaction(SIGUSR2, {SIG_IGN}, NULL, 8) = 0
waitpid(18766, 0xbff0a6f8, WNOHANG) = -1 ECHILD (No child processes)
kill(18766, SIGUSR1)= 0
write(2, rsync error: error in rsync prot..., 92) = 92
write(2, \n, 1) = 1
exit_group(12) = ?
Process 18767 detached
---
read(3, \263\272\213?5\314\344\244\226M\4\215\305W)\1II\305\31...,
8192) = 128
close(5)= 0
close(4)= 0
close(6)= 0
select(7, [3], [3], NULL, NULL) = 1 (out [3])
write(3, \243\17K,.sR\227^\6\W\377\267\27\200\34\254O\331\304\34...,
32) = 32
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfe18678) = -1 EINVAL (Invalid
argument)
fcntl64(0, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK)
fcntl64(0, F_SETFL, O_RDWR) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfe18678) = -1 EINVAL (Invalid
argument)
fcntl64(1, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK)
fcntl64(1, F_SETFL, O_RDWR) = 0
ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
gettimeofday({1212802417, 879075}, NULL) = 0
shutdown(3, 2 /* send and receive */) = 0
close(3)= 0
brk(0x9c65000) = 0x9c65000
brk(0x9c5b000) = 0x9c5b000
brk(0x9c3d000) = 0x9c3d000
brk(0x9c23000) = 0x9c23000
exit_group(30) = ?
Process 18766 detached
read(3, \263\272\213?5\314\344\244\226M\4\215\305W)\1II\305\31...,
8192) = 128
close(5)= 0
close(4)= 0
close(6)= 0
select(7, [3], [3], NULL, NULL) = 1 (out [3])
write(3, \243\17K,.sR\227^\6\W\377\267\27\200\34\254O\331\304\34...,
32) = 32
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfe18678) = -1 EINVAL (Invalid
argument)
fcntl64(0, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK)
fcntl64(0, F_SETFL, O_RDWR) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfe18678) = -1 EINVAL (Invalid
argument)
fcntl64(1, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK)
fcntl64(1, F_SETFL, O_RDWR) = 0
ioctl(2, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0
gettimeofday({1212802417, 879075}, NULL) = 0
shutdown(3, 2 /* send and receive */) = 0
close(3)= 0
brk(0x9c65000) = 0x9c65000
brk(0x9c5b000) = 0x9c5b000
brk(0x9c3d000) = 0x9c3d000
brk(0x9c23000) = 0x9c23000
exit_group(30) = ?
Process 18766 detached
And this from the sending side:
select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {60, 0})
read(0, \1\0\0\7, 4) = 4
select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {60, 0})
read(0, \0, 1)= 1
select(2, NULL, [1], [1], {60, 0}) = 1 (out [1], left {60, 0})
write(1, \1\0\0\7\0, 5) = 5
select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {55, 486000})
read(0, \1\0\0\7, 4) = 4
select(1,
Re: rsync error: timeout in data send/receive (code 30) at /home/lapo/packaging/tmp/rsync-2.6.3/io.c(153)
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 support for keep-alive messages in the protocol and see if that helps. ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: timeout in data send/receive (code 30) at /home/lapo/packaging/tmp/rsync-2.6.3/io.c(153)
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 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 replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error Code 23
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 see errors. You should be able to redirect stderr (file-handle 2) like this: rsync -av src/ dest/ 2/tmp/rsync-$$.txt That should give you the errors in whatever file you like. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: some files could not be transferred -- How to ignore
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 such errors? If I were you, I would try to fix the code 23 instead of ignoring it! Rsync exits with code 23 when at least one non-fatal error occurs that may affect the correctness of the transfer. Perhaps the errors currently causing the code 23 are unimportant, but if you ignore code 23, you risk missing more important errors in the future (e.g., the nonexistence of a source argument). Look for the specific error messages in the output that are causing the code 23. If it isn't immediately obvious how to fix them, post them to the list and I'll take a look. Or if you don't care about copying the offending files, you can --exclude them. Matt signature.asc Description: This is a digitally signed message part -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: some files could not be transferred -- How to ignore
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 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 such errors? I am using the bash shell in Mac OS 10.5.2. Any help would be much appreciated. Many thanks, Ken -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html The result code of a command is stored in a special variable named $? Check the value of that variable in an if statement immediately after the rsync line in your script If the value is 0 then there were no errors. If the value is 23, then you could log a warning or not. If there is any other value in $? , then you have another problem. If we could see the relevant lines of your script we might be able to provide more help. Also you control whether your script succeeds or fails based on the last line in your script. If you want it to succeed, the last line would be exit 0 Google for advanced bash scripting guide for more info. Kyle -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error
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 ... 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 This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to [EMAIL PROTECTED] -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error
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 /usr/local/bin/testrsync_mysql.sh I am getting the below error building 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 This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to [EMAIL PROTECTED] 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] Thanks and Regards Kaushal -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error
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] Check the permissions on the directory, and ensure that the user which rsync is running as can access that directory. -- Daniel Maher dma AT witbe.net signature.asc Description: PGP signature -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: protocol incompatibility (code 2) at rsync.c, using --iconv=. and (code 2) and rsync-3.0.0pre8
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 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) [sender=3.0.0pre8] If running without the --iconv=. option I get the following error rsync error: some files could not be transferred (code 23) at main.c(1058) [sender=3.0.0pre8] caused by the attached document file. I'm using libiconv-1.9.1 and a linux-2.4.31 Kernel System based on an open embedded linux similar to openslug libc-2.3.90 system my rsync command line ist as follows: /sbin/rsync -v --log-file=/var/log/rsync.status.log --delete-before --partial -y -ogt -vaxH /mnt/download /export/backup The transfer is local from rsync's perspective, so --iconv=. is not going to help because it converts filenames from the local machine's encoding to itself. Still, we should fix the crash with the --iconv=. option. And presumably you want to solve the problem without --iconv=. so you can transfer the file. So please re-run both commands (with and without --iconv) with verbosity level 3 (-vvv) and post the complete output of each. (In particular, the code 23 message means nothing to me without seeing the previous error message that led to it.) Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error when sending lot's of small files
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: 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] Fabian Cenedese wrote: 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/faqs/smart-questions.html -- View this message in context: http://www.nabble.com/rsync-error-when-sending-lot%27s-of-small-files-tf4811248.html#a13989618 Sent from the Samba - rsync mailing list archive at Nabble.com. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error when sending lot's of small files
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: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error?
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: rsync_xal_set: lsetxattr(Documents/Projects/CBT/SH20/HearingSubmission/ManukauBridgeSubCBT_PostPatrick_3_2.doc,user.Beagle.AttrTime) failed: Permission denied (13) rsync: rsync_xal_set: Though i'm relatively new to rsync, i've been mired in ACL and xattrs hell for a while now, and have seen this behaviour before. :P Can user morgan set ACLs on the filesystem of the receiving machine? If so, can user morgan set ACLs to the exactly the same state as the sending machine? If the answer to either of these is no, then you're going to run into problems like the one you've described. Don't know but suspect no is the answer to both Qs: destination system is my old laptop running fc5 that I'm begining to use as a mirror, with a file system that pre-dates fc5 (perhaps 4 or 3). Not sure ACLs were up and running on it. Once everything is sorted Ill be updating it. Regards, M. -- Getting errors: There are problems with the signature (or similar)? Update your system by installing certificates from CAcert Inc, see here: http://wiki.cacert.org/wiki/BrowserClients?#head-259758ec5ba51c5205cfb179cf60e0b54d9e378b Or, if Internet Explorer is your default browser, simply click this link: http://www.cacert.org/index.php?id=17 Morgan Read NEW ZEALAND mailto:mstuffATreadDOTorgDOTnz fedora: Freedom Forever! http://fedoraproject.org/wiki/Overview By choosing not to ship any proprietary or binary drivers, Fedora does differ from other distributions. ... Quote: Max Spevik http://interviews.slashdot.org/article.pl?sid=06/08/17/177220 RMS on fedora: http://fedoraproject.org/wiki/FreeSoftwareAnalysis/FSF smime.p7s Description: S/MIME cryptographic signature -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error?
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, rsync probably gives a non-zero exit status. lsetxattr(Documents/Projects/CBT/SH20/HearingSubmission/ ManukauBridgeSubCBT_PostPatrick_3_2.doc,user.Beagle.AttrTime) failed: Permission denied (13) The things that failed to copy are meta-data used by beagle (the gnome desktop search tool). This meta-data is expendable. Don't worry. As a point of interest; what version of rsync is this, and was the file read-only? Thanks Wesley Yes, it was read only file - but, only one of many in that particular directory. Version of rsync: [EMAIL PROTECTED] ~]$ rpm -q rsync rsync-2.6.9-3.fc7 Regards, M. -- Getting errors: There are problems with the signature (or similar)? Update your system by installing certificates from CAcert Inc, see here: http://wiki.cacert.org/wiki/BrowserClients?#head-259758ec5ba51c5205cfb179cf60e0b54d9e378b Or, if Internet Explorer is your default browser, simply click this link: http://www.cacert.org/index.php?id=17 Morgan Read NEW ZEALAND mailto:mstuffATreadDOTorgDOTnz fedora: Freedom Forever! http://fedoraproject.org/wiki/Overview By choosing not to ship any proprietary or binary drivers, Fedora does differ from other distributions. ... Quote: Max Spevik http://interviews.slashdot.org/article.pl?sid=06/08/17/177220 RMS on fedora: http://fedoraproject.org/wiki/FreeSoftwareAnalysis/FSF smime.p7s Description: S/MIME cryptographic signature -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error when sending lot's of small files
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/faqs/smart-questions.html
Re: rsync error when sending lot's of small files
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: received SIGUSR1 (code 19) at main.c(1182) [receiver=2.6.9] Fabian Cenedese wrote: 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/faqs/smart-questions.html
Re: rsync error?
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/Projects/CBT/SH20/HearingSubmission/ ManukauBridgeSubCBT_PostPatrick_3_2.doc,user.Beagle.AttrTime) failed: Permission denied (13) The things that failed to copy are meta-data used by beagle (the gnome desktop search tool). This meta-data is expendable. Don't worry. As a point of interest; what version of rsync is this, and was the file read-only? -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error?
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, rsync probably gives a non-zero exit status. lsetxattr(Documents/Projects/CBT/SH20/HearingSubmission/ ManukauBridgeSubCBT_PostPatrick_3_2.doc,user.Beagle.AttrTime) failed: Permission denied (13) The things that failed to copy are meta-data used by beagle (the gnome desktop search tool). This meta-data is expendable. Don't worry. As a point of interest; what version of rsync is this, and was the file read-only? Thanks Wesley Yes, it was read only file - but, only one of many in that particular directory. Version of rsync: [EMAIL PROTECTED] ~]$ rpm -q rsync rsync-2.6.9-3.fc7 Regards, M. -- Getting errors: There are problems with the signature (or similar)? Update your system by installing certificates from CAcert Inc, see here: http://wiki.cacert.org/wiki/BrowserClients?#head-259758ec5ba51c5205cfb179cf60e0b54d9e378b Or, if Internet Explorer is your default browser, simply click this link: http://www.cacert.org/index.php?id=17 Morgan Read NEW ZEALAND mailto:mstuffATreadDOTorgDOTnz fedora: Freedom Forever! http://fedoraproject.org/wiki/Overview By choosing not to ship any proprietary or binary drivers, Fedora does differ from other distributions. ... Quote: Max Spevik http://interviews.slashdot.org/article.pl?sid=06/08/17/177220 RMS on fedora: http://fedoraproject.org/wiki/FreeSoftwareAnalysis/FSF smime.p7s Description: S/MIME cryptographic signature -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error?
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: rsync_xal_set: lsetxattr(Documents/Projects/CBT/SH20/HearingSubmission/ManukauBridgeSubCBT_PostPatrick_3_2.doc,user.Beagle.AttrTime) failed: Permission denied (13) rsync: rsync_xal_set: ... Can user morgan set ACLs on the filesystem of the receiving machine? If so, can user morgan set ACLs to the exactly the same state as the sending machine? If the answer to either of these is no, then you're going to run into problems like the one you've described. Don't know but suspect no is the answer to both Qs: destination system is my old laptop running fc5 that I'm begining to use as a mirror, with a file system that pre-dates fc5 (perhaps 4 or 3). Not sure ACLs were up and running on it. Once everything is sorted Ill be updating it. Regards, M. -- Getting errors: There are problems with the signature (or similar)? Update your system by installing certificates from CAcert Inc, see here: http://wiki.cacert.org/wiki/BrowserClients?#head-259758ec5ba51c5205cfb179cf60e0b54d9e378b Or, if Internet Explorer is your default browser, simply click this link: http://www.cacert.org/index.php?id=17 Morgan Read NEW ZEALAND mailto:mstuffATreadDOTorgDOTnz fedora: Freedom Forever! http://fedoraproject.org/wiki/Overview By choosing not to ship any proprietary or binary drivers, Fedora does differ from other distributions. ... Quote: Max Spevik http://interviews.slashdot.org/article.pl?sid=06/08/17/177220 RMS on fedora: http://fedoraproject.org/wiki/FreeSoftwareAnalysis/FSF smime.p7s Description: S/MIME cryptographic signature -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
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::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION This might be the same crash that Erik Jan Tromp reported here: http://lists.samba.org/archive/rsync/2007-October/018934.html That crash was fixed in the CVS rsync after rsync 3.0.0.pre2 . Please try again with the latest rsync from CVS. Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: rsync error: STATUS_ACCESS_VIOLATION
That appears to have been the problem. I pulled the latest CVS version and the backup passed the same point and is still running. If I get another failure I'll post it back. Thanks Matt! Rob -Original Message- From: Matt McCutchen [mailto:[EMAIL PROTECTED] On Behalf Of Matt McCutchen 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::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION This might be the same crash that Erik Jan Tromp reported here: http://lists.samba.org/archive/rsync/2007-October/018934.html That crash was fixed in the CVS rsync after rsync 3.0.0.pre2 . Please try again with the latest rsync from CVS. Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: protocol incompatibility (code 2) at main.c(1385)
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 connect to the client with an unpriviledged user, that has a forced command in his authorized_keys file. The particular data sent by the rsync protocol depends heavily on the options used, so if the forced command doesn't match the remote command that rsync is trying to invoke, the protocol will get corrupted. I bet this is what caused the error. Forcing a particular --server command is brittle; instead, you should force an appropriately configured single-use daemon (my personal preference) or use the support/rrsync script in the source tree. See https://bugzilla.samba.org/show_bug.cgi?id=4163 . Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: protocol incompatibility (code 2) at main.c(1385)
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 on the server side rsync -avz --numeric-ids -e ssh -i $key --delete --delete-excluded [EMAIL PROTECTED]:/ $DATA_PATH/$client/daily.0 The backup return with the following message on the server side rsync error: protocol incompatibility (code 2) at main.c(1385) [generator=2.6.9], but i can't see any error message on the client side. On both machines the newest version of rsync from the debian stable repository is installed (2.6.9-2etch1). The first command is of the form that rsync uses to invoke itself over a remote shell. Are you running this command yourself? If so, why? Is this instead of or in addition to rsync invoking itself on the client as a result of the second command? If you explain your setup a bit more, I will have a better idea of why it isn't working. Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: rsync error
I ran it again with no changes and it worked. Any ideas why it didn't run
the few times I tried it earlier.
Additionally, this backup contains about 100GB of photos. It seems to
backup each file every backup. Any ideas? If I run the -c, it doesn't
backup each file but it takes forever (over 1hr) to run.
_
Stephen Zemlicka
Integrated Computer Technologies
PH. 608-558-5926
E-Mail [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt
McCutchen
Sent: Sunday, October 07, 2007 2:36 PM
To: Stephen 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
Executing: rsync.exe -v -rlt --delete /cygdrive/C/Documents and
Settings/User/Local Settings/Application
Data/Identities/{DFF16927-88E6-4EAA-A097-460B7E65289B}/Microsoft/Outlook
Express/ localhost::Backup/Outlook Express/
rsync: writefd_unbuffered failed to write 4 bytes: phase unknown
[sender]: Connection reset by peer (104)
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at
/home/lapo/packaging/tmp/rsync-2.6.6/io.c(584)
Something is interfering with the connection between the rsync client
and the DeltaCopy-managed daemon to which it is pushing files, even
though the daemon is on localhost. Here are some things you could try
to get more information about what is causing the problem:
(1) Run rsync at -vvv verbosity level.
(2) Check the daemon's log file for any relevant messages.
(3) Run the rsync client directly at the command line instead of
through DeltaCopy. Perhaps strace rsync to see exactly what happens
before the failure.
Matt
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
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. Any ideas? Try --modify-window=1 . Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: rsync error
Still seems to transfer all files. Funny thing is it seems to only do it for the pictures folder. _ Stephen Zemlicka Integrated Computer Technologies PH. 608-558-5926 E-Mail [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL 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. Any ideas? Try --modify-window=1 . Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error
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: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: some files could not be transferred (code 23)
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 looks like you've got at least one strangely named directory there (since it includes backslash characters). rsync: recv_generator: mkdir /Documents and Settings\Amministratore\Desktop (in pc-5) failed: Invalid argument (22) The Invalid argument error is from your OS. It most likely means that the OS doesn't allow a backslash in the name of a file. You right, I belive that the guilty is NasBackup, because I add these path with NasBackup GUI interface. I hope to find a solution... Best Read this topic online here: Sent using Mail2Forum (http://www.mail2forum.com). http://forums.nasbackup.com/viewtopic.php?p=5640#5640 -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: some files could not be transferred (code 23)
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 named directory there (since it includes backslash characters). rsync: recv_generator: mkdir /Documents and Settings\Amministratore\Desktop (in pc-5) failed: Invalid argument (22) The Invalid argument error is from your OS. It most likely means that the OS doesn't allow a backslash in the name of a file. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: some files could not be transferred (code 23)
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 If the source path is given as Documents and Settings\Amministratore\Desktop, rsync can access the source files just fine because Cygwin knows to split the path at backslashes. However, rsync considers the path to be a single component, includes it in the file list because there's no trailing slash, and tries to recreate it inside the destination. Adding a trailing slash in the command should solve the problem. Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: rsync error: error starting client-server protocol
-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] 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 your rsyncd.conf file to temporarily remove the hosts allow line and all other access restrictions. If that doesn't allow you to connect then you are probably editing the wrong config file for the daemon. If that does let you in, add back various auth rules to see what stops you from connecting. ..wayne.. Thank you very much. I fixed the problem it must bet he wrong config file I edited. I deleted the service and installed the service again. I added the config file to the command line of the service and everything work fine. I didn't see any parameter in the service view of Windows so I thought the default values are in use. But after I installed the service again still no parameters where visible in the service view of Windows. The parameters for the service are hidden somewhere. Again. Thank you very much. Franz IMPORTANT I will read replies only from the mailing list. If you send me email directly it will be deleted. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
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] 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 your rsyncd.conf file to temporarily remove the hosts allow line and all other access restrictions. If that doesn't allow you to connect then you are probably editing the wrong config file for the daemon. If that does let you in, add back various auth rules to see what stops you from connecting. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: rsync error: error starting client-server protocol
-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: @ERROR: access denied to home from localhost (127.0.0.1) Consult the rsync log file for a more detailed reason why the authorization was rejected and then fix the reason for the failure. In the log is nearly not information about the failure. --rsyncd.log 2006/11/28 14:52:07 [18536] rsyncd version 2.6.6 starting, listening on port 873 2006/11/28 14:52:36 [26584] rsync denied on module home from localhost (127.0.0.1) --rsyncd.log How could I get more information to fix the failure? Thanks for any help Franz IMPORTANT I will read replies only from the mailing list. If you send me email directly it will be deleted. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: rsync error: error starting client-server protocol
-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 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 information (which is hidden from the client on purpose), but I'd imagine that you need to add localhost to the list of acceptable IPs that are authorized to connect. ..wayne.. I change the rsync.conf. I appended the rsync.conf at the bottom. On the remote machin I still get the error $ /usr/local/bin/rsync -v -v -avz rsync://[EMAIL PROTECTED]:/home/bin ~/temp/rsync opening tcp connection to localhost port opening connection using --server --sender -vvvlogDtprz . home/bin @ERROR: access denied to home from localhost (127.0.0.1) rsync error: error starting client-server protocol (code 5) at main.c(1171) _exit_cleanup(code=5, file=main.c, line=1171): about to call exit(5) I tried on the local pc which has the ip 192.168.180.53 with /bin/rsync -v -avz rsync://[EMAIL PROTECTED]:873/home/bin/ahk /tmp/ahk Everything work. But if start on the local pc which is localhost I got an error /bin/rsync -v -avz rsync://[EMAIL PROTECTED]:873/home/bin/ahk /tmp/ahk opening tcp connection to localhost port 873 opening connection using --server --sender -vvlogDtprz . home/bin/ahk @ERROR: access denied to home from localhost (127.0.0.1) rsync error: error starting client-server protocol (code 5) at /home/lapo/packaging/tmp/rsync-2.6.6/ma in.c(1171) Rsync.conf - use chroot=false strict modes=true auth users=backup secrets file=/etc/rsyncd.secrets hosts allow=*, localhost, 127.0.0.1, 192.168.180.53 log file=/var/log/rsyncd.log max verbosity = 2 transfer logging = yes [home] path=/cygdrive/d/home/ exclude=.ssh/ .ssh/** TEST/ TEST/** read only=true timeout=600 cut-other-modul-configuration--- -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: rsync error: error starting client-server protocol
-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 in the command that you're running and any error messages that rsync outputs prior to the one you cited. Are you using the right port number and hostname to access the tunnel? ..wayne.. I have installed 2.) installed a tunnel via ssh from the remote machine to my pc ssh [EMAIL PROTECTED] -N -R pcbn0205.dpcom.de::localhost:873 3.) I could run rsync from the remote machine to make bakups The command to run the backup and the error messages is /usr/local/bin/rsync -v -v -avz rsync://[EMAIL PROTECTED]:/home/bin ~/temp/rsync opening tcp connection to localhost port opening connection using --server --sender -vvvlogDtprz . home/bin @ERROR: access denied to home from localhost (127.0.0.1) rsync error: error starting client-server protocol (code 5) at main.c(1171) _exit_cleanup(code=5, file=main.c, line=1171): about to call exit(5) When I start the following rsync command on my local pc everything is ok /bin/rsync -v -avz rsync://[EMAIL PROTECTED]:873/home/bin/ahk /cygdrive/c/Temp/rsyncTEST/bin/ahk On the remote machine and on my pc I have rsync version 2.6.6 protocol version 29. The network admins decided to make 2.) inpossible. So I build the ssh tunnel from the pc to the remote machine. But the backup does not longer run. If there is not enough info in that mail please ask Thanks for any help Franz IMPORTANT I will read replies only from the mailing list. If you send me email directly it will be deleted. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: error starting client-server protocol
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 information (which is hidden from the client on purpose), but I'd imagine that you need to add localhost to the list of acceptable IPs that are authorized to connect. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync error on client end: unexpected tag 3 [sender]
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 previous mails it is not clear what is causing this and whether the patch is required on the server, client or both. (The less I need change at the moment the better). ThanksJulianOn 18/05/06, Wayne Davison [EMAIL PROTECTED] wrote: 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 endedup with a slightly cleaner fix in CVS when all was said and done.Hereis an updated patch for 2.6.8 that fixes this tag-3 problem the way CVS now fixes it...wayne..--To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsyncBefore posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync error on client end: unexpected tag 3 [sender]
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 you're transferring one direction, upgrade whichever side is receiving the files. If you're transferring both directions, upgrade both sides. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync error on client end: unexpected tag 3 [sender]
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 slightly cleaner fix in CVS when all was said and done. Here
is an updated patch for 2.6.8 that fixes this tag-3 problem the way CVS
now fixes it.
..wayne..
--- old/io.c2006-04-21 09:40:19 -0700
+++ new/io.c2006-05-18 10:45:16 -0700
@@ -273,10 +273,7 @@ static void read_msg_fd(void)
exit_cleanup(RERR_STREAMIO);
}
read_loop(fd, buf, len);
- if (defer_forwarding_messages)
- msg_list_add(msg2sndr, MSG_DELETED, buf, len);
- else
- io_multiplex_write(MSG_DELETED, buf, len);
+ send_msg(MSG_DELETED, buf, len);
break;
case MSG_SUCCESS:
if (len != 4 || !am_generator) {
@@ -286,10 +283,7 @@ static void read_msg_fd(void)
read_loop(fd, buf, len);
if (remove_sent_files) {
decrement_active_files(IVAL(buf,0));
- if (defer_forwarding_messages)
- msg_list_add(msg2sndr, MSG_SUCCESS, buf, len);
- else
- io_multiplex_write(MSG_SUCCESS, buf, len);
+ send_msg(MSG_SUCCESS, buf, len);
}
if (preserve_hard_links)
flist_ndx_push(hlink_list, IVAL(buf,0));
@@ -309,10 +303,7 @@ static void read_msg_fd(void)
if (n = sizeof buf)
n = sizeof buf - 1;
read_loop(fd, buf, n);
- if (am_generator am_server
defer_forwarding_messages)
- msg_list_add(msg2sndr, tag, buf, n);
- else
- rwrite((enum logcode)tag, buf, n);
+ rwrite(tag, buf, n);
len -= n;
}
break;
@@ -386,14 +377,19 @@ static int msg2genr_flush(int flush_it_a
return 1;
}
-void send_msg(enum msgcode code, char *buf, int len)
+int send_msg(enum msgcode code, char *buf, int len)
{
if (msg_fd_out 0) {
- io_multiplex_write(code, buf, len);
- return;
+ if (!defer_forwarding_messages)
+ return io_multiplex_write(code, buf, len);
+ if (!io_multiplexing_out)
+ return 0;
+ msg_list_add(msg2sndr, code, buf, len);
+ return 1;
}
msg_list_add(msg2genr, code, buf, len);
msg2genr_flush(NORMAL_FLUSH);
+ return 1;
}
int get_redo_num(int itemizing, enum logcode code)
--- old/log.c 2006-04-08 09:04:34 -0700
+++ new/log.c 2006-05-18 10:45:16 -0700
@@ -264,7 +264,7 @@ void rwrite(enum logcode code, char *buf
if (am_server) {
/* Pass the message to the non-server side. */
- if (io_multiplex_write((enum msgcode)code, buf, len))
+ if (send_msg((enum msgcode)code, buf, len))
return;
if (am_daemon) {
/* TODO: can we send the error to the user somehow? */
--- old/proto.h 2006-04-22 08:38:34 -0700
+++ new/proto.h 2006-05-18 10:45:31 -0700
@@ -104,7 +104,7 @@ void set_msg_fd_in(int fd);
void set_msg_fd_out(int fd);
void increment_active_files(int ndx, int itemizing, enum logcode code);
void decrement_active_files(int ndx);
-void send_msg(enum msgcode code, char *buf, int len);
+int send_msg(enum msgcode code, char *buf, int len);
int get_redo_num(int itemizing, enum logcode code);
int get_hlink_num(void);
void io_set_filesfrom_fds(int f_in, int f_out);
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
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]
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 handle the timezone situation by using localtime()
prior to the chroot call, but on some systems this is not enough to keep
the library code really happy. I've checked in a change that makes
rsync also call strftime() prior to the chroot (for those systems that
are configured to use strftime()).
..wayne..
--- log.c 25 Apr 2006 23:51:15 - 1.146
+++ log.c 3 May 2006 06:06:19 -
@@ -154,17 +154,14 @@ static void logfile_open(void)
void log_init(void)
{
- time_t t;
-
if (log_initialised)
return;
log_initialised = 1;
/* this looks pointless, but it is needed in order for the
* C library on some systems to fetch the timezone info
* before the chroot */
- t = time(NULL);
- localtime(t);
+ timestring(time(NULL));
/* optionally use a log file instead of syslog */
logfname = lp_log_file();
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: Rsync error on client end: unexpected tag 3 [sender] rsyncerror: error in rsync protocol data stream (code 12) atio.c(843) [sender]
Hi Wayne: Just letting you know, you were right about that patch; it wasn't installed correctly. What we had tried was to get it compiled inside of a RPM and install from the RPM. Something went wrong there, we don't know what. After you told us that it had gone wrong, we went and download the nightly build from CVS and compiled that and installed it. After that, it all worked. Our backups all went through with no problems. Thank you very much for your effort and for the very short time with which you came back to me with a fix. We had all been a bit uncomfortable with our 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: unexpected tag 3 [sender] rsyncerror: error in rsync protocol data stream (code 12) atio.c(843) [sender] 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 handle the timezone situation by using localtime() prior to the chroot call, but on some systems this is not enough to keep the library code really happy. I've checked in a change that makes rsync also call strftime() prior to the chroot (for those systems that are configured to use strftime()). ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
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]
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() like
they should be. Furthermore, the MSG_LOG message doesn't actually need
to be deferred, since they cannot result in any data being written to
the socket. This bug can only affect an rsync daemon that is receiving
files, as all other scenarios behave correctly with the existing code.
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).
Thanks for the detailed report, it was very helpful.
..wayne..
--- io.c25 Apr 2006 23:51:15 - 1.193
+++ io.c3 May 2006 05:13:31 -
@@ -294,6 +294,7 @@ static void read_msg_fd(void)
exit_cleanup(RERR_STREAMIO);
}
close_multiplexing_out();
+ defer_forwarding_messages = 0;
/* FALL THROUGH */
case MSG_INFO:
case MSG_ERROR:
@@ -303,7 +304,8 @@ static void read_msg_fd(void)
if (n = sizeof buf)
n = sizeof buf - 1;
read_loop(fd, buf, n);
- if (am_generator am_server
defer_forwarding_messages)
+ if (am_generator am_server
+ defer_forwarding_messages tag != MSG_LOG)
msg_list_add(msg2sndr, tag, buf, n);
else
rwrite((enum logcode)tag, buf, n);
@@ -1134,11 +1136,20 @@ static void msg2sndr_flush(void)
while (msg2sndr.head io_multiplexing_out) {
struct msg_list_item *m = msg2sndr.head;
+ int tag = (IVAL(m-buf, 0) 24) - MPLEX_BASE;
if (!(msg2sndr.head = m-next))
msg2sndr.tail = NULL;
- stats.total_written += m-len;
defer_forwarding_messages = 1;
- writefd_unbuffered(sock_f_out, m-buf, m-len);
+ switch (tag) {
+ case MSG_INFO:
+ case MSG_ERROR:
+ rwrite((enum logcode)tag, m-buf + 4, m-len - 4);
+ break;
+ default:
+ stats.total_written += m-len;
+ writefd_unbuffered(sock_f_out, m-buf, m-len);
+ break;
+ }
defer_forwarding_messages = 0;
free(m);
}
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error help required
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 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 bringsyou to the DIAGNOSTICS section, which explains what the problem is and how to test for it and fix it. John -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error code 12 on Mac OS X 10.4.4
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 rsync since 10.4.0. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error help required
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 test for it and fix it. John -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error help required
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 problem with ssh. You need to get the /bin/true test to work with no resulting output so that rsync doesn't read garbage when it connects with the remote host. I have a look at root .bashrc as follows [ snip ] Does your sshd on 172.29.5.130 allow connections by user root? See PermitRootLogin in the sshd man page. Can you do the /bin/true test successfully as a non-root user? John -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error - error in rsync protocol data stream (code 12) at io.c(420)
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] 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 aren'tpicked up when running from cron?Or there's some hidden character after one of the backslashes, or something like that... Try putting it all on one line in the script.Paul Slootman -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error at the end of a transfer
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 like that a couple versions ago. Alternately, turn off -z (--compress). ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error at the end of a transfer
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 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 like that a couple versions ago. Alternately, turn off -z (--compress). ..wayne.. -- ---If you ain't the lead dog, the scenery never changes BE SURE TO REMOVE THE OBVIOUS ANTI-SPAM STUFF IN MY RETURN ADDRESS James W. Beauchamp, P.E. Global Environmental Solutions, Inc. 2121 Newmarket Pkwy. Suite 140 Marietta, Georgia 30067 Phone - 770-690-9552 ext. 227 Mobile - 404-290-9453 Fax - 770-690-9529 Email - jbeauchamp-at-gesinc.com -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error ?
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 rsync manpage synopsis do you see that you could run rsync without any options? Isn't it common sense that you need to supply arguments to rsync to let it work? Paul Slootman -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error ?
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: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: rsync error: some files could not be transferred -- How to ignore
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 most things, just not deletions that happen after the warnings (such as --delete-after), but see the --ignore option to handle that. If you mean that your script halts, you can code a script to ignore only specific return codes (namely code 23). One would need to know what shell you're using to help with that. ..wayne.. Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: some files could not be transferred -- How to ignore
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 (such as --delete-after), but see the --ignore option to handle that. If you mean that your script halts, you can code a script to ignore only specific return codes (namely code 23). One would need to know what shell you're using to help with that. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: protocol incompatibility (code 2) at main.c(451)
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 unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
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] 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 present. I'm confident that will take care of the problem for you. Thanks for the help! ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: protocol incompatibility (code 2) at main.c(451)
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, and the latest nightly tar file has this fix present. I'm confident that will take care of the problem for you. Thanks for the help! Great service. :) I will package rsync-HEAD-20050315-1733GMT and send some feedback. Thanks ! -- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power] -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: rsync error: protocol incompatibility (code 2) at main.c(451)
Dunno if this has any relationship (or even if this is the right place to break in) SERVER: rsync-HEAD-20050314-2227GMT rsync error: protocol incompatibility (code 2) at io.c(915) rsync error: protocol incompatibility (code 2) at sender.c(157) CLIENT: rsync version 2.6.3 protocol version 29 Server upgraded from VERY OLD 2.4.1-2 (rpm) to latest (bugsall) Server to current version 2.6.3 and everything is fine, as far as I am concerned. I have the latest on a very sacrificial clone of the SERVER and can duplicate the errors. Mar 15 10:21:46 2bizbox rsyncd[24957]: rsyncd version 2.6.4pre2 starting, listening on port 873 Mar 15 10:21:46 2bizbox modprobe: modprobe: Can't locate module net-pf-10 Mar 15 10:50:52 2bizbox rsyncd[1204]: rsyncd version 2.6.3 starting, listening on port 873 Mar 15 10:50:52 2bizbox modprobe: modprobe: Can't locate module net-pf-10 The above is from the server. The clone is sufficiently messed up that most everything is disabled. Better to make mistakes where the consequences are irrelevant. If this is relevant or if I can help with it, please let me know. I've been around awhile, but it's safer to assume that I'm a very green newbie. (You guys are too fast) CLONE: rsync-HEAD-20050315-1733GMT] [EMAIL PROTECTED] local]# rsync -avPLz --password-file=/etc/rsync/rsync.2bb [EMAIL PROTECTED]::mysql-2bb/srv/b* /tmp/ receiving file list ... 6 files to consider bm.MYD Invalid file index: 65536 (count=6) [sender] rsync error: protocol incompatibility (code 2) at sender.c(157) rsync: connection unexpectedly closed (139 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(363) rsync: connection unexpectedly closed (123 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(363) Different place in io.c (but different test from different server) Same result going back to rsync-HEAD-20050314-2227GMT on clone. Actually I'm impressed. I like things that do little to no damage when broken. -Original Message- From: [EMAIL PROTECTED] [mailto:[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] 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 present. I'm confident that will take care of the problem for you. Thanks for the help! ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: protocol incompatibility (code 2) at main.c(451)
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 io.c(915) rsync error: protocol incompatibility (code 2) at sender.c(157) CLIENT: rsync version 2.6.3 protocol version 29 That 2.6.3 version is really a CVS version of the work that went into 2.6.4 from before it was being properly labelled as 2.6.4cvs (the give-away is that the protocol-version says 29, and 2.6.3 only supports up to 28). So, this error is actually expected due to some earlier changes to the protocol that happened before the pre-releases started. Your options are: upgrade the client to the same version of prerelease 2.6.4 as the server, downgrade the client to the real 2.6.3 release, or just add the option --protocol=28 and the two rsyncs will communicate via the older protocol that they both have in common. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
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] 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: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: protocol incompatibility (code 2) at main.c(451)
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 --delay-updates --exclude bert/ --exclude dries/ --exclude redhat/6.2 --exclude redhat/8.0 -e /usr/bin/ssh -oCompression=no Thanks, -- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power] -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: protocol incompatibility (code 2) at main.c(451)
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 (--delay-updates). I seem to be missing the files and the next run they're transfered again. Probably related to the error because the first few updates worked without receiving this error. -- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power] -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: protocol incompatibility (code 2) at main.c(451)
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 transfered or not updated at the end of the run (--delay-updates). I seem to be missing the files and the next run they're transfered again. Probably related to the error because the first few updates worked without receiving this error. Another update. Only some of the hardlinks seem to be actually missing. Does this make any sense ? I'll be doing some more tests to see if there's a pattern or I'm just making things up. Definitely something wrong though :) -- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power] -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: syntax or usage error (code 1) at /home/lapo/packaging/tmp/rsync-2., 6.3/main.c(1073)
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 unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: syntax or usage error (code 1) at /home/lapo/packaging/tmp/rsync-2., 6.3/main.c(1073)
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 wrong. ..wayne.. Sorry, I thought that was clear. In this case, I was just inputting rsync with no flags or args. With args, it is producing this result: bash-2.05b$ rsync -avc --progress --stats rsh=ssh -l adminuser rsync-path=/usr/local/bin/rsync /cygdrive/g/source/ [EMAIL PROTECTED]:/My/Shared/Volume/ [EMAIL PROTECTED] password: building file list ... rsync: link_stat /usr/bin/rsh=ssh -l adminuser failed: No such file or directory (2) rsync: link_stat /usr/bin/rsync-path=/usr/local/bin/rsync failed: No such file or directory (2) 0 files... And it continues to build file list before I escape using Ctrl-C Source machine is a Win2K Server and target is Panther client. Thanks. Jeff It was also appearing along with another error when attempting to sync a loadset between a Win2K Server machine and Linux, but the cause of the other error has been identified and resolved -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: syntax or usage error (code 1) at /home/lapo/packaging/tmp/rsync-2., 6.3/main.c(1073)
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. It would be very strange if the usage message were not printed. bash-2.05b$ rsync -avc --progress --stats rsh=ssh -l adminuser rsync-path=/usr/local/bin/rsync /cygdrive/g/source/ [EMAIL PROTECTED]:/My/Shared/Volume/ You missed the -- in front of the --rsh and --rsync-path options, so rsync complained that it each one wasn't found as a file. Also, you must not both specify -l adminuser to ssh and adminuser@ -- choose one or the other (since they both do the same thing). I'd recommend setting RSYNC_RSH=ssh in your environment so that you don't need to specify --rsh=ssh (which just makes the commands easier to type) and then using the adminuser@ prefix to control the user. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: syntax or usage error (code 1) at /home/lapo/packaging/tmp/rsync-2., 6.3/main.c(1073)
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 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. It would be very strange if the usage message were not printed. bash-2.05b$ rsync -avc --progress --stats rsh=ssh -l adminuser rsync-path=/usr/local/bin/rsync /cygdrive/g/source/ [EMAIL PROTECTED]:/My/Shared/Volume/ Yes, of course. Next time I should RTFM, ay! Great advice about setting the environment variable. Do I set this in the environment variable tab on the Windows machine under System Properties as you would under Cygwin? You missed the -- in front of the --rsh and --rsync-path options, so rsync complained that it each one wasn't found as a file. Also, you must not both specify -l adminuser to ssh and adminuser@ -- choose one or the other (since they both do the same thing). I'd recommend setting RSYNC_RSH=ssh in your environment so that you don't need to specify --rsh=ssh (which just makes the commands easier to type) and then using the adminuser@ prefix to control the user. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error Code 23?
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 warning is something like an access permission not allowing the reading of a source file or directory, however it might also be a read error when reading the file, which could indicate a disk problem -- but that is usually not the case. Finding the error in the verbose output should tell you what's going on. You should be able to to re-run rsync to see it again. Note that if the transfer is going to or from a daemon (which your command-line example did not show, but I'll mention this just to be complete) that some versions of rsync only put these warnings into the daemon logfile. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: error in rsync protocol data stream (code 12) at io.c(189)
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 --rsync-path=/path/on/the/remote/host/to/rsync commonly --rsync-path=/usr/local/bin/rsync . You can also link it into someplace in your path, if you're the admin, and are going to be having a lot of users doing their own rsync commandlines. The stuff you're doing with services and inetd.conf are irrelevant, unless you're going to run an inetd-managed rsyncd, which is NOT what you are doing or accessing in the commandline given. Also your inet hupping is a bit scary. If you have anything that has the word inetd in the ps line, it's going to get a HUP, and many things react to a HUP like to a TERM. I'd suggest a pattern like /usr/sbin/in[eE]td -s$, as you're on Solaris 8. To call that rsync server, forget the -e ssh. have this in your /etc/rsyncd.conf: ++ [home] path = /home ++ Or tighter yet: ++ [homeforbob] path = /home/a078479/bob ++ rsync -va /export/home/a078479/bob smmk39::homeforbob I see, having read to the bottom of your message, that you did the linking thing. That's cool, and well-documented. Glad you figured it out. It's not an rsync issue, but an environmental one. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] 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 rsync protocol data stream (code 12) at io.c(189) root:# -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error..
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 and what they'd mean, and haven't heard back. I think that might have been late Friday. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] 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. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error..
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 ++ lrwxr-xr-x 15 2003/08/19 08:13:58 services + The file persmissions are different from what you mentioned. With three v's i got the following output: + Or like this, with three vs. + [EMAIL PROTECTED] /usr/local/admin/binrsync -vvv -e rsh --rsync-path=/usr/local/bin/rsync hostwithrsync:/etc/services opening connection using rsh hostwithrsync /usr/local/bin/rsync --server --sender -vvvr . /etc/services add_exclude(/*/*,exclude) add_exclude(/*/*,exclude) server_sender starting pid=6090 make_file(1,services) expand file_list to 4000 bytes, did move recv_file_name(services) received 1 names -rw-r--r-- 73490 2003/10/27 09.26.50 services recv_file_list done get_local_name count=1 generator starting pid=5968 count=1 delta transmission enabled generate_files phase=1 recv_files(1) starting send_file_list done send_files starting recv_files phase=1 generate_files phase=2 send_files phase=1 send files finished total: matches=0 tag_hits=0 false_alarms=0 data=0 recv_files finished wrote 24 bytes read 331 bytes 236.67 bytes/sec total size is 15 speedup is 0.40 _exit_cleanup(code=0, file=main.c, line=1045): about to call exit(0) [EMAIL PROTECTED] /usr/local/admin/bin So, I suppose the problem is not something related to rsync timeout. I really appreciate for your time and help. Thanks, Naveen. 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 same error as i used to get before. opening connection using rsh 66.123.34.123 rsync --server -vvbnlogDtprz . /destinationpath 66.123.34.123: operation timed out rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) - Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error..
assuming you replaced hostwithrsync with 66.123.34.123, you're in. It's fine that your /etc/services is a symlink... the important thing is that you can see it with rsync over rsh. Use the rsync-path option, and enjoy the tool. Tim Conway Unix System Administration Contractor - IBM Global 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 --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 ++ lrwxr-xr-x 15 2003/08/19 08:13:58 services + The file persmissions are different from what you mentioned. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error..
In my case rsync -e rsh 66.123.34.123:/etc/services just works fine. I understand that now i dont have to use rsync-path. My whole purpose of using rsync is to backup a directory from source machine to destination machine. In order to accomplish that i gave the command at the source machine: rsync -aznrbe rsh /sourcepath 66.123.34.123:/destinationpath [[ which logically should work because rsync -e rsh 66.123.34.123:/etc/services works fine. ]] . But when i use the above command i get the errors i mentioned in my previous emails. I hope you got my problem. Thanks, Naveen. Tim Conway [EMAIL PROTECTED] wrote: I gave the example, and understood that you'd used it. If instead of rsync -e rsh --rsync-path=/usr/local/bin/rsync 66.123.34.123:/etc/services , you used rsync -e rsh 66.123.34.123:/etc/services and it worked, then you don't need the --rsync-path= option. If however, the second example above fails, and the first one works, that's what you need, and it contains the exact correct syntax for your use. Someone has done some really good work writing and formatting the man pages. These give more detail and explain much more precisely than I can. You might want to take a quick glance. - for instance, see below: SunOS 5.8 Last change: 26 Jan 2003 15 User Commands rsync(1) --rsync-path=PATH Use this to specify the path to the copy of rsync on the remote machine. Useful when it's not in your path. Note that this is the full path to the binary, not just 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: assuming you replaced hostwithrsync with 66.123.34.123, you're in. Yes, i replaced it with the ip address. I have a question about rsync-path option. The command I am giving at the source machine is: rsync -aznrbe rsh /sourcepath 66.123.34.123:/destinationpath Could you please tell me how to use rsync-path option for the above command. Thanks, Naveen. It's fine that your /etc/services is a symlink... the important thing is that you can see it with rsync over rsh. Use the rsync-path option, and enjoy the tool. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] Naveen Babu 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 --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 ++ lrwxr-xr-x 15 2003/08/19 08:13:58 services + The file persmiss! ions are different from what you mentioned. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html - Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error..
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 network timeout. I don't remember if that's true of any FreeBSD. If this is the case, use --rsync-path=/wherever/it/is/on/66.123.34.123 Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] opening connection using rsh 66.123.34.123 rsync --server -vvbnlogDtprz . /destinationpath 66.123.34.123: operation timed out rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error..
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 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 network timeout. I don't remember if that's true of any FreeBSD. If this is the case, use --rsync-path=/wherever/it/is/on/66.123.34.123 Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] opening connection using rsh 66.123.34.123 rsync --server -vvbnlogDtprz . /destinationpath 66.123.34.123: operation timed out rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html - Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error..
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 and usernames deleted to protect the innocent). egrep ^shell|^login /etc/services /etc/inetd.conf /etc/services:login 513/tcp /etc/services:shell 514/tcp cmd # no passwords used /etc/inetd.conf:shell stream tcp nowait root/usr/sbin/in.rshd in.rshd /etc/inetd.conf:login stream tcpnowait root /usr/sbin/in.rlogind in.rlogind You probably have the shell line in inetd.conf commented out. open it, HUP inetd, and you're probably in business. No sane security guys could complain about shell if login is permitted. I'm pretty sure that's your issue. It's also possible, of course, that you shell service is on an alternate port, or commented out of services. You'll see it, whatever it is. All ssh sessions go through the sshd service, on port 22, and most systems that have one or the other of login and shell enabled have both. Yours is just an unusual case. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] 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..? -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error..
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 it for remote command execution, it isn't going to serve as an rsync transport. Jim Salter JRS Systems 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 wrote: 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 network timeout. I don't remember if that's true of any FreeBSD. If this is the case, use --rsync-path=/wherever/it/is/on/66.123.34.123 Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] opening connection using rsh 66.123.34.123 rsync --server -vvbnlogDtprz . /destinationpath 66.123.34.123: operation timed out rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) - Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error..
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 same error as i used to get before. opening connection using rsh 66.123.34.123 rsync --server -vvbnlogDtprz . /destinationpath 66.123.34.123: operation timed out rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) Thanks, Naveen. Tim Conway [EMAIL PROTECTED] wrote: 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 and usernames deleted to protect the innocent). egrep ^shell|^login /etc/services /etc/inetd.conf /etc/services:login 513/tcp /etc/services:shell 514/tcp cmd # no passwords used /etc/inetd.conf:shell stream tcp nowait root /usr/sbin/in.rshd in.rshd /etc/inetd.conf:login stream tcp nowait root /usr/sbin/in.rlogind in.rlogind You probably have the shell line in inetd.conf commented out. open it, HUP inetd, and you're probably in business. No sane security guys could complain about shell if login is permitted. I'm pretty sure that's your issue. It's also possible, of course, that you shell service is on an alternate port, or commented out of services. You'll see it, whatever it is. All ssh sessions go through the sshd service, on port 22, and most systems that have one or the other of login and shell enabled have both. Yours is just an unusual case. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] 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..? - Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync Error..
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: not found. rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) [EMAIL PROTECTED] /usr/local/admin/bin + I don't think it's the remote host binary, but just in case, try a plain rsync -e rsh --rsync-path=/usr/local/bin/rsync 66.123.34.123:/etc/services I remember once upon a time, rsync choked on verbosity, which is why I left out the vs. If that command fails, try it with vvv. It doesn't tell much more than with none at all, but I'd like to see it. + [EMAIL PROTECTED] /usr/local/admin/binrsync -vvv -e rsh --rsync-path=/usr/local/bin/rsync hostwithoutrsync:/etc/services opening connection using rsh hostwithoutrsync /usr/local/bin/rsync --server --sender -vvvr . /etc/services sh: /usr/local/bin/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(165) _exit_cleanup(code=12, file=io.c, line=165): about to call exit(12) [EMAIL PROTECTED] /usr/local/admin/bin + I'd expect more something like this + [EMAIL PROTECTED] /usr/local/admin/binrsync -e rsh --rsync-path=/usr/local/bin/rsync hostwithrsync:/etc/services lrwxr-xr-x 15 2003/08/19 08:13:58 services [EMAIL PROTECTED] /usr/local/admin/bin + Or like this, with three vs. + [EMAIL PROTECTED] /usr/local/admin/binrsync -vvv -e rsh --rsync-path=/usr/local/bin/rsync hostwithrsync:/etc/services opening connection using rsh hostwithrsync /usr/local/bin/rsync --server --sender -vvvr . /etc/services add_exclude(/*/*,exclude) add_exclude(/*/*,exclude) server_sender starting pid=6090 make_file(1,services) expand file_list to 4000 bytes, did move recv_file_name(services) received 1 names lrwxr-xr-x 15 2003/08/19 08:13:58 services recv_file_list done get_local_name count=1 NULL generator starting pid=5968 count=1 delta transmission enabled generate_files phase=1 recv_files(1) starting send_file_list done send_files starting recv_files phase=1 generate_files phase=2 send_files phase=1 send files finished total: matches=0 tag_hits=0 false_alarms=0 data=0 recv_files finished wrote 24 bytes read 331 bytes 236.67 bytes/sec total size is 15 speedup is 0.40 _exit_cleanup(code=0, file=main.c, line=1045): about to call exit(0) [EMAIL PROTECTED] /usr/local/admin/bin + Instead, you're getting this: + [EMAIL PROTECTED] /usr/local/admin/binrsync -e rsh --rsync-path=/usr/local/bin/rsync hostwithoutrsh:/etc/services hostwithoutrsh: Connection timed out rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) [EMAIL PROTECTED] /usr/local/admin/bin [EMAIL PROTECTED] /usr/local/admin/binrsync -vvv -e rsh --rsync-path=/usr/local/bin/rsync hostwithoutrsh:/etc/services opening connection using rsh hostwithoutrsh /usr/local/bin/rsync --server --sender -vvvr . /etc/services hostwithoutrsh: Connection timed out rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) _exit_cleanup(code=12, file=io.c, line=165): about to call exit(12) [EMAIL PROTECTED] /usr/local/admin/bin + If this one fails, rsh 66.123.34.123 /usr/local/bin/rsync / Maybe your timeout is an rsync timeout instead of an rsh timeout. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] 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 same error as i used to get before. opening connection using rsh 66.123.34.123 rsync --server -vvbnlogDtprz . /destinationpath 66.123.34.123: operation timed out rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read:
Re: Rsync Error..
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 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 it for remote command execution, it isn't going to serve as an rsync transport. Jim Salter JRS Systems 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 wrote: 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 network timeout. I don't remember if that's true of any FreeBSD. If this is the case, use --rsync-path=/wherever/it/is/on/66.123.34.123 Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] opening connection using rsh 66.123.34.123 rsync --server -vvbnlogDtprz . /destinationpath 66.123.34.123: operation timed out rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) - Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25? -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: some files could not be transferred (code 23) at main.c
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 knowing all along about the chowning problem. Jon -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error using ssh : @ERROR: access denied to server.domain.com from unknown (0.0.0.0) {Scanned By MailScanner}
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 = 10.1.2.200 10.1.2.201
hosts deny = 0.0.0.0/0.0.0.0
use chroot = yes
max connections = 3
#syslog facility =
[website]
path = /var/www/website
comment = Connex Live WWW Server
uid = nobody
gid = nobody
read only = no
list = yes
auth users = someone,root
secrets file = /etc/rsync.d/rsync.secrets
I use the --rsh=ssh option to use a ssh protocol
A typical script contains:
#!/bin/ash
PATH=/usr/local/bin:/bin:/usr/bin
### Setting user
USER=root
echo Synchronizing Website
#echo
rsync --rsh=ssh \
--password-file=/root/.rsyncpwd \
--compress --recursive --times --perms --links --owner --group \
--include web_order* --include web_user.* --include
web_user_c* --include web_user_h* \
--include web_user_l* --include web_org* --include web_in* --include
web_quote* \
--include quick_connect.* \
--exclude * \
10.1.2.190::website /var/www/website
Everything worked perfectly.
I am now getting the error
@ERROR: access denied to server.domain.com from unknown (0.0.0.0)
The question is, what changed?
If I changed the script so I do not use a ssh shell, everything works fine.
I have hunted the web for a solution, but no joy.
Please advise how I correct the problem.
As near as i can tell it never should have worked because
a local connection, via ssh, would never be allowed access with hosts
allow clause unless perhaps one of the hosts listed were
0.0.0.0
I've attached an UNTESTED patch (against CVS HEAD but should
be applicable to some older versions) that disables hosts
[allow|deny] for rsync over ssh so that the same config file
may be used for both ssh and direct socket connections.
--
J.W. SchultzPegasystems Technologies
email address: [EMAIL PROTECTED]
Remember Cernan and Schmitt
? ..clientserver.patch
Index: clientserver.c
===
RCS file: /data/cvs/rsync/clientserver.c,v
retrieving revision 1.115
diff -u -p -r1.115 clientserver.c
--- clientserver.c 27 Jan 2004 07:57:12 - 1.115
+++ clientserver.c 28 Jan 2004 01:02:45 -
@@ -226,17 +226,16 @@ static int rsync_module(int f_in, int f_
int ret;
char *request=NULL;
- if (!allow_access(addr, host, lp_hosts_allow(i), lp_hosts_deny(i))) {
+ if (am_daemon am_server) {
+ rprintf(FINFO, rsync allowed access on module %s from %s (%s)\n,
+ name, host, addr);
+ }
+ else if (!allow_access(addr, host, lp_hosts_allow(i), lp_hosts_deny(i))) {
rprintf(FERROR,rsync denied on module %s from %s (%s)\n,
name, host, addr);
io_printf(f_out, @ERROR: access denied to %s from %s (%s)\n,
name, host, addr);
return -1;
- }
-
- if (am_daemon am_server) {
- rprintf(FINFO, rsync allowed access on module %s from %s (%s)\n,
- name, host, addr);
}
if (!claim_connection(lp_lock_file(i), lp_max_connections(i))) {
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error using ssh : @ERROR: access denied toserver.domain.com from unknown (0.0.0.0) {Scanned By MailScanner}
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 v1.x, ash). When I use SSH keys, I use a forced command, with a from address, but I also use the rsync hosts allow/deny so that the keys can be used to access some shares from some machines, and some from others. the 2.05b version can be found at http://www.gnu.org/directory/GNU/bash.html . Hope that helps. 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 = 10.1.2.200 10.1.2.201 hosts deny = 0.0.0.0/0.0.0.0 use chroot = yes max connections = 3 #syslog facility = [website] path = /var/www/website comment = Connex Live WWW Server uid = nobody gid = nobody read only = no list = yes auth users = someone,root secrets file = /etc/rsync.d/rsync.secrets I use the --rsh=ssh option to use a ssh protocol A typical script contains: #!/bin/ash PATH=/usr/local/bin:/bin:/usr/bin ### Setting user USER=root echo Synchronizing Website #echo rsync --rsh=ssh \ --password-file=/root/.rsyncpwd \ --compress --recursive --times --perms --links --owner --group \ --include web_order* --include web_user.* --include web_user_c* --include web_user_h* \ --include web_user_l* --include web_org* --include web_in* --include web_quote* \ --include quick_connect.* \ --exclude * \ 10.1.2.190::website /var/www/website Everything worked perfectly. I am now getting the error @ERROR: access denied to server.domain.com from unknown (0.0.0.0) The question is, what changed? If I changed the script so I do not use a ssh shell, everything works fine. I have hunted the web for a solution, but no joy. Please advise how I correct the problem. As near as i can tell it never should have worked because a local connection, via ssh, would never be allowed access with hosts allow clause unless perhaps one of the hosts listed were 0.0.0.0 I've attached an UNTESTED patch (against CVS HEAD but should be applicable to some older versions) that disables hosts [allow|deny] for rsync over ssh so that the same config file may be used for both ssh and direct socket connections. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error using ssh : @ERROR: access denied toserver.domain.com from unknown (0.0.0.0) {Scanned By MailScanner}
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 also works as normal in every other shell I've tested (zsh, csh, bash v1.x, ash). When I use SSH keys, I use a forced command, with a from address, but I also use the rsync hosts allow/deny so that the keys can be used to access some shares from some machines, and some from others. the 2.05b version can be found at http://www.gnu.org/directory/GNU/bash.html . Hope that helps. Sure enough i've two versions of bash here and 2.05.0 unexports all the SSH environment variables but 2.05b.0 passes them. As near as i can tell it never should have worked because a local connection, via ssh, would never be allowed access with hosts allow clause unless perhaps one of the hosts listed were 0.0.0.0 I've attached an UNTESTED patch (against CVS HEAD but should be applicable to some older versions) that disables hosts [allow|deny] for rsync over ssh so that the same config file may be used for both ssh and direct socket connections. That patch is no good. If you are stuck with bash trashing your environment variables and want to share the rsyncd.conf file with a regular daemon while using hosts allow you can use a forced command or put 0.0.0.0 in the hosts allow list. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: some files could not be transferred (code 23) at main.c(1045)
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 be that rsync is being too paranoid in this instance. ..wayne.. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: some files could not be transferred (code 23) at main.c(1045)
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 rsync is running as root anyway? That's annoyed me a couple of times myself. Jim Salter -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
