search for: mongrel_cluster_ctl

...nstall: gem install mongrel_cluster --source=http:// railsmachine.rubyforge.org/releases/ Changes: * Suppress output from mongrel_rails. * Added a verbose option (-v, --verbose) to print output from mongrel_rails. * Added support for changing the user/group of mongrel_rails process. * Added bin/mongrel_cluster_ctl to start/stop all clusters on a server. Usage: mongrel_cluster_ctl (start|stop|restart) [options] * Addred resources/mongrel_cluster * Fixed bugs in Capistrano recipes with mongrel_config variable. * Remove use_sudo from configure_mongrel_cluster task. * Changed restart_mongrel_cluster task to ca...

...nstall: gem install mongrel_cluster --source=http:// railsmachine.rubyforge.org/releases/ Changes: * Suppress output from mongrel_rails. * Added a verbose option (-v, --verbose) to print output from mongrel_rails. * Added support for changing the user/group of mongrel_rails process. * Added bin/mongrel_cluster_ctl to start/stop all clusters on a server. Usage: mongrel_cluster_ctl (start|stop|restart) [options] * Addred resources/mongrel_cluster * Fixed bugs in Capistrano recipes with mongrel_config variable. * Remove use_sudo from configure_mongrel_cluster task. * Changed restart_mongrel_cluster task to ca...

...t 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 also made sure that the mongrel_cluster_ctl location is in the PATH variable. Just to be on the safe side I created a symbolic link in /usr/bin and still no luck. The next thing I did was to trace the mongrel_cluster script. There is something strange about it, and I can''t believe that nobody complained about it yet: the script tak...

...tc/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 mongrel_cluster_config="/etc/mongrel_cluster" The default config path is /usr/local/etc/mongrel_cluster Would be nice if mongrel_cluster_ctl had some sort of "status" switch to see if the servers are actually running and what their pids are. Andrew Bennett potatosaladx at gmail.com -------------- next part -------------- A non-text attachment was scrubbed... Name: mongrel_cluster.sh Type: application/x-sh Size: 936 bytes Desc...

...* Added cluster::status to display basic process status information for the cluster. Returns ''0'' if all processes are found and ''2'' if a process or pidfile is missing. Supports ''--only''. Status commands were also added to the init.d script, mongrel_cluster_ctl, and the cap recipes. * The init.d script (resources/mongrel_cluster) will now create /var/run/mongrel_cluster and chown to a defined user on start. To fully use this feature, update your cluster yml files to store the pidfile in /var/run/mongrel_cluster. This will support cleaning up orphaned...

...; 0) (Gem::LoadError) from /usr/local/lib/site_ruby/1.8/rubygems.rb:141:in `activate'' from /usr/local/lib/site_ruby/1.8/rubygems.rb:37:in `require_gem_with_options'' from /usr/local/lib/site_ruby/1.8/rubygems.rb:31:in `require_gem'' from /usr/bin/mongrel_cluster_ctl:17 This may be more of a ruby gems question, but any thoughts/help would be appreciated. Thanks, --James

I''m trying to emulate the mongrel_cluster_ctl but it takes a -c conf_file option... meaning I can run it from anywhere as long as I tell it where the conf file is. Merb doesn''t have that capability does it? (it has an additional/supplemental config like mup.conf etc) Do I have to be under the merb_app root /path/to/merb/app/ to be ab...

I have installed mongrel and mongrel_cluster fine and have them running great with my app. I tried using the init.d script provided with mongrel_cluster 2.1 to start it up on boot but it doesn''t. mongrel_cluster_ctl works fine for me by hand and so does /etc/init.d./mongrel_cluster start. I am on Debian so I installed the service links with sudo update-rc.d mongrel_cluster defaults. And yes I chmod''ed it. I checked and double checked /etc/mongrel_cluster and my yml file and everything I can think of....

...rt'' now calls ''mongrel_rails stop'' and ''mongrel_rails start''. ''cluster::restart'' now accepts the ''force'' argument instead of ''soft''. - Added ''.conf'' as a valid file extension for mongrel_cluster_ctl. - Added check for missing script and directory to the init.d script. (Thanks, Neil Wilson) To install: gem install mongrel_cluster --source http:// railsmachine.rubyforge.org/releases/ I''m working on documentation the next few days so if you have any burning questions or confusion,...

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

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

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 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

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

...ls stop 8002 mongrel_rails stop 8003 mongrel_rails stop 8004 [.....503....application offline.....] mongrel_rails start 8001 mongrel_rails start 8002 mongrel_rails start 8003 mongrel_rails start 8004 (yuck!) It''s has been very difficult for me to figure out where to install the hacked mongrel_cluster_ctl that Carl provides in his blog. The execution path is not clear. Would anyone be willing to give me some ideas? Thank you, Elliott -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/mongrel-users/attachments/20090203/2bee5115/attach...

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, I''m able to run a ROR application in a Red Hat Enterprise Linux 4.4 environment, as long as I start my mongrel_cluster via the command line: [chris at localhost ~]$ mongrel_cluster_ctl start I take a look at the two mongrel_rails processes that were just created: [chris at localhost log]$ ps -ef | grep mongrel chris 4781 1 5 05:55 ? 00:00:02 /usr/local/bin/ruby /usr/local/bin/mongrel_rails start -d -e production -a 0.0.0.0 -c /home/chris/kitry/FDS_Server --user...

...; This is on Debian testing distro. Additionally, if I don''t have Debian package libgems-ruby1.8 installed I get errors when trying to use gem. The error in then, when I reboot I get an error from /usr/lib/ruby/1.8/rubygems.rb that RubyGem mongrel_cluster could not be found. Clearly mongrel_cluster_ctl is trying to use the Debian rubygems and not the user directory. Although I''ve modifed both the user and root .bashrc file to export PATH and GEM_HOME to the user directory gems. I''ve posted a similar type question on the ruby list, being that it seemed to be a ruby problem....

...t so I''m filling in for him. This is a short announcement to tell everyone using the mongrel_cluster gem to manage their Mongrels that there''s a new official version out. Version 0.2.0 is sporting the following features: * Added support for specifying user to run * Added script, mongrel_cluster_ctl for starting/stopping all clusters on a server. * Added example init.d script in gem_path/resources * Changed license to LGPL You should update your RubyGem with: gem update Or, reinstall with: gem uninstall mongrel_cluster gem install mongrel_cluster The mongrel_cluster instructions hav...

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?