[SOLVED] Error while getting quota : Connection refused

[ashwith]

We recently upgraded the hard disk on our NFS server. This one has quota enabled. When I run the command 'quota' on any of the client machines, I get an error before the quota for my account is displayed (this happens for other users as well).

Code: Select all

quota: Error while getting quota from 10.107.90.41:/cad3 for 1585: Connection refused
Disk quotas for user ashwith (uid 1585): 
     Filesystem  blocks   quota   limit   grace   files   quota   limit   grace
10.107.90.3:/home1/users
                  69428  3500000 4000000           16310       0       0      

The IP address listed in the error, is *not* the server that has quota enabled. It is an NFS server though. Here's the output for rpcinfo -p:

Code: Select all

   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  41825  status
    100024    1   tcp  54333  status
    100007    2   udp    669  ypbind
    100007    1   udp    669  ypbind
    100007    2   tcp    672  ypbind
    100007    1   tcp    672  ypbind
    100021    1   udp  32769  nlockmgr
    100021    3   udp  32769  nlockmgr
    100021    4   udp  32769  nlockmgr
    100021    1   tcp  32803  nlockmgr
    100021    3   tcp  32803  nlockmgr
    100021    4   tcp  32803  nlockmgr
    100011    1   udp    875  rquotad
    100011    2   udp    875  rquotad
    100011    1   tcp    875  rquotad
    100011    2   tcp    875  rquotad
    100005    1   udp    892  mountd
    100005    1   tcp    892  mountd
    100005    2   udp    892  mountd
    100005    2   tcp    892  mountd
    100005    3   udp    892  mountd
    100005    3   tcp    892  mountd
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    2   tcp   2049  nfs_acl
    100227    3   tcp   2049  nfs_acl
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    2   udp   2049  nfs_acl
    100227    3   udp   2049  nfs_acl

What have I missed and what do I do to fix this? Please do let me know if any other information is needed.

[jlehtone]

Do note that there are two servers: 10.107.90.41 and 10.107.90.3
One responds to rquota-queries and the other does not.

Either the 10.107.90.41 does not have rquotad or a firewall blocks access to it.

[ashwith]

Thanks for the hint! Yes, indeed it was a firewall problem. Here are the steps I used on the NFS server to fix it (all done as root):

1. Uncomment or add the following line in /etc/sysconfig/nfs

Code: Select all

RQUOTAD_PORT=875

2. Restart rpcbind and nfs servers by running the following as root (I preferred to stop and then start):

Code: Select all

service rpcbind stop
service nfs stop
service rpcbind start
service nfs start

3. Open the above port:

Code: Select all

iptables -I INPUT 5 -p tcp -m state --state NEW -m tcp --dport 875 -j ACCEPT; done
iptables -I INPUT 6 -p udp -m state --state NEW -m udp --dport 875 -j ACCEPT; done

4. Save the configuration

Code: Select all

service iptables save

[jlehtone]

The iptables command does change only the runtime config.
It is not stored on shutdown by default and thus does not survive reboot.

Use 'service iptables save' to store the configuration.

[ashwith]

Thanks again! I've added it to the post.