similar to: mongrel_rails production vs development mode

Following errors are taken from monrgrel running in development mode. It complained routes.rb, no such file or directory and then sometimes i get application.rb, no such file or directory.Doesn''t seem correct to me. Though not so often, but even production servers throw these errors sometimes, and i have no special routes setup or something.Its pretty much default one, except few changes

We have a Centos server with a number of virtual hosts, and my rails app runs under one of those virtual hosts using mongrel_rails. The app lives in /home/mydomain/railsapp where /home/mydomain/railsapp/public is the rails root. It runs under mongrel on port 8008, so to get to it users invoke the url http://www.mydomain.com:8008/ - all is fine to this point. Now I have some users whose

I just noticed something interesting (or not) about getting to my RoR app on the 2 browsers. I''ve tested it running Webrick or Mongrel_rails and get the same behavior. The app is at http://www.mydomain.com:myport#/app/list Specifying that complete URL works fine in both browsers. However in IE if you just specify www.mydomain.com:myport#/app/list I get page not found. In FF the URL

Alright, it seems that I am having a bit of a problem with mongrel. My mongrel processes have been crashing pretty often and twice last night. I''m really not sure why, but I really need to fix it. I am running 0.3.13.3. Here is the mongrel.log file. Any ideas, things to look at, etc... is appreciated. Thanks, Carl PS, do all the broken pipe lines mean Mongrel is serving the static

Following is the output of top command at my server and i find the high usage very much alarming. We are basically a team of three developers working on same machine(remotely), so we run mongrel_rails servers from out ~/public/app directories. We also run a cluster of mongrel servers using apache2.2. Is this much memory use normal? PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+

Newbie question here: I''m hitting my rails app and killing mongrel. Any ideas? Here''s the error: /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:628:in `accept'': Software caused connection abort (Errno::ECONNABORTED) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in `join'' from

Hello, I have mongrel 1.0.1, rails 1.2.2 ruby 1.8.5 running on Centos 4.4. When I execute the mongrel_rails start -d I see that 3 processes are spawned. See below: [root at ccc aaa]# mongrel_rails start -d [root at ccc aaa]# ps -def |grep mong root 2743 1 9 07:14 ? 00:00:01 /usr/bin/ruby /usr/bin/mongrel_rails start -d root 2744 2743 0 07:14 ? 00:00:00

Hi One of the two mongrel processes has died in the middle of the night four times in the past 9 days, and I need help debugging this. Each time the symptoms are the same: * Each time I can restart the process via cap -a restart_app. * Before the restart, there is nothing unusual in production.log or mongrel.log. * During the restart, about 100 repetitions of an error message are generated in

Hello all, new convert to Mongrel here and am trying to get things going. Right now I can start mongrel up just fine and it seems to work great, but I''m trying to use the nifty console I heard about and can''t seem to get it going. `mongrel_rails console` Cannot run the console script: unititialized constant RailsConfigurator Any ideas? I just installed everything yesterday

Hi everyone, I''m having a problem starting rails on solaris. I have made the changes suggested in the joyeur article but it doesn''t make any difference. The error is below. Does anyone have any idea? /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in `register'': undefined method `resolve'' for nil:Mongrel::URIClassifier (NoMethodError)

Hello all, I''m new to Mongrel and am very impressed with what I see so far. This thing beats FastCGI hands down, and is even simpler to use than SCGI. Great job Zed! Thanks for all the hard work. I am a bit surprised at the memory usage patterns though. I''m not sure if I''m doing something wrong (most likely I am), or if this is a problem with the app I''m

Hi Everyone, I have a small pre-release for Mongrel that will eventually be the 0.3.13.3 release, but it needs some quick testing before I make it official. There''s a bug for only some folks and I need to find out what''s causing it. The bug is that the object_id method gets the signature: def object_id(param) end Which is incredibly evil. Normally this does nothing to

Hey Folks, I''ve been holding off the official 0.3.13 release so that Luis can get the win32 side very nice and clean. We fixed a major problem last night so it''s only a short time before we get it out. Luis is working really hard on it, so just be patient. In the meantime, I''ve been doing a code audit of the Mongrel code as it is now and fixing any little things I

I''m not sure what''s to blame, but it seems that if I delete or move a template, restarting is necessary. For example, I recently moved a partial from app/views/members/_login.rhtml to app/views/members/_login.mab, after which I got a blank-page-of-death. Once I restarted my Mongrel cluster, it worked. Shouldn''t changes like this get picked up automatically in

I just moved from apache2/fcgi to apache2.2/mongrel and everything seems to work great except for 2 issues, one being major and one minor. the major issue i am experiencing is that after a period of time where my rails apps are not used, typically overnight, the mongrel processes become unresponsive. I currently have 3 apps running behind an apache2.2 proxy. every morning when i come in to

Hello Everyone, This is the official 0.3.13.3 release of Mongrel. Mongrel is now released under the *Ruby license* instead of the LGPL. I''m hoping this increases the adoption of Mongrel even further and hopefully I can start pushing to get Mongrel included in Ruby directly. INSTALL As usual, you install it with your friendly gem install method of choice: gem install mongrel Or

Hi, On os x.3.9, with ruby 1.8.4 installed through darwinports and mongrel through gems, everything works until I restart: mongrel_rails restart adds the logs: ** USR2 signal received. ** Restarting with arguments: ruby /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails start -p 3001 -d /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails:134: in

Hi everybody, I have installed mongrel and mongrel cluster in a new linux box .... at the end of the day I was able to lunch mongrel (mongrel_rails start -e production) and all is working fine with. However, when I tried to set a mongrel cluster the command mongrel_rails cluster::start get the following output : starting port 8000 starting port 8001 starting port 8002 But when I lunched the

Hi, I wanted to set port in config file (via mongrel_rails -C config/config.yaml), and it seems to not take it into account. I''ve looked into the code, (line 58), and it reads: settings = conf.merge(settings) Now settings contain all the possible (important) keys (possibly with nil values, line 49, and lib/mongrel/command.rb, line 46) so everything from conf get overwritten with

Hi am a newbie to mongrel. am using mongrel cluster in my ruby application. When i start mongrel cluster it is working fine and when i stop it it says already stopped port 8000. it is giving the error as follows ********* simple selection ********* ********* selection by list ********* -A all processes -C by command name -N negate selection -G by real