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
/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
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
On Sat, Mar 29, 2008 at 04:18:57PM -0400, Erik Jan Tromp wrote:
I've done some experimenting locally narrowed things down. In essense,
I'm tripping over subtle changes in daemon exclude behaviour.
Thanks for figuring out what was going wrong. Rsync should not allow
the exclusion of a . dir
On Fri, 28 Mar 2008 19:04:27 -0400
Erik Jan Tromp [EMAIL PROTECTED] wrote:
Just tripped over this one today.
$ rsync --no-motd rsync://alphageek.dyndns.org/slackware
rsync: link_stat . (in slackware) failed: No such file or directory (2)
rsync error: some files could not be transferred
Just tripped over this one today.
$ rsync --no-motd rsync://alphageek.dyndns.org/slackware
rsync: link_stat . (in slackware) failed: No such file or directory (2)
rsync error: some files could not be transferred (code 23) at main.c(1498)
[receiver=3.0.1pre2]
$ rsync --no-motd rsync
I'm getting this error message and I don't really understand what
rsync is trying to tell me:-
rsync: link_stat /rdiffBackup/gradwell/Mail/. failed: No such file or
directory (2)
rsync error: some files could not be transferred (code 23) at main.c(977)
[sender=2.6.9]
Can anyone explain
On Tue 25 Mar 2008, Chris G wrote:
I'm getting this error message and I don't really understand what
rsync is trying to tell me:-
rsync: link_stat /rdiffBackup/gradwell/Mail/. failed: No such file or
directory (2)
rsync error: some files could not be transferred (code 23
On Tue, Mar 25, 2008 at 12:41:25PM +0100, Paul Slootman wrote:
On Tue 25 Mar 2008, Chris G wrote:
I'm getting this error message and I don't really understand what
rsync is trying to tell me:-
rsync: link_stat /rdiffBackup/gradwell/Mail/. failed: No such file or
directory (2
On Tue 25 Mar 2008, Chris G wrote:
On Tue, Mar 25, 2008 at 12:41:25PM +0100, Paul Slootman wrote:
On Tue 25 Mar 2008, Chris G wrote:
I'm getting this error message and I don't really understand what
rsync is trying to tell me:-
rsync: link_stat /rdiffBackup/gradwell/Mail
On Tue, Mar 25, 2008 at 01:31:37PM +0100, Paul Slootman wrote:
On Tue 25 Mar 2008, Chris G wrote:
On Tue, Mar 25, 2008 at 12:41:25PM +0100, Paul Slootman wrote:
On Tue 25 Mar 2008, Chris G wrote:
I'm getting this error message and I don't really understand what
rsync is trying
On Tue 25 Mar 2008, Chris G wrote:
BTW, is there a reason why you're doing -r and not -a ?
I don't want some of the options that -a gives me, in particular not
the -D and -l.
That's what the -no-* things are for. You could use -a -no-D -no-l
Paul Slootman
--
To unsubscribe or change
On Tue, Mar 25, 2008 at 02:32:34PM +0100, Paul Slootman wrote:
On Tue 25 Mar 2008, Chris G wrote:
BTW, is there a reason why you're doing -r and not -a ?
I don't want some of the options that -a gives me, in particular not
the -D and -l.
That's what the -no-* things are for. You
On Tue 25 Mar 2008, Chris G wrote:
On Tue, Mar 25, 2008 at 02:32:34PM +0100, Paul Slootman wrote:
On Tue 25 Mar 2008, Chris G wrote:
BTW, is there a reason why you're doing -r and not -a ?
I don't want some of the options that -a gives me, in particular not
the -D and -l.
On Tue, Mar 11, 2008 at 03:00:25PM +0100, Giuliano Gavazzi wrote:
rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
This just tells you that the receiver side went away, but we don't know
why it went away. If it is crashing, try to get a core dump and report
the
. 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
I'm getting errors in my rsync.logs using rsync3.0.0pre8 with the -vv
option. The client is running on cygwin as the client, CentOS as the
server. The error in the log is:
rsync: delete_file: rmdir(filepath) failed: No error (0)
When I look on the server/receiving side the directory does
Just as clarification, when I said the directory does not exist I mean that
is was properly deleted by the server/receiving side. It appears as if
rsync did everything that it should but an error code of zero is being
returned and the exit code is set to 23, non-zero.
Full options:
-ruvvityz
That's the missing info I needed to fix the problem. There was a
call in the sender that was being run when it shouldn't have in dry-
run mode. The latest dev version (git, nightly, etc.) has this fixed.
And it looks like all the problems I was having are now resolved.
Many thanks to
On Mon, Feb 04, 2008 at 01:59:54AM +0100, Giuliano Gavazzi wrote:
Running without -n transfers the file correctly.
That's the missing info I needed to fix the problem. There was a call
in the sender that was being run when it shouldn't have in dry-run mode.
The latest dev version (git, nightly,
On 13 Jan 2008, at 08:06, Wayne Davison wrote:
On Sat, Jan 12, 2008 at 08:29:43PM +, Max Lane wrote:
[receiver] internal abbrev error!
Aha, I fixed on on the sending side, but yours is on the receiving
side.
I just checked-in a change that should hopefully fix that too. If you
could
On Sun, 2008-01-13 at 11:31 +, Max Lane wrote:
I'm still getting the error with rsync-HEAD-20080113-0640GMT:
sync: writefd_unbuffered failed to write 5 bytes [sender]: Broken pipe
(32)
[receiver] internal abbrev error! len=61 datum[0]=98
rsync: connection unexpectedly closed (52620
https://bugzilla.samba.org/show_bug.cgi?id=5221
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=5221
Summary: rsync error: partial transfer (code 23) at main.c(576)
Product: rsync
Version: 2.6.3
Platform: Sparc
OS/Version: SunOS
Status: NEW
Severity: major
Priority
https://bugzilla.samba.org/show_bug.cgi?id=5221
--- Comment #1 from [EMAIL PROTECTED] 2008-01-23 01:03 CST ---
Rsync prints the code 23 message at the end of the run when at least one
non-fatal error occurred that may have affected the correctness of the run.
Rsync should have
des fichiers joints, merci d'en solliciter une
copie sur papier.
-Message d'origine-
De : Matt McCutchen [mailto:[EMAIL PROTECTED]
Envoyé : mardi 15 janvier 2008 18:33
À : Sylvain Gargasson
Cc : rsync@lists.samba.org
Objet : RE: 4TB and 150 000 000 files out of memory error
On Tue, 2008
On Tue, 2008-01-15 at 09:55 +0100, Sylvain Gargasson wrote:
I work in a production and I not very happy from use pre-release version...
I have use FAQ and calculate I need 15GB of RAM or SWAP...
I can create big swap without problem but my client use Samba for share is
150 Millions files
Hi all,
Thank you for your very useful product but I have a memory problem.
I want use you product to migrate 4TB of data (in 150 millions files)
When rsync make the list of files it full my RAM and after my SWAP and my
server crash.
I have 4GB of RAM and 4GB of SWAP
Do you know what can I
On Mon, 2008-01-14 at 17:05 +0100, Sylvain Gargasson wrote:
I want use you product to migrate 4TB of data (in 150 millions files)
When rsync make the list of files it full my RAM and after my SWAP and my
server crash.
Use a development version of rsync 3.0.0, which has an incremental
On 13/01/2008, Wayne Davison [EMAIL PROTECTED] wrote:
On Sat, Jan 12, 2008 at 08:29:43PM +, Max Lane wrote:
[receiver] internal abbrev error!
Aha, I fixed on on the sending side, but yours is on the receiving side.
I just checked-in a change that should hopefully fix that too. If you
On Wed, Jan 09, 2008 at 12:22:27PM -0800, Wayne Davison wrote:
I have an idea of what may be the problem, and will check into it
soon.
The latest dev version now has this fixed, including git nightly tar
file. Thanks for the report!
..wayne..
--
To unsubscribe or change options:
rsync: writefd_unbuffered failed to write 5 bytes [sender]: Broken pipe (32)
[receiver] internal abbrev error!
rsync error: error in rsync protocol data stream (code 12) at xattrs.c(565)
[receiver=3.0.0pre8]
rsync: connection unexpectedly closed (51836 bytes received so far) [sender]
rsync error
On Sat, Jan 12, 2008 at 08:29:43PM +, Max Lane wrote:
[receiver] internal abbrev error!
Aha, I fixed on on the sending side, but yours is on the receiving side.
I just checked-in a change that should hopefully fix that too. If you
could give the latest dev version a try, I'd like to know
Hello,
I'm trying the latest rsync(3.0.0prev7) on Mac OS 10.5.1 and getting the
following error:
rsync: writefd_unbuffered failed to write 887 bytes [sender]: Broken pipe
(32)
recv_xattr_request: internal abbrev error!
rsync: connection unexpectedly closed (26242 bytes received so far) [sender
On Wed, Jan 09, 2008 at 09:41:33AM +, Max Lane wrote:
Can someone explain what an internal abbrev error is?
The internal code that that is trying to request the contents of a large
xattr value from the sender is confusing the receiver somehow. I have
an idea of what may be the problem
rsync: recv_generator: failed to stat
/freecom/backup/www/html/chris/info/computer/hardware/networkStorage/freecom/objects\5151.pdf:
Invalid argument
The file exists OK.
--
Chris Green
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting,
Hi All, finally got round to trying this again
-Original Message-
From: Matt McCutchen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 2 January 2008 12:46 AM
To: Gav
Cc: rsync@lists.samba.org
Subject: Re: error code 10 when using ::
On Tue, 2008-01-01 at 17:44 +0900, Gav
: Wednesday, 2 January 2008 12:46 AM
To: Gav
Cc: rsync@lists.samba.org
Subject: Re: error code 10 when using ::
On Tue, 2008-01-01 at 17:44 +0900, Gav wrote:
This works :
sudo rsync -rtlzv --delete [EMAIL PROTECTED]:/var/virtual/web
/usr/local/websites
This does not :
sudo rsync
if I can.
1. Why does the second one not work -- I get connecion timed out and error
in socket IO (code 10) for the second one, whereas the first one works.
2. Even the one that works requires me to enter my local root password and
then the remote root password. Is this secure enough?
3
/rsyncd.conf file then restarted
xinetd.
3 questions if I can.
1. Why does the second one not work -- I get connecion timed out and error
in socket IO (code 10) for the second one, whereas the first one works.
In addition to creating /etc/rsyncd.conf , you may need to add the rsync
daemon
Le mardi 01 janvier 2008, Matt McCutchen a écrit :
2. Even the one that works requires me to enter my local root password
and then the remote root password. Is this secure enough?
You'll have to decide that for yourself. SSH does encrypt the remote
root password before sending it over the
On Wed, 2008-01-02 at 03:20 +0100, Olivier Thauvin wrote:
IIRC, rsync protocol do not transfert password in clear text, but use a
challenge method to perform the password verification.
This mean either with rsync or ssh, the authentication is secure. But
saying
both are secure is not
Hi,
I am doing a delta transmission through rsync from a SOURCE to TARGET
with same folder name.
My config files looks as below:
HOSTTOBACKUP1=ctlrws002
SOURCE1=/opt/mscdr/
TARGET1=/opt/mscdr/
I am getting a error while running the cron job for the above config
and sh file as below
Error
https://bugzilla.samba.org/show_bug.cgi?id=5108
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
Richard Jones wrote:
Help. This one's defeated me so far. I'm tring to push files from from a
local Ubuntu 6.06 server to a remote Ubuntu 6.06 server using rsync (v
2.6.6 installed on both via apt-get). Every time I get the same eg:
Not much help so far :-( I've managed to isolate the problem
closed (84 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(434)
When there are new sub-directories involved, they get created OK on the
remote server (proving we get a vaild connection), but no files get
transfered. So I tried synch'ing just
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
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://bugzilla.samba.org/show_bug.cgi?id=5108
--- Comment #2 from [EMAIL PROTECTED] 2007-11-27 02:06 CST ---
hunter[15]$ gdb rsync
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
https://bugzilla.samba.org/show_bug.cgi?id=5108
--- Comment #3 from [EMAIL PROTECTED] 2007-11-27 07:45 CST ---
To get the symbols: https://wiki.ubuntu.com/DebuggingProgramCrash . I found
this by Googling ubuntu debug info and following a few links.
The free suggests that the crash
https://bugzilla.samba.org/show_bug.cgi?id=5108
--- Comment #4 from [EMAIL PROTECTED] 2007-11-27 09:18 CST ---
Trying with rsync 3.0.0pre5 built locally, I get:
hunter[32]$ rsync -aAH --delete . /tmp/gwk
rsync: ACLs are not supported on this client
rsync error: syntax or usage error
https://bugzilla.samba.org/show_bug.cgi?id=5108
Summary: --delete causes: segfault at fff9 rip
2af8229bb6ab rsp 7fff88788830 error 4
Product: rsync
Version: 2.6.9
Platform: x64
OS/Version: Linux
to start the daemon would immediately exit
with RC=1, no error message.
That's because you aren't using an rsync daemon. Just run your original rsync
command under gdb or strace -f.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because
https://bugzilla.samba.org/show_bug.cgi?id=5075
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
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:
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
Hello,
there are problems syncing files with special charcters in the filename.
The special characters in the filename are displayed as a question mark.
During synchronization, the rsync tells the file is vanished.
Here is the standard output with level 1 verbosity. Higher verbosity
levels dont
Hi All,
I have a problem when transferring files from a rsyncd. This is my setup:
* server: runs rsyncd on port 873.
* firewall: forwarding for the 873 port from outside (using SNAT and DNAT).
* client: manually running rsync command using modules.
The problem occurs when lots of small
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
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
Hi Folks
Can anyone help me with the following error - is it serious; is the file
transferred; are the other files transferred?
[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
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
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
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:
was detected and reported.
rsync error: error in file IO (code 11) at receiver.c(298)
[receiver=3.0.0pre5]
rsync: connection unexpectedly closed (27 bytes received so far)
[sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(601)
[sender=3.0.0pre5]
_exit_cleanup(code=12, file
Hello,
Sometimes when I am using the command:
rsync -avR -e rsh /raid/system/Images/./GHOST.BAT
192.168.192.2:/raid/system/Images/ --delete -z --progress
--exclude-from=/usr/local/excludes --bwlimit=70
I get the following error:
rsync: mkdir /raid/system/Images failed: File exists (17
https://bugzilla.samba.org/show_bug.cgi?id=5075
--- Comment #1 from [EMAIL PROTECTED] 2007-11-12 00:14 CST ---
Created an attachment (id=2963)
-- (https://bugzilla.samba.org/attachment.cgi?id=2963action=view)
Diffs to fix bug
--
Configure bugmail:
https://bugzilla.samba.org/show_bug.cgi?id=5075
--- Comment #2 from [EMAIL PROTECTED] 2007-11-12 00:17 CST ---
Sorry, I meant to add this too:
There is also an uninitialized variable in readfd_buffered that can cause
garbage to be read independently of the bug in mplex_write. Under
https://bugzilla.samba.org/show_bug.cgi?id=5064
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=5064
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from
https://bugzilla.samba.org/show_bug.cgi?id=5064
Summary: compile error - SCO 5.0.6a
Product: rsync
Version: 3.0.0
Platform: x86
OS/Version: Other
Status: NEW
Severity: normal
Priority: P3
Component: core
McCutchen wrote:
On 7/19/07, WCSL [EMAIL PROTECTED] wrote:
Error received when trying to use rsync -vz on the client
inflate (token) returned -5
rsync error: error in rsync protocol data stream (code 12) at
token.c(458)
rsync: writefd_unbuffered failed to write 4092 bytes: phase unknown
This is an extrememly old post, so it might not be of any use anymore.
I encountered this same error, and the problem ended up being a full
filesystem (my destination filled up before completion).
rsync error: error in rsync protocol data stream (code 12) at io.c(140)
Dave Dykstra dwd at bell
I received the following error on the client when testing the pre2 release.
I'm not sure what it means or if it helps. Rsync 2.6.9 runs the same backup
without error. I compiled rsync under cygwin CVS so it may be an issue
there as well. Server side did not crash. It did log an error, but I'm
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
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
On Thu, 18 Oct 2007 07:06:40 -0700
Wayne Davison [EMAIL PROTECTED] wrote:
I haven't been able to reproduce the error, but I believe I found its
cause. Please try the latest CVS version and see if it works.
Thanks!
Pardon the long delay - had my test rig torn down for other projects.
I just
On Wed, Oct 17, 2007 at 08:20:41PM -0400, Erik Jan Tromp wrote:
Just a quick heads up to say I'm still getting this (reproducable) error
while doing daily backups:
rsync: generator.c:1872: check_for_finished_files: Assertion `flist != ((void
*)0)' failed.
I haven't been able to reproduce
https://bugzilla.samba.org/show_bug.cgi?id=1442
--- Comment #11 from [EMAIL PROTECTED] 2007-10-18 11:36 CST ---
Created an attachment (id=2945)
-- (https://bugzilla.samba.org/attachment.cgi?id=2945action=view)
receiver-backtrace.txt
This may be related - or not. I see a hang while
https://bugzilla.samba.org/show_bug.cgi?id=1442
--- Comment #12 from [EMAIL PROTECTED] 2007-10-18 11:37 CST ---
Created an attachment (id=2946)
-- (https://bugzilla.samba.org/attachment.cgi?id=2946action=view)
sender-backtrace.txt
--
Configure bugmail:
Just a quick heads up to say I'm still getting this (reproducable) error while
doing daily backups:
rsync: generator.c:1872: check_for_finished_files: Assertion `flist != ((void
*)0)' failed.
rsync: writefd_unbuffered failed to write 4092 bytes [receiver]: Broken pipe
(32)
rsync error: error
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
||FIXED
Summary|i always get rsync error: |i always get rsync error:
|some files could not be |some files could not be
|transferred (code 23) even |transferred (code 23) even
|when there is nothing to|when
/
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
-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
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
_
Stephen Zemlicka
Integrated Computer Technologies
PH. 608-558-5926
E-Mail
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
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
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
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:
I am running windows xp and I suddenly have no sound, maybe there is a
simply explanation?
Can you give a long distance diagnosis?
Thanks in advance
peter
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read:
and recently I got a error with the setup. I
searched in the forums but I couldn't find much clues on this. Once I
restarted the rsync daemon and rerunning the job didn't gave any errors
further. I also tried to reproduce the issue for much details. But I
couldn't do that even after hours
While using dirvish, I ran into a runaway rsync process, which was
continually spewing errors after encountering a Too many links error.
This was with 2.6.9.
I tried it again with the latest cvs version, and now at least it
doesn't endless-loop with errors, but instead gives an assertion error
Did you found a solution for your Problem? I have the same problem!
Read this topic online here:
Sent using Mail2Forum (http://www.mail2forum.com).
http://forums.nasbackup.com/viewtopic.php?p=6049#6049
--
On 9/13/07, Suresh Kumar [EMAIL PROTECTED] wrote:
Can anybody tell me the good way of find out the which process is opened too
many files and this is causing rsync fails to open new fd??
The error message tells you: it's the client/receiver process.
Currently i want to see /proc/pid/fd
Hi,
I am replicating the oracle database files from one system to another. This
error is not always present. I tried to find out what is going on on the
system that is causing too many open files.. But didn't get success.
Can anybody tell me the good way of find out the which process is opened
Hi,
I am using rsync 2.6.9 and recently I got a error with the setup. I
searched in the forums but I couldn't find much clues on this. Once I
restarted the rsync daemon and rerunning the job didn't gave any errors
further. I also tried to reproduce the issue for much details. But I
couldn't do
On Tue, Sep 11, 2007 at 03:41:48AM -0700, Suresh Kumar Pedamallu wrote:
rsync: pipe failed in do_recv: Too many open files (24)
This is the error that caused the failure. Your system had too many
open files on it for some reason, causing the pipe() system call to
fail.
..wayne
Hello rsync users I'm having the following problem could someone help me?
Inicio do backup - Seg Set 10 14:45:07 BRT 2007
@ERROR: auth failed on module srvmail
rsync error: error starting client-server protocol (code 5) at main.c(1383)
[sender=2.6.9]
Fim do backup - Seg Set 10 14:45:07 BRT 2007
On Mon, Sep 10, 2007 at 02:55:36PM -0300, infolistas listas wrote:
@ERROR: auth failed on module srvmail
That means that you didn't specify the right user and/or the right
password to the rsync daemon transfer. The server's log will tell you
exactly what was wrong, if you have access
501 - 600 of 1491 matches
Mail list logo
