similar to: Running Shell Scripts/Commands at Startup?

Howdy, I''m trying to debug a situation where a Rails app running on Mongrel +Apache stops listening to requests. Restarting Mongrel and Apache brings it back to life. First off, here''s some info on versions, etc...: Red Hat Enterprise Linux ES release 3 (Taroon Update 8) ruby 1.8.5 (2006-12-04 patchlevel 2) [x86_64-linux] Mongrel 1.0.1 Rails 1.2.1 fastthread (0.6.2)

Hi. I''m a fairly new mongrel user and have a scenario that I wanted to run by you all, see if anyone''s synapses connect -- mine def. aren''t! I''m running a fairly simple rails app through a mongrel cluster (2 mongrels). This site is consistently sloooow -- memory on the server is regularly paging (and shouldn''t be). ssh-ing in and running top shows

Hi all, Both the rails book (1st Ed) and the docs on the rails site (*and* the Mongrel FAQ) tell me that rails (& ActionPack /ActiveRecord) is not threadsafe. Since I need lots of worker threads in the app I''m working on (details at the end of this mail) this poses quite a problem for me. Is the lack of thread safety a conscious design decision (kind of understandable for rails

Hi, Are there any recommendations as to what is currently the most stable setup is for mongrel & apache? I read somewhere (probably here) that you should avoid using PStore for sessions. Are there any more of such recommendations? Also, what is currently the safest version of mongrel to use in production? Jeroen

I''m having no luck trying to daemonize mongrel running a camping server. When mongrel daemonizes, I get: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723:in `accept'': closed stream (IOError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' ... (This was after I disabled the unhandled exception catchall in the

Hi, what is the preferd way to configure/start mongrel? [ ] with Mongrel::Configurator => HttpServer [ ] @var = HttpServer.new(...) @var.run I ask because the only debug methode i have found was in Mongrel::Configurator ;-) @Zed: are you also subscribed on nitro list?! regards Alex

I have an archiving application that handles large file uploads. I already use backgroundrb to run a behind the scenes bulk import of records. All good. Thank you Ezra. Now I would like to add long running file uploads to the things that backgroundrb does for me. That''s right that ole chestnut. I''ve seen a lot of mention of this practice around the web, but have yet

Hi. I am using BackgrounDRb to process thumbnails and upload to S3 - things are hunky-dory in development (thumbs are generated, these are uploaded to S3, the metadata is saved to trhe DB, and I get a nice status page updated by periodic calls via ask_status), but when I tried to deploy to our staging server and stop/start BackgrounDRb via Capistrano, things blew up - well, not exactly,

Hi, I have mongrel 0.3.14, with ruby 1.8.5, rails 1.1.6 and mongrel cluster 0.2.1, on debian sage 3.1 with apache 2.0, and fastthread 0.6.1. I am load balancing 3 mongrel processes using the random port trick. When I start mongrel the processes have about 60MB, but after some hour of usage the memory ballons upto more than 180MB and the site becomes terribly slow. Forcing me to restart mongrel

We have been searching for a Rails deployment architecture which works for us for some time. We''ve recently moved from Apache 1.3 + FastCGI to Apache 2.2 + mod_proxy_balancer + mongrel_cluster, and it''s a significant improvement. But it still exhibits serious performance problems. We have the beginnings of a fix that we would like to share. To illustrate the problem, imagine a

Howdy, I recently switched an app to Mongrel and since the switch, when I upload files using the file_column plug-in, the files are not uploaded with the correct permissions. I want something like this: -rw-rw-rw- file.jpg But I am getting: -rw------- file.jpg So, of course the files aren''t being served up by the Web server. Mongrel is running as the ''mongrel''

I see that the RubyOnRails.com site has migrated to Mongrel with Apache as a front-end proxy. Is that now the/a recommended setup for Rails apps? We''re still using FCGI but I''m always interested to learn more about other folk''s successful deployment choices. Across all of our sites we''re pumping out about 300k pages per day so anything that saves memory or has

Apologies for the formatting, but this is the error I get when I try to start up mongrel. The app does work under webrick, so I''m not real sure what''s going on here. Thanks for any insight into what''s going on. -j ** Starting Mongrel listening at 0.0.0.0:3000 /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in `register'': undefined method

Hi Mongrels, Anyone used Packet? http://rubyforge.org/projects/packet It''s a pure-Ruby (I think) evented framework. It might offer a nice way forward for 1.9''s system threads, JRuby, and Windows, all at once. Mongrel''s green thread queue doesn''t have a lot of life left in it. Evan -- Evan Weaver Cloudburst, LLC

I start up an external process when I start my rails environment. I currently do this in config/environment.rb by forking a process and recording it''s process id in log/foo.pid, I''d like to kill that process when I close mongrel. Is there an API in mongrel for responding to the shutdown event? Or do I need to listen for the term signal and do my clean up that way? Thanks,

Hello Everyone, Mongrel is due for a 0.3.12 release which will feature some pretty insane goodies for everyone. There''s talk of IOWA support, lots of speed improvements (including sendfile support), a great Configurator which makes configuring Mongrel a snap (especially for framework implementers), and a ton of debugging stuff. WARNING This is a pre-release announcement for the

IE6 happily sends unsafe* characters unencoded if you''ve typed them into the URL bar of your IE6 window. This could happen if you copy & paste a URL from an email or web page. Mongrel doesn''t seem to handle these properly. In 0.3.13.3 it would print out something like: Sun Oct 15 23:05:38 CST 2006: BAD CLIENT (192.168.1.2): Invalid HTTP format, parsing fails. 0.3.13.5

I do some indexing using acts_as_ferret in a rails app. I need to do some preloading of the index''s sort fields so that the first request that sorts doesn''t take 5 minutes to complete. I tried sticking my preload code in config/environment.rb and that worked but it gets ran in rake migrations, tests, etc, when it''s not really needed. Is there anything specific to

Hi all, I just wanted to let you know that I built some Debian (Sarge) packages to allow an apt-get only installation of Mongrel, Ruby and friends. Also contained is an init script that is capable of managing multiple applications. Support for the Pen load balancer is also included. More info can be found there:

I updated to ruby 1.8.6p111 last night and updated some gems and now mongrel doesn''t work: MacOS 10.4.10 $ ruby --version ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-darwin8.10.1] $ gem list rails *** LOCAL GEMS *** rails (1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2.0, 1.1.6) Here''s a simple test: $ rails test5 create ... $ cd test5 $ script/server => Booting