[Gluster-users] unable to start client, new setup 2.0.6 centos5.3

Charles cshtreck at yahoo.com
Fri Oct 2 17:18:47 UTC 2009


aha, ... I was missing the mount point at the end of my line
glusterfs -f /etc/glusterfs/glusterfs.vol -l /var/log/messages -L DEBUG --debug -N   /dagumbigdir

thanks!
=cm

--- On Fri, 10/2/09, Anush Shetty <anush at gluster.com> wrote:

> From: Anush Shetty <anush at gluster.com>
> Subject: Re: [Gluster-users] unable to start client, new setup 2.0.6 centos5.3
> To: "Charles" <cshtreck at yahoo.com>
> Cc: gluster-users at gluster.org
> Date: Friday, October 2, 2009, 12:48 PM
> Hi Charles, I think you didn't
> specify the mount point  while starting
> the client.
> 
> Something like this,
> 
> glusterfsd -f client1.vol -l client1.log /mnt/client1
> 
> 
> On Fri, Oct 2, 2009 at 10:01 PM, Charles <cshtreck at yahoo.com>
> wrote:
> > Hi,
> >
> > when attempting to start the client I received:
> > no valid translator loaded at the top, orno mount
> point given. exiting
> > [2009-10-02 10:34:40] E
> [glusterfsd.c:570:glusterfs_graph_init] glusterfs: no valid
> translator loaded at the top or no mount point given.
> exiting
> > [2009-10-02 10:34:40] E [glusterfsd.c:1217:main]
> glusterfs: translator initialization failed.  exiting
> >
> > - running 2.0.6 on centos 5.3
> > - 3 servers, 1 client
> > - I'm attempting to replicate across the 3 servers
> > - pls help
> >
> > # client config
> > # file: /etc/glusterfs/glusterfs.vol
> > volume remote1
> >  type protocol/client
> >  option transport-type tcp
> >  option remote-host rh1
> >  option remote-subvolume brick
> > end-volume
> >
> > volume remote2
> >  type protocol/client
> >  option transport-type tcp
> >  option remote-host rh2
> >  option remote-subvolume brick
> > end-volume
> >
> > volume remote3
> >  type protocol/client
> >  option transport-type tcp
> >  option remote-host rh3
> >  option remote-subvolume brick
> > end-volume
> >
> > volume replicate
> >  type cluster/replicate
> >  subvolumes remote1 remote2 remote3
> > end-volume
> >
> > volume writebehind
> >  type performance/write-behind
> >  option window-size 1MB
> >  subvolumes replicate
> > end-volume
> >
> > volume cache
> >  type performance/io-cache
> >  option cache-size 512MB
> >  subvolumes writebehind
> > end-volume
> >
> > #
> > # server config
> > #
> > volume posix
> >  type storage/posix
> >  option directory /bigpartition
> > end-volume
> >
> > volume locks
> >  type features/locks
> >  subvolumes posix
> > end-volume
> >
> > volume brick
> >  type performance/io-threads
> >  option thread-count 8
> >  subvolumes locks
> > end-volume
> >
> > volume server
> >  type protocol/server
> >  option transport-type tcp
> >  option auth.addr.brick.allow *
> >  subvolumes brick
> > end-volume
> >
> > =cm
> >
> >
> >
> >
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
> >
> 
> 
> 
> -- 
> Anush,
> Team Gluster,
> http://gluster.com
> 


      



More information about the Gluster-users mailing list