Error Running Install Command For Nfsd
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more rpc nfsd unable to access proc fs nfsd errno 2 about Stack Overflow the company Business Learn more about hiring developers or posting ads fatal: error inserting nfsd with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for nfsd dead but subsys locked system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the exportfs: internal: no supported addresses in nfs_client top having trouble setting up NFS server on centos 6.5 up vote 1 down vote favorite Setup: Provider: Linode nfs server: a linode with centos 6.5 nfs client: a linode with centos 6.5 When I tried mounting mount.nfs: access denied by server while mounting x.x.x.x:/shared This is happening when I try to start nfs service both on client and server [shortfellow@li829-73 ~]$ sudo service nfs restart Shutting down NFS daemon:
Starting Nfs Quotas: Cannot Register Service: Rpc: Unable To Receive; Errno = Connection Refused
[ OK ] Shutting down NFS mountd: [ OK ] Shutting down RPC idmapd: [ OK ] FATAL: Module nfsd not found. FATAL: Error running install command for nfsd Starting NFS services: [ OK ] Starting NFS mountd: [ OK ] Starting NFS daemon: [ OK ] Starting RPC idmapd: [ OK ] I do not understand the problem. linux centos nfs linode share|improve this question edited Jan 15 '15 at 13:19 ewwhite 151k47298576 asked Jan 14 '15 at 11:20 Ranjith Ramachandra 16817 What is the output of uname -a. –ewwhite Jan 14 '15 at 11:42 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote Please post your kernel version with the output of uname -a. Being that this is a Linode instance, you're probably running a special kernel managed by the provider. The errors you're seeing indicate that NFS is not compiled into the kernel or the module not available. Can you try: # modinfo nfsd # modprobe nfsd share|improve this answer answered Jan 14 '15 at 11:42 ewwhite 151k47298576 and when you get modinfo: ERROR: Module nfsd not found...? –dylnmc Dec 16 '15 at 18:54 add a comment| up vote 0 down vote # /etc/init.d/nfs start FATAL: Mo
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org >
Mount.nfs: Requested Nfs Version Or Transport Protocol Is Not Supported
Fedora 23/24 > Servers & Networking [SOLVED] NFSD won't compile in the mount unknown filesystem type nfsd kernel FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts mount.nfs: no such device Search Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums http://serverfault.com/questions/659389/having-trouble-setting-up-nfs-server-on-centos-6-5 Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 24th May 2010, 03:08 AM Taniel Offline Registered User Join Date: Jan 2009 Posts: 9 NFSD won't compile in the kernel Hi I'm runing FC11 and have compiled the vanilla kernel 2.6.33.4 to support Dazuko. It has broken http://forums.fedoraforum.org/showthread.php?t=245525 my NFSD server in the process, and I can't figure out why. I get these errors on boot. FATAL: Module nfsd not found. FATAL: Error running install command for nfsd Starting NFS services: [60G[[0;32m OK [0;39m] Starting NFS quotas: [60G[[0;32m OK [0;39m] Starting NFS daemon: [60G[[0;32m OK [0;39m] Starting NFS mountd: [60G[[0;32m OK [0;39m] I'm not sure why it's looking for nfsd as a module. I have compiled the kernel with CONFIG_NFSD=y In my .config file I have also set up the following options CONFIG_NFS_FS=y CONFIG_NFS_V3=y CONFIG_NFS_V3_ACL=y CONFIG_NFS_V4=y # CONFIG_NFS_V4_1 is not set CONFIG_ROOT_NFS=y CONFIG_NFSD=y CONFIG_NFSD_V2_ACL=y CONFIG_NFSD_V3=y CONFIG_NFSD_V3_ACL=y CONFIG_NFSD_V4=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_EXPORTFS=y CONFIG_NFS_ACL_SUPPORT=y CONFIG_NFS_COMMON=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y CONFIG_IP_PNP_BOOTP=y CONFIG_IP_PNP_RARP=y CONFIG_NET_ETHERNET=y Does anyone know why it isn't compiled into the kernel? It's very frustrating. Regards Taniel Taniel View Public Profile Find all posts by Taniel #2 24th May 2010, 05:14 AM forkbomb Offline Registered User Join Date: May 2007 Location: U.S. Posts: 4,851 Re: NFSD won't compile in the kernel You've compiled NFS support into the kernel, but the nfs init script is looking for a module for nfs. See line 79-82 of /etc/
Sign in Pricing Blog Support Search GitHub This repository Watch 2,917 Star 35,892 Fork 10,557 docker/docker Code Issues 1,813 Pull requests 154 Projects 0 https://github.com/docker/docker/issues/20430 Wiki Pulse Graphs New issue Install NFS in docker container #20430 Closed teknowmics opened this Issue Feb 18, 2016 · 5 comments Projects None yet Labels None yet https://www.svennd.be/nfs-in-a-centos-6-lxc-proxmox-4-1/ Milestone No milestone Assignees No one assigned 3 participants teknowmics commented Feb 18, 2016 Hello, We are trying to install NFS service in docker container but getting following error unable to message when trying to start the service. [root@sweb ~]# service rpcbind start Starting rpcbind: [ OK ] [root@sweb ~]# service nfs start FATAL: Could not load /lib/modules/3.10.0-327.el7.x86_64/modules.dep: No such file or directory Starting NFS services: [ OK ] Starting NFS mountd: [ OK ] Starting NFS daemon: rpc.nfsd: Unable to access /proc/fs/nfsd errno 2 (No such file or directory). Please error running install try, as root, 'mount -t nfsd nfsd /proc/fs/nfsd' and then restart rpc.nfsd to correct the problem [FAILED] [root@sweb ~]# [root@sweb ~]# cat /etc/issue CentOS release 6.7 (Final) Kernel \r on an \m [root@sweb ~]# uname -a Linux sweb 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux nfsd kernel module is loaded on host system. [root@dockerhost ~]# lsmod | grep nfs nfsd 302418 1 auth_rpcgss 59343 1 nfsd nfs_acl 12837 1 nfsd lockd 93600 1 nfsd grace 13295 2 nfsd,lockd sunrpc 300464 7 nfsd,auth_rpcgss,lockd,nfs_acl Please advise. HackToday commented Feb 18, 2016 Did this nfs need to access host resource ? And how do you start this container ? Could you append your docker run specific commands you run ? Docker member thaJeztah commented Feb 18, 2016 I suspect the nfs server may need more privileges, e.g. this example ("use at your own risk") needs to be run with --privileged https://hub.docker.com/r/cpuguy83/nfs-server/ teknowmics commented Feb 18, 2016 Thank you Sebastiaan for the comment. I was able to start nfs service after running docker command with --pr
only recently switched part of our infrastructure over to LXC. But no NFS would be definitely a no-go. We only work in a virtualized environment because its easy for backups and to efficiently use the computational resources on each of our server. That's the reason, security of what a container can do, is only a second to functionality. On top of that, most of these containers are not giving out a service to the outside world, the only reason they have a connection to the web is for LAN and updates. So before you use this "guide", know that I did not look into it. Installing NFS I started by updating & installing nfs common's. # updates yum update -y # install nfs yum install nfs-utils nfs-utils-lib Next I tried to start & keep them online after reboot. # mark them as start-during-boot chkconfig rpcbind on chkconfig nfs on # start the services service rpcbind start service nfs start I received this error : Starting NFS daemon: rpc.nfsd: Unable to access /proc/fs/nfsd errno 2 (No such file or directory). Please try, as root, 'mount -t nfsd nfsd /proc/fs/nfsd' and then restart rpc.nfsd to correct the problem Which I believe means, that some of the nfs kernel modules was not loaded when the container was started. This was solved by installing nfs-kernel-server on the proxmox head. apt-get install nfs-kernel-server I also needed to add an exception to apparmor, I don't know exactly how apparmor works, but it can be overruled in the lxc configuration (/etc/pve/lxc/101.conf) with : (add) lxc.aa_profile: unconfined After that I restarted the container in proxmox webgui. (cause I don't know the console commands 🙂 ) I retried and the services started. Although I found that NFS was not reporting as working : service nfs status rpc.svcgssd is stopped rpc.mountd (pid 1061) is running... nfsd dead but subsys locked However a mount from an external machine worked. /etc/exports from lxc container /data *(rw,sync,no_root_squash,no_subtree_check) and a soft mount from the client (non lxc in this test) mount -o soft,rw lxc_ip:/data /mnt/tmp So not 100% its save, but its working 🙂 This entry was posted in Linux, SysAdmin. Bookmark the permalink. Post navigation ← Bye OpenVZ, Hey LXC rethinking dynamic/static pages → Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website Related Posts:mount: unknown filesystem type ‘nfs' (proxmox)Mount shareable dir to openvz & proxmoxSetting up distributed filesystem glusterFS on CentOS 6.7…Se