** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/782890
Title:
no ping response on all hosts after upgrade
To manage notifications about this bug go to:
https://
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/782890
Title:
no ping response on all hosts after upgrade
To manage notifications about this bug go to:
https://bu
This came up again during my daily triage. Nothing has changed since
the last time I looked into the bug. I still don't think it's a good
candidate for an SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I have installed backuppc on Jammy (current development release) and
verified that $Conf{Ping6Path} is correctly set to /bin/ping6. I also
installed the package on Bionic (our oldest LTS), and verified that
Ping6Path is empty there. The same issue happens on Focal.
I think the easiest solution h
Thank you for the update. This looks like it should be straightforward
to fix, so I've added it to the server team's backlog. But since the
workaround is trivial it will be prioritised quite low and we may
continue to not get to it any time soon.
If someone can volunteer a patch (in the form of th
This bug is quite old, but I stumbled on a broken backuppc (refusing
backup due to ping) after upgrading the backup server. Backuppc now has
version 3.3.0 (I am even not sure that this has changed during the
upgrade that broke the backup).
ping6 hostname failed, but ping succeeded.
The ping6 con
This still occurs (at least with localhost) with BackupPC 3.3.0 on *buntu 14.04
(Trusty Tahr). The Ping6Path value is still "undef" by default. Workaround is
to set it to /bin/ping6 (or force it true for localhost):
http://sourceforge.net/p/backuppc/mailman/message/27518026/
--
You received t
Oh. I guess that's not a module any more, because I'm behind the times
on my legacy IPv4 network. :)
So, to check if this is the problem, you can temporarily disable IPv6:
sauer@pyro:~$ ip addr show lo
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:0
I'm pretty sure this is a bug in BackupPC, since:
sauer@pyro:~$ lsmod | grep -c ipv6
0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/782890
Title:
no ping response on all hosts after upgrade
To man
This happened on my lucid-to-precise upgrade. I didn't even have the
Ping6Path in my config.pl; I would have never thought that maybe the
tool would use IPV6 on a network without IPV6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
This bug was opened because a Maverick to Natty upgrade, but the Lucid
(Server LTS) current version (3.2.0-3ubuntu4~lucid1) of BackupPC is also
affected. I see that recent versions of Ubuntu Server have more recent
version of BackupPC, and I presume that this bug is solved on that
versions, but Luc
** Changed in: backuppc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/782890
Title:
no ping response on all hosts after upgrade
To manage notifications abou
** Changed in: backuppc (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/782890
Title:
no ping response on all hosts after upgrade
To manage notifications abo
Thanks for the response, ipv6 shouldnt be the default and I will try to
get this fixed soon.
Regards
chuck
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/782890
Title:
no ping response on all hosts
I was hit by the same bug after upgrade to Natty - the original poser's
solution worked (configuring "$Conf{Ping6Path} = '/bin/ping6';".
I totally agree that this should be set by default - there's no reason
for others to waste time trying to figure out why backups aren't working
(there's no clear
Chuck,
Actually, I'm not really sure. I installed server 10.10 and I don't think I
strayed much from the defaults. For some reason, either backuppc thinks that
I am using ipv6, or it was installed/enabled during the upgrade to 11.04. Is
it usually installed or enabled by default? How can I tell if
So you are using ipv6?
Thanks
chuck
** Changed in: backuppc (Ubuntu)
Importance: Undecided => Low
** Changed in: backuppc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
17 matches
Mail list logo
