Displaying 8 results from an estimated 8 matches for "msg_error".
2006 Dec 10
1
Rsync 2.6.9 Develops Conflict Between --stats, I think --delete-after and Local Filesystem Replication
Hi all,
Well, yeah, that's it, really. :-) Try it. Works consistently, on Doze
and Linux here ...
# rsync -vvrlHSPtiypogD --stats --numeric-ids --delete-after --force --
partial-dir=.partial /tmp/ /var/tmp/
[...show stats...]
unknown message 4:1 [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(307)
[generator=2.6.9]
rsync: connection unexpectedly closed (26
2004 Jan 17
1
--delete-sent-files (AKA --move-files)
...buf, 4);
redo_list_add(IVAL(buf,0));
break;
+ case MSG_SUCCESS:
+ if (len != 4) {
+ rprintf(FERROR, "invalid message %d:%d\n", tag, len);
+ exit_cleanup(RERR_STREAMIO);
+ }
+ read_loop(fd, buf, 4);
+ io_multiplex_write(MSG_SUCCESS, buf, 4);
+ break;
case MSG_INFO:
case MSG_ERROR:
case MSG_LOG:
@@ -637,6 +645,16 @@ static int read_unbuffered(int fd, char
}
read_loop(fd, buffer, remaining);
bufferIdx = 0;
+ break;
+ case MSG_SUCCESS:
+ if (remaining != 4) {
+ rprintf(FERROR, "invalid multi-message %d:%ld\n",
+ tag, (long)remaining);
+...
2004 May 02
1
2.6.2 patch for AIX
...doesn't like a trailing comma after the last
enum constant.
--
albert chin (china@thewrittenword.com)
-- snip snip
--- rsync.h.orig 2004-05-01 16:52:14.000000000 -0500
+++ rsync.h 2004-05-01 16:52:18.000000000 -0500
@@ -123,7 +123,7 @@
MSG_DATA=0, /* raw data on the multiplexed stream */
MSG_ERROR=FERROR, MSG_INFO=FINFO, MSG_LOG=FLOG, /* remote logging */
MSG_REDO=4, /* reprocess indicated flist index */
- MSG_DONE=5, /* current phase is done */
+ MSG_DONE=5 /* current phase is done */
};
#include "errcode.h"
2004 Aug 18
1
[PATCH] fix AIX compile
...the next version of rsync.
diff -ur src-2.6.2/rsync.h src-2.6.2-local/rsync.h
--- src-2.6.2/rsync.h 2004-04-27 03:36:16.000000000 +0200
+++ src-2.6.2-local/rsync.h 2004-08-18 11:36:18.000000000 +0200
@@ -123,7 +123,7 @@
MSG_DATA=0, /* raw data on the multiplexed stream */
MSG_ERROR=FERROR, MSG_INFO=FINFO, MSG_LOG=FLOG, /* remote logging */
MSG_REDO=4, /* reprocess indicated flist index */
- MSG_DONE=5, /* current phase is done */
+ MSG_DONE=5 /* current phase is done */
};
#include "errcode.h"
2010 Apr 01
0
OpenSSH Coredump and "Bad packet length" errors seen on 5.10 sparc sun4v (Generic_125100-10)
...on unit1 but not on unit0
A snippet:
message_out ${MSG_TRACE} "The replicated file $a_file does not exist;
remove it from the other unit: $OTHERUNIT." yes
/usr/local/bin/ssh root@${OTHERUNIT} "rm -f ${a_file}"
rc=$?
if [ $rc -ne 0 ]; then
message_out $MSG_ERROR "Failed to delete ${a_file} on
${OTHERUNIT} with return code $rc." yes
return 1
fi
FYI: No record now if or not this calling (rm -f
/etc/init.d/staticroutes) succeeded.
Coredump and message files have back ups. Tell me if I need upload it
somewhere.
Looking forward to y...
2006 May 03
2
Rsync error on client end: unexpected tag 3 [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(843) [sender]
Hi guys:
First post for me on this list.
THE PROBLEM
===========
I have several linux servers (ranging from Redhat 7.3 to FC3) that use Rsync (version 2.6.8 and 2.6.7, read on for reasons) to backup their data. A typical rsync backup script looks like this:
------------------------------------------------------------------------------------------
#!/bin/sh
RSYNC_PASSWORD=<PASSWORD>
rsync
DO NOT REPLY [Bug 4320] New: Daemon should send stdout, stderr of {pre, post}-xfer command to client
2007 Jan 02
3
DO NOT REPLY [Bug 4320] New: Daemon should send stdout, stderr of {pre, post}-xfer command to client
...ent: core
AssignedTo: wayned@samba.org
ReportedBy: hashproduct+rsync@gmail.com
QAContact: rsync-qa@samba.org
It would be nice if an rsync daemon returned data that the pre-xfer or
post-xfer command writes to stdout or stderr to the rsync client in the form of
MSG_INFO and MSG_ERROR messages.
This enhancement would be good for two reasons:
- Pre-xfer and post-xfer commands could report progress and errors to the user.
In particular, a pre-xfer command could provide a meaningful error message to
accompany rsync's "pre-xfer exec returned failure".
- An rsync da...
2006 Sep 30
2
DO NOT REPLY [Bug 4139] New: Generator process (running as daemon) hangs after kill SIGINT.
...()
#1 0x4748cddd in ___newselect_nocancel () from /lib/libc.so.6
#2 0x0806a397 in writefd_unbuffered (fd=0, buf=0xbfec9dfc "]", len=97)
at io.c:1074
#3 0x080692e9 in mplex_write (code=Variable "code" is not available.
) at io.c:1169
#4 0x080693db in io_multiplex_write (code=MSG_ERROR,
buf=0xbfecae88 "rsync error: received SIGINT, SIGTERM, or SIGHUP
(code 20) at rsync.c(260) [generator=2.6.8]\n", len=93) at io.c:1377
#5 0x0805c5b2 in rwrite (code=FERROR, buf=0xbfecae88 "rsync error:
received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(260)
[generator=...