similar to: mongrel_rails restart not working

Sorry for the newbie question but I''m stumped: I have an app that requires sudo to run mongrel_rails. For my capistrano recipe is do it like this: sudo "mongrel_rails start -e production -p #{application_port} -d -c #{current_path}" Which works famously. Now I have tried several things for my restart task. Here they are: sudo "cd #{current_path} && sudo

I''m using the latest Mongrel (0.3.13.4) and restarting causes Mongrel to die. From mongrel.log: ** USR2 signal received. ** Restarting with arguments: ruby /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails start -C config/mongrel.yml /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:142:in `exec'': Operation not supported - ruby

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"

Hey folks. Sorry for the SUPER long email but if you''ve been experiencing the same problems with restarting your mongrel cluster with Capistrano, then I have two solutions that have worked for me and I''m pretty sure will for you as well. THE PROBLEM I was having trouble restarting my clusters using Capistrano. I''ve seen this come up before on the mailing list and

On Zed''s suggestion, I caught two new spinning mongrels and sent a SIGUSR2. The code appears to be stuck in read_multipart for both processes: # kill -USR2 6109 ** USR2 signal received. Thu Sep 21 14:55:39 EDT 2006: Reaping 1 threads for slow workers because of ''shutdown'' Thread #<Thread:0x419d7ce0 run> is too old, killing. Waiting for 1 requests to finish, could

Hey all, Has anyone out there got Mongrel deployments working with Capistrano? I''ve had a crack at setting it up, and I''ve found that after a deployment (with updated symlinks) that a mongrel restart does not pick up the new deployed site. It seems to me (in my linkted experience) that the HUP that is sent to mongrel does not re-evaluate the ./current symlink that Cap puts in

Hi everyone. Zed, thanks for Mongrel. I''ve been running mongrel on my WiFi cafe site (http://wifi.earthcode.com), and it''s been great. It handled a front-page digg a few weeks ago without blinking. However, I''m setting up a staging environment right now, and I''m getting what looks like three mongrel processes *all listening on the same port* for each mongrel

mongrel_rails cluster::start doesn''t seem to pay attention to whether or not the processes exist or not. If you run it twice, the first set of processes are created, then then second run will overwrite the log/{pidfiles} files with the new process numbers. Problem is that the second group of processes are gone, since the first ones had the port open. I''d think that the right

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

First off: Our clusters are LVS balanced Apache 2.2.3 + mod_proxy_balancer + gem mongrel 0.3.13.3 / mongrel_cluster 0.2 + memcached / gem memcache_client + gem rails 1.1.6 on debian boxen, and a pgcluster backend. On 2 of our deployed clusters, we are getting the "spinning mongrel" problem. As the clusters are very low volume right now, it takes days to collect a spinner, making it

Hi all... Hopefully this is the last prelease. If people on non-linux systems could post back any problems with cluster::status, I''d appreciate it. Install with: gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ Note: This is only an update to mongrel_cluster and not Mongrel or other gems. Details about what''s new (if you missed the first

Just a quick note for a few new features/fixes available on the Mongrel pre-release and a new document that covers nearly all the big features and configurations for Mongrel. First, the document is http://mongrel.rubyforge.org/docs/howto.html and it covers: * All the start command options including the fresh -G option to generate a config for -C. * The format and usage of the MIME type file (-m

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

Hey Zed! When I do... $ mongrel_rails start --version it outputs: Version 1.8.4 I assume that''s not correct ;). (Looks like my Ruby version.) Joe -- Posted via http://www.ruby-forum.com/.

First off, a big thank you to Zed and the development team for mongrel and mongrel cluster. I''ve deployed it for two apps (through an apache 2.2 proxy) and it''s amazing how much snappier everything is. Previously we were using lighttpd and lighttpd-fastcgi proxying through apache 2.0, which was turning into a hassle for lots of reasons, most notably the ruby fcgi

I am migrating from mongrel_rails in development mode to production mode. I have a number of debugging statements based on "puts" in my code that emit info that I see scroll by when mongrel_rails is not daemonized and running in development mode. In daemonized production mode what happens to the output from these statements? I have looked into all the logs, and while I see the

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

Hello, I''ve install ror/mongrel etc, etc on a linux server (rhes). As i''m not root, all package startinf from ruby have been install into ~/gconf/usr ruby-1.8.6 and all of this gem package: -r-xr--r-- 1 dimnce dba 168448 Aug 9 14:53 rails-1.2.3.gem -r-xr--r-- 1 dimnce dba 84480 Aug 9 14:56 rake-0.7.3.gem -r-xr--r-- 1 dimnce dba 217088

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

I ma trying to get this upload working, http://mongrel.rubyforge.org/docs/upload_progress.html, ....after starting from the command line, mongrel_rails start -d -p 3001 -S config/mongrel_upload_progress.conf I get this eror in the browser, NameError uninitialized constant UploadProgressRailsController RAILS_ROOT: /usr/opt/tomcat/workspace/upload/config/.. Application Trace | Framework Trace