Re: [galaxy-dev] Galaxy static assets and redirect woes

2011-03-01 Thread Nate Coraor
Paul-Michael Agapow wrote:
> This is not a Galaxy problem per se, but a problem during Galaxy setup
> so maybe others will have an insight.
> 
>  
> 
> So we're installing our own Galaxy for production / general use. I've
> been following the config and advanced config guides and installed
> Galaxy in its own account and home directory. It runs off the built-in
> web-server fine - the problem comes when I try to put it through an
> Apache proxy. Galaxy has to run off a subdirectory
> (http://foobar/galaxy) and if I just rewrite everything through there
> (RewriteRule ^/galaxy(.*) http://localhost:7070$1 [P]), it works fine.
> 
>  
> 
> The problem comes when I introduce the rewrite rules to have Apache
> serve the static content directly. None of the static content shows up
> and the error log shows "(13) permission denied" errors. Things I have
> tried:
> 
>  
> 
> * Logged the rewrite calls to see they rewrite to the correct
> paths for the static content
> 
> * Checked the proxy-filter and filter-with declarations
> 
> * Checked the unix permissions on the static dir
> 
> * Tested for non-existent or incorrect paths (which generate a
> different error)
> 
> * Inserted directory declarations to "Allow from all" for the
> static dir
> 
> * Checked for and tried .htaccess files
> 
> * SELinux is disabled

Hi Paul,

This is the whole list of things I would've suggested checking,
especially looking for any high level (i.e. "/")  "Deny from
all" declarations and .htaccess files anywhere in the tree.  Beyond
this, have you increased the error log level as high as possible to see
if it yields any more information about what's going on?

The webserver user will also need read/execute permissions on every
directory above/below the static directory, so you may want to double
check this if you haven't.

--nate

> 
>  
> 
> I feel I must have a blindspot about the solution - any ideas about
> where else to look? Technical details: cloned the latest Galaxy
> distribution, running on Fedora 9, Apache 2.2.
> 
>  
> 
> 
> 
> Paul Agapow (paul-michael.aga...@hpa.org.uk)
> 
> Bioinformatics, Centre for Infections, Health Protection Agency
> 
>  
> 
> 
> 
> -
> **
> The information contained in the EMail and any attachments is
> confidential and intended solely and for the attention and use of
> the named addressee(s). It may not be disclosed to any other person
> without the express authority of the HPA, or the intended
> recipient, or both. If you are not the intended recipient, you must
> not disclose, copy, distribute or retain this message or any part
> of it. This footnote also confirms that this EMail has been swept
> for computer viruses, but please re-sweep any attachments before
> opening or saving. HTTP://www.HPA.org.uk
> **

> ___
> To manage your subscriptions to this and other Galaxy lists, please use the 
> interface at:
> 
>   http://lists.bx.psu.edu/

___
To manage your subscriptions to this and other Galaxy lists, please use the 
interface at:

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


[galaxy-dev] Galaxy static assets and redirect woes

2011-03-01 Thread Paul-Michael Agapow
This is not a Galaxy problem per se, but a problem during Galaxy setup
so maybe others will have an insight.

 

So we're installing our own Galaxy for production / general use. I've
been following the config and advanced config guides and installed
Galaxy in its own account and home directory. It runs off the built-in
web-server fine - the problem comes when I try to put it through an
Apache proxy. Galaxy has to run off a subdirectory
(http://foobar/galaxy) and if I just rewrite everything through there
(RewriteRule ^/galaxy(.*) http://localhost:7070$1 [P]), it works fine.

 

The problem comes when I introduce the rewrite rules to have Apache
serve the static content directly. None of the static content shows up
and the error log shows "(13) permission denied" errors. Things I have
tried:

 

* Logged the rewrite calls to see they rewrite to the correct
paths for the static content

* Checked the proxy-filter and filter-with declarations

* Checked the unix permissions on the static dir

* Tested for non-existent or incorrect paths (which generate a
different error)

* Inserted directory declarations to "Allow from all" for the
static dir

* Checked for and tried .htaccess files

* SELinux is disabled

 

I feel I must have a blindspot about the solution - any ideas about
where else to look? Technical details: cloned the latest Galaxy
distribution, running on Fedora 9, Apache 2.2.

 



Paul Agapow (paul-michael.aga...@hpa.org.uk)

Bioinformatics, Centre for Infections, Health Protection Agency

 



-
**
The information contained in the EMail and any attachments is
confidential and intended solely and for the attention and use of
the named addressee(s). It may not be disclosed to any other person
without the express authority of the HPA, or the intended
recipient, or both. If you are not the intended recipient, you must
not disclose, copy, distribute or retain this message or any part
of it. This footnote also confirms that this EMail has been swept
for computer viruses, but please re-sweep any attachments before
opening or saving. HTTP://www.HPA.org.uk
**___
To manage your subscriptions to this and other Galaxy lists, please use the 
interface at:

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