I've noticed this too when using some of the prebuilt configurations. Try specifying the transport-type as tcp/client or tcp/server rather than just tcp. Example: volume brick01 type protocol/client option transport-type tcp/client option remote-host 172.22.11.1 option remote-subvolume brick01 end-volume volume server type protocol/server option transport-type tcp/server option auth.ip.brick01.allow 172.22.* subvolumes brick01 end-volume 2008/12/19 Kun Rich?rd <kun.richard at kirzen.hu> > Hi, > > I wanted to try glusterfs 1.3.12a from source, on the basis of the > documentation. > When I started the glusterfsd, I get this message: > > [transport.c:86:transport_load] transport: dlopen > (/usr/local/lib/glusterfs/1.3.12a/transport/tcp.so): > /usr/local/lib/glusterfs/1.3.12a/transport/tcp.so: cannot open shared > object > file: No such file or directory > > The file doesn't exist, but I don't have any error messages at compile > time. > What's wrong? > > Please reply me too, I'm not in list. > > Thanks: > > -- > ?dv, > Ricsi > kun.richard at kirzen.hu > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://zresearch.com/pipermail/gluster-users/attachments/20081222/6dc7cc25/attachment.htm
