https://bugzilla.samba.org/show_bug.cgi?id=11654
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.samba.org/show_bug.cgi?id=13953
Bug ID: 13953
Summary: error message instead of --stats informations (in case
of vanished files), using rsync 3.1.1 and rsync 3.0.9
Product: rsync
Version: 3.1.1
Hardware
https://bugzilla.samba.org/show_bug.cgi?id=11215
--- Comment #2 from George ---
Anyone experiencing a similar issue may want to have a look at bug 10372 .
( Possibly related: bug 10332. )
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for m
https://bugzilla.samba.org/show_bug.cgi?id=11654
--- Comment #1 from Taso Hatzi ---
rsync bombs with "rsync error: syntax or usage error (code 1) at main.c(873)
[Receiver=3.1.1]" if it doesn't have write permissions on the destination.
This is somewhat misleading as everything works OK with the -
https://bugzilla.samba.org/show_bug.cgi?id=11654
Bug ID: 11654
Summary: Misleading error message
Product: rsync
Version: 3.1.1
Hardware: x64
OS: Linux
Status: NEW
Severity: normal
Priority: P5
https://bugzilla.samba.org/show_bug.cgi?id=11215
--- Comment #1 from Shevek ---
I think this bug is affecting us too, over multi-gigabyte files. There's one
specific file which is killing rsync, but it doesn't always kill it in the same
place.
--
You are receiving this mail because:
You are the
https://bugzilla.samba.org/show_bug.cgi?id=11215
Bug ID: 11215
Summary: compression/zlib errors discard the zlib error message
Product: rsync
Version: 3.1.0
Hardware: All
OS: All
Status: NEW
Severity
https://bugzilla.samba.org/show_bug.cgi?id=10951
--- Comment #3 from Wayne Davison ---
Let me also add that if the cause was a bash shell variable that ended up being
empty, then you should note that it is a bash-ism to require parameters to be
double-quoted in order for them to behave sanely (e.
https://bugzilla.samba.org/show_bug.cgi?id=10951
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Summary: Emtpy parameter triggers unwanted behavior, but no
> error message
>Product: rsync
>Version: 3.1.0
> Hardware: x64
> OS: Linux
> Status: NEW
> Severity: major
> Priority
https://bugzilla.samba.org/show_bug.cgi?id=10951
--- Comment #1 from Stian Ertvåg ---
The "--exclude" without a value was of course a punshing error in our system,
but we think this should trigger an error instead of syncing to the folder
defined as excluded. The lack of output may occour because
https://bugzilla.samba.org/show_bug.cgi?id=10951
Bug ID: 10951
Summary: Emtpy parameter triggers unwanted behavior, but no
error message
Product: rsync
Version: 3.1.0
Hardware: x64
OS: Linux
After a long stream of output that ends with (wrapped for mail):
rsync error: some files/attrs were not transferred (see previous
errors) (code 23) at main.c(1039) [sender=3.0.6]
How can I locate the above mentioned error in the output from:
/usr/bin/rsync -aCvv --stats
--exclude-from=/u
https://bugzilla.samba.org/show_bug.cgi?id=5802
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=5802
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugzilla.samba.org/show_bug.cgi?id=5802
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=5802
Summary: misleading error message in atomic rsync
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: Linux
Status: NEW
Severity: trivial
Priority: P3
On Mon, Aug 18, 2008 at 11:57:43AM -0400, [EMAIL PROTECTED] wrote:
> which gives me the error "Killed: 9" when it terminates.
That's not an rsync error, but is likely to be a shell message that says
that something else killed rsync. I'd suggest checking the system log
files and/or process history
Hi,
I'm trying to use rsync to backup one server to another, so I'm using this
line of code: "rsync -avz -e "ssh -i /usr/home/davis201/rsync-key"
/usr/www/users/davis201 [EMAIL PROTECTED]:/backup/",
which gives me the error "Killed: 9" when it terminates.
I've tried turning on verbose to see if i
This is to suggest a possible improvement in an error message.
On a recent rsync transfer I see a message like
> rsync: failed to set permissions on ".../somedir": Permission denied (13)
for several dirs that have the sgid bit set
There seems to be a retry pass, because all the
On Wed, 2008-03-26 at 12:34 +, Chris G wrote:
> On Wed, Mar 26, 2008 at 08:23:42AM -0400, Matt McCutchen wrote:
> > Only mtime is used in the decision of whether a file needs to be
> > transferred, so -t is enough. I personally find it clearer to list the
> > things I do want preserved rather
On Wed, Mar 26, 2008 at 08:23:42AM -0400, Matt McCutchen wrote:
> On Tue, 2008-03-25 at 15:29 +0100, Paul Slootman wrote:
> > 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:
> > > > > >
> > > > > > B
On Tue, 2008-03-25 at 15:29 +0100, Paul Slootman wrote:
> 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
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 "/rdiffBa
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
> >
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-* thin
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
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 erro
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:-
>
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 "/rdiffBa
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 f
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)
[sende
Title: cwrsync strange path in error message
Dear Patricia:
First off, my apologies ahead of time for bothering you.
I am attempting to locate a Patricia Palumbo. She worked in Doylestown, Pa., as a court officer in the '60s. She would now be somewhere in her 70s. She was a very
On Thu, Jul 13, 2006 at 01:10:11PM -0700, Brett Hamilton wrote:
> I confirmed that CAN_HARDLINK_SPECIAL was already commented out in
> config.h, and I'm wondering if rsync should still be producing these
> errors?
The code that produces the cited error is in the function
try_dests_non() in gener
Thanks Wayne. Indeed, it looks like my Mac cannot hard link device files.
I confirmed that CAN_HARDLINK_SPECIAL was already commented out in
config.h, and I'm wondering if rsync should still be producing these
errors? Also, I do in fact want to backup the device files in my
snapshots. Makes it
On Fri, Jul 07, 2006 at 02:43:27PM -0700, Brett Hamilton wrote:
> rsync: failed to hard-link /Volumes/backups/vanguard/backup.0/dev/agpgart
> with dev/agpgart: Invalid argument (22)
The message "Invalid argument" is from your OS, and it looks like it is
being generated when trying to hard-link a
rd-linked snapshot backup: (produces the error message)
/Users/foo/bin/rsync -avH --link-dest=/Volumes/backups/vanguard/backup.0 \
--numeric-ids --exclude=/proc --delete -e ssh [EMAIL PROTECTED]:/ backup.new
Thanks for your help. --Brett
--
To unsubscribe or change options: https://lists.samba.o
Wayne,
Frank Fegert wrote:
> Wayne,
>
> thanks for your prompt response!
>
> [self-inflicted pain snipped]
thanks for your help, but never mind! As usual, the problem
was sitting in front of the keyboard, between the headphones
;-)
For security reasons i use a wrapper script on the sending
machin
Wayne,
thanks for your prompt response!
Wayne Davison wrote:
> On Sat, Jun 24, 2006 at 03:03:10PM +0200, Frank Fegert wrote:
>
>>i'm having a rather strange problem with rsync (v2.6.8). Rsync is run to
>>synchronize
>>two identical, rather old Solaris 2.6 servers.
>
> I have heard of some prob
On Sat, Jun 24, 2006 at 03:03:10PM +0200, Frank Fegert wrote:
> i'm having a rather strange problem with rsync (v2.6.8). Rsync is run to
> synchronize
> two identical, rather old Solaris 2.6 servers.
I have heard of some problems with some Solaris versions of ssh, so it
may help to install openss
Hi all,
i'm having a rather strange problem with rsync (v2.6.8). Rsync is run to
synchronize
two identical, rather old Solaris 2.6 servers. All filesystems rsync fine
except for one.
Rsync bails out on this particular FS with the following messages:
# /var/tmp/bin/rsync -avz -e "ssh -i $keyfile
https://bugzilla.samba.org/show_bug.cgi?id=3076
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3076
Summary: Unsuitable error message in flist.c.
Product: rsync
Version: 2.6.5
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
On Tue, Jun 15, 2004 at 08:54:34AM -0700, Wayne Davison wrote:
> On Tue, Jun 15, 2004 at 10:00:56AM +0200, Louis-David Mitterrand wrote:
> > make_bak_dir mkdir
> > "/backup/naxos.premier-lnc.com/2004-06-09/home/ddegrolard/profile/Local
> > Settings/Application Data" failed: File exists
>
> This
On Tue, Jun 15, 2004 at 10:00:56AM +0200, Louis-David Mitterrand wrote:
> make_bak_dir mkdir
> "/backup/naxos.premier-lnc.com/2004-06-09/home/ddegrolard/profile/Local
> Settings/Application Data" failed: File exists
This is a bug that is currently fixed in the CVS version. If you click
on the "
Hello,
I use rsync for incrmental backups in the following way:
rsync \
$EXCLUDE \
-e ssh \
--archive \
--numeric-ids \
--compress \
--relative \
--one-file-system \
That now makes sense..
Thanks Tim!
Patricia
> That's where main.c was when the binary was compiled. It's telling you
> that if you took the same source code and looked at line 383 of main.c,
you
> would see the line that generated that error 23.
>
> Tim Conway
> Unix System Administration
> Co
That's where main.c was when the binary was compiled. It's telling you
that if you took the same source code and looked at line 383 of main.c,
you would see the line that generated that error 23.
Tim Conway
Unix System Administration
Contractor - IBM Global Services
desk:3032734776
[EMAIL PROTE
Hi,
I am running cwrsync.
2004/05/11 [93] rsync error: some files could not be transferred (code
23) at /home/lapo/packaging/tmp/rsync-2.5.7/main.c(383)
I am uncertain as to what this path statement is about in the above error
message.
/home/lapo/packaging/tmp/rsync-2.5.7/main.c(383
On Thu 29 Apr 2004, Ryan Holowaychuk wrote:
>
> I am getting the following error
>
> [EMAIL PROTECTED] etc]# rsync 192.168.100.25::backup
You're missing the local target (or source, depending on what you were
trying to do).
> rsync: failed to connect to 192.168.100.25: Connection refused rsync
I am running 2.57
I am getting the following error
[EMAIL PROTECTED] etc]# rsync 192.168.100.25::backup
rsync: failed to connect to 192.168.100.25: Connection refused rsync error:
error in socket IO (code 10) at clientserver.c(83)
The rsyncd.conf file looks like this
[backup]
path = /backup
rsync: error writing 16385 unbuffered bytes - exiting:
Broken pipe
rsync error: error in rsync protocol data stream (code
12) at io.c(463)
When this happens the file transfer fails. Why does
this happen?
If its the network, anyway to tell rsync to try again
where it left off?
___
Wayne Davison writes:
> My patch leaves out the IPv6 logic if INET6 is not configured into rsync.
Sounds reasonable.
> I've checked-in the appended patch. See if you like it.
Looks good to me. I'll report to the Debian bug tracking system that
these issues are now fixed in CVS upstream.
T
introducing the other change in my patch; [...]
> This gives a more descriptive error message when
> getaddrinfo fails, instead of just telling us that it failed.
Yes, my only concern was with the portability of gai_strerror(), but
when I had a chance to finally look into this, I noticed that
aps do.)
Also, please consider introducing the other change in my patch;
i.e. replacing
rprintf(FERROR,"malformed address %s\n", tok);
with
rprintf(FERROR,
"error matching address %s: %s\n",
tok,
On Fri, Jul 04, 2003 at 11:07:02PM -0500, John Van Essen wrote:
> I had submitted a similar bug report and small patch on April 10:
> There were no followups to it at the time.
Ah yes, I recall thinking that your patch should go in, but I thereafter
forgot about it. I've gone ahead and committed
ess (non-hostname) match is
> also attempted. If the pattern isn't a valid address (maybe because
> it is a hostname that didn't match the pattern) the less helpful
> error message "malformed address " is written to the log for
> every failed match. If hostname &q
Sorry, I missed that an address should be able to contain a slash
(used with netmask) and a % and some more stuff too if it's a scoped
IPv6 address. Here's a new patch.
Thorild Selén
Datorföreningen Update / Update Computer Club, Uppsala, SE
---
tname that didn't match the pattern) the less helpful
error message "malformed address " is written to the log for
every failed match. If hostname "baz" is matched against the
pattern list "foo, bar, baz" this will give two confusing error
messages "
Scott Sipe <[EMAIL PROTECTED]> writes:
> May 31 19:30:49 boud rsyncd[81707]: /etc/pwd.db: No such file or directory
>
> The file is definitely there, and readable.
The server is looking for a /etc/pwd.db in the chroot tree.
> boud# ls -l /etc/pwd.db
> -rw-r--r-- 1 root wheel 40960 May 22 08:0
FreeBSD rsync server (and client as well), running latest rsync port.
I have a nightly cron job that runs rsync. Every time the client
connects I get this message in the server logs:
May 31 19:30:49 boud rsyncd[81707]: /etc/pwd.db: No such file or directory
The file is definitely there, and re
5
> |
> | The machine that I try to copy from :
> | IBM rs6000
> | AIX 4.3
> | Rsync 2.3.1
> |
> | The command I use is
> | /usr/local/bin/rsync -au -q --stats --progress
> | --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2
> | /diskbackup/kanal1/maximus/
> |
> |
. januar 2003 13:45
To: [EMAIL PROTECTED]
Subject: RE: Error message
On Thursday, January 23, 2003 12:36:52 PM +0100 Boris Gegenheimer
<[EMAIL PROTECTED]> wrote:
+--
| The versions of the different machines I use are the initiating
| machine : Sun 450 Solaris 8
| Rsync 2.5.5
|
| The machin
2.3.1
|
| The command I use is
| /usr/local/bin/rsync -au -q --stats --progress
| --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2
| /diskbackup/kanal1/maximus/
|
| The error message comes when he tries to copy that file mentioned below
| which is 14GB big it is not the filesystem or the name of th
> The command I use is
> /usr/local/bin/rsync -au -q --stats --progress
> --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2
> /diskbackup/kanal1/maximus/
>
> The error message comes when he tries to copy that file mentioned below
> which is 14GB big it is not the filesystem or the
/diskbackup/kanal1/maximus/
The error message comes when he tries to copy that file mentioned below
which is 14GB big it is not the filesystem or the name of the file because
it worked with ncftpget.
But that program has other problems that I will not mention here.
Regards Boris
-Original
On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote:
> Hello when i get this message what is wrong:
>
> /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large to be
> stored in data type
>
> Regards Boris
Dunno. That error message is not i
Title: Message
Hello when i get
this message what is wrong:
/PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large to
be stored in data type
Regards
Boris
ECTED]
Sent by: [EMAIL PROTECTED]
05/29/2002 07:24 AM
To: [EMAIL PROTECTED]
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject:Rsync doing nothing and no error message
Classification:
Hi *
I'm using rsync to mirror software from one Sun Workstation
ng at all. just after being called it
exits without any error message, warning, whatever..
here the log files. I did the sync on mecc27 and mecc29 just in case... and it showed
different behaviour !!!
BTW, the two directories are local to each machine, no NFS.
on mecc27 :
/home/cadmgr/bin/rsync
Hi,
I am receiving "reverse name lookup mismatch" errors on one of our rsync
servers. The clients address is both forward and reverse resolvable.
The server is a RedHat 6.2 machine running rsync 2.5.1 and the clients
are Redhat 7.2 machines running rsync 2.5.1. Both the server and the
clients
When I feed a bogus hostname to rsync, it reports "Undefined
error". It would be useful if instead it would say something more
informative, like "Host not found".
Thanks for rsync!
Chris P
Time Connect within Philips, n9hmg on AIM
perl -e 'print pack(,
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
".\n" '
"There are some who call me Tim?"
"David Nickel Jr." <[EMAIL PROTECTED]>
01/1
8:49 AM
To: "Rsync Mailing List" <[EMAIL PROTECTED]>
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject:Error Message!!
Classification:
When rsync starts I get the following messages in my log file
Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync:
When rsync starts I get the following messages in my log file
Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync: bind failed on port 873
Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync error: error in socket IO (code
10) at socket.c(361)
Anybody know what might be causing this?
David
Dave Dykstra <[EMAIL PROTECTED]> wrote:
> ...
> On Wed, Jan 09, 2002 at 11:55:24AM -0500, Philip Mak wrote:
> > Can I make rsync suppress this sort of error
> > message, so that these messages don't show up in my mailbox?
>
> No, you'll have to post-pr
> Is my assessment correct?
Yes.
> Can I make rsync suppress this sort of error
> message, so that these messages don't show up in my mailbox?
No, you'll have to post-process the output of rsync.
- Dave
started, but as it
was running that file (it's a file that stores an e-mail message;
presumably the user retrieved and deleted it) was removed, so rsync
was not able to get it.
Is my assessment correct? Can I make rsync suppress this sort of error
message, so that these messages don't sho
t; and getting this error. My guess is that rsync cannot access all the
> > areas in the source. I got some permission denied errors prior to getting
> > the IO error message..
>
>
> Usually there should have been some other message telling you what the
> problem was.
areas in the source. I got some permission denied errors prior to getting
> the IO error message..
Usually there should have been some other message telling you what the
problem was. If you're coming from an rsync daemon, the error may be in
the daemon's log and not printed to you.
Does anybody know under what conditions does the error,
"IO ERROR skipping delete" show up? I'm trying to sync some areas
and getting this error. My guess is that rsync cannot access all the
areas in the source. I got some permission denied errors prior to getting
the IO error message..
sri
> does that mean?
I'd guess that Dave's guess at the spelling of the error message is what you
actually saw.
If so, it means exactly what Dave said - the command line is too long.
Do you have an '*' or other globber (as it were ;-) somewhere in that
rsync command line
On Tue, Jun 05, 2001 at 03:28:02PM -0400, eric.deandrea wrote:
> i am running rsync from a shell script out of cron to transfer a module
> between 2 solaris servers. I am getting the error "Argument too long". What
> does that mean? I can run the rsync command without a problem from the
> command
i am running rsync from a shell script out of cron to transfer a module
between 2 solaris servers. I am getting the error "Argument too long". What
does that mean? I can run the rsync command without a problem from the
command line. Its only when the rsync command is started from inside the
shell
I get this error message when trying to connect to a rsync daemon:
"permission denied
unexpected EOF in read_timeout"
Does anyone have any idea for the origination of this problem?
Thank you,
Giorgos
> From: "Hoffman, Micah (NCI)" <[EMAIL PROTECTED]>
> Date: Wed, 06 Dec 2000 14:28:18 -0500
> Subject: First time post - cron error message - help needed
>
> I just began to run rsync on a couple of my servers (Solaris 7). I'm
> running the following as a
I just began to run rsync on a couple of my servers (Solaris 7). I'm
running the following as a cron job on server 2 every hour to sync server 2
with server 1:
/usr/local/bin/rsync -vvaxuz --stats --progress --delete \
--rsh=/usr/local/bin/ssh server1:/share/* /share/ \
2>&1 >> /rsync_
87 matches
Mail list logo
