Logging problem

René van der Kroft rene at backup.nl
Wed Jul 30 17:45:53 EST 2003

At 02:42 29-7-2003 -0700, you wrote:
>On Tue, Jul 29, 2003 at 10:55:56AM +0200, René van der Kroft wrote:
> >
> > All the files are transferred successfully but logging doesn't work OK.
> > When I add a file into the /home directory rsync picks him up and 
> transfers
> > him to the server, but when I look into the logfile he says that the file
> > is uptodate and did not transfer anything. That's strange because the new
> > file is on the server...
>The "is uptodate" is reporting that the file metadata was
>not changed.

Isn't that strange? The file is just new, and isn't on the server...

> > Also when I check the server Internet statistics I see that the outgoing
> > traffic is much bigger than the incoming traffic (23M IN, 35M OUT). Is 
> this
> > correct???
>If the size or modtime differs the receiver will
>send approximately 6 bytes for every 700 (0.9%) to the
>sender.  If there isn't any change in the file the sender
>only instructs the receiver to do a local copy of the data
>in huge chunks.  Those copy instructions don't take much
>bandwidth.  Even accounting for the file-list with metadata
>the sender transmits it is perfectly reasonable to see what
>you report.

Today the rsync run again, the backup directory shows that there where no 
file changed.
The Internet statistics for that connection shows: IN 14M, OUT 
133M!  (Incoming on IP port 22, outgoing keep state)
That while the logs shows that there where no files where copied.

The follwing error showed up today in the logfile:

Received disconnect from IP: 2: fork failed: Resource temporarily unavailable^M
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(150)
_exit_cleanup(code=12, file=io.c, line=150): about to call exit(12)

More information about the rsync mailing list