>>> What is in /tmp/amanda/sendsize*debug on paperbark after a failed amdump?
>
>sendsize: debug 1 pid 31909 ruid 0 euid 0 start time Wed Nov 8 08:30:17
>2000
>/usr/local/amanda/libexec/sendsize: version 2.4.1p1
That's it?? That would certainly explain the message. The file is
very incomplete.
What's in /tmp/amanda/amandad*debug? Make sure you don't run anything
of Amanda between the failure and grabbing the file as it's usually
overwritten (unless you used --with-pid-debug-files).
Can you tell if there are any stray processes running for your Amanda
user?
Are there any messages in the system logs about amandad or sendsize?
What happens if you do this on paperbark (or whatever machine you used
to build those binaries):
cd client-src
gmake getfsent
./getfsent /home ### run this on paperbark
(none of this has to be done as root). This tests out some of the file
system name conversion routines. According to some of my log files,
that's the next line that should have show up in the debug file.
>back to the line "paperbark /home lev 0 FAILED [missing result for /home in
>paperbark response]"
>
>does the lev 0 mean anything? ...
It means Amanda was asking about a level 0 (full) backup. Probably not
of interest, but we'll keep it in mind.
>Nathan
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
