similar to: Can''t get value params[:model] first request?

I''m a mongrel newbie and a linux newbie. I have two CENTOS 5 servers. On server A, my app works fine, with mongrel in daemon mode. On server B, it works fine if I just say mongrel_rails start, but if I add -d, it doesn''t run. Suggestions? -- Posted via http://www.ruby-forum.com/.

Hi All, I''m a newbie and I''m soooo confused at the moment! Here''s my setup: 1) I''ve installed Ruby 1.8 on an Ubuntu 7.10 platform. I used apt to install that. 2) I downloaded rubygems_1.1.1 and installed that (tar -xzf, then ruby setup.rb) 3) I installed rails (gem install rails --include-dependencies) 4) I installed mongrel (gem install mongrel

hi. apologies if this has been asked before... my configs: ruby -v 1.8.5 mongrel 1.0.1 rails 1.2.3 i do a mongrel_rails start -e production -p 4000 -d it''ll say: ''** Ruby version is not up-to-date; loading cgi_multipart_eof_fix'' but that shouldn''t be the problems, since i see that all the time and my clusters work.. ( oh yeah, does it matter i have other

Thanks Bill for the answer ! In fact, my application is working well with webrick and also with a single mongrel instance lunched via the command : mongrel_rails start When I check what is the difference in the gem loaded in both cases (mongrel_rails start and mongrel_rails cluster::start) it seems that mongrel_rails cluster::start does not load all the gems that the first command is loading. So

I played around with this some more and when I changed line 142 of /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails from "exec cmd" to "system cmd" Mongrel has successfully restarted every time I''ve tried ("mongrel_rails restart"). Hell if I know why exec doesn''t work -- googling on "exec Operation not supported ruby"

Dear all, In the past, I''ve been successfully using mongrel_cluster following codahale setup [1]. Now I updated mongrel_cluster through gem to 1.0.2, and my previosly worked config is not working anymore. I report below a snip of one of logfile, it seems to me it is a missing gem problems, but this sounds strange to me, because my config was ok before the upgrade. Does

Hi, I''m calling restart from my Capistrano task. I have this in my deploy.rb file: # until mongrel_cluster updates to cap2... namespace :deploy do task :start, :roles => :app do start_mongrel_cluster end task :stop, :roles => :app do stop_mongrel_cluster end task :restart, :roles => :app do restart_mongrel_cluster end end (What''s the scoop on

After the upgrade my memory usage is shown like this: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4592 flipl 16 0 197m 150m 2360 S 0.0 14.9 6:17.28 mongrel_rails 4585 mongrel 16 0 190m 140m 1756 S 0.0 13.9 0:52.86 mongrel_rails 4579 mongrel 16 0 200m 157m 1752 S 0.0 15.5 0:56.31 mongrel_rails 4582 mongrel 16 0 189m 139m 1752 S 0.0 13.8

Hi I have a rather strange problem with mongrel and I would be grateful if anyone could assist me with resolving. I have an application running mongrel 1.1.1 and rails 1.2.5 with ruby 1.8.6. It was all working fine and starting as expected. But I did a server reboot once and mongrel has refused to start up since. I get the following error:

I''m trying to use the Ferret DRB server to avoid concurrency issues when using multiple mongrels. I can successfully add and edit data on my index via the DRB server, however, when I search the index, I get the following error: DRb::DRbConnError (DRb::DRbServerNotFound): /usr/lib/ruby/1.8/drb/drb.rb:1647:in `current_server'' /usr/lib/ruby/1.8/drb/drb.rb:1709:in

Hello, I don''t know if this is really relevant anymore because a new version is about to be released it seems, however I''ve been trying to run mongrel 0.3.12.4 on a development server in development mode (simply with mongrel_rails start). I try to access the server and the first page (static file) loads, but then the server dies and I get this in the logs. I''m

Hello everyone, Mongrel now has plugins that are based entirely on RubyGems. This feature was so slick that I decided to bust it out into a separate project called GemPlugin (more on that later). What the new plugin system does is makes it so that people can distribute Mongrel plugins as just plain gems, and mongrel will load them on the fly if people install them. There''s no

I''m getting the following exceptions when running mongrel_rails. Any ideas what might be causing the problem? Error details... $ mongrel_rails /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.3/lib/mongrel/command.rb:168:in `run'': When creating '''': undefined method `downcase'' for nil:NilClass (NoMethodError) from

I''m trying to deploy a rails app for development on slicehost and I can''t seem to get mongrel to work correctly. When I run mongrel_rails start I get: ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop

Sorry if this is the wrong place to ask, but when I run mongrel evented using swiftiply and then send it the USR2 signal to restart it, it dies. Without eventing, USR2 restarts mongrel as expected. Anyone else seen this? Here''s a dump: $ EVENT=1 mongrel_rails start -d -P /tmp/m.pid -p 4321 Using Evented Mongrel ** Ruby version is up-to-date; cgi_multipart_eof_fix was not loaded $ kill

I want to restart my Mongrels from crontab periodically to free up memory. I tried this: [admin at mudcrapce ~]$ mongrel_rails cluster::restart -C /var/www/apps/mudcrapce/current/config/mongrel_cluster.yml Restarting 5 Mongrel servers... mongrel_rails restart -P log/mongrel.3040.pid !!! PID file log/mongrel.3040.pid does not exist. Not running? mongrel::restart reported an error. Use

Hi there, I''m using Mongrel (0.3.13 prerelease, installed today) to serve up some Rails apps in production. Everything works fine if I give all the appropriate options on the command line, such as: $ mongrel_rails start -c /home/mcornick/rails/mcornick.org/current -P log/mongrel.pid -l log/mongrel.log -e production -d -a 127.0.0.1 -p 6833 So, having accomplished that, I thought it

In the several months I''ve been using Mongrel, I''ve experienced two crashes. Both were immediately following a "Socket read returned insufficient data" error from HTTPRequest. Both times, the mongrel process would hang indefinitely (and not respond to requests) untill manually killed. The first instance references a line where I was using

Hi, I am working on deplying my Rail app to QA and then move to production. Since on our QA servers, there is no internet access and also for production servers, internet access is strictly prohibited. As a result, there is no way to install mongrel by use "gem install mongrel" command. The first option I tried is to put mongrel and all other gems under the vendor directly in my app,

When I go to a missing page in my rails app, I get the 500.html page, and this in my log output: no route found to match "/asdasd" with {:method=>:get} ./script/../config/../vendor/rails/actionpack/lib/action_controller/ routing.rb:1057:in `recognize_path'' ./script/../config/../vendor/rails/actionpack/lib/action_controller/ routing.rb:1047:in `recognize''