Re: [galaxy-dev] Load Balancer config doesn't work

2012-06-07 Thread Nate Coraor
On Jun 1, 2012, at 4:36 AM, julie dubois wrote:

 Hi,
 After several post in an Apache Forum, I've solve any problem of my apache 
 configuration to enable load balancer configuration.
 It seems work but when I launch my galaxy application, I arrive in this web 
 page :
 
 Service temporarily Unavailable
 
 And my log apache shows this :
 [Tue May 29 09:37:32 2012] [error] (111)Connection refused: proxy: HTTP: 
 attempt to connect to 127.0.0.1:8083
  (localhost) failed
 [Tue May 29 09:37:32 2012] [error] ap_proxy_connect_backend disabling worker 
 for (localhost)
 [Tue May 29 09:37:32 2012] [error] (111)Connection refused: proxy: HTTP: 
 attempt to connect to 
 127.0.0.1:8082
  (localhost) failed
 [Tue May 29 09:37:32 2012] [error] ap_proxy_connect_backend disabling worker 
 for (localhost)
 [Tue May 29 09:37:32 2012] [error] (111)Connection refused: proxy: HTTP: 
 attempt to connect to 
 127.0.0.1:8081
  (localhost) failed
 [Tue May 29 09:37:32 2012] [error] ap_proxy_connect_backend disabling worker 
 for (localhost)
 [Tue May 29 09:37:32 2012] [error] (111)Connection refused: proxy: HTTP: 
 attempt to connect to 
 127.0.0.1:8080
  (localhost) failed
 [Tue May 29 09:37:32 2012] [error] ap_proxy_connect_backend disabling worker 
 for (localhost)
 
 It means that galaxy doesn't listen the port 8080, 8081 ...
 
 I think it's my run.sh which cannot read my universe_wsgi.ini correctly. 
 Because if it could read correctly, in my terminal I could see this type of 
 line :
 
 Handling web0 with log file web0.log...
 Entering daemon mode...
 Now, Idon't see that! 
 after the command GALAXY_RUN_ALL=1 sh run.sh --daemon,
  I just see : Entering Daemon mode.
 So in my view,  it's not an Apache problem but a shell script galaxy problem.
 Somedy has already met this problem ? 
 Have you a solution ?

Hi Julie,

If you have a look in run.sh you can see how the script is attempting to parse 
your config file.  It's possible that the inline sed script is not working 
correctly in your environment.  This:

% sed -n 's/^\[server:\(.*\)\]/\1/  p' universe_wsgi.ini | xargs echo

Should return a list of the servers you have defined in your universe_wsgi.ini, 
so if you have:

[server:web0]
[server:web1]

The output of the above command should be:

web0 web1

You can also start each server individually with:

% python ./scripts/paster.py serve universe_wsgi.ini --server-name=web0 
--pid-file=web0.pid --log-file=web0.log --daemon
...

--nate

 
 Thank you.
 Julie
 
 
 
 
 
 
 
 
 ___
 Please keep all replies on the list by using reply all
 in your mail client.  To manage your subscriptions to this
 and other Galaxy lists, please use the interface at:
 
  http://lists.bx.psu.edu/


___
Please keep all replies on the list by using reply all
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

  http://lists.bx.psu.edu/


[galaxy-dev] Load Balancer config doesn't work

2012-06-01 Thread julie dubois
Hi,
After several post in an Apache Forum, I've solve any problem of my apache
configuration to enable load balancer configuration.
It seems work but when I launch my galaxy application, I arrive in this web
page :

Service temporarily Unavailable

And my log apache shows this :

[Tue May 29 09:37:32 2012] [error] (111)Connection refused: proxy:
HTTP: attempt to connect to 127.0.0.1:8083 (localhost) failed
[Tue May 29 09:37:32 2012] [error] ap_proxy_connect_backend disabling
worker for (localhost)
[Tue May 29 09:37:32 2012] [error] (111)Connection refused: proxy:
HTTP: attempt to connect to 127.0.0.1:8082 (localhost) failed
[Tue May 29 09:37:32 2012] [error] ap_proxy_connect_backend disabling
worker for (localhost)
[Tue May 29 09:37:32 2012] [error] (111)Connection refused: proxy:
HTTP: attempt to connect to 127.0.0.1:8081 (localhost) failed
[Tue May 29 09:37:32 2012] [error] ap_proxy_connect_backend disabling
worker for (localhost)
[Tue May 29 09:37:32 2012] [error] (111)Connection refused: proxy:
HTTP: attempt to connect to 127.0.0.1:8080 (localhost) failed
[Tue May 29 09:37:32 2012] [error] ap_proxy_connect_backend disabling
worker for (localhost)

It means that galaxy doesn't listen the port 8080, 8081 ...

I think it's my run.sh which cannot read my universe_wsgi.ini correctly.
Because if it could read correctly, in my terminal I could see this type of
line :

Handling web0 with log file web0.log...Entering daemon mode...

Now, Idon't see that!
after the command GALAXY_RUN_ALL=1 sh run.sh --daemon,
 I just see : Entering Daemon mode.
So in my view,  it's not an Apache problem but a shell script galaxy
problem.
Somedy has already met this problem ?
Have you a solution ?

Thank you.
Julie
___
Please keep all replies on the list by using reply all
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

  http://lists.bx.psu.edu/