similar to: pid file info not working in config file

Hi there, I''m using Mongrel (0.3.13 prerelease, installed today) to serve up some Rails apps in production. Everything works fine if I give all the appropriate options on the command line, such as: $ mongrel_rails start -c /home/mcornick/rails/mcornick.org/current -P log/mongrel.pid -l log/mongrel.log -e production -d -a 127.0.0.1 -p 6833 So, having accomplished that, I thought it

upgraded to 0.3.13.4 this morning in order to correct the above titled problem but mongrel is still not writing the pid file when starting with a config file verified i am running 03.13.4 with --version if i run this command: mongrel_rails start -p 3000 -e production -d --user mongrel --group webdev mongrel DOES create the pid file if i run the same, and include -G config/mongrel.conf, the

Hi all, I''m trying to start Mongrel using a configuration file, but Mongrel complains: $ sudo mongrel_rails start --config /usr/local/www/xltester.com/config/mongrel.yml !!! Path to log file not valid: log/mongrel.log mongrel::start reported an error. Use mongrel_rails mongrel::start -h to get help. I''m using sudo above to replicate monit, not because I run Mongrel as root.

i posted some of these questions on the rails list, but thought that i should probably post them here instead. zed has already answered one of my questions, but i did have a couple more. 1) mongrel is not writing the pid file, which i have specified in the config file --- :cwd: /srv/www/railsapps/rftrack :includes: - mongrel :log_file: log/mongrel.log :config_script: :pid_file: log/mongrel.pid

I am running mongrel-0.3.13.1. Have used lighty and fcgi in the past, and I must say that apache-2.0.x proxying to mongrel is much nicer to deal with! I am having this problem, however. If I am in root''s homedirectory, and start mongrel with this command: --------- mongrel_rails start -a 127.0.0.1 -e production -c /home/www/rails/myapp -l log/mongrel.log --user mongrel --group mongrel

Can anyone tell me how to get x_send_file working with mongrel 1.1.1 and apache 2.2? I''ve installed the mod_xsendfile apache module from http://tn123.ath.cx/mod_xsendfile/ and it works fine serving content from a PHP script, but I can''t get it to work with my single Mongrel instance and ProxyPass. I''m using the following Apache configuration: <VirtualHost *:80>

Hello! hey, I''ve been writing this man page for mongrel_rails for some time and now I wanted the list to take a look at it and see if it''s good. After it''s ok, and if zed want to integrate it in mongrel (or any other distribution wants it), the debian note can be removed :D Manual Page: .TH MONGREL_RAILS 1 "2006-11-17" "Mongrel Rails" .SH NAME

I posted this to the rails list before by mistake, and only later realized that there is a specific mongrel list. Uff, I got lost. I had mongrel_cluster 0.1working fine, even with capistrano (my own hack). Then came mongrel_cluster 0.1.1 and I tried to set it up, but somehow I messed up things and nothing worked anymore. So here is what I did: on production machine: (debian linux, rails 1.1)

Hello! Run problems after upgrading to mongrel 1.0.3 from 1.0.1: # uname -sr FreeBSD 7.0-BETA1 # mongrel_rails start ** Starting Mongrel listening at :3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload

First off, apologies if this is addressed.. I didn''t find anyone having the same problem (which usually means the problem is me!) I''m running the standard command to start a Rails server, with additional custom mime YAML: mongrel_rails start -m /etc/mongrel_mime.yml Content of the /etc/mongrel_mime.yml is only a single line: .xml: text/xml However, the custom mime

According to the mongrel_cluster.yml file you provided, you''re starting only 14 mongrels, but in your proxy balancer config you have 30 mongrels listed on ports 21000 - 21029. In this scenario, if apache tries to proxy to any ports higher than 21014 then you''ll get a proxy error as a mongrel doesn''t exist on that port. Or am I missing something? -----Original

struct cpufreq_policy, including a cpumask_t member, gets copied in cpufreq_limit_change(), cpufreq_add_cpu(), set_cpufreq_gov(), and set_cpufreq_para(). Make the member a cpumask_var_t, thus reducing the amount of data needing copying (particularly with large NR_CPUS). Signed-off-by: Jan Beulich <jbeulich@suse.com> --- 2011-09-20.orig/xen/arch/x86/acpi/cpufreq/cpufreq.c 2011-10-12

I am using mongrel and mongrel_cluster to serve a rails site. The site requires several environment variables to be set. I am thinking about using the :config_script option and writing a script that sets the required environment variables. Is this a good solution or does anyone have any other suggestions? Thanks for your help. jeremy

I''ve moved an application that was running under apache2/fcgi to apache2/mongrel(mod_proxy). under the original setup i had no problems with sessions. now under mongrel, the users are experiencing application errors. after looking at the logs, I am seeing that a piece of code that relies on a session variable is what is causing the error. It seems that the session variable no longer

I''m reading a book "Beginning Ruby on Rails" I made an table, and tried to make an Model class. But it doesn''t work. I made the table as below. mysql> show columns from books ; +-------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra |

Hello Everyone, This is the official 0.3.13.3 release of Mongrel. Mongrel is now released under the *Ruby license* instead of the LGPL. I''m hoping this increases the adoption of Mongrel even further and hopefully I can start pushing to get Mongrel included in Ruby directly. INSTALL As usual, you install it with your friendly gem install method of choice: gem install mongrel Or

This is for when you pass mongrel 0 for the port and the OS assigns an open one. Corey --- mongrel-1.0.1/lib/mongrel.rb 2007-08-05 15:29:59.000000000 -0700 +++ mongrel-1.0.1/lib/mongrel.rb.zero_port_fix 2007-08-05 15:29:23.000000000 -0700 @@ -560,7 +560,7 @@ @socket = TCPServer.new(host, port) @classifier = URIClassifier.new @host = host - @port = port

Remove unused and pointless bits from mpparse.c (and other files where they are related to it). Of what remains, move whatever possible into .init.*, and some data items into .data.read_mostly. Signed-off-by: Jan Beulich <jbeulich@novell.com> --- 2011-03-09.orig/xen/arch/x86/acpi/boot.c +++ 2011-03-09/xen/arch/x86/acpi/boot.c @@ -177,7 +177,8 @@ acpi_parse_x2apic(struct acpi_subtable_h

Rails instances themselves are almost always single-threaded, whereas Mongrel, and it''s acceptor, are multithreaded. In a situation with long-running Rails pages this presents a problem for mod_proxy_balancer. If num_processors is greater than 1 ( default: 950 ), then Mongrel will gladly accept incoming requests and queue them if its rails instance is currently busy. So even

Hello all. I too found out that I sometimes have some action that can take up to 10 seconds in my rails application. I''ve read all arguments Zed made about polling/and inbox strategies, and I think I just can''t work around my feeling that a "wrong" request that takes up too much time should be able to lock subsequent requests in mongrels queue. That''s what