WW 3.7: Configure NFS on Centos7
1,294 views
Skip to first unread message
Vince Forgetta
Sep 22, 2015, 4:06:35 PM9/22/15
to Warewulf
Hi all,
I have installed WW3.7 (latest svn) on Centos7. I have provisioned a Centos7 image to some nodes that also boot fine. I can ping the NFS server from the provisioned nodes. NFS works fine on the master node and can mount shares from the NFS server.
I noticed that the kernel module on the provisioned node does not have nfs (lsmod | grep nfs returns nothing).
Anyone have tips on how to set this up?
I have tried poking around with installing the packages for nfs (yum --config= --installroot= install nfs-utils), but reports it is already installed:
yum --config=/var/chroots/hydraex-centos7/root/yum-ww.conf --installroot=/var/chroots/hydraex-centos7/ install nfs-utils
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Package 1:nfs-utils-1.3.0-0.8.el7.x86_64 already installed and latest version
Nothing to do
Any tips would be greatly appreciated.
Thanks,
Vince
Vince Forgetta
Sep 22, 2015, 4:10:23 PM9/22/15
to ware...@lbl.gov
Output from trying to start the nfs-server service:
# systemctl start nfs-server
A dependency job for nfs-server.service failed. See 'journalctl -xn' for details.
[root@D1P-HYDRAEX01 ~]# journalctl -xn
-- Logs begin at Tue 2015-09-22 08:53:33 EDT, end at Tue 2015-09-22 09:08:04 EDT. --
Sep 22 09:08:03 D1P-HYDRAEX01.ldi.lan systemd[1]: Starting Notify NFS peers of a restart...
-- Subject: Unit rpc-statd-notify.service has begun with start-up
-- Defined-By: systemd
--
-- Unit rpc-statd-notify.service has begun starting up.
Sep 22 09:08:03 D1P-HYDRAEX01.ldi.lan mount[4646]: mount: unknown filesystem type 'nfsd'
Sep 22 09:08:03 D1P-HYDRAEX01.ldi.lan sm-notify[4662]: Version 1.3.0 starting
Sep 22 09:08:03 D1P-HYDRAEX01.ldi.lan systemd[1]: Started Notify NFS peers of a restart.
-- Subject: Unit rpc-statd-notify.service has finished start-up
-- Defined-By: systemd
--
-- Unit rpc-statd-notify.service has finished starting up.
--
-- The start-up result is done.
Sep 22 09:08:03 D1P-HYDRAEX01.ldi.lan rpc.statd[4664]: Version 1.3.0 starting
Sep 22 09:08:03 D1P-HYDRAEX01.ldi.lan rpc.statd[4664]: Flags: TI-RPC
Sep 22 09:08:03 D1P-HYDRAEX01.ldi.lan rpc.statd[4664]: Initializing NSM state
Sep 22 09:08:03 D1P-HYDRAEX01.ldi.lan systemd[1]: Started NFS status monitor for NFSv2/3 locking..
-- Subject: Unit rpc-statd.service has finished start-up
-- Defined-By: systemd
--
-- Unit rpc-statd.service has finished starting up.
--
-- The start-up result is done.
Sep 22 09:08:04 D1P-HYDRAEX01.ldi.lan systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun with start-up
-- Defined-By: systemd
--
-- Unit systemd-tmpfiles-clean.service has begun starting up.
Sep 22 09:08:04 D1P-HYDRAEX01.ldi.lan systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
--
-- Unit systemd-tmpfiles-clean.service has finished starting up.
--
-- The start-up result is done.
From /var/log/messages:
Sep 22 09:10:01 D1P-HYDRAEX01 systemd: Starting Session 10 of user root.
Sep 22 09:10:01 D1P-HYDRAEX01 systemd: Started Session 10 of user root.
Sep 22 09:10:01 D1P-HYDRAEX01 systemd: Starting Session 11 of user root.
Sep 22 09:10:01 D1P-HYDRAEX01 systemd: Started Session 11 of user root.
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Mounting RPC Pipe File System...
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Started Kernel Module supporting RPCSEC_GSS.
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Starting NFSv4 ID-name mapping service...
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Mounting NFSD configuration filesystem...
Sep 22 09:10:16 D1P-HYDRAEX01 mount: mount: unknown filesystem type 'rpc_pipefs'
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: var-lib-nfs-rpc_pipefs.mount mount process exited, code=exited status=32
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Failed to mount RPC Pipe File System.
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Dependency failed for RPC security service for NFS server.
Sep 22 09:10:16 D1P-HYDRAEX01 systemd:
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Dependency failed for RPC security service for NFS client and server.
Sep 22 09:10:16 D1P-HYDRAEX01 systemd:
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Unit var-lib-nfs-rpc_pipefs.mount entered failed state.
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: nfs-idmapd.service: control process exited, code=exited status=1
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Failed to start NFSv4 ID-name mapping service.
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Unit nfs-idmapd.service entered failed state.
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: proc-fs-nfsd.mount mount process exited, code=exited status=32
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Failed to mount NFSD configuration filesystem.
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Dependency failed for NFS server and services.
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Dependency failed for NFS Mount Daemon.
Sep 22 09:10:16 D1P-HYDRAEX01 systemd:
Sep 22 09:10:16 D1P-HYDRAEX01 systemd:
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Unit proc-fs-nfsd.mount entered failed state.
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Starting Notify NFS peers of a restart...
Sep 22 09:10:16 D1P-HYDRAEX01 systemd: Started Notify NFS peers of a restart.
Sep 22 09:10:16 D1P-HYDRAEX01 rpc.idmapd[4693]: main: open(/var/lib/nfs/rpc_pipefs//nfs): No such file or directory
Sep 22 09:10:16 D1P-HYDRAEX01 sm-notify[4699]: Version 1.3.0 starting
Sep 22 09:10:16 D1P-HYDRAEX01 sm-notify[4699]: Already notifying clients; Exiting!
Sep 22 09:10:16 D1P-HYDRAEX01 mount: mount: unknown filesystem type 'nfsd'
--
You received this message because you are subscribed to the Google Groups "Warewulf" group.
To unsubscribe from this group and stop receiving emails from it, send an email to warewulf+u...@lbl.gov.
To post to this group, send email to ware...@lbl.gov.
To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/warewulf/fd16c3af-d68b-4857-b11e-255cd808c1e2%40lbl.gov.
For more options, visit https://groups.google.com/a/lbl.gov/d/optout.
Chu Ruilin
Sep 22, 2015, 4:12:16 PM9/22/15
to ware...@lbl.gov
did wwinit nsfd success on the master node?
To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/warewulf/CAEO3gsBxMRgWP4xOYCu44W7-yVTcZBZgas_jwMYMhTUuAUvsOg%40mail.gmail.com.
Vince Forgetta
Sep 22, 2015, 4:17:56 PM9/22/15
to ware...@lbl.gov
Hi Chu,
I will check this and report back. In meantime I also observe this warning when bootstrapping kernel:
[root@D1P-HYDRAMS01 ~]# wwbootstrap `uname -r`
Number of drivers included in bootstrap: 441
depmod: WARNING: could not open /var/tmp/wwinitrd.iOjYsaror3P3/initramfs/lib/modules/3.10.0-229.14.1.el7.x86_64/modules.order: No such file or directory
depmod: WARNING: could not open /var/tmp/wwinitrd.iOjYsaror3P3/initramfs/lib/modules/3.10.0-229.14.1.el7.x86_64/modules.builtin: No such file or directory
Number of firmware images included in bootstrap: 90
Building and compressing bootstrap
WARNING: Do you wish to overwrite '3.10.0-229.14.1.el7.x86_64' in the Warewulf data store?
Yes/No> Y
Integrating the Warewulf bootstrap: 3.10.0-229.14.1.el7.x86_64
Including capability: provision-adhoc
Including capability: provision-files
Including capability: provision-selinux
Including capability: provision-vnfs
Including capability: setup-filesystems
Including capability: transport-http
Compressing the initramfs
Locating the kernel object
Bootstrap image '3.10.0-229.14.1.el7.x86_64' is ready
Done.
To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/warewulf/CAC_eze9Xj5Tx4vsEuqiCQM%2B0t5M%3DHy2QUTrRKZGuRGSHmZ28wQ%40mail.gmail.com.
Vince Forgetta
Sep 22, 2015, 4:19:13 PM9/22/15
to ware...@lbl.gov
Output from wwinit ALL:
[root@D1P-HYDRAMS01 ~]# wwinit ALL
database: Checking to see if RPM 'mysql-server' is installed NO
database: Checking to see if RPM 'mariadb-server' is installed OK
database: Activating Systemd service: mariadb
database: + /bin/systemctl -q enable mariadb.service OK
database: + /bin/systemctl -q restart mariadb.service OK
database: Database version: 1
wwsh: Confirming that wwsh accepts some basic commands
wwsh: + wwsh quit OK
wwsh: + wwsh help OK
wwsh: + wwsh node new testnode0000 OK
wwsh: + wwsh node list OK
wwsh: + wwsh node delete testnode0000 OK
domain: Setting default node domain to: "cluster" OK
authfiles: Checking to see if /etc/passwd is in the WW Datastore OK
authfiles: Checking if /etc/passwd is part of default node configuration
authfiles: Checking to see if /etc/group is in the WW Datastore OK
authfiles: Checking if /etc/group is part of default node configuration
dhcp: Checking to see if RPM 'dhcp' is installed OK
dhcp: Activating Systemd service: dhcp
dhcp: + /bin/systemctl -q enable dhcpd.service OK
dhcp: + /bin/systemctl -q restart dhcpd.service OK
nfsd: Activating Systemd service: nfsd
nfsd: + /bin/systemctl -q enable nfs-server.service OK
nfsd: + /bin/systemctl -q restart nfs-server.service OK
ntpd: Configured NTP services
ntpd: Activating Systemd service: ntp
ntpd: + /bin/systemctl -q enable ntpd.service OK
ntpd: + /bin/systemctl -q restart ntpd.service OK
ssh_keys: Checking ssh keys for root OK
ssh_keys: Checking root's ssh config OK
ssh_keys: Checking for default RSA1 host key for nodes OK
ssh_keys: Checking for default RSA host key for nodes OK
ssh_keys: Checking for default DSA host key for nodes OK
tftp: Checking to see if RPM 'tftp-server' is installed OK
tftp: Activating xinetd service: tftpd
tftp: + sed -ie s@\(disable\s*=\s*\)\S*@\1no@ /etc/xinetd.d/tftp OK
tftp: Activating Systemd service: xinetd
tftp: + /bin/systemctl -q enable xinetd.service OK
tftp: + /bin/systemctl -q restart xinetd.service OK
bootstrap: Checking for bootstrap (3.10.0-229.14.1.el7.x86_64): OK
vnfs: CHROOTDIR is not defined, run 'wwvnfs' by hand. SKIPPED
Vince Forgetta
Sep 23, 2015, 9:15:33 AM9/23/15
to ware...@lbl.gov
So, I suspected that initial maybe initialization was issue i.e. wwinit ALL initially reported problem with NFS. However, even after wwinit ALL shows NFS is OK *and* I reboot provisioned node, the NFS client still does not work. Moreover, lsmod reports that nfs kernel modules are not loaded.
Chu Ruilin
Sep 23, 2015, 9:37:22 AM9/23/15
to ware...@lbl.gov
i also cant find nfs module on client nodes but nfs works
To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/warewulf/CAEO3gsALZ4_1LA0VBUP2soqiQtQg7ezjfHqyjt6A2kuTQy%3DKCg%40mail.gmail.com.
Vince Forgetta
Sep 23, 2015, 9:49:26 AM9/23/15
to ware...@lbl.gov
I got a little farther, I noticed that showmount -e did not work, so I installed nfs4-acl-tools:
yum --config=/var/chroots/hydraex-centos7/root/yum-ww.conf --installroot=/var/chroots/hydraex-centos7/ install nfs4-acl-tools
Now showmount -e <ip_nfs_server> works.
But mounting NFS share still fails. Specifically, I cannot start the nfs-server service:
[root@D1P-HYDRAEX01 ~]# systemctl start nfs-server
A dependency job for nfs-server.service failed. See 'journalctl -xn' for details.
[root@D1P-HYDRAEX01 ~]# journalctl -xn
-- Logs begin at Wed 2015-09-23 02:36:26 EDT, end at Wed 2015-09-23 02:49:22 EDT. --
Sep 23 02:49:22 D1P-HYDRAEX01.ldi.lan systemd[1]: Failed to mount NFSD configuration filesystem.
-- Subject: Unit proc-fs-nfsd.mount has failed
-- Unit proc-fs-nfsd.mount has failed.
--
-- The result is failed.
Sep 23 02:49:22 D1P-HYDRAEX01.ldi.lan systemd[1]: Dependency failed for NFS server and services.
-- Subject: Unit nfs-server.service has failed
-- Unit nfs-server.service has failed.
--
-- The result is dependency.
Sep 23 02:49:22 D1P-HYDRAEX01.ldi.lan systemd[1]: Dependency failed for NFS Mount Daemon.
-- Subject: Unit nfs-mountd.service has failed
-- Unit nfs-mountd.service has failed.
--
-- The result is dependency.
Sep 23 02:49:22 D1P-HYDRAEX01.ldi.lan systemd[1]: Unit proc-fs-nfsd.mount entered failed state.
Sep 23 02:49:22 D1P-HYDRAEX01.ldi.lan systemd[1]: Starting Notify NFS peers of a restart...
-- Subject: Unit rpc-statd-notify.service has begun with start-up
-- Defined-By: systemd
--
-- Unit rpc-statd-notify.service has begun starting up.
Sep 23 02:49:22 D1P-HYDRAEX01.ldi.lan systemd[1]: Started Notify NFS peers of a restart.
-- Subject: Unit rpc-statd-notify.service has finished start-up
-- Defined-By: systemd
--
-- Unit rpc-statd-notify.service has finished starting up.
--
-- The start-up result is done.
Sep 23 02:49:22 D1P-HYDRAEX01.ldi.lan sm-notify[4675]: Version 1.3.0 starting
Sep 23 02:49:22 D1P-HYDRAEX01.ldi.lan sm-notify[4675]: Already notifying clients; Exiting!
To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/warewulf/CAC_eze-%2Biqvu6rzXot2yvRBibheRaCkWjkExnThTT%3DjKCvxsdw%40mail.gmail.com.
Vince Forgetta
Sep 23, 2015, 10:08:45 AM9/23/15
to ware...@lbl.gov
Seems like something wrong with nfsd:
[root@D1P-HYDRAEX01 ~]# rpc.nfsd -d
rpc.nfsd: Checking netconfig for visible protocols.
rpc.nfsd: Enabling inet udp.
rpc.nfsd: Enabling inet tcp.
rpc.nfsd: Enabling inet6 udp.
rpc.nfsd: Enabling inet6 tcp.
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
Ralph Castain
Sep 23, 2015, 10:13:34 AM9/23/15
to Warewulf Group
I hit the same problem and am also stuck - FWIW the directory is there.
To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/warewulf/CAEO3gsBbXMT4fXTOZFtQ77ZEKTcyOOw9ex8LJMGmhGTy1Yiffw%40mail.gmail.com.
Vince Forgetta
Sep 23, 2015, 10:21:50 AM9/23/15
to ware...@lbl.gov
Yup. The kernel module seems to be on the provisioned node:
find /lib/modules/ -name nfsd.ko
But for some reason I can not find it via modinfo nfsd, where as on master this command works.
To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/warewulf/170D38B6-2FFA-4749-A55C-FFA1456A790D%40open-mpi.org.
Reply all
Reply to author
Forward
0 new messages