Joshua Baker-LePain ([EMAIL PROTECTED]):
> On Fri, 21 Sep 2001 at 8:43am, Jeremy Wadsack wrote
>> Joshua Baker-LePain ([EMAIL PROTECTED]):
>>
>> > What are the permissions on ~tape (the directory) itself?
>>
>>
>> drwx------ 4 tape disk 1024 Sep 20 23:06 tape
>>
>> Also:
>>
>> [root /home]# su tape
>> [tape /home]$ cat ~/.amandahosts
>> net-cf9a5425 root
> Well, thinking about this all more, this "should" work. Urgh.
That's what I thought. Which is why I brought it to the list... :)
>> > Am I right to say that amanda is still configured to run as user root on
>> > the backup server? If so, try setting up a 'tape' user there,
>> > reinstalling amanda, changing .amandahosts on the client to contain only
>> > the amanda server hostname, and giving it another shot.
>>
>> Ok, I'll give this a shot. I'm hesitant to recompile or rebuild
>> because it works, but this would be something I need to do eventually
>> anyway, so I'll take that step now.
> Ah, good.
Tried this, same error. I'm also getting this cryptic message from
amcheck:
Amanda Backup Client Hosts Check
--------------------------------
ERROR: running as user "tape" instead of "root"
The amcheck binary was updated today. The amandad log (on the backup
server itself, so same build run) shows that CLIENT_LOGIN is 'tape'. I
don't see anything similar for amcheck in it's logs. And it logs-in
just fine on the backup server (as it did before). It just gives this
'ERROR.'
I've tried with and without 'tape' in the client amandahosts and I
don't get access.
Here's something else that might help. 'hostname' on the server gives
me 'net-cf9a5431'. But when it connects to other machines, it looks
like 'net-cf9a5425'. I tried adding both to the client and it still
won't connect.
Any suggestion where I can look next?
Thanks,
--
Jeremy Wadsack
Wadsack-Allen Digital Group
