I never used 2.x so I am not sure if this it the issue or not, but do you have
an allow line in your glusterfsd.vol file?
That is how glusterfs authenticates clients, if the server can not authenticate
the client the mount will fail.
My allow line looks like this:
option auth.addr.tcb_brick.allow *
Obviously your auth line would need to change "tcb_brick" to the name
of your volume export.
Plus my auth is wide open because my servers and clients are on a totally
private network.
^C
m.roth at 5-cent.us wrote:> Well, I've been following what I think are good directions, and I'm
at the
> point of mounting it all. So, I run glusterfs /export/glusterfs, and what
> I see in the log is
> [2010-03-08 11:56:19] E [glusterfsd.c:554:_xlator_graph_init] <highest
> number servername>:/glusterfs1: validating translator failed
> [2010-03-08 11:56:19] E [glusterfsd.c:1291:main] glusterfs: translator
> initialization failed. exiting
>
> CentOS 5.4, glusterfs 2.0.8.
>
> I did see, while googling, a *very* few emails about this, but that was
> with 2rc, and the response was try 2.0. Any ideas what I've got wrong?
>
> mark
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>
>