On Fri, 2019-09-06 at 13:12 -0400, Gene Heskett wrote: > On Friday 06 September 2019 11:52:15 Pascal Hambourg wrote: > > > Le 06/09/2019 à 16:39, Gene Heskett a écrit : > > > On Friday 06 September 2019 10:20:14 Greg Wooledge wrote: > > >> I could very easily see amanda itself breaking from usrmerge, if > it > > >> contains programs that try to invoke commands using their full > > >> paths (e.g. /bin/rm -f ...). > > > > Why would that break ? Old paths are still valid, this is the > purpose > > of the symlinks. > > > > Before usr merge : > > /bin/rm -> ok > > /usr/bin/rm -> ko > > > > After usr merge : > > /bin/rm -> ok > > /usr/bin/rm -> ok > > > > Unless something is unable to follow symlinks. > > > > > FAILURE DUMP SUMMARY: > > > picnc / lev 0 FAILED [data timeout] > > > picnc / lev 0 FAILED [[request failed: No route to host]] > > > picnc / lev 0 FAILED [dumper TRYAGAIN: [request failed: No > route > > > to host]] > > > > This is a network error (ARP or NDP address resolution failure). I > > wonder what it has to do with usr merge. > > Good question. Network is working fine on that machine, until amanda > touches it. Amanda's own logs on that machine look normal. > > And I am running out of hair. Ideas to check next appreciated.
Is the problem being talked about here different to amanda usr-merge bug 939411 [1] which I saw that mentioned in another thread [2] ? [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939411 [2] https://lists.debian.org/debian-user/2019/09/msg00219.html -- Tixy
