List, How does one request a change to fedora packages? Do we need to file a report in the Fedora bugzilla? - Kaushal On Wed, Jul 24, 2013 at 8:38 PM, Kaushal M <kshlmster@xxxxxxxxx> wrote: > The problem is with the glusterfsd.service systemd unit, it does > nothing and will always fail to start because it isn't given a > volfile. glusterd.service depends on glusterfsd.service, and thus > fails to start as glusterfsd fails to start. The fedora packages need > to be rebuilt without glusterfsd.service. > For the time being, if you absolutely want to use systemd to start > glusterd, edit the /usr/lib/systemd/system/glusterd.service file and > remove the 'Wants=glusterfsd.service' line. Or you could just start > glusterd directly. > > -Kaushal > > On Wed, Jul 24, 2013 at 6:58 PM, Sahina Bose <sabose@xxxxxxxxxx> wrote: >> Hi all, >> >> Could someone help? While testing on ovirt test day - could not start >> glusterd on F19 using #service glusterd start >> >> I installed glusterfs from fedora updates-testing repo. >> >> From /var/log/messages >> Jul 23 14:02:01 localhost systemd[1]: Starting GlusterFS an clustered >> file-system server... >> Jul 23 14:02:01 localhost glusterfsd[8422]: [2013-07-23 18:02:01.488421] C >> [glusterfsd.c:1406:parse_cmdline] 0-glusterfs: ERROR: parsing the volfile >> failed (No such file or directory) >> Jul 23 14:02:01 localhost glusterfsd[8422]: USAGE: /usr/sbin/glusterfsd >> [options] [mountpoint] >> Jul 23 14:02:01 localhost GlusterFS[8422]: [2013-07-23 18:02:01.488421] C >> [glusterfsd.c:1406:parse_cmdline] 0-glusterfs: ERROR: parsing the volfile >> failed (No such file or directory) >> Jul 23 14:02:01 localhost systemd[1]: glusterfsd.service: control process >> exited, code=exited status=255 >> Jul 23 14:02:01 localhost systemd[1]: Failed to start GlusterFS an clustered >> file-system server. >> Jul 23 14:02:01 localhost systemd[1]: Unit glusterfsd.service entered failed >> state. >> Jul 23 14:14:26 localhost systemd[1]: Starting GlusterFS an clustered >> file-system server... >> Jul 23 14:14:26 localhost systemd[1]: glusterd.service: control process >> exited, code=exited status=1 >> Jul 23 14:14:26 localhost systemd[1]: Failed to start GlusterFS an clustered >> file-system server. >> Jul 23 14:14:26 localhost systemd[1]: Unit glusterd.service entered failed >> state. >> Jul 23 14:14:26 localhost systemd[1]: Starting GlusterFS an clustered >> file-system server... >> Jul 23 14:14:26 localhost glusterfsd[8465]: [2013-07-23 18:14:26.753504] C >> [glusterfsd.c:1406:parse_cmdline] 0-glusterfs: ERROR: parsing the volfile >> failed (No such file or directory) >> Jul 23 14:14:26 localhost glusterfsd[8465]: USAGE: /usr/sbin/glusterfsd >> [options] [mountpoint] >> Jul 23 14:14:26 localhost GlusterFS[8465]: [2013-07-23 18:14:26.753504] C >> [glusterfsd.c:1406:parse_cmdline] 0-glusterfs: ERROR: parsing the volfile >> failed (No such file or directory) >> Jul 23 14:14:26 localhost systemd[1]: glusterfsd.service: control process >> exited, code=exited status=255 >> Jul 23 14:14:26 localhost systemd[1]: Failed to start GlusterFS an clustered >> file-system server. >> Jul 23 14:14:26 localhost systemd[1]: Unit glusterfsd.service entered failed >> state. >> >> thanks >> sahina >> >> >> _______________________________________________ >> Gluster-devel mailing list >> Gluster-devel@xxxxxxxxxx >> https://lists.nongnu.org/mailman/listinfo/gluster-devel
