[Gluster-users] Getting ERROR: parsing the volfile failed (No such file or directory) when starting glusterd on Fedora 19

[Greg Scott]

I don't get this.  I am using a freshly installed copy of Fedora 19 and starting up glusterd for the first time.  The goal is to have a replicated directory on two systems.  But for right now, I can't even start up the glusterd daemon right out of the box.

Trying to follow the Quick Start directions at http://gluster.org/community/documentation/index.php/QuickStart is, well, challenging.  Those QuickStart directions are for Gluster 3.3.something and Fedora 19 seems include 3.4.beta3, so those directions are wrong.  

This is a brand new, fresh installation with no volumes yet.  Anaconda apparently installed these packages with the initial Fedora installation:

[root at chicago-fw1 ~]# rpm -qa | grep gluster
glusterfs-fuse-3.4.0-0.6.beta3.fc19.x86_64
glusterfs-3.4.0-0.6.beta3.fc19.x86_64
glusterfs-api-3.4.0-0.6.beta3.fc19.x86_64
[root at chicago-fw1 ~]#

So then I did:

yum install glusterfs-server

and it successfully installed.  Next I did:

systemctl start glusterd.service

This starts without error but then blows up a few seconds later:

[root at chicago-fw1 system]# systemctl start glusterd.service
[root at chicago-fw1 system]# tail /var/log/messages
Jul  7 06:18:28 chicago-fw1 dbus-daemon[508]: dbus[508]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd'
Jul  7 06:18:29 chicago-fw1 setroubleshoot: SELinux is preventing /usr/sbin/glusterfsd from name_bind access on the tcp_socket . For complete SELinux messages. run sealert -l 6ef33b0e-94fc-4eba-8a11-f594985ba312
Jul  7 06:18:30 chicago-fw1 systemd[1]: Started GlusterFS an clustered file-system server.
Jul  7 06:18:30 chicago-fw1 systemd[1]: Starting GlusterFS an clustered file-system server...
Jul  7 06:18:30 chicago-fw1 glusterfsd[1728]: [2013-07-07 11:18:30.717075] C [glusterfsd.c:1374:parse_cmdline] 0-glusterfs: ERROR: parsing the volfile failed (No such file or directory)
Jul  7 06:18:30 chicago-fw1 glusterfsd[1728]: USAGE: /usr/sbin/glusterfsd [options] [mountpoint]
Jul  7 06:18:30 chicago-fw1 GlusterFS[1728]: [2013-07-07 11:18:30.717075] C [glusterfsd.c:1374:parse_cmdline] 0-glusterfs: ERROR: parsing the volfile failed (No such file or directory)
Jul  7 06:18:30 chicago-fw1 systemd[1]: glusterfsd.service: control process exited, code=exited status=255
Jul  7 06:18:30 chicago-fw1 systemd[1]: Failed to start GlusterFS an clustered file-system server.
Jul  7 06:18:30 chicago-fw1 systemd[1]: Unit glusterfsd.service entered failed state.
[root at chicago-fw1 system]#

The SELinux message above is just a warning - I set SELINUX=permissive in /etc/selinux/config.  The real issue is the No such file or directory error.  

Am I dealing with a bug?  Should I be installing different versions of different packages?  That vol file exists and is part of the virgin installation - unless the beta 3 of glusterd is looking for it in a different spot than where the installation puts it.  

[root at chicago-fw1 system]# cd /etc
[root at chicago-fw1 etc]# ls | grep gluster
glusterfs
[root at chicago-fw1 etc]# ls -al glusterfs
total 24
drwxr-xr-x.   2 root root  4096 Jul  7 05:17 .
drwxr-xr-x. 140 root root 12288 Jul  7 05:17 ..
-rw-r--r--.   1 root root   278 Jun 11 13:06 glusterd.vol
-rw-r--r--.   1 root root   541 Jun 11 13:06 glusterfs-logrotate
[root at chicago-fw1 etc]# more glusterfs/glusterd.vol
volume management
    type mgmt/glusterd
    option working-directory /var/lib/glusterd
    option transport-type socket,rdma
    option transport.socket.keepalive-time 10
    option transport.socket.keepalive-interval 2
    option transport.socket.read-fail-log off
end-volume
[root at chicago-fw1 etc]#

Any idea what's going on and how to fix it?

Thanks

- Greg Scott