similar to: Mongrel Cluster init.d problems

Which web server does mongrel fair best with? -Ron

I wanted to be able to specify in my /etc/rc.conf file whether mongrel_cluster should be enabled and the mongrel_cluster_config file for the init script, so I wrote this simple rc.d style script. Just throw it in /usr/local/etc/rc.d/ and do a chmod +x /usr/local/etc/rc.d/mongrel_cluster.sh To enable the script, add mongrel_cluster_enable="YES" to /etc/rc.conf and optionally add

Hi everyone, I''ve been working with Mongrel, Mongrel_cluster and Apache and it is great. However, I can''t get mongrel_cluster to start at boot time. I followed the instructions from http://mongrel.rubyforge.org/docs/mongrel_cluster.html (On Boot Initialization Setup) and mongrel_cluster does not start after rebooting the machine. I made sure that the shebang line is correct and

I''ve installed pen and mongrel with mongrel_cluster (as gems) on Debian sarge. I can run everything from the command line fine including starting from the /etc/init.d/mongrel_cluster script On boot though mongrel_cluster fails with this msg: /usr/local/lib/site_ruby/1.8/rubygems.rb:204:in `report_activate_error'': Could not find RubyGem mongrel_cluster (> 0) (Gem::LoadError)

Hi, I''m in the process of moving my blog over from lighttpd -> apache 2.2 + mongrel. Everything works fine as long as I don''t reboot :) On reboot apache comes up but mongrel_cluster doesn''t start up the pooches... I have added the mongrel_cluster call to my startup scripts like so: www:/etc/init.d# update-rc.d mongrel_cluster defaults Adding system startup for

Hey y''all: I''ve added some new stuff to mongrel_cluster. Give it try and let me know if it works for you. * Added ''--clean'' to cluster::start to force removal of the pidfile before trying to start the cluster member. This is useful for recovering from unexpected process death. * Added ''--only PORT'' to cluster::* to support running a

I''m running the latest mongrel (1.0.1) and the latest mongrel_cluster (1.0.1.1) on FreeBSD 6.1. When I use capistrano to try to stop or restart my cluster I get this (partial) output: ps: Process environment requires procfs(5) And my Mongrel processes haven''t stopped. Any ideas? Thanks, Jamie

Hi, I''m trying to setup my mongrel clusters to start on boot. I have followed the instructions under the "On Boot Initialization Setup" section at http://mongrel.rubyforge.org/docs/mongrel_cluster.html. When I try to start it up, I get the following error: me at mybox.com: sudo /etc/init.d/mongrel_cluster start Starting all mongrel_clusters... !!! Path to log file not

Hi there, I've been a happy djbdns+tinydns user for many, many years. I want to keep using it, so answers of the form "bletch! Use ISC BIND the way BSD intended" will be ignored :-) Having said that, one annoying consequence of my transition some time ago to using ntpd, rather than just setting the clock once-off with ntpdate as I used to, is that the /etc/rc.d mechanism starts

Hi, I''m running CentOS 4.3 and the latest Mongrel (0.3.13.3) and mongrel_cluster (0.2.0). I have set up a cluster, following the instructions at http://mongrel.rubyforge.org/docs/mongrel_cluster.html . I created a symbolic link in the directory /etc/mongrel_cluster . When I run mongrel_rails cluster::start -c test.yml, the mongrel servers start up. But at boot, the command

It appears the spawner in Rails 1.2 will do Mongrel clustering. I''m curious what this means for mongrel_cluster. They appear to overlap in features quite a bit. I don''t think the spawner uses a config, so that''s one difference. Will they be different enough? I only ask because mongrel_cluster could, theoretically, be made extinct if the spawner script has all the same

Hi Y''all, Just a quick note announce an update to mongrel_cluster. Changes: - ''mongrel_rails cluster::restart'' now calls ''mongrel_rails stop'' and ''mongrel_rails start''. ''cluster::restart'' now accepts the ''force'' argument instead of ''soft''. - Added ''.conf'' as

Hi all, I am having trouble transitioning from fastcgi to Mongrel. I have it all working apart from one small part, I can''t get the service to start on boot. I have followed the instructions and if I call the script directly: i.e. "/etc/init.d/mongrel_cluster start" it works fine, but if I call it using "service mongrel_cluster start" it fails with the

Hello, I''m trying to write a rails application serves by mongrel and using accentuated characters in the .rhtml page. But Mongrel replace them by ''?'' . It works fine for static pages by defining the charset to iso-8859-1 in the mongrel_mime.yml But how to change the default encoding (seems to be UTF-8) for the dynamic pages ? thanks for your help. -------------- next

Hello, I''ve been trying (unsuccessfully) to hack my mongrel_cluster to re-ststart in an alternating manner. Specifically, this soluiton: http://blog.carlmercier.com/2007/09/07/a-better-approach-to-restarting-a-mongrel-cluster/#content Which means I an call to mongrel_rails cluster::restart to do this: mongrel_rails start 8001 mongrel_rails stop 8001 mongrel_rails start 8002

Calling All Mongrel Minions! I wanna have some fun and would like this as a Christmas present. The site http://www.workingwithrails.com/ has this lame popularity system that''s kind of irking some of the main Ruby contributors. I think it''s kind of funny, but would like to demonstrate what an army of motivated people can do to these kinds of popularity contests. So, as a

What''s the difference, architecturally between cluster::restart and cluster::stop/start (I haven''t looked at the code, which is kinda lazy of me to ask the question I know) If they aren''t very different actually, can I put a plug in for having cluster::restart do a "start" if something''s happened and mongrel is stopped for that configuration?

Hello, I''ve completed the update of all my servers to the new mongrel. No problems whatsoever to report, well done. But, I have some colleagues who are wondering what the primary improvements are to mongrel with this new release. I read the Change log but it was a bit cryptic for me. Can anyone provide an executive summary of why 1.0.1 is better than 0.3.xx? a few main bullet

Hi, I have an application which is dying horrible deaths (i.e. segmentation faults) in mid-flight, in production... And of course, I should fix it. But while I find and fix the bugs, I found something I think should be different - I can work on submitting a patch, as it is quite simple, but I might be losing something on my rationale. When Mongrel segfaults, it does not -obviously- get to clean

Hi All, I am modifying typo so as, I can host multiple blogs on the same typo. And its almost done, except that...i am stuck at one place. When a user posts a new article, depending upon current blog_id, I would like to set the blog_id attribute of @article object. So..in the admin/content_controller.rb: We have: def new_or_edit if request.post? set_article_author