Hi,
Ward... James Ward wrote on 2008-08-22 08:30:22 -0700 [Re: [BackupPC-users]
busybox tar problem?]:
> On Aug 21, 2008, at 7:04 PM, Holger Parplies wrote:
> >Ward... James Ward wrote on 2008-08-19 16:02:16 -0700 [Re: [BackupPC-
> >users] busybox tar problem?]:
> >>$Conf{PingCmd} = '/usr/local/bin/check_ssh $host';
> >>[...]
> >>$Conf{BackupFilesOnly} = '/etc';
> >>
> >>When the last line contains a '/', I get "no ping response".
> >>When I leave it out, I get "No files dumped for share /".
> >>[and sometimes] I get "lost network connection during backup"?
> >
> >That most certainly has nothing to do with the '/', because the ping
> >command
> >is run long before the tar command line is built.
actually, there is a pattern, and your error messages are incomplete (you
don't just get one message, you get more in your XferLOG, and more than the
one message is relevant). I am convinced that check_ssh is not working
properly for whatever reason (see below).
If it fails initially, you get "no ping response". If it works initially, you
apparently get "No files dumped for share /" (in *both* cases - '/etc' and
'etc', as they're both changed to './etc' by BackupPC::Xfer::Tar, and there's
no reason why an identical command line should behave differently depending on
the contents of an unrelated configuration file on a remote host), which in
turn triggers another "ping" check. If that fails, you get "lost network
connection ..." (and if it doesn't fail, you don't). So, we're back to the
question I forgot to ask initially: what's in /etc/config/users/backup/tarSend?
What shell is it run with, busybox ash? And while we're at it:
$Conf{TarFullArgs}, $Conf{TarIncrArgs} use the default values? What command is
actually executed (XferLOG)? What happens if you pipe that command into
'tar tvf -' on the command line?
> >What does /usr/local/bin/check_ssh contain?
>
> /usr/local/bin/check_ssh is a nagios (binary) plugin that checks for
> ssh connectivity. I use it on all my linux boxes as we have ping
> blocked by the firewall.
>
> [...]
>
> Well, I'd like to think it was that simple, but the network is 1G
> ethernet hard wired.
That's a contradiction. Either you have a firewall or a simple hard wired
ethernet. A firewall can and will limit what goes across the wire - that's its
purpose. It's not uncommon to limit more than you really want to (and that's
better than limitting less than you really want to).
First of all: I don't know check_ssh. Does it reliably return exit code 0 for
success and nonzero for failure? Can you run it repeatedly from a shell
without getting a failure? Try something like
% for i in `seq 1 100`; do
> /usr/local/bin/check_ssh $host || echo "failed on iteration $i"
> done
Yes, that's a tight loop on purpose.
> And these results are 100% repeatable.
If that is true, you must have put considerable effort into verifying it.
There are up to 4 invocations of the ping command if I counted correctly. It
is obviously failing sometimes - the occurrences of "no ping response" and
"lost network connection ..." prove that. You can get more information on
which ones are failing by running BackupPC_dump with a -v option.
> I gave up and am just running a tar via cron.
Presuming you are not satisfied with that solution.
Regards,
Holger
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
