Re: amrecover index empty
2005-11-24 15:12:31
On Thu, Nov 24, 2005 at 05:44:03PM +0100, Jehan PROCACCIA wrote:
> Jon LaBadie wrote:
>
> Anyway .. we found the solution :-)
> It's just a question of rights modes on /tmp on the client stations.
> Certainly due to misse use of amrecover on clients /tmp , the "restore
> owner modes on "." [Y,n]" might have been answered Yes :-( !
> so just resetting chmod 1777 on /tmp on the clients systems which had
> lost their indexes corrected the problem.
> Apperently the dump is "forking" the dump to the amanda server and to a
> local pipe which finally does a "started index creator: "/sbin/restore
> -tvf - 2>&1 | sed -e '..." and this restore is done on the local /tmp !
> if tmp is not writable, here's the problem I had .
>
I was wondering why there was no restore in your ps listing.
Maybe that was your "defunct" process. It tried to open a file
on /tmp, failed, and terminated. Just a guess.
BTW, you got the permissions on /tmp correct now, 1777.
But are the owner/group correct? If not owned by root,
then whomever owns it could remove others files.
--
Jon H. LaBadie jon AT jgcomp DOT com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
|
|