Jennifer,
I recall getting some error like this when I setup rsync on Solaris 9. I'd
recommed the following:
1. Check the rsync version is the same at both ends.
2. Use option --rsync-path to tell rsync where its friend keeps the binary.
3. Check your runtime library path with crle command
Hi,
I've got another error that is not in the FAQ ;) Ran from a script in a
directory that doesn't exist anymore:
shell-init: could not get current directory: getcwd: cannot access parent
directories: No such file or directory
building file list ...
pop_dir /mnt/dar
.i386.rpm
rsync: error writing 4 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
I'm using rsync-2.5.5-4 (the rsync shipped with RH9). The first time rsync
halted (indefinitely), every other run gives the above error
/avifile/avifile-0.7.34-1.dag.rh90.i386.rpm
rsync: error writing 4 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
I'm using rsync-2.5.5-4 (the rsync shipped with RH9). The first time rsync
halted (indefinitely), every
Hi,
I just compiled new release 2.5.6 rsync in solaris5.9 machines,
and ran a rsync job,I got the following errors:
rsync error: unexplained error (code 255) at main.c(620)
Both source and destination servers are running 5.9, can you please
tell me should I update anything in main.c file
Hi I've got rsync setup to replicate DNS for an irc network I help run.
I'm the primary DNS, so I use the rsync client to connect to a friend running another
DNS server, and he has the rsync daemon setup.
the conf is as follows
log file = /root/rsync.log
[tinydns]
path = /etc/tinydns/root/
can't find it
mentioned in the NEWS -- hmm). There have also been some changes to
improve the mkstemp error (to make it contain the full path to the temp
file), but I note that it needs a little more improvement to handle
daemon mode -- I'll look into that.
..wayne..
--
To unsubscribe or change
I have seen this error in many postings, but the solutions seem not to
apply in this case. This error happens during a small file transfer
(gif image) and after 75% of a 165G rsync job (the building file list
portion is complete.) Most solutions I saw were related to not having
enough RAM
On Wed, Sep 03, 2003 at 03:49:12PM -0400, Matt Miller wrote:
I have seen this error in many postings, but the solutions seem not to
apply in this case. This error happens during a small file transfer
(gif image) and after 75% of a 165G rsync job (the building file list
portion is complete
Hit the not a regular file (recv_files) error last night
having replaced a directory with a file.
The really dumb part is that this was hit doing a link-dest
on an empty destination so the robust_unlink would have
presented no problem anyway.
I can see no reason why non-directory special files
What is the exact command you are using on the cygwin
client to do the rsync transfer?
--
Hardy Merrill
Red Hat, Inc.
IMAC, Sebastian Mangelkramer [EMAIL PROTECTED] wrote:
hi rsync-list,
i have an authentication problem with my rsync-server.
@ERROR auth failed on module XXX
i`ve
On 22 Aug 2003 16:11:21 +0200
Lars Bungum [EMAIL PROTECTED] wrote:
Greetings!
I'm experiencing these problems as described in this mail:
---
From: Thomas Quinot ([EMAIL PROTECTED])
Subject: Rsync 2.5.5: FreeBSD mknod can't create FIFO's
This is the only article in this thread
On Tue, 2003-08-26 at 03:08, Martin Pool wrote:
I'm experiencing these problems as described in this mail:
---
From: Thomas Quinot ([EMAIL PROTECTED])
Subject: Rsync 2.5.5: FreeBSD mknod can't create FIFO's
This is the only article in this thread
Newsgroups: mailing.unix.rsync
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
Thank you,
Finally, my porblem is the secret file have to key in a enter at the end of
line.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 23, 2003 2:42 PM
To: CHEUNG Chi Wai, Chris
Cc: '[EMAIL PROTECTED]'
Subject: Re: authentication error
Greetings!
I'm experiencing these problems as described in this mail:
---
From: Thomas Quinot ([EMAIL PROTECTED])
Subject: Rsync 2.5.5: FreeBSD mknod can't create FIFO's
This is the only article in this thread
View: Original Format
CHEUNG Chi Wai, Chris [EMAIL PROTECTED] wrote:
I have setup a Rysnc server in Mandrake 9.1
When I add a auth user into my Rsync.conf and rsync.secrets,
it do not work, everytime it shows
[EMAIL PROTECTED] rsync [EMAIL PROTECTED]::X/.html/. /
Password:
@ERROR: auth failed on module
I have setup a Rysnc server in Mandrake 9.1
When I add a auth user into my Rsync.conf and rsync.secrets,
it do not work, everytime it shows
[EMAIL PROTECTED] rsync [EMAIL PROTECTED]::X/.html/. /
Password:
@ERROR: auth failed on module X
rsync: connection unexpectedly closed (89 bytes
I am receiving the following error on an HP UX machine on execution of
make.
make
gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c
lib/snprintf.c
-o lib/snprintf.o
lib/snprintf.c: In function `dopr':
lib/snprintf.c:199: warning: signed and unsigned type in conditional
Okay, with this patch I now get error messages, but it still creates
null
filled output files. I guess that is what you meant by the behavior is
the
same.
That is correct. At the point in which we detect the
problem there isn't anything we can do to produce
good files. The most i can
On Mon, Aug 18, 2003 at 01:41:51PM -0700, David Norwood wrote:
Okay, with this patch I now get error messages, but it still creates
null
filled output files. I guess that is what you meant by the behavior is
the
same.
That is correct. At the point in which we detect the
problem
jw schultz writes:
I've had a chance to think on it. Attached is a patch that
allows unmap_file() to report the first read error that
map_ptr found. The behaviour is the same. I doubt this will
apply against anything but CVS HEAD as of now.
This should probably use FERROR instead
On Thu, Aug 14, 2003 at 11:46:51PM -0700, [EMAIL PROTECTED] wrote:
jw schultz writes:
I've had a chance to think on it. Attached is a patch that
allows unmap_file() to report the first read error that
map_ptr found. The behaviour is the same. I doubt this will
apply against anything
I get an error when copying a specific directory using rsync. It works for a lot of
smaller files, but when it comes to a 1.2 GB file, it always fails with the following
error:
rsync: writefd_unbuffered failed to write 4 bytes: phase unknown: Broken pipe
rsync error: error in rsync
Oops, sorry - this was a stupid beginner's mistake.
Just found out that when I was issuing the commands I never had the target disk
mounted, so the copied files went to the mount directory on the root filesystem
instead, where there was not enough space - ouch :(
Regards,
Steve
--
To
I've had a chance to think on it. Attached is a patch that
allows unmap_file() to report the first read error that
map_ptr found. The behaviour is the same. I doubt this will
apply against anything but CVS HEAD as of now.
This should probably use FERROR instead of FINFO so that a
partial
On Fri, Aug 15, 2003 at 02:04:50PM -0700, David Norwood wrote:
I've had a chance to think on it. Attached is a patch that
allows unmap_file() to report the first read error that
map_ptr found. The behaviour is the same. I doubt this will
apply against anything but CVS HEAD as of now
I'm using rsync to mirror files from a Windows XP machine mounted via smbfs.
Apparently I have something configured wrong as I get a permisson denied error
accessing some of the files on the smbfs mount with cp, od, etc. However, rsync
produces no error messages on these files. It happily
On Thu, Aug 14, 2003 at 12:41:19PM -0700, David Norwood wrote:
[reformatted because someone doesn't know how to compose email]
I'm using rsync to mirror files from a Windows XP machine
mounted via smbfs. Apparently I have something configured
wrong as I get a permisson denied error accessing
configured
wrong as I get a permisson denied error accessing some
of the files on the smbfs mount with cp, od, etc.
However, rsync produces no error messages on these files.
It happily creates files in the target directory that are
the right size, but filled with null bytes
On Wed, Jul 30, 2003 at 12:33:45AM -0400, Thomas Cort wrote:
Hello All,
I keep getting rsync: connection unexpectedly closed (1074142 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(165). Does
anyone have any idea of what could cause this? I've gotten
Hi Thomas,
On Wed, Jul 30, 2003 at 12:33:45AM -0400, Thomas Cort wrote:
I keep getting rsync: connection unexpectedly closed (1074142 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(165). Does
anyone have any idea of what could cause this? I've gotten
Are you using the -z flag for compression? If so, are you using
the latest CVS version? There was a bug in token.c that was recently
I've tried it with and without compression and I get the same error.
I think it may be a problem with the server I'm connecting to.
My box is part of a mirror
Hello All,
I keep getting rsync: connection unexpectedly closed (1074142 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(165). Does
anyone have any idea of what could cause this? I've gotten the same error on
two seperate machines. One UltraSparc running Linux
Hi guys,
anyone ever seen that kind of error?
ESNW01:rsync -vruzt --delete 10.1.1.10::SITE/aodat vol1:/progstest
Loading module RSYNC.NLM
RSync 2.5.5
Version 2.55July 10, 2003
Copyright 2003 Andrew Tridgell, Paul Mackerras, Martin Pool
(1013) read_timeout: Error peer socket closed
On Thu, Jul 24, 2003 at 01:26:45PM +0200, Marcus Forthuber wrote:
Hi guys,
anyone ever seen that kind of error?
ESNW01:rsync -vruzt --delete 10.1.1.10::SITE/aodat vol1:/progstest
Loading module RSYNC.NLM
RSync 2.5.5
Version 2.55July 10, 2003
Copyright 2003 Andrew Tridgell, Paul
On Fri, Jul 18, 2003 at 11:10:39AM +0200, [EMAIL PROTECTED] wrote:
Hi,
after syncing I get the following error:
rsync error: unexplained error (code 255) at main.c(620)
Line 620 has moved but i'd say that it is most likely that
ssh returned -1. You might try fiddling with blocking-io
Hi,
after syncing I get the following error:
rsync error: unexplained error (code 255) at main.c(620)
If I use -vvv I get the follwing error:
rsync error: errors with program diagnostics (code 13) at log.c(284)
_exit_cleanup(code=13, file=log.c, line=284): about to call exit(13)
All files
Just for the record, the patch to token.c for the -z bug that was
discovered by Yasuoka Masahiko and patched by him and Wayne Davison
has fixed the problem that I reported here:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg07289.html
Thanks guys, this bug has been biting me for the past 6
HI,
I'm trying to transfer a list of files within a filesystem to another filesystem. I've
used the option:
# rsync -avzol --progress /wp05/global/FCSI/WP_RLS05/rundir/ /nfs_proj/global/WP/
However, it had produced the error below:
building file list ... global/FCSI/WP_RLS05/rundir
, Leaw, Chern Jian wrote:
HI,
I'm trying to transfer a list of files within a filesystem to another filesystem.
I've used the option:
# rsync -avzol --progress /wp05/global/FCSI/WP_RLS05/rundir/ /nfs_proj/global/WP/
However, it had produced the error below:
building file list ... global/FCSI
. replacing
rprintf(FERROR,malformed address %s\n, tok);
with
rprintf(FERROR,
error matching address %s: %s\n,
tok,
gai_strerror(gai));
in match_address. This gives a more descriptive error message when
but not transfer
files.
When I try to transfer a file from the client to the server I use
the command:
rsync -avz fapmenu fisdev::bak
The client displays the following messages:
@ERROR: access denied to bak from pgiprd.forsoft.com
(192.168.2.19)
rsync
enough to be able to list modules but not transfer
files.
When I try to transfer a file from the client to the server I use
the command:
rsync -avz fapmenu fisdev::bak
The client displays the following messages:
@ERROR: access denied to bak from
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 we already
supply a compatibility function
Hi Hardy:
Nice catch - I missed that one when I reviewed the man page.
Unfortunately it made no difference. I have also tried moving
the module params from the global section to the module section
but that also made no difference - exactly same messages.
Just to keep things straight, here is my
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.
On Fri, Jul 04, 2003 at 12:17:43PM -0700, Hugh E Cruickshank wrote:
hosts allow = fisdev pgiprd
Each of these names needs to be either a fully-qualified hostname, a
wildcard expression that matches a fully-qualified hostname, an IP
address, localhost, or some combination thereof. E.g.:
hosts
will probably
get the same error you had before. Your hosts allow line
looked like this:
hosts allow = fisdev pgiprd
3) Now, change the values of that hosts allow to be complete
domain names, like 'fisdev.your.domain.com' and
'pgiprd.your.domain.com' and see if that works now.
If you're not sure
On Mon, Jul 07, 2003 at 03:38:15PM -0400, Hardy Merrill wrote:
[...] kill and restart the rsync daemon, and try your rsync again.
I've noticed that it's not necessary to kill and restart the rsync
daemon to get it to honor changes to the rsyncd.conf file. FYI.
..wayne..
--
To unsubscribe or
Hi Wayne:
You are correct. This did make a difference but did not resolve the
problem. See my previous response to Hardy Merrill's message.
Thanks, Hugh
--
Hugh E Cruickshank, Forward Software, www.forward-software.com
From: Wayne Davison Sent: Monday, July 07, 2003 12:36
On Fri, Jul 04,
Hi Wayne:
That's good to know. I thought that it might be the case (as it is
with SAMBA), but I did not see anything obvious in the man pages
(that or I am blind - always a good possibility).
Regards, Hugh
From: Wayne Davison Sent: Monday, July 07, 2003 12:44
On Mon, Jul 07, 2003 at
, and try your
rsync again. Hopefully that will work.
This made a small difference. The client no reports:
building file list ... done
rsync: connection unexpectedly closed (28 bytes read so far)
rsync error: error in rsync
.
This made a small difference. The client no reports:
building file list ... done
rsync: connection unexpectedly closed (28 bytes read so
far)
rsync error: error in rsync protocol data stream (code 12
On Mon, Jul 07, 2003 at 02:38:02PM -0700, Hugh E Cruickshank wrote:
Hi Wayne:
That's good to know. I thought that it might be the case (as it is
with SAMBA), but I did not see anything obvious in the man pages
(that or I am blind - always a good possibility).
It is documented in the
Yes, the man page clearly states:
Note that you should not send the rsync server a HUP sig-
nal to force it to reread the /etc/rsyncd.conf. The file
is re-read on each client connection.
So I am obviously blind or at least not as attentive as I should be.
to be able to list modules but not transfer
files.
When I try to transfer a file from the client to the server I use
the command:
rsync -avz fapmenu fisdev::bak
The client displays the following messages:
@ERROR: access denied to bak from pgiprd.forsoft.com
(192.168.2.19
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
messages:
@ERROR: access denied to bak from pgiprd.forsoft.com
(192.168.2.19)
rsync: connection unexpectedly closed (80 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at
io.c(150)
While the server issues the following log message
that didn't match the pattern) the less helpful
error message malformed address foo 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 malformed address foo malformed address bar
);
+ rprintf(FERROR,
+ error matching address %s: %s\n,
+ tok,
+ gai_strerror(gai));
freeaddrinfo(resa);
return 0;
}
@@ -192,6 +195,19 @@
return ret;
}
+/* Test if a string is likely
isn't a valid address (maybe because
it is a hostname that didn't match the pattern) the less helpful
error message malformed address foo 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
, and then after that I get a problem.
rsync: read error: Connection reset by peer
rsync error: error in rsync protocol data stream (code 12) at io.c(177)
If I remove the contents on the server and backup again, it works fine.
Then of course, the next incremental backup will fail like above. If I
control-C
daemon.warning] inflate returned -3 (0
bytes)
Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] rsync error: error in
rsync protocol data stream (code 12) at ../token.c(416)
Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] rsync: connection
unexpectedly closed (197041 bytes read
on the rsyncd server:
Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] inflate returned -3
(0 bytes)
Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] rsync error: error in
rsync protocol data stream (code 12) at ../token.c(416)
Jun 18 00:48:18 ead62 rsyncd[9632
On Mon, 16 Jun 2003 at 16:24:25 -0700, jw schultz wrote:
After looking at io.c, it seems like the problem (rather, the symptom)
for
this error message is a failed write() call (which explains the Broken
Pipe message to stderr). I thought maybe --blocking-io would avoid this
issue
On Tue, Jun 17, 2003 at 09:10:38AM -0500, Nathaniel Case wrote:
On Mon, 16 Jun 2003 at 16:24:25 -0700, jw schultz wrote:
After looking at io.c, it seems like the problem (rather, the symptom)
for
this error message is a failed write() call (which explains the Broken
Pipe message
I'm an new to rsync and am having the following problem:
On a HP-UX 11.0 server, I am trying to install rsync 2.5.6. After running
configure, I run the standard HP make, but with the GCC compiler specified.
I get the following error.
lib/snprintf.c:760: conflicting types for `snprintf'
/usr
I am running rsync ver 2.5.5 on HP-UX 11.0. Whenever I run an rsync
specifying the o or g option to maintain owner or group info, I get
an error similar to the one below. The actual error code changes every
time, but it's always the same main.c line number. The error
message does not occur if I
On Tue, Jun 17, 2003 at 04:48:26PM -0600, Hursch, Robert wrote:
I am running rsync ver 2.5.5 on HP-UX 11.0. Whenever I run an rsync
specifying the o or g option to maintain owner or group info, I get
an error similar to the one below. The actual error code changes every
time, but it's always
PROTECTED]::backup/dest
Password:
building file list ... rsync: writefd_unbuffered failed to write 4092
bytes: phase send_file_entry: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(515)
---[snip]---
With more -v's, I end up with the same message at the end, but it's
:
---[snip]---
# rsync -a -v --modify-window=2 /backup/Source/Dir/
[EMAIL PROTECTED]::backup/dest
Password:
building file list ... rsync: writefd_unbuffered failed to write 4092
bytes: phase send_file_entry: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(515)
---[snip
My setup rsync --version 2.5.5
on client and server
client is behind firewall/nat
on client I run:
rsync -av --progress 110mb_file.mov [EMAIL PROTECTED]::dir1
on server:
rsync --daemon
it asks for password, starts to transfer the file, and at about 80% gives me
this error message:
==cut
the file, and at about 80% gives me
this error message:
==cut==
Password:
building file list ...
1 file to consider
110mb_file.mov
rsync: error writing 4 unbuffered bytes - exiting: Connection reset by peer
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
==cut
Rsync 2.5.6 has a problem with pathnames or filenames longer than 255.
I redefined them in rsync.h, which generated errors on make pointing to
the previous definitions which look fine. Any ideas on where to check next?
Here's the error I got trying to rsync:
receiving file list ... done
media
On Tue, Jun 10, 2003 at 08:25:54AM -0500, Edward King wrote:
Rsync 2.5.6 has a problem with pathnames or filenames longer than 255.
I redefined them in rsync.h, which generated errors on make pointing to
the previous definitions which look fine. Any ideas on where to check next?
Those were
I am using rsync 2.5.6 to copy from a system running redhat 6.2
(192.168.0.50) to another system running redhat 6.2 (192.168.0.70).
The command line I'm using is:
rsync -avW --numeric-ids --delete 192.168.0.50::vgroup00/* /vgroup00/
It complains
IO error encountered - skipping file deletion
/ ' also:
# rsync -ax --showtogo --stats --exclude /Volumes/ / /Volumes/System
But I get a protocol error (broken pipe) in io.c. When copying all the
subdirectories manually, everything works, so I think he tries toa void a
cyclic copy.
(I'm using rsync 2.5.5, or rather rsyncx 1.7d, a special
rsync the parameters -x for one-file-system, and
'--exclude /Volumes/ ' also:
# rsync -ax --showtogo --stats --exclude /Volumes/ / /Volumes/System
But I get a protocol error (broken pipe) in io.c. When copying all the
A broken pipe means that the process on the other end of the
pipe died
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
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:08
On Thu, May 29, 2003 at 10:10:57AM -0400, Manuel Soto wrote:
Each time I try to rsync I get error 23
rsync error: some files could not be transferred (code 23) at
main.c(636)
I see that files that has 700 permission are not synchronized by the
root
I'm sure it is more than just 0700
When I run rsync -a to mirror a large directory structure on Mac OS/X
10.2.4, it always (100%) produces a bus error. Small directory structures
work fine.
The computer in question has 768 MB RAM and 10 GB free disk space, so
memory is not a problem. This is rsync 2.5.2 supplied with Mac OS/X
On Tue, Apr 01, 2003 at 10:43:55PM -0500, Daniel Barrett wrote:
When I run rsync -a to mirror a large directory structure on Mac OS/X
10.2.4, it always (100%) produces a bus error. Small directory structures
work fine.
The computer in question has 768 MB RAM and 10 GB free disk space, so
Rsync Ver: 2.5.5
OS: HPUX-11
Hello List,
I'm using rsync with ssh with this command line:
rsync -avz -e ssh some_file [EMAIL PROTECTED]:/home/user-b
Which does work, however I get the following error output:
rsync error: protocol incompatibility (code 2) at main.c(578)
Since the file does
, however I get the following error output:
rsync error: protocol incompatibility (code 2) at main.c(578)
Since the file does transfer, is the error output just some sort of bug? I
looked in the maillist archives, and I found only one person that replied
stating that the error message was merely
JW,
Thank you for replying. You are correct in that I do have two identical
machines, thanks for clarifying.
It seems I still get the same exact error message with or without using SSH.
Which brings me back to why I'm I getting the error message, eventhough the
file has transferred?
Regards
to be the whole tree backed up (AFAICT by looking).
However, at the end of the log I often see the following error:
rsync error: partial transfer (code 23) at main.c(578).
Looking at the rsync website, I've seen several reports of this behaviour,
but there's nothing there to tell me (a) whether it is actually
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
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 in the rsync source.
Since you
/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
-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 the file because
it worked with ncftpget.
But that program
|
| 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 the file
:
| 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/
|
| The error message comes when he tries to copy that file mentioned below
| which is 14GB big
On Thu, Jan 23, 2003 at 08:53:21PM -0600, Paul wrote:
Hello! This is not a real problem, since it seems to work correctly
anyway. But I'm still wondering about it. If I just execute rsync with
no switches or targets, it prints the usage, then gives an error at the
bottom:
rsync error
Hi!
I use PHP exec function Run rsync
?
exec(/usr/bin/rsync -azrvlHpogDtS --delete --progress --password-
file=/root/rsyncd_db.secrets /home/bruce [EMAIL PROTECTED]::brucebackup);
?
but run error
error message: @ERROR: auth failed on module brucebackup
but login linux run form command
/usr
Using this command: rsync -azurvp /Users/spaceman/ -e ssh
[EMAIL PROTECTED]:/home/test --timeout=60
wrote 2577422743 bytes read 79546 bytes 448846.72 bytes/sec
total size is 2831489571 speedup is 1.10
rsync error: partial transfer (code 23) at
/SourceCache/rsync/rsync-8/rsync/main.c(576
::TMP
opening tcp connection to moby port 873
@ERROR: auth failed on module tmp
rsync: connection unexpectedly closed (87 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(150)
[root@core /]#
[root@moby /]# tail /var/log/messages
Dec 11 12:07:51 moby rsyncd[16370
/local/bin/rsync --rsync-path=/usr/local/bin/rsync
--password-file=/etc/rsyncd.secrets -vv /tmp nexnix@moby::TMP
opening tcp connection to moby port 873
@ERROR: auth failed on module tmp
rsync: connection unexpectedly closed (87 bytes read so far)
rsync error: error in rsync protocol data stream
Thanks - that fixed it. I failed to spot the difference between
the secrets file on the server and the password file on the client.
many thanks
nick@nexnix
The secrets file on the server (moby) needs the user names
in it as specified in rsyncd.conf(5) The format isn't the same as
the
1101 - 1200 of 1491 matches
Mail list logo
