Hi Ian,
I'm not sure why it would suddenly stop working for you as that seems like a
completely legitimate solution.
FWIW, this is the command I use for unpingable clients:
$Conf{PingCmd} = '/bin/echo $host';
Best of luck!
________________________________
From: Ian via BackupPC-users <backuppc-users@lists.sourceforge.net>
Sent: Friday, April 5, 2024 1:27 PM
To: backuppc-users@lists.sourceforge.net <backuppc-users@lists.sourceforge.net>
Cc: Ian <ran...@pithed.org>
Subject: [BackupPC-users] PingCmd no longer having effect
Hi,
I've been using BackupPC for many years now, and have used /usr/bin/true as the
ping command for hosts that can't respond to ping. However after a reboot on
January 31st, my server stopped obeying pingcmd and stopped backing up those
hosts due to lack of ping response. I am using BackupPC 4.4.0-5ubuntu2 amd64
on Ubuntu 22.04.
So far I have tried:
Overriding $Conf{PingCmd}, $Conf{PingPath}, and $Conf{Ping6Path} in the global
config from webui and config file.
Setting $Conf{PingCmd} in the client config to either /usr/bin/true or ping
-c1 127.0.0.1 using webui and config file.
None of the above seem to make any difference at all anymore. No matter what I
set, I restart the service and get the same error:
2024-04-05 13:58:38 can't ping (client = myclient.com); exiting
However I can confirm other changes to the client config files do have an
effect. For example setting a ClientNameAlias in the client config works.
I also tried deleting the client config file and allowing the webui to create
it, and doing an apt-get --reinstall install backuppc. Same effect.
I'm wondering if anyone has noticed anything similar, or has advice on how to
debug.
Thanks,
Ian
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
