If you mean the time out I've changed it to 10000, which AFAIK means ten
seconds. And as you'll see below, I see results on the command line in
about 1 second, so an order of magnitude larger should get the job done
if that's the issue. But perhaps that's not what you meant.
I've tried the following:
What Works:
from server command line:
ssh <remoteA> "ping -c 1 -w 3 <remoteB>"
This works with both full paths the command only. It also works with
the "-w" set to 3 or 10. I'm seeing pings returned from B to A in a a
few tens of ms and from remote A back to my terminal in about a second
(over Internet).
What Does Not Work:
from GUI:
ssh <remoteA> "ping -c 1 -w 10 <remoteB>"
$sshPath <remoteA> "ping -c 1 -w 10 <remoteB>"
$sshPath $host "ping -c 1 -w 10 <remoteB>"
I've also run the above with PingMaxMsec with 500, 1000, 2500, and 10000
and not found any change in the error.
So if you or anyone has any idea what to change to make it always
succeed, I'd sure love to know what that is.
One extra note is that this host config uses a ClientNameAlias as it
needs to first ssh to 'remote A'. This seems most logical to me as I
can then leave the $hosts variable and simply override selected
commands. However, I don't believe this should be the issue since I'm
still seeing failures when the ping command uses full paths rather than
variables.
Additionally, I don't see any more indepth debugging info even with
XferLogLevel set to 5. Thoughts?
Eric
On Thu, 2011-11-03 at 16:59 -0500, Les Mikesell wrote:
> On Thu, Nov 3, 2011 at 4:00 PM, Eric Chowanski <eric AT wwek DOT org> wrote:
> >
> > What Does Not Work:
> > Ping to remote machine B works from GUI as part of a manual backup does
> > not work. The backup fails with the error: "no ping response".
> >
> > What I Tried:
> > I researched via Google of course; the BackupPC manual. I also tried
> > via the GUI a number of different combinations for the ping command that
> > were equivalent to the command line command that works.
> >
> >
> > If anyone can point me in the right direction please let me know what
> > that might be. And yes, I know that a VPN is probably the way to go but
> > unfortunately, that is not the highest priority ATM. Please let me know
> > what / if other details are relevant. Thank you for your time.
>
> The quick fix would be to change the ping command for that target to
> something that always succeeds. The down side is that you will then
> have a longer timeout if the ssh connection attempt actually fails.
>
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
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/
|
