similar to: Website down - Mongrel Log file issue...

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 want to deploy RoR site''s (Intranet) for small offices/businesses that will get light traffic (estimating at max about 40 hits per minute at peak times). Lots of AJAX going on more than anything (update checks to the DB - Postgresql). I''d rather not use Lighttd, Apache, etc. as I want to have a streamlined install that is very easy for the end users. The catch is I

Our Mephisto install kills Mongrels and causes Apache to pound the CPU. This started when we moved to Apache+mod_proxy_balancer+Mongrel. Here''s what we know: The following things are working OK, except when used in the combination listed above: mongrel, mongrel_rails, MySQL, Apache, mod_proxy_balancer. We believe these are all OK because we moved five other Rails apps to this

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

Hi, I have had trouble with mongrel freezing after a period of inactivity. Following the advice from the mongrel FAQ, I added: ActiveRecord::Base.verification_timeout = 14400 to my environment.rb file. Unfortunately, that registered a mongrel error: "uninitialized constant ActiveRecord (NameError)" How do I overcome this one? I tried: require ActiveRecord::Base but that registered

> From: "Roy" <roy@xxx.lt> > > I want to set interface to promisc mode and do all routing with iptables. > Is it somehow possible? as I see now kernel do not pass everything to > ipables. > > Basicaly I want to ignore ethernet addess and use only ip for routing. > > I suppose this may require writting special kernel driver or it > is possible > in

http://visualwx.altervista.org/ A visual builder for wxWindows that purports to support Ruby. I''ll play with this some and see if I can design projects that work with wxRuby2. Roy

What do you think about adding a shebang line to the samples so they can be launched on linux/mac like you can on windows? Roy

I decided to try my hand at hacking SWIG and successfully produced a patch that fixes the error I demonstrated. I''m not -positive- it''s correct for all cases but I''ll re-run my version of SWIG over the library and see how things turn out. Roy

I think it''s time to get me onto the project at rubyforge so I can subscribe to the bug tracker. As we move forwards with more maintenance oriented tasks it will be helpful to be able to patch directly to SVN. For now, I''ll keep submitting patches to the list. Roy

How''d we get listed on the top page of projects for Ruby? (See right side below ''Top Ruby Projects'') :) Roy

Hello Everyone, This is an ultra quick announce for a bug fix release to Mongrel. It corrects a small change in the HTTP parser that causes an error when people use multi-part forms in a certain way. The fix is literally 4 characters changed in the parser specification. Everyone should update to this release and let me know if their forms act really weird. I''ve tested various upload

I am considering upgrading to either Mongrel 1.1.1 or 1.0.4, and Mongrel-cluster to 1.0.5. Are there any gotchas or issues I need to be aware of? Also where can I find the release notes for the various releases? (The ones I found seem very sparse). Thanks, Brian -------------- next part -------------- An HTML attachment was scrubbed... URL:

SWIG 1.3.29 isn''t going to cut it for us. We''ll have to wait until 1.3.30, unless I can hack together a nasty workaround for a problem with the object tracking. It seem that each SWIG module gets its own hash for tracking objects. This means that, for example, you create a find dialog (in FindReplaceDialog.cpp) events you get from it (from FindDialogEvent.cpp)

Hello, I''m a noobie to Rails and even more to mongrel. I have an issue with one server that I''ve installed mongrel. Its a Fedora Core 5 box, and it is having problems loading the Oracle OCI8 libraries. However, this only occurs when I use mongrel_cluster, or mongrel with out the - d switch. I have no problem using the library from the commandline and with Webrick or

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,

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

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

I''m proud to announce the official Mongrel certification program: http://mongrel.rubyforge.org/certified.html Move quick, seats are filling fast for the RubyConf courses. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.