Just came across a really weird bug, want to see if anyone else can replicate. If you cause an error, usually an exception is thrown and you are able to see the traceback to what caused it. What I have found, is that right after I restart Apache, if the first page I load, whether it be www.example.com/asset/new, or whatever, that causes an error along the lines of something like syntax, the FCGI process won''t start to show you the exception page. Anyone else able to replicate this in their Apache2/FCGI/Rails 0.14.2/Ruby 1.8.2 environment? Warmest regards, Nathan. -------------------------------------------------------------- Nathaniel S. H. Brown Toll Free 1.877.4.INIMIT Inimit Innovations Phone 604.724.6624 www.inimit.com Fax 604.444.9942
Nathaniel S. H. Brown wrote:>Anyone else able to replicate this in their Apache2/FCGI/Rails 0.14.2/Ruby >1.8.2 environment? > >My experience with hosting Apache2 and FastCGI has been pretty painful, sometimes it works and sometimes it doesn''t. I ended up using Lighttpd. Very easy to configure & host. Some people say Apache 1.3 + FastCGI is also a good option, but I haven''t tried that. Vamsee.
I am currently setup in a hosting environment where I utilize Plesk to manage my systems. So lighttpd doesn''t particularly suit my needs. Unless someone has experience integrating the two? Also, I am finding a lot of orphaned /usr/local/bin/ruby processes happening when I restart the apache service. Currently I am using EdgeRails, and heard that this was supposed to be fixed in this? Warmest regards, Nathan. -------------------------------------------------------------- Nathaniel S. H. Brown Toll Free 1.877.4.INIMIT Inimit Innovations Phone 604.724.6624 www.inimit.com Fax 604.444.9942> Nathaniel S. H. Brown wrote: > > >Anyone else able to replicate this in their Apache2/FCGI/Rails > >0.14.2/Ruby > >1.8.2 environment? > > > > > My experience with hosting Apache2 and FastCGI has been > pretty painful, sometimes it works and sometimes it doesn''t. > I ended up using Lighttpd. > Very easy to configure & host. Some people say Apache 1.3 + > FastCGI is also a good option, but I haven''t tried that. > > Vamsee.
I truly second this, I tried to setup Apache 2.0.55 with fastcgi and got nothing but core dumps *all* over the place from irb.rb or something like that. I fought with Lighttpd a slight bit but had it working within the day. But this was on Solaris 10 on Sparc. I would assume that Linux install would be way easier. But Lighttpd+FastCGI+RoR is the bomb diggity ! Go combo ! Cheers, Aly. Vamsee Kanakala wrote:> Nathaniel S. H. Brown wrote: > >> Anyone else able to replicate this in their Apache2/FCGI/Rails >> 0.14.2/Ruby >> 1.8.2 environment? >> >> > My experience with hosting Apache2 and FastCGI has been pretty painful, > sometimes it works and sometimes it doesn''t. I ended up using Lighttpd. > Very easy to configure & host. Some people say Apache 1.3 + FastCGI is > also a good option, but I haven''t tried that. > > Vamsee. > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails-- Aly S.P Dharshi aly.dharshi-EynCeXvFgoheoWH0uzbU5w@public.gmane.org "A good speech is like a good dress that''s short enough to be interesting and long enough to cover the subject"
On Thu, 2005-11-03 at 12:09 +0530, Vamsee Kanakala wrote:> Some people say Apache 1.3 + FastCGI is > also a good option, but I haven''t tried that.I''ve been using Apache 1.3.33 + FastCGI for a site that''s a mix of XML-RPC and HTTP fronted by Rails. It''s working fine... no problems yet. Yours, tom