similar to: Mongrel Issue... Site shutting down...

I am new to Mongrel. We have a website that was created by someone using Ruby. The problem we are having is that the mongrel log file is shutting the site down when the log file gets to 1mb. Is there a way to configure the log file to cycle at a given size? What are my options to keep the site running? Thanks for your help!! Roy -------------- next part -------------- An HTML

I have a website that is running Mongrel that is CONSTANTLY going down. There seems to be no rhyme or reason... There must be something in the way the site was written. Is there a recommended Mongrel monitoring tool that will monitor our sites mongrel services and restart mongrel when the site goes down? The server is a UNIX machine... Thanks!! Roy -------------- next part

We have a site that is running Mongrel and is down. Below is the Mongrel log file information. The server is a Linux server with 2gb of RAM. EV1 (hosting site) says that since this is a Linux server that the RAM is cached and that there is plenty of free memory available. Can anyone make sense of this error and have some suggestion of options that I may take to correct this issue and get

I''m on a VPS running CentOS. I startup my server with: mongrel_rails start -d -p 3000 -e production and it runs for a while. But later I receive ''502 Bad Gateway'' errors implying my mongrel has crapped out. So in the console I do this: [prompt]# mongrel_rails start -d -p 3000 -e production ** !!! PID file log/mongrel.pid already exists. Mongrel could be running

I''m trying to deploy a rails app for development on slicehost and I can''t seem to get mongrel to work correctly. When I run mongrel_rails start I get: ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop

Finally! I''ve released Mongrel 0.3.13 OFFICIALLY to the public for better or worse. This release is pretty huge compared to previous releases. It''s got oodles of fixes, design improvements, hosting enhancements, win32 changes, and the release even works with the latest cygwin. Read all about it at http://mongrel.rubyforge.org/news.html GETTING 0.3.13 Most people do this:

"Another Mongrel release?! Is he insane?" Yeah, basically. This is yet another release of Mongrel that adds a bunch of little features people requested and I found were needed. This release is almost entirely targeted at Ruby on Rails folks as the majority of the changes went into the mongrel_rails runner. Get this release from the (correctly linked) site: *

Hello Everyone, Francois Simond inadvertently found a way to replicate a rare but deadly bug right as I was working up the official release of Mongrel 0.3.13. This bug only happened to a few people, but thanks to the wonderful fuzzing tool Apache Bench[1] he could replicate the slow select starvation people were seeing. TESTING This bug is now fixed in the current pre-release, and I''d

On 1/23/07, mongrel-users-request at rubyforge.org < mongrel-users-request at rubyforge.org> wrote: > > > Date: Mon, 22 Jan 2007 21:48:21 -0800 > From: "Zed A. Shaw" <zedshaw at zedshaw.com> > Subject: [Mongrel] [ANN] Mongrel 1.0.1 Officially Released > To: mongrel-users at rubyforge.org > Message-ID: <20070122214821.4804e941.zedshaw at zedshaw.com>

This release of Mongrel is coming at you with lots of very little but important features and fixes. The big highlights are: * Initial beginning of the plugin support that will let people write their own handlers and other things for Mongrel. * Timeout now works again but couldn?t find an alternative to the buggy Timeout class. * SwitchTower friendly signal handling for

Hi All/Zed, win32 : Is there an Installer/setup for Mongrel along with rails(1.1.6 security patches included) ? Thank you, BR, ~A -----Original Message----- From: Zed Shaw [mailto:zedshaw at zedshaw.com] Sent: Friday, August 11, 2006 11:59 AM To: mongrel-users at rubyforge.org Cc: ruby-talk ML; rails at lists.rubyonrails.org Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- PID Files

Hello All Mongrel Users, For the unintiated, Mongrel is a web server that runs Ruby web applications really fast. Read http://mongrel.rubyforge.org/ to get find out more about it. This is the Iron Mongrel release. It is the result of trying to trash Mongrel until it can''t move and then fixing anything that comes up. The work was done on EastMedia''s and VeriSign''s

Hi Luis, answers in CAPS. -----Original Message----- From: Luis Lavena [mailto:luislavena at gmail.com] Sent: Tuesday, December 26, 2006 5:39 PM To: mongrel-users at rubyforge.org Subject: [Mongrel] no log/mongrel.log file on win32, looking for suggestions... Hello Mongrels around the world! Been thinking a way to unify the issue I described in the subject. For those who aren''t

Just a quick note for a few new features/fixes available on the Mongrel pre-release and a new document that covers nearly all the big features and configurations for Mongrel. First, the document is http://mongrel.rubyforge.org/docs/howto.html and it covers: * All the start command options including the fresh -G option to generate a config for -C. * The format and usage of the MIME type file (-m

This might just have affected my particular setup but thought it might be worth noting for others. >gem -v 0.9.2 >gem list --local cgi_multipart_eof_fix (1.0.0) Fix an exploitable bug in CGI multipart parsing which affects Ruby <= 1.8.5. mongrel (1.0.1, 1.0, 0.3.20, 0.3.18, 0.3.13.4) A small fast HTTP library and server that runs Rails, Camping, Nitro and Iowa apps.

Hello Folks, This is the long awaited (like 2 weeks) 0.3.12 release of Mongrel. This release has received heavier testing than previous releases and supports a whole raft of improvements to existing functionality plus some new stuff. For those not clued in, Mongrel is a web server written in (mostly) Ruby. Check the funny dogs and read the docs about it at http://mongrel.rubyforge.org/. The

Hi Folks, This is another pre-release announcement with lots of goodies for people to test and play with. At this rate the 0.3.13 release may just turn into 0.4. GETTING IT Pretty simple, just gem install mongrel --source=http://mongrel.rubyforge.org/releases/ You can get more information at http://mongrel.rubyforge.org/ WHAT''S IN IT This release has lots of little things, mostly

Another fancy release with just a few little changes from yesterday: * Set-Cookie, Set-Cookie2, Warning, and WWW-Authenticate are allowed as duplicate headers. * mongrel_rails stop now has a --wait option to go with --force. It will wait for either the given timeout in SECONDS or the PID file to go away. If the PID file goes away it just exits. If the timeout happens then it does a kill -9 on

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

Hello Guys, Been testing fastthread (known on previous releases as optimized_locking) for soon to be released 0.3.18 mswin32 gems (official ones). Attached to this message is the ruby script I used for the test results shown on graphics [1] and [2] The idea of the script is simulate what Mongrel do with threads creating a simple workload for testing Ruby VM stability. [1] refers to normal,