similar to: restart - `exec'': Operation not supported

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"

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

Hi everyone, I''m having a problem starting rails on solaris. I have made the changes suggested in the joyeur article but it doesn''t make any difference. The error is below. Does anyone have any idea? /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in `register'': undefined method `resolve'' for nil:Mongrel::URIClassifier (NoMethodError)

Alright, it seems that I am having a bit of a problem with mongrel. My mongrel processes have been crashing pretty often and twice last night. I''m really not sure why, but I really need to fix it. I am running 0.3.13.3. Here is the mongrel.log file. Any ideas, things to look at, etc... is appreciated. Thanks, Carl PS, do all the broken pipe lines mean Mongrel is serving the static

I''m trying to get a rails app running with this configuration: Mongrel, Apache 2.2, mod_proxy load balancer and Rails 1.1.6 error I have a rails app on another server working with (apparantly) the same configuration and it runs fine so I''m stumped. I''m wondering if anyone has any insight into the error I have pasted below. It seems to be one of those errors that

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

Hi, On os x.3.9, with ruby 1.8.4 installed through darwinports and mongrel through gems, everything works until I restart: mongrel_rails restart adds the logs: ** USR2 signal received. ** Restarting with arguments: ruby /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails start -p 3001 -d /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails:134: in

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 list, I''m seeing a couple of issues with Mongrel. I''m running FreeBSD 6.1 and have previously been told that there are known conflicts between this and Mongrel, yet I hope these issues will be resolved with time. I''m overloading Mongrel with httperf on my local workstation. Mongrel is started directly with the mongrel_rails command and there is only one mongrel

Newbie question here: I''m hitting my rails app and killing mongrel. Any ideas? Here''s the error: /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:628:in `accept'': Software caused connection abort (Errno::ECONNABORTED) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in `join'' from

Hello all. Hope this doesn''t appear as spam... I am trying to run Mongrel on Win XP (SP2) for a web site (just one at the moment). For some reason it is giving me this error: E:\web\app2>mongrel_rails start -p 4001 -d ** WARNING: Win32 does not support daemon mode. ** Daemonized, any open files are closed. Look at log/mongrel.pid and log/mongr el.log for info. ** Starting Mongrel

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

Hi all, I encounter timeout errors during file uploads in my Rails application. I think the problem may be in the Mongrel configuration. Here is my setup: * Load balancer (Cisco CSM, my provider''s Catalyst 6509) * Apache 2.2.3 with mod_proxy_balancer * Mongrel 0.3.13.3 * Rails 1.1.6 * Ruby 1.8.4 * MySQL 5.0.22 * file_column I host an application in which users may upload medium files

Following errors are taken from monrgrel running in development mode. It complained routes.rb, no such file or directory and then sometimes i get application.rb, no such file or directory.Doesn''t seem correct to me. Though not so often, but even production servers throw these errors sometimes, and i have no special routes setup or something.Its pretty much default one, except few changes

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

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

I just created a test rails app, and am having very wierd issues with mongrel cluster. Here''s what I''m doing: rails test sudo chown -R mongrel:mongrel test cd test sudo mongrel_rails \ cluster::configure -e production \ -p 8000 -N 3 -a 127.0.0.1 --user mongrel \ --group mongrel It correctly writes the mongrel_cluster.yml file to the config directory. Now,

Hello world, I''m having some problems setting up a new Debian deployment box...just installed the rails stack, mongrel, etc... When I go to start mongrel I''m getting a weird error I can''t figure out. Some help please? -> mongrel_rails start ** Starting Mongrel listening at 0.0.0.0:3000

I''m setting up a Rails app for a client that uses Windows. I''m getting this error: c:/ruby/lib/ruby/gems/1.8/gems/mongrel-0.3.18/lib/mongrel/rails.rb: 32: uninitial ized constant Mongrel::HttpHandler (NameError) from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:21:in `re quire'' from c:/ruby/lib/ruby/gems/1.8/gems/mongrel-0.3.18/bin/

FYI: I don''t think this is a very well know. It seems that, on some operating systems, ActionMailer/SMTP crashes when it sends an email with only a ''.'' (aka a ''dot'' or a ''period''). Specifically, you get Net::SMTPSyntaxError (502 Error: command not implemented): Environment Details: $ uname -a Linux private1 2.6.15-26-server #1 SMP