Re: [Radiant] 500 Error on page update.
Okay, this is starting to seem like the most likely answer, but I have
never before had issues deploying Rails apps with a similar config.
I have added the AllowOverride none to the virtual host, but I am not
sure if it is correct. As I still get the same error.
I think you were on to the problem though Sean.
Here is my virtual host config. I have commented out anything I thought
could be the problem. Anything fishy (or strait out ridiculous wrong)?
VirtualHost *:80
ServerAdmin [EMAIL PROTECTED]
DocumentRoot /path/to/my/app/public
ServerName www.gapdesigns.com
ServerAlias gapdesigns.com
RewriteEngine on
#Rewrite all non www to www.
#RewriteCond %{HTTP_HOST} !www\.gapdesigns\.com$ [NC]
#RewriteCond %{HTTP_HOST} !^$
#RewriteRule ^(.*)$ http://www.gapdesigns.com$1 [R=301,L]
Directory /path/to/my/app/public/
AllowOverride none
/Directory
Proxy balancer://mongrel_cluster
BalancerMember http://127.0.0.1:8000
BalancerMember http://127.0.0.1:8001
/Proxy
RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ balancer://mongrel_cluster%{REQUEST_URI} [P,QSA,L]
/VirtualHost
Alan
Sean Cribbs wrote:
Alan,
My guess is that your Apache config is still trying to read .htaccess
in the public folder. Make sure to have AllowOverride none in your
Apache config that sets up the reverse proxy (inside the Directory
or VirtualHost).
Sean
Alan Peabody wrote:
Andrew Neil wrote:
On 9 Aug 2008, at 19:04, Alan Peabody wrote:
I seem to be getting a 500 error no matter how I deploy my radiant
site.
That is an internal server error. You might get an idea of what is
going on if you can look at the log files on your server. I had a
similar problem recently, and when I read the error log it became
clear that I was missing a gem on the server.
One of my extensions required a gem, which was installed on my local
machine, but not on the server. Only when I ran an action within
that extension did this become an issue (and I saw a 500 error).
When I installed the gem on the server, everything was fixed.
Perhaps you have a similar issue.
Drew
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
I have double and triple checked, and I have all the gems and
dependencies required installed. No dice, but thanks for the
suggestion Drew.
I have checked the logs. the apache logs show nothing but that it is
serving a 500 error and the rails logs show nothing.
I can boot a single instance of mongrel (script/server) on the actual
production machine and it works great. So I am really mystified. Any
more hints?
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 500 Error on page update.
On 10.08.2008, at 20:46, Alan Peabody wrote: Alan Peabody wrote: Andrew Neil wrote: On 9 Aug 2008, at 19:04, Alan Peabody wrote: I have checked the logs. the apache logs show nothing but that it is serving a 500 error and the rails logs show nothing. Does the apache process have write acces to the cache dir and log dir? This is a problem I run into earlier ... cu edi -- DI Edmund Haselwanter, [EMAIL PROTECTED], http://edmund.haselwanter.com/ ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 500 Error on page update.
On 9 Aug 2008, at 19:04, Alan Peabody wrote: I seem to be getting a 500 error no matter how I deploy my radiant site. That is an internal server error. You might get an idea of what is going on if you can look at the log files on your server. I had a similar problem recently, and when I read the error log it became clear that I was missing a gem on the server. One of my extensions required a gem, which was installed on my local machine, but not on the server. Only when I ran an action within that extension did this become an issue (and I saw a 500 error). When I installed the gem on the server, everything was fixed. Perhaps you have a similar issue. Drew ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 500 Error on page update.
Andrew Neil wrote: On 9 Aug 2008, at 19:04, Alan Peabody wrote: I seem to be getting a 500 error no matter how I deploy my radiant site. That is an internal server error. You might get an idea of what is going on if you can look at the log files on your server. I had a similar problem recently, and when I read the error log it became clear that I was missing a gem on the server. One of my extensions required a gem, which was installed on my local machine, but not on the server. Only when I ran an action within that extension did this become an issue (and I saw a 500 error). When I installed the gem on the server, everything was fixed. Perhaps you have a similar issue. Drew ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant I have double and triple checked, and I have all the gems and dependencies required installed. No dice, but thanks for the suggestion Drew. I have checked the logs. the apache logs show nothing but that it is serving a 500 error and the rails logs show nothing. I can boot a single instance of mongrel (script/server) on the actual production machine and it works great. So I am really mystified. Any more hints? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 500 Error on page update.
Alan, My guess is that your Apache config is still trying to read .htaccess in the public folder. Make sure to have AllowOverride none in your Apache config that sets up the reverse proxy (inside the Directory or VirtualHost). Sean Alan Peabody wrote: Andrew Neil wrote: On 9 Aug 2008, at 19:04, Alan Peabody wrote: I seem to be getting a 500 error no matter how I deploy my radiant site. That is an internal server error. You might get an idea of what is going on if you can look at the log files on your server. I had a similar problem recently, and when I read the error log it became clear that I was missing a gem on the server. One of my extensions required a gem, which was installed on my local machine, but not on the server. Only when I ran an action within that extension did this become an issue (and I saw a 500 error). When I installed the gem on the server, everything was fixed. Perhaps you have a similar issue. Drew ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant I have double and triple checked, and I have all the gems and dependencies required installed. No dice, but thanks for the suggestion Drew. I have checked the logs. the apache logs show nothing but that it is serving a 500 error and the rails logs show nothing. I can boot a single instance of mongrel (script/server) on the actual production machine and it works great. So I am really mystified. Any more hints? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
