LinuxSA Mailing list archives

  From: David Lloyd <lloy0076@rebel.net.au>
  To  : Jason Tan <jason@rebel.rebel.net.au>
  Date: Wed, 22 May 2002 15:49:27 +0930

Re: Amanda problem

Jason

> > > Any suggestons would be very wlecome, I'm afraid Im rather stumped.
> >
> > Amanda is particularly cantankerous but one gets used to it.
> >
> > Have you tried:
> >
> > 1) logging in as the amanda user
> > 2) running dump
> 
> Yes.
> 
> It seems to work.
> I can dump for example amanda's log file dir as the amanda user.

On the machine that is being backed up, in /tmp/amanda there are log
files. Almost always you'll find the problem described there (amanda is
*very* verbose to the point of being difficult to tell the wood for the
trees).

You could also try running tcpdump (or ethereal) on the amanda client
whilst the amanda server is running if amanda is not logging anything.
In addition, if you the client and/or server is running a firewall
(packet filtering) then it would be best to consult the amanda
documentation, contained with the source and the mailing list archives.
Amanda doesn't particularly like it when any of its packets get mangled
or nat'ted.

PS: It's better to build amanda by hand from source; the RPM's are
shockers

DSL
-- 
And Ptah begat the thought and the word
 And by these thoughts and words
 Atum, mighty God, created the world from the void!
 [An interpretation of the Memphite Creation myphs]

-- 
LinuxSA WWW: http://www.linuxsa.org.au/  IRC: #linuxsa on irc.linux.org.au
To unsubscribe from the LinuxSA list:
  mail linuxsa-request@linuxsa.org.au with "unsubscribe" as the subject