rsync - Apr 2006 - logging problems

Hi!

I'd also like to report a strange logging problem I have.
OS: Solaris 2.8
rsync version: 2.6.7

When I run rsync in daemon mode invoked at a command prompt, it does log
information in my configured log file (i.e. /var/log/rsyncd.log). But when I
invoke it via inetd with an entry in inetd.conf, it does not log any
information.

rsync version 2.5.6 did not have this problem.
My inetd.conf entry is:
rsync   stream  tcp     nowait  root    /usr/bin/rsync rsyncd --daemon


Thanks,

Brett Bartick
VP
Corporate Technology
Nomura Securities International
2 World Financial Center
New York, NY  10281





PLEASE READ: This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No confidentiality
or privilege is waived or lost by any mistransmission. If you receive this
message in error, please delete it and all copies from your system, destroy any
hard copies and notify the sender. You must not, directly or indirectly, use,
disclose, distribute, print, or copy any part of this message if you are not the
intended recipient. Nomura Holding America Inc., Nomura Securities
International, Inc, and their respective subsidiaries each reserve the right to
monitor all e-mail communications through its networks. Any views expressed in
this message are those of the individual sender, except where the message states
otherwise and the sender is authorized to state the views of such entity. Unless
otherwise stated, any pricing information in this message is indicative only, is
subject to change and does not constitute an offer to deal at any price quoted.
Any reference to the terms of executed transactions should be treated as
preliminary only and subject to our formal written confirmation.
-------------- next part --------------
HTML attachment scrubbed and removed

On Wed, Apr 05, 2006 at 07:47:03PM -0400, Bartick, Brett
wrote:
> When I run rsync in daemon mode invoked at a command prompt, it does
> log information in my configured log file (i.e. /var/log/rsyncd.log).
> But when I invoke it via inetd with an entry in inetd.conf, it does
> not log any information.
It does log, just not to the named log file (check your syslog).  This
was discussed on the list recently in the context of a single-use daemon
over ssh, but the bug is the same.  One patch is here:

    http://lists.samba.org/archive/rsync/2006-March/015143.html

You'll also find this is fixed in the latest CVS version (which is
available in the latest "nightly" tar file).

..wayne..

Hi Wayne,
Thanks for your mail.
I would just like to confirm that the problem is with my setup:
Using both 2.6.7 with patch, and then 2.6.8cvs ("nightly"), I have the
following scenario:

On linux box 1 (Suse), in /home/julian I have an rsyncd.conf, including 
the global options:

log file = /var/log/rsyncd.log (a 666 mod file)
log format =  etc...
transfer logging = true
etc..

... then the [modules]..

I have no /etc/rsyncd.conf on linuxbox 1, just per-user files.

Now, from linuxbox 2, i run:
rsync -av --delete -e "ssh -i rskey -l julian"   /dir_to_sync   
linuxbox1::julian
which invokes a single-use daemon over ssh.

In the named file (/var/log/rsyncd.log)  I get nothing, and everything 
goes to syslog.

I am slightly confused as to whether this is actually the normal case, 
or the named file should indeed be used.
Was the patch you had sent to correct the "connect" message being
output
to the wrong spot,
or all the log messages being output to the wrong spot? ("wrong spot" 
being syslog...)
I would appreciate your confirmation to this.

Thanks again
Julian

On Thu, Apr 06, 2006 at 03:26:16PM +0200, Julian Pace Ross
wrote:
> I would just like to confirm that the problem is with my setup:
> Using both 2.6.7 with patch, and then 2.6.8cvs ("nightly")
Are you sure you updated the rsync exectuable on the remote machine?
Run "ssh -i rskey -l julian rsync --version" and see if it reports
2.6.8cvs or something earlier.

..wayne..

Hi Wayne!
I downloaded the latest CVS version (rsync-HEAD-20060406-0751GMT.tar.gz at the
time) and gave it a try. It seemed to intermittently work. Reading through this
thread and your conversations with Julian Pace Ross, I believe I am having the
same problem he is. I downloaded the new CVS build
(rsync-HEAD-20060408-1643GMT.tar.gz) and that seemed to fix the problem I was
having! Upon some further investigation, I found out how I could easily
duplicate the problem. If the source machine I was rsyning from couldn't be
resolved on the destination machine running rsyncd from inetd.conf, I
wouldn't get any output in the log file. As soon as I added an entry in
/etc/hosts, it would log again.


2006/04/10 15:05:40 [26642] name lookup failed for XXX.XXX.XXX.XXX: DNS
temporary failure
2006/04/10 15:05:40 [26642] connect from UNKNOWN (XXX.XXX.XXX.XXX)
2006/04/10 15:05:40 [26642] rsync on ABC-upload from jsmith@unknown
(XXX.XXX.XXX.XXX)
2006/04/10 15:05:40 [26642] sent 141 bytes  received 117 bytes  total size 36352

Hope this helps info helps.

Brett

-----Original Message-----
From: Wayne Davison [mailto:wayned@samba.org]
Sent: Thursday, April 06, 2006 4:05 AM
To: Bartick, Brett
Cc: rsync@lists.samba.org
Subject: Re: logging problems


On Wed, Apr 05, 2006 at 07:47:03PM -0400, Bartick, Brett
wrote:
> When I run rsync in daemon mode invoked at a command prompt, it does
> log information in my configured log file (i.e. /var/log/rsyncd.log).
> But when I invoke it via inetd with an entry in inetd.conf, it does
> not log any information.
It does log, just not to the named log file (check your syslog).  This
was discussed on the list recently in the context of a single-use daemon
over ssh, but the bug is the same.  One patch is here:

    http://lists.samba.org/archive/rsync/2006-March/015143.html

You'll also find this is fixed in the latest CVS version (which is
available in the latest "nightly" tar file).

..wayne..


PLEASE READ: This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No confidentiality
or privilege is waived or lost by any mistransmission. If you receive this
message in error, please delete it and all copies from your system, destroy any
hard copies and notify the sender. You must not, directly or indirectly, use,
disclose, distribute, print, or copy any part of this message if you are not the
intended recipient. Nomura Holding America Inc., Nomura Securities
International, Inc, and their respective subsidiaries each reserve the right to
monitor all e-mail communications through its networks. Any views expressed in
this message are those of the individual sender, except where the message states
otherwise and the sender is authorized to state the views of such entity. Unless
otherwise stated, any pricing information in this message is indicative only, is
subject to change and does not constitute an offer to deal at any price quoted.
Any reference to the terms of executed transactions should be treated as
preliminary only and subject to our formal written confirmation.