similar to: log and pid file problems when using a config file w/ -C

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

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''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''ve been trying to store the pid file option for Mongrel and it seems that I can only set it from the command line options, not from the configuration file. I''m using Mongrel gem version 0.3.13.3. Has anyone else experiend something like this? Here''s an example of a config file I generated using the -G option. The address and port options work fine but the pid file

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

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

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

Hey y''all: mongrel_cluster provides management tools for running Mongrel behind a reverse-proxy/load balancer. It is an extraction from Rails Machine, a deployment service and Ruby library that simplifies Rails application deployment. This release fixes bugs and adds a Capistrano task library. Changes: -changed pid file format to include port -only write configuration options

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

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>

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, Thank you for your development of Mongrel, great job. :) I am using mongrel_cluster, but I have a problem where my rails application name includes a "." such as mydomain.com, which causes an error when generating the PID file for mongrel. I have attached below a diff of the current working copy in the trunk and the changes I made to overcome this problem. I kept your

Hi, I have an application which is dying horrible deaths (i.e. segmentation faults) in mid-flight, in production... And of course, I should fix it. But while I find and fix the bugs, I found something I think should be different - I can work on submitting a patch, as it is quite simple, but I might be losing something on my rationale. When Mongrel segfaults, it does not -obviously- get to clean

The full description of this bug is here: https://bugzilla.redhat.com/show_bug.cgi?id=838592 and the effect it has on OpenStack is described here: https://bugzilla.redhat.com/show_bug.cgi?id=835466#c9 Rich.

Hi ! I''m using Mongrel 1.0.1 with --pid and --user/--group. The PID files are correctly owned by the user/group, but their permissions is 0666. Is that normal ? Shouldn''t it be something like 0664 ? Just curious to know if I''m wrong. Configurator has this (line 77): # Writes the PID file but only if we''re on windows. def write_pid_file if

Hi everyone, I am going crazy over here! :) I just want to be able to use --clean with my mongrel_rails cluster::start command. I''ve upgraded to mongrel_cluster 1.0.1.1 and mongrel_rails 1.0.1. my config file is in /etc/mongrel_rails/config.yml and contains: --- log_file: log/mongrel.log port: 8000 pid_file: /var/run/mongrel_cluster/mongrel.pid servers: 2 address: 127.0.0.1 environment:

Hello all... I know its been a while since the last one, but a new prerelease is available with a gratuitous increase in version numbers! gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ This one has some new features in it that need to be tested on all unix platforms. Please run --clean and cluster::status on every *nix you can find. I run linux so the rest are up

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

http://bugzilla.mindrot.org/show_bug.cgi?id=606 Summary: sshd [-t] should warn when cannot create pid file Product: Portable OpenSSH Version: -current Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org