ERROR [can not access /dev/hdg1 (/dev/hdg1): Permission denied]
I corrected the ~amanda .amandahosts access issue by changing amandas default home dir. I still get access Errors on the partitions for my newly added clients. I have tried using both hdg1 and /dev/hdg1 in the disk list. Amanda Backup Client Hosts Check ERROR: sunny3.neptune.com: [can not access /dev/hdg1 (/dev/hdg1): Permission denied] ERROR: sunny2.neptune.com: [can not access /dev/hda1 (/dev/hda1): Permission denied] sunny3 is running REDHAT 7.1 sunny2 is running REDHAT 7.0
Re: ERROR [can not access /dev/hdg1 (/dev/hdg1): Permission denied]
ERROR: sunny3.neptune.com: [can not access /dev/hdg1 (/dev/hdg1): Permission denied] ERROR: sunny2.neptune.com: [can not access /dev/hda1 (/dev/hda1): Permission denied] Well this look like a problem inside each client now, not a problem between server and client. On sunny2 (and 3) connect as the user youdefined for Amanda and see whether you can access /dev/hdg1. If not, find the reason and correct it. Olivier
Re: ERROR [can not access /dev/hdg1 (/dev/hdg1): Permission denied]
Denise Ives wrote: I still get access Errors on the partitions for my newly added clients. I have tried using both hdg1 and /dev/hdg1 in the disk list. Amanda Backup Client Hosts Check ERROR: sunny3.neptune.com: [can not access /dev/hdg1 (/dev/hdg1): Permission denied] ERROR: sunny2.neptune.com: [can not access /dev/hda1 (/dev/hda1): Permission denied] The amanda user on the clients (suny[23]) needs to have read access to the raw disk devices. Usually making the amanda user a member of the disk group is okay. On some machines I have to chmod g+r /dev/sdb1 -- [EMAIL PROTECTED] - HMC UNIX Systems Manager My opinions are my own and probably don't represent anything anyway.
