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

[Greg Scott]

This might be important.  

Re: Joe, from my other node offline thread earlier today:

> As it turns out, reading further that error you're seeing comes from glusterfsd.service (not glusterd.service) 
> which shouldn't even be enabled unless you're trying to use old legacy volfiles from 3.0. The "parsing the 
> volfile failed" was spurious, as you discovered.

I'm using glusterfs-3.4-beta3, packaged right in with Fedora 19.   Check this out - this is the config file that drives what happens when you do:

systemctl start glusterd.service

Notice how glusterd wants glusterfsd.  I remember wondering, why are there two of them?  Now I guess I know.  Is this a Fedora bug?  Hopefully the emailer won't butcher the pasted in output below.

[root at chicago-fw1 system]# pwd
/usr/lib/systemd/system
[root at chicago-fw1 system]# more glusterd.service
[Unit]
Description=GlusterFS an clustered file-system server
Wants=glusterfsd.service
After=network.target rpcbind.service

[Service]
Type=forking
PIDFile=/run/glusterd.pid
LimitNOFILE=65536
ExecStart=/usr/sbin/glusterd -p /run/glusterd.pid

[Install]
WantedBy=multi-user.target
[root at chicago-fw1 system]# 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-server-3.4.0-0.6.beta3.fc19.x86_64
glusterfs-geo-replication-3.4.0-0.6.beta3.fc19.x86_64
glusterfs-api-3.4.0-0.6.beta3.fc19.x86_64
[root at chicago-fw1 system]#

- Greg