On Tue, Nov 20, 2001 at 09:01:59PM +0100, Stefan G. Weichinger wrote:
> Hello amanda-users,
>
> I�m writing to you, because -surprise- I have a problem.
> I set up Amanda 2.4.2 last week on our Suse Linux-box.
> I took all the (working) config-files from my recent installation
> and modified them for the new host.
>
> I tried running amcheck and got the message
>
> "Access as amanda not allowed from root@linux"
>
> Spent 2 days looking through mail-archives, edited my .amandahosts,
> moved it to /root, to ~/amanda, did the chmod 0600, the chown
> amanda, tried this and that.
> Found some mail from John R. Jackson, in which he described the
> problem very detailed. Did all the steps, checked everything ...
> Finally I built the security-binary in the common-src-dir, ran it,
> and it ran through ok.
>
> The one thing I don�t quite understand is, that it wants to have the
> .amandahosts-file at /root/.amandahosts while I configured with
> --WITH-USER=amanda
>
Please check your /etc/inetd.conf file. Which user is starting amandad?
> I had some earlier amanda-installation on the machine which I
> removed because of amrecover-problems.
>
> My questions:
>
> Is there an explanation for the failing amcheck while security runs
> through ?
>
There is one problem i once had. The amandad binary had the wrong
shared libraries and that broke DNS.
> Should I remove amanda completely again and
> configure-compile-install from scratch to get it right ?
No, i would start with checking amandad generates debugging files
in /tmp/amanda and send them to the list.
--
Alles Gute / best wishes
Dietmar Goldbeck E-Mail: [EMAIL PROTECTED]
Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
Civilization? Gandhi: I think it would be a good idea.
