I'm interested in this too. I think other than access control, there's
no reason preventing gluster from running as a normal user. I'm
wondering if there's someway of disabling the access control part to
bypass this error.
- Wei
G Feng wrote:> [aimi at centos ~]$ /sbin/glusterfsd -f ~/vol/glusterfsd.vol --debug
> [2009-09-16 16:42:24] D [glusterfsd.c:339:_get_specfp] glusterfs: loading
> volume file /home/aimi/vol/glusterfsd.vol
>
===============================================================================>
Version : glusterfs 2.0.2 built on Jul 7 2009 14:55:51
> TLA Revision : 07019da2e16534d527215a91904298ede09bb798
> Starting Time: 2009-09-16 16:42:24
> Command line : /sbin/glusterfsd -f /home/aimi/vol/glusterfsd.vol --debug
> PID : 6240
> System name : Linux
> Nodename : centos.localdomain
> Kernel Release : 2.6.18-92.1.18.el5
> Hardware Identifier: i686
>
> Given volfile:
>
+------------------------------------------------------------------------------+
> 1: volume posix
> 2: type storage/posix
> 3: option directory /home/aimi/new
> 4: end-volume
> 5:
> 6: volume locks
> 7: type features/locks
> 8: subvolumes posix
> 9: end-volume
> 10:
> 11: volume brick
> 12: type performance/io-threads
> 13: option thread-count 8
> 14: subvolumes locks
> 15: end-volume
> 16:
> 17: volume server
> 18: type protocol/server
> 19: option transport-type tcp
> 20: option auth.addr.brick.allow *
> 21: subvolumes brick
> 22: end-volume
>
+------------------------------------------------------------------------------+
> [2009-09-16 16:42:24] D [xlator.c:634:xlator_set_type] xlator:
dlsym(notify)
> on /usr/local/lib/glusterfs/2.0.2/xlator/features/locks.so: undefined
> symbol: notify -- neglecting
> [2009-09-16 16:42:24] D [xlator.c:634:xlator_set_type] xlator:
dlsym(notify)
> on /usr/local/lib/glusterfs/2.0.2/xlator/performance/io-threads.so:
> undefined symbol: notify -- neglecting
> [2009-09-16 16:42:24] D [glusterfsd.c:1179:main] glusterfs: running in pid
> 6240
> [2009-09-16 16:42:24] C [posix.c:3864:init] posix: Extended attribute not
> supported, exiting.
> [2009-09-16 16:42:24] E [xlator.c:736:xlator_init_rec] xlator:
> Initialization of volume 'posix' failed, review your volfile again
> [2009-09-16 16:42:24] E [glusterfsd.c:498:_xlator_graph_init] glusterfs:
> initializing translator failed
> [2009-09-16 16:42:24] E [glusterfsd.c:1191:main] glusterfs: translator
> initialization failed. exiting
>
>
> It could work with the same setting when I run it as root.
>
> how to run gluster as non-root user?
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>