similar to: evented mongrel question - maybe for Kirk

Sorry if this is the wrong place to ask, but when I run mongrel evented using swiftiply and then send it the USR2 signal to restart it, it dies. Without eventing, USR2 restarts mongrel as expected. Anyone else seen this? Here''s a dump: $ EVENT=1 mongrel_rails start -d -P /tmp/m.pid -p 4321 Using Evented Mongrel ** Ruby version is up-to-date; cgi_multipart_eof_fix was not loaded $ kill

Just a quick announcement that an update to swiftiplied_mongrel and evented_mongrel which fixes the incompatibility with Mongrels > 1.0.1 has been released. http://swiftiply.swiftcore.org Let me know if you have any problems. Kirk Haines

Hi, was wondering if anyone else had a similar problem and knows why or a solution. basically my mongrels seems to work fine. i am running three clusters all which are monitored by monit. monit has the ability to restart a mongrel if it doesn''t pass a port connection test. so the problem is that after some time. aprox. 6hrs. to 20hrs. after clusters are started, the mongrels get

Does someone know how to tell mongrel_rails to read the public/system/maintenance.html file? -- Posted via http://www.ruby-forum.com/.

Hi folks. Using mongrel_rails and the mongrel_cluster capistrano recipes, I often encounter a situation where some of the mongrel processes don''t die in time to be restarted. The output of capistrano will tell me something like "mongrel on port 8001 is already up", but that''s only because capistrano/mongrel_rails failed to take it down in the first place. The solution

Hi, Im a newbie to ruby and rails. I installed mongrel using the command: sudo gem install mongrel --include-dependencies When i try to start mongrel with mongrel_rails start -d, its throwing the same error as it did to you: /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `gem_original_require'': no such file to load -- http11 (LoadError) from

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,

Hi, I''ve a few problems with my rails app at the minute, causing mongrels in a cluster to die, while I debug I''ve setup monit to keep the site running. Problem is, whenever monit starts one of my mongrels via mongrel_rails cluster::start --only 8000 --clean -C /url/to/yml/file I get the following in my log/mongrel.log: ** Mongrel available at 127.0.0.1:8000 ** Writing PID file

I want to restart my Mongrels from crontab periodically to free up memory. I tried this: [admin at mudcrapce ~]$ mongrel_rails cluster::restart -C /var/www/apps/mudcrapce/current/config/mongrel_cluster.yml Restarting 5 Mongrel servers... mongrel_rails restart -P log/mongrel.3040.pid !!! PID file log/mongrel.3040.pid does not exist. Not running? mongrel::restart reported an error. Use

I''m running two sets of mongrels using mongrel 1.1.4, one for production one for staging. When executing ''ps'' from a linux shell, the production mongrels report as expected, however the staging processes are listed as [ruby 18]. The result seems to be that mongrel_rails cannot stop the staging processes because it doesn''t recognize [ruby18] as a mongrel

hi all I''m running background tasks using BJ 1.0.1 (gem version). On some requests, the tasks are executed as expected. On others, I get the following error: RuntimeError (no bj found in ["/u/apps/igniter/releases/20080408205801/ script", "/bin", "/usr/bin", "/sbin", "/usr/sbin"]): when it runs, it runs fine but does anyone know what

Hi One of the two mongrel processes has died in the middle of the night four times in the past 9 days, and I need help debugging this. Each time the symptoms are the same: * Each time I can restart the process via cap -a restart_app. * Before the restart, there is nothing unusual in production.log or mongrel.log. * During the restart, about 100 repetitions of an error message are generated in

I''m playing with the mongrel clustering, and am having a problem getting 2 mongrels to start up reliably. This should be a pretty simple cluster, with just 2 instances running. My mongrel config (mongrel_cluster.yml) looks like: cwd: /deployment/installed/myapp/current log_file: log/mongrel.log port: "8000" environment: production address: 127.0.0.1 pid_file:

Hi -- I have been reading documentation and googling around to find the correct way to do this but I have found many ways that seem to not work, or the documentation makes no reference to. I am using mongrel cluster with 10 mongrels for each server. Recently I installed monit but which lead me to find the correct way to start/stop mongrel instances one pid at a time. I am assuming one pid at a

Hello Mongrels, Building on the last messages about Fastthread, can we get a detailed survey of the different ways people are deploying their applications? It will help with near-future Mongrel development. Please include the following things: * Framework, if any (Camping, Merb, Rails, Nitro, Ramaze, IOWA, Rack...) * Mongrel version * Mongrel handlers used (rails, dirhandler, camping,

Hello, sorry if creating a dupe... I''m trying to download files to authenticated users in my app. I''ve set up x_send_file. All seems to be correct to me, however when I try to download any file, I get a 1-byte long file downloaded. I am getting this already in development - so no Apache, no lighthttpd, just a mongrel_rails start in the root of my app. Any help/hint would be

Just a quick question to those of you using merb and sequel or datamapper. How do you setup your merb app? For example: merb -X off -c 5, then run mod_proxy_balancer or nginx to load balance between the 5 (or whatever #) of merb nodes? merb -X off -d, then simply use something like proxypass merb -c 5, keep the mutex lock and cluster it haproxy, swiftiply, evented mongrel...... What

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! I run a mongrel cluster with 6 mongrels in it. I want to monitor them individually for process hangs (and then restart them) and this is the solution I came up with: Here''s my configuration file for monit (/usr/local/etc/monitrc): [snipped relevant bits] ------ #check lighttpd process check process lighttpd with pidfile /var/run/lighttpd.pid start program =

I''ve done a clean install of Ubuntu 7.04 server in 2 different machines and everytime I reboot the machine or manually run /etc/ init.d/mongrel_cluster restart/start the mongrels won''t start correctly. I have to manually start them by using mongrel_rails cluster::start from each app folder. I''ve been searching around and it looks like mongrel has some problems