Author: Jukka Salmi <j+amanda AT 2008.salmi DOT ch>
Date: Wed, 25 Jun 2008 12:37:15 +0200
Hello, since I upgraded an Amanda installation from 2.4.4p4 to 2.5.2p1, backup reports always contain lines like these: FAILURE AND STRANGE DUMP SUMMARY: amreport: ERROR unexpected log line: 20080625
Author: Jukka Salmi <j+amanda AT 2008.salmi DOT ch>
Date: Thu, 26 Jun 2008 14:34:12 +0200
Jukka Salmi --> amanda-users (2008-06-25 12:37:15 +0200): I just had a closer look at this problem and it seems to be caused by a race condition between programs started by Amanda's driver program: a
Author: "Dustin J. Mitchell" <dustin AT zmanda DOT com>
Date: Thu, 26 Jun 2008 10:11:54 -0400
On Thu, Jun 26, 2008 at 8:34 AM, Jukka Salmi <j+amanda AT 2008.salmi DOT ch> wrote: Yuck! For those playing along at home, note that these are the amdump logs, which are only used by amreport and ams
Author: Jukka Salmi <j+amanda AT 2008.salmi DOT ch>
Date: Thu, 26 Jun 2008 17:02:55 +0200
Dustin J. Mitchell --> amanda-users (2008-06-26 10:11:54 -0400): [...] What about using record locking on a file in the logdir (maybe on the logfile itself)? I.e. making sure that all involved proces
Author: Jean-Louis Martineau <martineau AT zmanda DOT com>
Date: Thu, 26 Jun 2008 10:12:11 -0400
Amanda lock the file while writing to it. What is the output of: amadmin vv version | grep LOCKING Which filesystem is used, is it NFS mounted? Jean-Louis since I upgraded an Amanda installation from
Author: Jukka Salmi <j+amanda AT 2008.salmi DOT ch>
Date: Thu, 26 Jun 2008 17:34:41 +0200
Jean-Louis Martineau --> amanda-users (2008-06-26 10:12:11 -0400): Hmm, amadmin reveals that LOCKING=**NONE** on my system, which probably explains the problem... Furthermore, reading ./configure out
Author: Jean-Louis Martineau <martineau AT zmanda DOT com>
Date: Thu, 26 Jun 2008 11:23:30 -0400
Jukka Salmi wrote: What about using record locking on a file in the logdir (maybe on the logfile itself)? I.e. making sure that all involved processes always acquire an exclusive lock, then write the
Author: "Dustin J. Mitchell" <dustin AT zmanda DOT com>
Date: Fri, 27 Jun 2008 13:56:06 -0400
On Thu, Jun 26, 2008 at 11:34 AM, Jukka Salmi <j+amanda AT 2008.salmi DOT ch> wrote: We had a bit of this sort of trouble in 2.5.2, and the code has been re-worked in 2.6.0. I imagine that some rathe
Author: Jukka Salmi <j+amanda AT 2008.salmi DOT ch>
Date: Sat, 28 Jun 2008 19:05:34 +0200
Dustin J. Mitchell --> amanda-users (2008-06-27 13:56:06 -0400): I'm not familiar with the autotools and with m4, but AFAICT the source of this problem is in config/gnulib/alloca.m4. The resulting `c
Author: "Dustin J. Mitchell" <dustin AT zmanda DOT com>
Date: Sat, 28 Jun 2008 13:53:43 -0400
On Sat, Jun 28, 2008 at 1:05 PM, Jukka Salmi <j+amanda AT 2008.salmi DOT ch> wrote: Actually, it's not quite "wrong." Gnulib is a little weird. What the rest of that macro does is to *check* for allo
Author: Jukka Salmi <j+amanda AT 2008.salmi DOT ch>
Date: Sun, 29 Jun 2008 16:40:40 +0200
Dustin J. Mitchell --> amanda-users (2008-06-28 13:53:43 -0400): ^^ I assume with "it" you mean the "local copy of the file", and not the alloca.h "in the system" (which doesn't exist on my system),
Author: "Dustin J. Mitchell" <dustin AT zmanda DOT com>
Date: Sun, 29 Jun 2008 14:22:16 -0400
On Sun, Jun 29, 2008 at 10:40 AM, Jukka Salmi <j+amanda AT 2008.salmi DOT ch> wrote: Exactly. I would remove the "#ifdef HAVE_ALLOCA_H" from amanda.h and just unconditionally include alloca.h. That'd
Author: Jukka Salmi <j+amanda AT 2008.salmi DOT ch>
Date: Mon, 30 Jun 2008 01:46:13 +0200
Dustin J. Mitchell --> amanda-users (2008-06-29 14:22:16 -0400): Hmm, the problem was that there is no alloca.h on my systems, so this won't work ;-) The attached patch fixes the problem for me, but
Author: "Dustin J. Mitchell" <dustin AT zmanda DOT com>
Date: Sun, 29 Jun 2008 21:04:10 -0400
On Sun, Jun 29, 2008 at 7:46 PM, Jukka Salmi <j+amanda AT 2008.salmi DOT ch> wrote: Well, what works, works, I suppose, and you're welcome to add that to pkgsrc. From my perspective, I'd prefer that