planner error with sendsize permissions

2014-09-16 Thread Michael Stauffer
Amanda 3.3.4 Hi, I made some changes to an amanda client. I created a new DLE that pointed to a dir without world-read/exec permissions, and then amcheck gave this error: ERROR: cfile-local: service selfcheck: selfcheck: Failed to chdir(/jag/cnds): Permission denied I googled a bit and saw that

Re: planner error with sendsize permissions

2014-09-16 Thread Debra S Baddorf
I’ve had problems when my amanda temp area was pre-created and had the wrong owner. Is your area owned by (in your case) amandabackup , so that it can both create and delete log files freely? Deb Baddorf Fermilab On Sep 16, 2014, at 3:12 PM, Michael Stauffer wrote: > Amanda 3.3.4 > > H

Re: planner error with sendsize permissions

2014-09-16 Thread Michael Stauffer
Thanks for the reply. I presume that the errors are saying the trouble is writing the log file on the *client* side, correct? On the client, it looks like this: drwx--. 2 amandabackup disk 4096 Sep 16 16:11 /var/log/amanda/amandad/ And when logged in as user amandabackup I can write/delete

Re: planner error with sendsize permissions

2014-09-16 Thread Debra S Baddorf
Well, there IS a log on both the client and the server side. Best to check both. Those permissions from your client match what mine has, so they seem okay. Oh, do check them a level higher too, at your /var/log/amandalevel since that’s the top of the logfile tree. I use bsdtcp (on some cl

Re: planner error with sendsize permissions

2014-09-16 Thread Michael Stauffer
The client-side full tree for logs looks like this: [amandabackup@cfile ~]$ ls -ld /var /var/log/ /var/log/amanda/ /var/log/amanda/amandad/ drwxr-xr-x. 23 root root 4096 Nov 12 2013 /var drwxr-xr-x. 13 root root 4096 Sep 14 05:00 /var/log/ drwxr-x---. 4 amandabackup disk 4096 Sep

Re: planner error with sendsize permissions

2014-09-16 Thread Nathan Stratton Treadway
On Tue, Sep 16, 2014 at 16:45:39 -0400, Michael Stauffer wrote: > Thanks for the reply. > I presume that the errors are saying the trouble is writing the log > file on the *client* side, correct? If I've followed your description correctly, you only made changes on the client side, so I'd also exp