Comment 23 for bug 782890

Hi Eric,

I did try to reproduce that problem, but I could not do that. I've read through the backuppc documentation and what I can say is:

First, I have built "backuppc setup" to be able to perform the crucial operations on backuppc.
I have built bionic and focal lxc containers.

I wanted to backuppc focal from bionic what was successful.

Then in config.pl file I have put "undef" to both ping(v4) and pingv6. The output:
Can't connect to server (unix connect: Connection refused)

So it was kind of expected.

To do that I have used:

$ BackupPC_serverMesg backup IP focal1 backuppc 1

The BackupPC_serverMesg command verifies that BackupPC is running. This send a message to BackupPC and prints the response.

Then I have set undef to pingv4 and defined pingv6 ('/bin/ping6') and vice-versa.
I could not reproduce that issue then.
I think that a regular ping in that case handles both IPv4 and IPv6.

Could you please help me identify where I am wrong in my testing? I'd appreciate your answer.

P.S. I have tried more complex tests like sending email after backup is done. At first sight, I thought it was successful, but it turned out not to be as successful as I assumed.