Apparently I did not have enough space left on the client's hard drive (only
10% available free space left). After I made some room on the drive I did
not receive any error messages in the log.
However when I try to do a recovery I get an unexpected end of file error.
Any suggesstions.
BTW thanks Jon for your help.
Rodney
From: Jon LaBadie <[EMAIL PROTECTED]>
Reply-To: amanda-users@amanda.org
To: amanda-users@amanda.org
Subject: Re: can not back up client
Date: Wed, 16 Nov 2005 12:48:40 -0500
On Tue, Nov 15, 2005 at 11:17:58PM -0500, Rodney Johnson wrote:
> The version of tar that is installed on the debian client is 1.13.25
>
> When I manually create and extract the tar I do not get any errors.
>
>
> >From: Jon LaBadie <[EMAIL PROTECTED]>
> >
> >On Tue, Nov 15, 2005 at 09:41:04AM -0500, Rodney Johnson wrote:
> >> I am able to successfully back up Solaris and Red Hat clients. I can
> >not
> >> back up the Debian client. The server is running on Red Hat.
> >>
> >> This is the error message in the log:
> >>
> >> STRANGE dumper <FQDN><DLE> 0 [sec 3057.777 kb 9339610 kps 3054.4
orig-kb
> >> 9749540]
> >> sendbackup: start [<FQDN><DLE> level 0]
> >> sendbackup: info BACKUP=/bin/tar
> >> sendbackup: info RECOVER_CMD=/bin/tar -f... -
> >> sendbackup: info end
> >> ??free(): invalid pointer 0x8063fd8!| Total bytes written:
9983528960
> >> (9.3GB, 3.1MB/s)
> >> sendbackup: size 9749540
> >> sendbackup: end
> >>
> >> Any help would be greatly appreciated.
> >>
> >
> >My first guess is that is a message from tar. The tar is running
> >on the Debian client. What version has Debian supplied?
> >
> >If you manually do the "RECOVER_CMD" on the client do you get an error?
Tar version looks fine.
Disappointing you can't reproduce the problem manually.
Was this a one time occurance or each time you run a dump?
Does it happen on other DLEs from same client?
Have any core dump files been left behind during the run?
On the Debian client, can you see any other error messages
in the debug files (common location /tmp/amanda, but the
config could specify a different location)
Usually when free() (a system, not amanda, function) reports an error
it is a programming bug. Or a bad memory chip or a cosmic ray or ???
Right now we aren't even sure what program was generating the message.
Perhaps someone else has some ideas.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)