A few days ago I noticed that none of my hosts are backing up. All but two give the error, "no ping (ping too slow: 38.94msec (threshold is 35msec))" -- or some similar ping. One such host is named "
You are giving the wrong info here so you might be looking at it wrong. that 3002ms is the total time the ping operation took. This isnt really comparable to the actual ping times. here: PING www.yah
Author: Holger Parplies <wbppc AT parplies DOT de>
Date: Thu, 4 Sep 2008 04:50:42 +0200
Hi Dan, you might consider reading what you're replying to, which very much happens implicitly if you don't top-post. dan wrote on 2008-09-03 19:06:07 -0600 [Re: [BackupPC-users] Ping too slow]: This
Author: Craig Barratt <cbarratt AT users.sourceforge DOT net>
Date: Wed, 03 Sep 2008 22:21:27 -0700
BackupPC should parse this last line and extract 0.138msec as the round trip time. To see exactly the command it is running and the output it gets, run: su backuppc BackupPC_dump -f -v shipping Hit ^
but ping Good catch. It is doing: ping -c 1 shipping ... the trick being it is _not_ doing nmblookup to get the IP address of the windows host. Instead, it's trying to DNS "shipping" using opendns. O
Hi Andrew, This is a VERY good example of why you should avoid OpenDNS or any other DNS service that returns bogus data when queried for non-existing hosts. They create confusion and breaks the princ
Author: Craig Barratt <cbarratt AT users.sourceforge DOT net>
Date: Thu, 04 Sep 2008 18:34:23 -0700
Look at "How BackupPC Finds Hosts" in the documentation. First DNS is checked. If it fails, then nmblookup is done (if configured). Then ping is used to check if the host is alive (if configured). Yo
Look at "How BackupPC Finds Hosts" in the documentation. First DNS is checked. If it fails, then nmblookup is done (if configured). Then ping is used to check if the host is alive (if configured). Y