Hi,
obj AT jltechinc DOT com wrote on 2009-05-29 17:54:14 -0400 [Re:
[BackupPC-users] Backuppc - connection refused]:
> Chris88 said the following on 05/29/2009 05:19 PM:
> > Hi,
> >
> > I´m using bacckuppc now over 4 months without problems.
> >
> > But since yesterday the backup of every client fails with an connection
> > refused.
the basic question to ask is: what changed yesterday (or, more precisely,
between the last working backup and the first failing one)? Did you change
something (anything - even if you think it is unrelated)? Maybe someone else
changed something (eg. your provider) - that is harder to find out.
> > So, I checked somethings:
> >
> > On the server:
> >
> > rsync hostname::C
> > rsync: failed to connect to hostname: Connection refused (111)
> > rsync error: error in socket IO (code 10) at clientserver.c(122)
> > [receiver=3.0.3]
> >
> > rsync hostIP::C
> > password:
This basically indicates that "hostname" does not resolve to "hostIP" any
longer - probably a DNS issue. What *does* "hostname" resolve to now ("dig
hostname", "ping hostname", "host hostname" ...)? What does
"hostname.your-domain.com" resolve to (fill in your DNS domain)? What does
"hostname." (note the dot at the end) resolve to?
> > But,
> >
> > nmblookup hostname shows the correct ip-address?!
NMB is Windoze ... if at all possible, you should use DNS for IP name
resolution, not NMB. BackupPC has some provisions for using NMB, but I'm not
sure about the details right now. If you can, avoid it.
> > Clients has static-ip-addresses.
Meaning it should be easy to avoid NMB.
> > The OS is debian lenny.
On the server or on the clients (or both)? "hostname::C" looks like a Windoze
share (but need not be).
> > Is this a backuppc problem?
No. Definitely not. You showed above that command line rsync has the same
issue.
> > If I configure in the host.conf the client-name as the ip-address from
> > the client, the backup starts. But with the hostname it fails with an
> > connection refused?!
That is the same thing you demonstrated above. For some reason, name
resolution gives you an incorrect IP address.
Which is why this answer is, well, misleading, though not strictly wrong:
> This can happen is you inadvertently change the master "config.pl" Xfer
> type to "rsync" and all your clients are expecting "smb"...had this
> happen to me once, and all windows clients went red.
The obvious cause of that problem is that rsync is not set up to be used for
backups. The subtlety involved is that if you actually set up both SMB and
rsync, you might still observe this, because SMB in fact uses NMB name
resolution (and falls back to DNS, I believe) while rsync uses DNS. So a
broken DNS setup can cause rsync transfer to fail just as much as a missing
(or misconfigured) rsync can.
The thing I'd learn from this comment, though, is to explicitly set the
XferMethod in each host.pl file rather than relying on the default. If you
decide to change your XferMethod throughout your network, you're unlikely
to change all hosts at once, anyway.
Regards,
Holger
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
