LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Security (https://www.linuxquestions.org/questions/linux-security-4/)
-   -   NFS write access denied on one of two filesystems (https://www.linuxquestions.org/questions/linux-security-4/nfs-write-access-denied-on-one-of-two-filesystems-294060/)

TomF 02-23-2005 05:29 PM

NFS write access denied on one of two filesystems
 
I am running Fedora Core 3, with Selinux active but not completely configured, as an NFS server. In the past, I have successfully accessed several filesystems for read/write from my client. Today, I started getting "access denied" from one of the file systems, while writes continued to work on the other. The only configuration changes that I have made recently are related to installing a new monitor, and I have not touched the exports file.

I have several filesystems exported with
/ FrayneDesktop(ro,insecure,sync,no_root_squash)
/a/b/sata_bulk FrayneDesktop(rw,insecure,sync,no_root_squash)
/a/b/vg-maxtor-bulkdata FrayneDesktop(rw,insecure,sync,no_root_squash)
/a/b/as-hda3 FrayneDesktop(rw,insecure,sync,no_root_squash)
/a/b/as-hda5 FrayneDesktop(rw,insecure,sync,no_root_squash)
/a/b/as-hda5-boot FrayneDesktop(rw,insecure,sync,no_root_squash)
/a/b/as-hda7 FrayneDesktop(rw,insecure,sync,no_root_squash)
/a/b/hdaBulk-hda3 FrayneDesktop(rw,insecure,sync,no_root_squash)

I tried executing exportfs -ra on the server, restarting netfs on the client, and mounting the NFS filesystems. I got:

mount -l
...
asusPC:/a/b/sata_bulk on /a/as-sata_bulk type nfs (rw,noexec,nosuid,nodev,addr=192.168.1.100)
asusPC:/a/b/hdaBulk-hda3 on /a/as-hdaBulk-hda3 type nfs (rw,noexec,nosuid,nodev,addr=192.168.1.100)
[root@localhost root]# cd /a/as-hdaBulk-hda3
[root@localhost as-hdaBulk-hda3]# touch 050223test
touch: cannot touch `050223test': Permission denied
[root@localhost as-hdaBulk-hda3]# touch /a/as-sata_bulk/050223test
[root@localhost as-hdaBulk-hda3]#


I found no messages in /var/log.

Could this be problem with my Selinux configuration? Is there a way to get the error logged? Any other ideas for troubleshooting this problem?

Capt_Caveman 02-23-2005 06:59 PM

Try temporarily disabling SELinux. There should be a tab in the Security Level menu that lets you disable policy enforcement.

TomF 02-23-2005 08:48 PM

Disabling Selinux bypasses the problem
 
Now I need to figure out to enable Selinux and fix the write access problem permanently.


All times are GMT -5. The time now is 03:21 AM.