Re: Re: NFS problem after update to rpcbind-0.1.4-8.fc7

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Steve Dickson wrote:

>Is selinux in the picture? If so try 'setenforce 0'
>What does 'service rpcbind status' say?

selinux is disabled.
[root@pavilion etc]# sestatus -v
SELinux status:                 disabled


Tests:

1)
[root@pavilion etc]# service rpcbind status
rpcbind (pid 3387) is running...

2)
[root@pavilion etc]# service nfs status
rpc.mountd is stopped
nfsd is stopped
rpc.rquotad is stopped

3) root@pavilion etc]# service nfslock status
rpc.statd dead but pid file exists

4) [root@pavilion etc]# service nfslock restart
Stopping NFS statd:                                        [FAILED]
Starting NFS statd:                                        [FAILED]

5) [root@pavilion etc]# service nfs start
Starting NFS services:                                     [  OK  ]
Starting NFS quotas: Cannot register service: RPC: Authentication
error; why = Client credential too weak
rpc.rquotad: unable to register (RQUOTAPROG, RQUOTAVERS, udp).
                                                           [FAILED]
Starting NFS daemon:                                       [FAILED]


-- 

mike cohler

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux