On Tue, Aug 12, 2003 at 05:36:46PM +0200, Nicolas Ecarnot wrote:
> Jon LaBadie a écrit :
> 
> >To simplify things I'd suggest changing the disklist on the amanda
> >server so that only one DLE on the AIX client is uncommented.  You
> >will have many fewer debug files to contend with.
> 
> I already did that.
> To debug : the simpler, the better.
> 
> >Also, the debug files list the commands they start, arguments included.
> >You could run each by hand and see if you note a core dump.
> 
> *THAT* is what I wanted you to say ;o)
> How do I run commands by hand ?

After emptying out the amanda debug directory (default /tmp/amanda),
and running an amdump from your amanda server with your single DLE setup,
what files do you have in the debug directory?

Have you looked in them?  For example, in one of my "runtar" debug files
I find:

  runtar: debug 1 pid 16840 ruid 27 euid 0: start at Tue Aug 12 01:50:02 2003
  /usr/local/libexec/amgtar: version 2.4.4-20030529
  running: /usr/local/libexec/amgtar: /usr/local/libexec/amgtar --create \
  --file /dev/null --directory /u2 --one-file-system --listed-incremental \
  /usr/local/var/amanda/gnutar-lists/butch_u2_0.new --sparse \
  --ignore-failed-read --totals \
  --exclude-from /tmp/amanda/sendsize._u2.20030812015002.exclude .

You see, it shows the long, ugly, command line that was used for a run
of my wrapper, amgtar.

That is the type of entry I'm suggesting you find in the debug files and
run the commands by hand (as amanda user) to determine which one(s) may
cause problems and core dump.


-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)