dreamhost responded saying I ran against a memory limit for the user I'm running the app on. how i hit the limit with only development sites with no traffic and ruby processes only running for a fraction of the time, is a mistery to me. they suggested creating a new user and installing everything over again... sigh...
anyway, thanks for all the help jakob 2007/2/22, Oliver Barnes <[EMAIL PROTECTED]>: > Hi Jacob, > > no, the other log files are empty, aside from the db bootstraping info. > > I do have a couple of other rails projects running on the same > account, and I've compared both environment and dispatch files, > nothing seems to be wrong... here's my dispatch.fcgi: > ----------------------------- > require File.dirname(__FILE__) + "/../config/environment" > require 'fcgi_handler' > > class RailsFCGIHandler > private > def frao_handler(signal) > dispatcher_log :info, "asked to terminate immediately" > dispatcher_log :info, "frao handler working its magic!" > restart_handler(signal) > end > alias_method :exit_now_handler, :frao_handler > end > > RailsFCGIHandler.process! nil, 50 > ------------------------------- > > and my environment.rb is the standard one installed with radiant, I > just uncommented > > ENV['RAILS_ENV'] ||= 'production' > > on it. > > this problem is mentioned in a lot places on the web, but the > solutions given vary wildly - "force your GC to collect every 50 > requests", "run on dev mode first then run on production", "check > permissions on /tmp and /log"... tried them all out. > > There are threads mentioning hosting services (not just dreamhost) > deliberately killing off dispatch.fcgi processes from certain accounts > that have been "bad" with runaway processes. but thing is, the only > rails app I run full time here is running ok, and it doesn't have much > traffic at all... I did send a support ticket asking whether that's > happening, so let's see how it goes. > > meanwhile, i'm going to try running it as a standalone app as you suggested > > > > 2007/2/22, Jacob Burkhart <[EMAIL PROTECTED]>: > > Do you see any other information in other log files? > > > > > > As a test, try creating a fresh "empty" rails project. > > > > Can you run > > >> rails testproject > > on the dreamhost ssh command line > > > > See if you can get an empty rails site running. > > > > Then compare the dispatch.fcgi and environment.rb of the test project > > with the radiant you are trying to run. > > > > Also try installing radiant as a full standalone app instead of using > > the gem. > > > > -- > > Posted via http://www.ruby-forum.com/. > > _______________________________________________ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > _______________________________________________ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
