search for: steinfeld

Hi all, My mongrel server (1.0.3), with a very low usage, is taking more than 10% of cpu usage all the time (no background tasks were defined by me). This is very annoying and it is preventing me from being able to thing about good cluster configuration. Any idea on why this is happening? cheers and regards, Danilo -------------- next part -------------- An HTML attachment was scrubbed... URL:

...5 cycles then restart if loadavg(5min) greater than 10 for 8 cycles then restart if 3 restarts within 5 cycles then timeout Part of my confusion is if I should use mongrel_rails cluster::start or mongrel_rails start, Is there a difference? Any suggestions is really appreciated. -- Michael Steinfeld Linux Admin/Developer AIM: mikesteinfeld

...production servers: 10 group: wwwapp user: wwwapp I was using the monit script to start - "/etc/init.d/monit start" I have also tried "/usr/bin/monit -g www start all" My mongrel run as the user/group "wwwapp" any advice would really be appreciated. -- Michael Steinfeld Linux Admin/Developer AIM: mikesteinfeld GTALK: mikeisgreat at gmail.com

I just got the fire to clean up how our app is deployed and upgrading mongrel. Currently, our app is being deployed in a user''s home directory. This has caused some problems regards to user/group permissions... We decided we were going to move everything to /var/www/app which led me to the whole general layout of our deployment and some questions. ENV Ruby 1.8.5p12 Rails 1.2.3 Mongrel

Hi, I am a bit confused about what is the fastest way to run a rails application. I have seen examples which use Apache, mongrel, lighthttpd, fastcgi etc. Is there a correct way to do it? Or is it just a personal choice? Thanks, Keith --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk"

Hi all, I am out of my head here... I have a 3 node cluster with 10 mongrels running on each. When I deploy, I break all the mongrels every time. I have tried just about everything. I can restart my mongrels without a hitch manually, it''s only when I use cap deploy. Maybe I am missing something here... so if I can get some help it would be appreciated. The errors are the typical mongrel

I am not sure when it exactly occurred but I have 2 servers I am about to migrate to apache+mongrel from lighty+fastcgi oddly, both my servers seemed to have died at the same time everytime I restart within a 24 hr period ( I don''t know when, my logs don''t show it ). Can someone please point me in the direction of what I need to do to trace the cause of this. Or what you would

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

Okay, well the OpenBSD install/chroot guide is a good starting point.... Anyhow, Can someone shed some light on these particular error messages? [Sat Dec 17 18:42:34 2005] [notice] Initializing etag from /var/www/logs/etag-state [Sat Dec 17 18:42:34 2005] [notice] chrooted in /var/www [Sat Dec 17 18:42:34 2005] [notice] changed to uid 1, gid 1 [Sat Dec 17 18:42:34 2005] [notice] Apache/1.3.29

As a follow up from my previous post, I am pondering some changes to my env. I read that with AR I should change the verification timeout to be lower than the MySQL db Interactive_timeout. Now, I have done some performancing tuning to mysql in LAMP env''s but not RoR. MySQL typical set the default interactive_timeout to 8hrs (28800) this has bitten me a few times with sleeping processess

At the bottom there are two broken links under OS Repos "Hieraki and RForum". Don''t know if anyone cares or not... -- -mike --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

So it seems this account was cracked/hacked. Some of you may have received some bullshit email about buying a TV. Please ignore that message as it was sent from whoever hacked this account. It''s already been rectified. I apologize for the inconvenience.. damn hackers. for those that care the senders IP is 115.49.95.201 mike

Most of my machines have apache+mongrel running but the mongrels are using the localhost. In my production environment, I have 4 boxes. I have setup 2 http servers ( apache 2.2.4 ) and 2 app servers. They are currently using lighttpd+fastcgi. Which I am changing this week. I want to get advice from you guys before I actually do this since this is my production env. I have installed apache on the