Am 19.08.2010 16:37, schrieb Dustin J. Mitchell: > On Thu, Aug 19, 2010 at 5:30 AM, Stefan G. Weichinger <[email protected]> wrote: >> We use a wrapper there for gnu-tar .. > > That means that Amanda got an error writing to the input of > "/usr/local/bin/amgtar -tf - 2>/dev/null | sed -e 's/^\.//'" > which is used to generate the index. > > It looks like it happened 1 second after the dump started. > > I'm guessing this has to do with your wrapper -- perhaps some kind of > race condition where the wrapper quits before it has read all of its > input?
Sure, it's my wrapper ;-) Might be, yes, but it has worked with earlier amanda-releases for years. Reliable. And why does it work then at the second time, when I start amdump manually? The amount of input should be the same at the 2nd time ... ? Might the way amanda calls it has changed as well? My wrapper has one main IF: if [ "$1" = "--create" -a "$3" = "-" -a "$ROOT_DIR" = "/mnt/vm_apps" ] then This way it triggers specific behavior for the DLE "/mnt/vm_apps". The ELSE is: /bin/tar "$@" and no specific exit-clause somewhere. The wrapper writes logs, they all look OK, estimates ran through etc. - Sure, I might trigger that DLE-specific behavior with some pre-DLE-script, but I'd like to avoid that as it very likely won't get paid ... S
