rsync - Jan 2007 - rsync: mkstemp "/20070129_1012/.status.csv.IWS933" (in test) failed: No such file or directory (2)

Hi,

---
+ rsync -av --timeout 120 /home/20070129_1012/status.csv --port 5873
fileserver::test/20070129_1012/status.csv
building file list ... done
status.csv
rsync: mkstemp "/20070129_1012/.status.csv.IWS933" (in test) failed:
No such
file or directory (2)

sent 347 bytes  received 38 bytes  770.00 bytes/sec
total size is 228  speedup is 0.59
rsync error: some files could not be transferred (code 23) at main.c(789)
---

I keep getting these problems on and off (no every time!) when I run my
rsync command.
I'm using rsync 2.6.4 and also tried to compile 2.6.9 on both ends but that
failed to resolve my problem.

Any ideas?
-------------- next part --------------
HTML attachment scrubbed and removed

i'd appreciate any help here please :)

On 1/29/07, Shai <shaibn@gmail.com> wrote:
>
> Hi,
>
> ---
> + rsync -av --timeout 120 /home/20070129_1012/status.csv --port 5873
> fileserver::test/20070129_1012/status.csv
> building file list ... done
> status.csv
> rsync: mkstemp "/20070129_1012/.status.csv.IWS933" (in test)
failed: No
> such file or directory (2)
>
> sent 347 bytes  received 38 bytes  770.00 bytes/sec
> total size is 228  speedup is 0.59
> rsync error: some files could not be transferred (code 23) at main.c(789)
> ---
>
> I keep getting these problems on and off (no every time!) when I run my
> rsync command.
> I'm using rsync 2.6.4 and also tried to compile 2.6.9 on both ends but
> that failed to resolve my problem.
>
> Any ideas?
>
-------------- next part --------------
HTML attachment scrubbed and removed

On Mon, Jan 29, 2007 at 04:20:34PM +0200, Shai wrote:
> rsync: mkstemp "/20070129_1012/.status.csv.IWS933" (in test)
failed: No such
> file or directory (2)
That's an OS error that tells you that your directory is missing.  Why
that happens is most likely outside the scope of rsync.  You should
check the server logfile if you want to see the full pathname, but it
will just be the listed name prefixed with the "path" setting for the
module.

..wayne..

On 1/29/07, Shai <shaibn@gmail.com> wrote:
> + rsync -av --timeout 120 /home/20070129_1012/status.csv --port 5873
> fileserver::test/20070129_1012/status.csv
> rsync: mkstemp "/20070129_1012/.status.csv.IWS933" (in
> test) failed: No such file or directory (2)
Since you want the file to have the same name "status.csv" on the
destination as on the source, you can omit that name from the
destination path: "fileserver::test/20070129_1012/".  This will have
the same effect except that rsync will create the directory
"20070129_1012" if it doesn't exist before trying to receive a
file
into it.

Note to people who might encounter this message in the archives: since
rsync 2.6.7, when the receiver is receiving a single file that is not
a directory, it tries to change into the containing directory first.
Thus, people who try the original command with rsync 2.6.7 or newer
should see a "push_dir" error instead of a "mkstemp" error.

Matt