[Gluster-users] SOLVED:gluster not starting at boot, possible NFS conflict?

[Jason Hilton]

Hi All-
I think I solved it, I had forgotten about the find command. :-\  I found the 2 offending items and relocated them.  Glusterd started up fine on reboot.
Thanks for looking,
Jason

***************************************************************
Jason Hilton
Director of Technology Development
601 Madison Street, Suite 400
Alexandria, VA 22314
jason.hilton at aaae.org
Desk: 703.824.0500x167
FAX: 703.578.4952

AAAE Tech support:
IET at aaae.org
703.797.2555, opt. 2
***************************************************************

From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Jason Hilton
Sent: Monday, March 30, 2015 10:47 AM
To: gluster-users at gluster.org
Subject: [Gluster-users] gluster not starting at boot, possible NFS conflict?

Hi-
I'm having a little trouble with getting glusterd to start a boot up.  I believe it is due to NFS not disabling.  I have verified that most of the NFS related services are disabled at boot, but the rpcinfo command shows several nfs and mountd related services running a boot up.  (I can delete the processes and get glusterd to start manually.)  I was able to find that there are 2 items that are set as static items and I am not able to disable them:


*         var-lib-nfs-rpc_pipefs.mount

*         proc-fs-nfsd.mount

Is it safe to disable these items?  If so, how do I do it?  I would normally rm them from the systemd directory, but they do not seem to be listed there.  Any help or insight is greatly appreciated.
Thanks,
Jason

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150330/49ab94cf/attachment.html>