similar to: bug #4398

With the latest version of Mongrel, will Mongrel reopen log files when sent a HUP signal? I would like to do a log rotate, but would prefer not to restart the mongrel instances as monit is watching after them all. monit is great for restarting the individual instances, but I would prefer not to do a restart all through monit. I would be curious if this is advisable. -- ----- Christopher

Hi mongrel-herders, I''m just wondering what fellow railsers use to rotate their logs in an orderly fashion? I''d like to do something lightweight, i.e. (1) rename the logfile (2, optional) create a new empty logfile and (3) send a signal to each mongrel in the cluster and have them understand it''s time to reopen their log file handles. This is what I do with apache and

Installed gcc and make and the default friends that they bring along, then did # sudo gem install mongrel and got the following... andre at andre:~$ sudo gem install mongrel Attempting local installation of ''mongrel'' Local gem file not found: mongrel*.gem Attempting remote installation of ''mongrel'' Select which gem to install for your platform (i486-linux) 1.

Alright, this time a small announce going out to *just* the mongrel list so I can get some early testing. There''s a new pre-release of 0.3.13.4 out that includes the win32 version of the gem. ** WIN32 USERS SHOULD INSTALL THIS AND TEST.*** ***** BUT NOT ON PRODUCTION SYSTEMS. ****** As usual, you install it with: sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/

Zed / List, On my workstation I''m running lighttpd 1.4.11 and mongrel 0.3.12.4. Here are my proxy settings: proxy.debug = 0 proxy.balance = "fair" proxy.server = ( "/RailsAppSample" => (( "host" => "127.0.0.1", "port" => 1337 ))) I can access http://localhost/ (default lighty welcome page) and http://localhost:1337/

It''s gotta be Rascal. There''s no fixing Victoria - that''s a re-write from the ground up. And Jake a recipe for disaster; Class Jake < Bat include Pig attr_accessor :one_eye . . end That pig ''ll never fly. ---------- Forwarded message ---------- From: mongrel-users-request at rubyforge.org < mongrel-users-request at rubyforge.org> Date:

Mongrel''s tempfile generation on win32 is broken meaning large files can''t be uploaded. On line 198 of mongrel.rb (0.13.3) HttpRequest#initialize the tempfile function is called:       if clen &gt; Const::MAX_BODY         @body = Tempfile.new(self.class.name)         @body.binmode       else Unfortunately this also includes the module name as the example shows:

On the Mongrel FAQ forum, Josh Wehner was having problems with cygwin (don''t know if he fixed it). http://rubyforge.org/forum/forum.php?thread_id=6978&forum_id=5450 Due that, I manage to install cygwin, ruby and rails on my humble little computer, it compiled worked ok (taste like *nix, so I felt a bit off-road running this). Anyway, tried to pass test for mongrel, and still get 1

Hi all, I''m getting a strange, intermittent Thread deadlock in production: deadlock 0x2a988d7008: sleep:F(3) - /opt/ruby/default/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723 CPU usage spikes to a full core and Apache 502''s on requests that got handed to that particular listener each time. I tried attaching with gdb, and gdb twisted itself into a knot. Anyone have

I did a spike in my sandbox to make sure I understood how to do file uploads using CGI and there seems to be a problem with Mongrel. WEBrick doesn''t display the problem, but I can reproduce it everytime with Mongrel. I''d really appreciate it if someone would try out the code below and see if they see the same thing. The browser behavior is: - under IE6, a Page Not Found error

I wrote an x-sendfile thing for the railshandler to get mongrel to catch the response header and stream out files from an application I''m writing but I''m pretty sure that zed said he''d built in x-sendfile somewhere already. I couldn''t find it, could someone lead me to it? Does mongrel work with SSL? If not is anyone interested in having someone write in SSL

I got some advice from Rick last night and started coding this handler to allow for time-based secure downloading similar to mod_secdownload that lighttpd offers. I got most of the code in the handler worked out and packaged into a gem but am still having the following problems: 1) I have a configuration script as follows require ''mongrel'' config = Mongrel::Configurator.new

--- lib/unicorn/configurator.rb | 2 +- lib/unicorn/http_server.rb | 6 +++++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/lib/unicorn/configurator.rb b/lib/unicorn/configurator.rb index 89cbf5c..c9b6816 100644 --- a/lib/unicorn/configurator.rb +++ b/lib/unicorn/configurator.rb @@ -559,7 +559,7 @@ private def set_path(var, path) #:nodoc: case path - when

I just attempted to install Mongrel on Windows. I''m not going to run it as a service, so I thought I''d select the ruby flavor (option 1). See error message below. Q: Is the ruby flavor not supported on Windows? If so, it would be useful to update the website with this info. Thanks, Mike. K:\rails\apps\helloworld>gem install mongrel Attempting local installation of

Thread #<Thread:0xb7ac9dd4 sleep> is too old, killing. Error calling Dispatcher.dispatch #<Mongrel::StopServer: Timed out thread.> I''m getting lockups I''ve seen this too: Shutdown waited 1 for 9 requests, could take 10 seconds.^MThread #<Thread:0xb7815fa8 sleep> is too old, killing. Error calling Dispatcher.dispatch #<Mongrel::StopServer: Timed out

Hi. I have mongrel 1.0.1 running a really simple application and found to lock up (rarely, but still). There''s nothing in the logs, it just stops responding. When I mongrel_rails stop it, I get lots of entries like: Waiting for 3 requests to finish, could take 60 seconds /usr/lib64/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:675:in `process''

Dear all, In the past, I''ve been successfully using mongrel_cluster following codahale setup [1]. Now I updated mongrel_cluster through gem to 1.0.2, and my previosly worked config is not working anymore. I report below a snip of one of logfile, it seems to me it is a missing gem problems, but this sounds strange to me, because my config was ok before the upgrade. Does

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

Hey all: When using capistrano and/or manually restarting mongrel clusters we encounter errors when restarting that states: ** !!! PID file log/mongrel.8010.pid already exists. Mongrel could be running already. Check your log/mongrel.log for errors. ** !!! Exiting with error. You must stop mongrel and clear the .pid before I''ll attempt a start. ** !!! PID file log/mongrel.8011.pid

Hello, I don''t know if this is really relevant anymore because a new version is about to be released it seems, however I''ve been trying to run mongrel 0.3.12.4 on a development server in development mode (simply with mongrel_rails start). I try to access the server and the first page (static file) loads, but then the server dies and I get this in the logs. I''m