0

I recently installed kubuntu 16.04.6, 32-bit on a machine that I plan to use as a backup server. All went well until I tried to mount my other computers as a client. For example, when I try to mount the client at IP address 192.168.0.237 with:

mount -v -t nfs herman:/home /mnt/backup

I get the following error message:

mount.nfs: timeout set for Mon Oct 14 12:14:15 2019
mount.nfs: trying text-based options 'vers=4,addr=192.168.0.249,clientaddr=192.168.0.237'
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting herman:/home

On herman, my host.allows file includes:

portmap: 192.168.0.237
lockd: 192.168.0.237
mountd: 192.168.0.237
rquotad: 192.168.0.237
statd: 192.168.0.237

The host.deny file is:

ALL: PARANOID

The /etc/exports file includes the following line:

/home       192.168.0.237(rw,no_subtree_check)

On the host, 192.168.0.237,

rpcinfo -p

gives:

program vers proto   port  service
100000    4   tcp    111  portmapper
100000    3   tcp    111  portmapper
100000    2   tcp    111  portmapper
100000    4   udp    111  portmapper
100000    3   udp    111  portmapper
100000    2   udp    111  portmapper
100024    1   udp  47440  status
100024    1   tcp  41305  status
100021    1   udp  43041  nlockmgr
100021    3   udp  43041  nlockmgr
100021    4   udp  43041  nlockmgr
100021    1   tcp  58816  nlockmgr
100021    3   tcp  58816  nlockmgr
100021    4   tcp  58816  nlockmgr

and on the server, herman

rpcinfo -p

gives:

program vers proto   port  service
100000    4   tcp    111  portmapper
100000    3   tcp    111  portmapper
100000    2   tcp    111  portmapper
100000    4   udp    111  portmapper
100000    3   udp    111  portmapper
100000    2   udp    111  portmapper
100005    1   udp  57499  mountd
100005    1   tcp  37583  mountd
100005    2   udp  59970  mountd
100005    2   tcp  32963  mountd
100005    3   udp  37256  mountd
100005    3   tcp  60257  mountd
100003    2   tcp   2049  nfs 
100003    3   tcp   2049  nfs 
100003    4   tcp   2049  nfs 
100227    2   tcp   2049
100227    3   tcp   2049
100003    2   udp   2049  nfs 
100003    3   udp   2049  nfs 
100227    2   udp   2049
100227    3   udp   2049
100021    1   udp  57580  nlockmgr
100021    3   udp  57580  nlockmgr
100021    4   udp  57580  nlockmgr
100021    1   tcp  33809  nlockmgr
100021    3   tcp  33809  nlockmgr
100021    4   tcp  33809  nlockmgr
100024    1   udp  42137  status
100024    1   tcp  43815  status

I found another post where the user had the same problem and in his case the solution had something to do with, 'apparmor' and a "DENIED" included in the output of dmesg. I ran dmesg and had the following 2 lines in the output. I don't think this in meaningful, because as far as I know, I have no dependency on 'apparmor', but I thought I should include following excerpt from my dmesg output:

dmesg | fgrep -i denied
[   57.915343] audit: type=1400 audit(1570997933.469:24): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name="/proc/1577/status" pid=1577 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
[   57.915416] audit: type=1400 audit(1570997933.469:25): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name="/proc/1577/status" pid=1577 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

I have been looking at other posts with the same problem, but I have not found a solution yet.

Can anyone help with suggestions on why the client is being denied nfs access?

Thanks in advance.

Jim A

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.