Re: logging problems

[Julian Pace Ross]

Hi Wayne, yes indeed there is something output before the 'rsync allowed access...'

From my syslog:

Apr  8 10:43:32 mail rsyncd[30508]: forward name lookup for julian.malta.com failed: Name or service not known
Apr  8 10:43:32 mail rsyncd[30508]: connect from UNKNOWN (::ffff: 192.168.10.50)
Apr  8 10:43:32 mail rsyncd[30508]: rsync allowed access on module syncvault from UNKNOWN (::ffff:192.168.10.50)
Apr  8 10:43:32 mail rsyncd[30508]: rsync on syncvault from UNKNOWN (::ffff: 192.168.10.50)
Apr  8 10:43:32 mail rsyncd[30508]: sent 14358 bytes  received 79 bytes  total size 77522230
Could this be the problem?

 

Also, on the quest for more clues, I decided to play around a bit and did the following:

I made the the char pointer logfname (in log.c) a global variable in rsync.h.

Then in the function start_daemon (clientserver.c), I added:

rprintf(FLOG, "logfile is: %s\n, logfname);

to output this string to the logs just after

rprintf(FLOG, "connect from %s (%s)\n", host, addr);

 

The result is empty:

Apr  8 10:46:23 mail sshd[30537]: Accepted publickey for julian from ::ffff:192.168.10.50 port 1146 ssh2
Apr  8 10:46:23 mail rsyncd[30540]: forward name lookup for julian.sistinamalta.com failed: Name or service not known
Apr  8 10:46:23 mail rsyncd[30540]: connect from UNKNOWN (::ffff:192.168.10.50)
Apr  8 10:46:23 mail rsyncd[30540]: logfile is:
Apr  8 10:46:23 mail rsyncd[30540]: rsync allowed access on module syncvault from UNKNOWN (::ffff:192.168.10.50)
Apr  8 10:46:23 mail rsyncd[30540]: rsync on syncvault from UNKNOWN (::ffff: 192.168.10.50)
Apr  8 10:46:24 mail rsyncd[30540]: sent 14358 bytes  received 79 bytes  total size 77522230
 

Maybe the line in the conf file hasn't been read yet as you said?

I tried a brute force strcpy(logfname, "/var/log/rsyncd.log) just before this, but then nothing runs...

 

Any ideas?

Thanks

Julian

 

 

On 07/04/06, Wayne Davison <[EMAIL PROTECTED]> wrote:

On Fri, Apr 07, 2006 at 12:54:15PM +0200, Julian Pace Ross wrote:
> It seems something has to be bogged with my setup somewhere,
> and only with rsync --daemon is the log file accessed.

Is rsync complaining about something in your rsyncd.conf file?  If an
error gets output when reading the conf file, it will cause the log
output to initialize to using syslog (since the message needs to go
somewhere, and the log-file is still being parsed).  I'll look into
ways to mitigate this, but it would be good to know if this is the
problem you're seeing (check for any log output that comes before
the "rsync allowed access on module ..." message).

..wayne..

-- 
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html