I've successed install perlbal and mogilefs.
Our front end is  ZXTM (http://www.zeus.com)
then ->  2 perlbal nodes,
then ->2 web ap(mod_php)+mogilefs tracker nodes,
and 2 mogstored nodes as storage.
our web ap pass reproxy header back to perlbal for fetching real file
from mogstored.
All works fine, but we have some slow response problem,
Sometimes, browser just loading and hang , client should wait about 10
or more seconds..
after that the page display correctly.
So..
1. I test the web ap node, connect directly, no hang and slow problem.
2.I change ZXTM setting bypass perlbal node and go to web ap node
directly, -> no hang and slow problem,too.

I've no idea how to solve this..

My setup:
Gentoo Linux 2.6
perl 5.8.6
Dual  Opteron
2g
Perlabl 1.39
Danga-Socket 1.48
Mogilefs (cvs)

---------perlbal.conf--------
LOAD vhosts
xs enable headers
SERVER aio_mode =3D linux
SERVER aio_threads =3D 36
# apache pools
CREATE POOL apaches
POOL apaches ADD 10.0.0.31:80
POOL apaches ADD 10.0.0.32:80

# *.blog.foo.com
CREATE SERVICE blog
>---SET listen          =3D 0.0.0.0:81
>---SET role            =3D reverse_proxy
>---SET pool            =3D apaches
>---SET persist_client  =3D on
>---SET persist_backend =3D on
>---SET verify_backend  =3D on
SET always_trusted  =3D on
SET enable_reproxy  =3D on
SET buffer_uploads  =3D on
SET buffer_backend_connect =3D 128k
ENABLE blog

CREATE SERVICE maintains
SET listen      =3D 0.0.0.0:82
SET role        =3D web_server
SET docroot     =3D /home/system
SET dirindexing =3D 1
SET persist_client =3D on
ENABLE maintains
# *.*
CREATE SERVICE vhost-
SET listen         =3D 0.0.0.0:80
SET role           =3D selector
SET plugins        =3D vhosts
SET persist_client =3D on
VHOST *.blog.foo.com =3D blog
VHOST moblog.foo.com =3D blog
ENABLE vhost

# always good to keep an internal management port open:
CREATE SERVICE mgmt
SET role   =3D management
SET listen =3D 127.0.0.1:60000
ENABLE mgmt

[ Post a follow-up to this message ]

sorry..
That's mod_php's fault,not perlbal...
apache+mod_php broken sometimes..
" exit signal Segmentation fault (11)..."

[ Post a follow-up to this message ]

Phew.  Always good to know it's not my fault.  :-)


On Fri, 18 Nov 2005, Eric Chang wrote:

> sorry..
> That's mod_php's fault,not perlbal...
> apache+mod_php broken sometimes..
> " exit signal Segmentation fault (11)..."
>
>

[ Post a follow-up to this message ]