Thanks for the reply ....

After comparing this server to 9 others in the dump, amanda client seems
to be installed fine.

I did discover that this server was comprimsed and was running a SPAM
script from /usr/lib/asterisk/.amandad .....god forbid I ever run into
these script kiddies on the street.

Having said that, I am assuming that the compromise may have broke
something on this server.

I tried a re-installation of amanda-client with the same error. I did
notice that after re-installing
/etc/dumpdates was not created during the install, which tells me perms
are still a problem here, but im stuck
 because the Group ID is fine:
#>id amanda
   uid=33(amanda) gid=6(disk) groups=6(disk)

Perms on /etc/dumpdates is:

-rw-rw-r--  1 root disk 172 Dec 16 02:37 dumpdates

Would anything be logged about failing to create /etc/dumpdates (get
that long pole out, I used the RPM version for CentOS) ?

For 'fun', I tried putting the perms to 777 ..still same error


Any feedback on this would be appreciated :)



Paul Seniuk
Hosting Division,
Thinktel Communications 
-----Original Message-----
From: owner-amanda-users AT amanda DOT org
[mailto:owner-amanda-users AT amanda DOT org] On Behalf Of Gene Heskett
Sent: Monday, December 19, 2005 3:17 PM
To: amanda-users AT amanda DOT org
Subject: Re: /etc/dumpdates

On Monday 19 December 2005 13:20, Paul Seniuk wrote:
>For some reason, one of my clients returns this:
>
>ERROR [can not read/write /etc/dumpdates: Permission denied]
>
>The file permissions are proper and user amanda can access the file.
>
>Any ideas of what else could be thorwing this error on the client?
>Missing libraries perhaps? (client used to work)
>
>Paul Seniuk
>Hosting Division,
>Thinktel Communications

One thing thats crept into the build/install requirements the last
couple of years is a need to re-run ldconfig (as root of course) after
the install of an upgrade version on either the client or the server.

This from the tarball build of course as I won't normally touch an rpm
of amanda with a rather long pole.  Each rpm builder seems to have
his/her own set of favorite options & location for data files, and this
leads to all sorts of breakage when upgrading an rpm.

I hope this helps.

--
Cheers, Gene
People having trouble with vz bouncing email to me should use this
address: <gene.heskett AT verizononline DOT net> which bypasses vz's stupid
bounce rules.  I do use spamassassin too. :-) Yahoo.com and AOL/TW
attorneys please note, additions to the above message by Gene Heskett
are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.