[Gluster-devel] Re: how to run mod_glusterfs in apache 1.3
mingyang
bjmingyang at gmail.com
Tue Sep 15 08:41:08 UTC 2009
When I use the mod_glusterfs on apache 1.3, I try to wget glusterfs the
files, but has been shown to wait for connection, this is what is the
problem? How to solve? Thanks
[root @ web01 conf] # wget http://127.0.0.1:8080/glusterfs/abc
- 16:27:35 - http://127.0.0.1:8080/glusterfs/abc
Connecting to 127.0.0.1:8080 ... connected.
HTTP request sent, awaiting response ...
[root @ web01 conf] # wget http://127.0.0.1:8080/abc
- 16:30:51 - http://127.0.0.1:8080/abc
Connecting to 127.0.0.1:8080 ... connected.
HTTP request sent, awaiting response ...
> 2009/9/10 mingyang <bjmingyang at gmail.com>
>
> My application is a lot of random read, using the fuse, I see my back in
>> front of traffic flow is twice the
>> So, I do not think the use of fuse, but I have version 2.06 of the. /
>> Configure - help to see which has no mod_glusterfs
>> Options, and so I used the 2.04 version. Using a apache1.3, in the
>> apache's log which there are no errors, but in mod_glusterfs the log where a
>> large number of errors, as
>>
>> 2009-09-09 14:33:34] E [name.c: 420: client_bind] client10: cannot bind
>> inet socket (7) to port less than 1024 (Permission denied)
>> [2009-09-09 14:33:34] E [name.c: 420: client_bind] client3: cannot bind
>> inet socket (6) to port less than 1024 (Permission denied)
>> [2009-09-09 14:33:34] E [name.c: 420: client_bind] client3: cannot bind
>> inet socket (6) to port less than 1024 (Permission denied)
>> [2009-09-09 14:33:34] E [name.c: 420: client_bind] client2: cannot bind
>> inet socket (6) to port less than 1024 (Permission denied)
>> [2009-09-09 14:33:34] E [name.c: 420: client_bind] client3: cannot bind
>> inet socket (6) to port less than 1024 (Permission denied)
>> [2009-09-09 14:33:34] E [name.c: 420: client_bind] client3: cannot bind
>> inet socket (6) to port less than 1024 (Permission denied)
>> [2009-09-09 14:33:34] E [name.c: 420: client_bind] client4: cannot bind
>> inet socket (6) to port less than 1024 (Permission denied)
>> [2009-09-09 14:33:34] E [name.c: 420: client_bind] client4: cannot bind
>> inet socket (6) to port less than 1024 (Permission denied)
>> [2009-09-09 14:33:34] E [name.c: 420: client_bind] client5: cannot bind
>> inet socket (7) to port less than 1024 (Permission denied)
>> [2009-09-09 14:33:34] E [name.c: 420: client_bind] client3: cannot bind
>> inet socket (6) to port less than 1024 (Permission denied)
>> [2009-09-09 14:33:34] E [name.c: 420: client_bind] client4: cannot bind
>> inet socket (6) to port less than 1024 (Permission denied)
>>
>> What is the how to solve?
>> At this point, I can not read through the apache to the glusterfs where
>> the contents of the
>>
>>
>> my httpd.conf
>>
>> LoadModule glusterfs_module libexec/mod_glusterfs.so
>>
>> <Location "/glusterfs">
>> GlusterfsLogfile "/var/log/glusterfs/glusterfs.log"
>> GlusterfsLoglevel "warning"
>> GlusterfsVolumeSpecfile
>> "/usr/glusterfs/etc/glusterfs/client2.vol"
>> GlusterfsCacheTimeout "600"
>> GlusterfsXattrFileSize "65536"
>> SetHandler "glusterfs-handler"
>> </Location>
>>
>>
>> my client.vol
>> # client feature and attach to remote subvolume
>> volume client1 #b
>> type protocol/client
>> option transport-type tcp/client
>> option remote-host 192.168.1.1 # IP address of the remote brick
>> option remote-port 6996 # default server port is 6996
>> option remote-subvolume brick # name of the remote volume
>> end-volume
>>
>>
>> volume client2 #c
>> type protocol/client
>> option transport-type tcp/client
>> option remote-host 192.168.1.1 # IP address of the remote brick
>> option remote-port 6997 # default server port is 6996
>> option remote-subvolume brick # name of the remote volume
>> end-volume
>>
>> volume client3 #d
>> type protocol/client
>> option transport-type tcp/client
>> option remote-host 192.168.1.1 # IP address of the remote brick
>> option remote-port 6998 # default server port is 6996
>> option remote-subvolume brick # name of the remote volume
>> end-volume
>>
>> volume client4 #e
>> type protocol/client
>> option transport-type tcp/client
>> option remote-host 192.168.1.1 # IP address of the remote brick
>> option remote-port 6999 # default server port is 6996
>> option remote-subvolume brick # name of the remote volume
>> end-volume
>>
>> volume client5 #f
>> type protocol/client
>> option transport-type tcp/client
>> option remote-host 192.168.1.1# IP address of the remote brick
>> option remote-port 7000 # default server port is 6996
>> option remote-subvolume brick # name of the remote volume
>> end-volume
>>
>> volume client6 #g
>> type protocol/client
>> option transport-type tcp/client
>> option remote-host 192.168.1.1 # IP address of the remote brick
>> option remote-port 7001 # default server port is 6996
>> option remote-subvolume brick # name of the remote volume
>> end-volume
>>
>>
>> volume client7 #h
>> type protocol/client
>> option transport-type tcp/client
>> option remote-host 192.168.1.1 # IP address of the remote brick
>> option remote-port 7002 # default server port is 6996
>> option remote-subvolume brick # name of the remote volume
>> end-volume
>>
>>
>> volume client8 #i
>> type protocol/client
>> option transport-type tcp/client
>> option remote-host 192.168.1.1 # IP address of the remote brick
>> option remote-port 7003 # default server port is 6996
>> option remote-subvolume brick # name of the remote volume
>> end-volume
>>
>> volume client9 #j
>> type protocol/client
>> option transport-type tcp/client
>> option remote-host 192.168.1.1 # IP address of the remote brick
>> option remote-port 7004 # default server port is 6996
>> option remote-subvolume brick # name of the remote volume
>> end-volume
>>
>> volume client10 #k
>> type protocol/client
>> option transport-type tcp/client
>> option remote-host 192.168.1.1 # IP address of the remote brick
>> option remote-port 7005 # default server port is 6996
>> option remote-subvolume brick # name of the remote volume
>> end-volume
>>
>> #volume client11 #l
>> #type protocol/client
>> #option transport-type tcp/client
>> #option remote-host 192.168.1.1 # IP address of the remote brick
>> #option remote-port 7006 # default server port is 6996
>> #option remote-subvolume brick # name of the remote volume
>> #end-volume
>>
>> volume name
>> type protocol/client
>> option transport-type tcp
>> #option remote-host 192.168.211.128
>> option remote-port 7006
>> option remote-subvolume brick
>> end-volume
>>
>>
>> volume stripe1
>> type cluster/stripe
>> subvolumes client1 client2 client3 client4 client5 client6 client7
>> client8 client9 client10
>> option block-size 2MB # all striped in 1280kB block
>> end-volume
>>
>>
>> # ==== Performance Translators ====
>> # The default options for performance translators should be the best for
>> 90+% of the cases
>> volume iot
>> type performance/io-threads
>> subvolumes stripe1
>> option thread-count 8 #
>> end-volume
>>
>> volume wb
>> type performance/write-behind
>> subvolumes iot
>> option flush-behind on
>> end-volume
>>
>> volume ioc
>> type performance/io-cache
>> subvolumes wb
>> option page-size 2MB #(128KB)
>> option cache-size 128MB #(32MB)
>> end-volume
>>
>> volume ra
>> type performance/read-ahead
>> subvolumes ioc
>> option page-size 2MB # (256KB)
>> option page-count 16
>> option force-atime-update off
>> end-volume
>>
>
>
>
> --
> 致
> 礼！
>
>
> 王明阳
>
--
致
礼！
王明阳
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20090915/e30787e7/attachment-0003.html>
More information about the Gluster-devel
mailing list