Hi,
My nightly rsync jobs recently began to fail. I don't recall making any
modifications to the rsync config files or upgrading rsync. Below is the error I
receive when I try to rsync the home directory of serverA to serverB. Is there
anything obviously wrong? Thanks.
serverA rsync # rsync -arczv --delete --password-file=/etc/rsync/rsync.password
/home 192.168.1.4::home
@ERROR: auth failed on module home
rsync: connection unexpectedly closed (88 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(189)
/var/log/rsyncd.log on ServerB
2005/06/07 11:29:24 [22075] rsyncd version 2.6.0 starting, listening on port 873
2005/06/07 11:29:35 [20870] auth failed on module home from serverA.domain.com
(192.168.1.3)
Server Setup
---/etc/rsyncd/rsyncd.conf---
pid file = /var/run/rsyncd.pid
log file = /var/log/rsyncd.log
max connections = 2
[home]
path = /home
comment = /home on serverA server
uid = root
gid = root
auth users = root
hosts allow = 192.168.1.3
use chroot = yes
read only = no
list = yes
secrets file = /etc/rsyncd/rsyncd.secrets
strict modes = true
---/etc/rsyncd/rsyncd.secrets---
root:really_long_password_here
Client Setup
---/etc/rsync/rsync.password---
really_long_password_here
On Tue, Jun 07, 2005 at 12:07:49PM -0400, twsnnva@cox.net wrote:> 2005/06/07 11:29:35 [20870] auth failed on module home from serverA.domain.com (192.168.1.3)If you upgrade the server to 2.6.5, rsync will log the reason that the auth failed on that log-file line (password mismatch, missing secret, unauthorized user, invalid challenge response) Also, it doesn't have the bug (fixed in 2.6.3) that causes a secret (or password) file's last (or only) line to be ignored if it doesn't end in a newline (which you might also check for). If you can't upgrade, try various failure points, like manually specifying the rsyncd username (user@host::module), inputting the password manually, etc., to try and narrow down the failure. ..wayne..
On Tue, 7 Jun 2005, <twsnnva@cox.net> wrote: Thanks for the detail in your report. Error messages, log messages, config files all in one email. :)> /var/log/rsyncd.log on ServerB > > 2005/06/07 11:29:24 [22075] rsyncd version 2.6.0 starting, listening on port 873 > 2005/06/07 11:29:35 [20870] auth failed on module home from serverA.domain.com (192.168.1.3)I don't know if the fork() happens before or after the auth, but I would expect the PID values to be the same or the child's PID to be slightly higher after only 11 seconds. So the PID values imply that you have multiple daemons running. Have you checked for that? John