similar to: 503 Errors While Cluster Is Still Active

I''m trying to jump on the TDD/BDD bandwagon, but am having trouble understanding how i should mock my user. The user has a habtm relationship to a roles model (acl_system2 plugin), but I''m not sure how to tell rspec about a model. My code: describe UsersController do integrate_views before(:each) do @user = mock_model(User)

Hello Mongrels, Mongrel 1.1 is out with fullblown JRuby support, some reorganization, and some bugfixes. Also, Mongrel_cluster has been updated to 1.0.4. Go subscribe to the all-new news feed, because we probably won''t announce to the list anymore: http://mongrel.rubyforge.org/rss.xml Thanks Evan, and the Mongrel Team -- Evan Weaver Cloudburst, LLC

64bit Intel 8 CPU server Windows 2003 Server Service set to run as LocalSystem, doesn''t work as user account either The error we see is: "Service failed to start in a timely..." Which I have seen in the past email trails as working The app works from mongrel_rails start and from mongrel_service console -N servicename -p 3000 -c c:\rails_apps\appname -e production We upgraded

I''m using a cluster of mongrels behind an apache 1.3 proxy pass. I''ve been passing the request to pen, which in turn balances the cluster of mongrels. Now, I''d like to be able to use a different server to send the static files created by the rails application, so I tried to replace pen with nginx. Everything seems to work fine except the environment variable REMOTE_ADDR.

In May I had problem with mongrels suddenly consuming huge cpu resources for a minute or two and then returning to normal (load average spikes up to 3.8and then back down to a regular 0.2 over the course of 5 minutes, then again 1/2 hour later. or 4 hours later, no predictable rhythm). I posted to Litespeed forums because I thought the problem was there but didn''t get far. And a week

I''m trying to figure out a possible memory leak problem I have in my application. I''ve tested both with mongrel and webrick and the problem remains. So I think it''s not a mongrel problem, but I''m posting here to see if anybody can help me. The RAILS application is quite simple, no special plugins ( no RMagick that has the memory problem ),

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

Hi all, My environment is ruby-1.8.4, rails 1.2.2, mongrel 1.0.1, linux 2.6. Now, i have a problem on memory leaks with mongrel. My site is running 5 mongrel processes on a 2G RAM machine, the memory of each process grows from about 20M to about 250M, but it never recover to the initial 20M, so i had to restart the mongrel processes once per day. The load is about 1M hits per day. Waiting for

While I could figure this out, I''m asking here first to see if anyone has already dealt with/created this. I''m running a mongrel cluster, running 4 mongrels on ports 8001-4. I''m using capistrano to deploy. And I''d like to use monit to check to make sure everything is running nice. I''d like to have monit restart only single mongrels if they fail, and

Hi Y''all, Just a quick note announce an update to mongrel_cluster. Changes: - ''mongrel_rails cluster::restart'' now calls ''mongrel_rails stop'' and ''mongrel_rails start''. ''cluster::restart'' now accepts the ''force'' argument instead of ''soft''. - Added ''.conf'' as

Which web server does mongrel fair best with? -Ron

Hello all, I have mongrel service 0.3.2 running on Win2003 64-bit, special thanks to Luis for getting that running. You are a great asset! I am trying to figure out exactly what rights are needed by the account that is running the service. It works if I give it a domain account with local admin privileges, but it doesn''t work if I give it a domain account without local admin. I was

Greetings - I dug around a bit and I couldn''t find a definitive answer to this question, apologies if it''s been covered before. A box running a apache 2.2 -> mongrel cluster for a rails app got power cycled at my ISP. Unfortunately monit couldn''t start the mongrel processes because the pid files were still there. Here is my monit config (for each mongrel

I was able to find some information about this in the list archives, but it ended with a possible patch being submitted for Mongrel. I tried to follow a few of the instructions, but I''m still kind of stuck, since I''m not sure if what I''m seeing is the proper results. I have an application running on a cluster of mongrel servers, which is behind pen, which in turn is

I''m using god* to monitor my mongrels. God looks at pid files to know the status of the cluster. It seems as though mongrel does not write a pid file until it has loaded the entire rails/project environment, which in my case, takes upwards of 90 seconds. Meanwhile, god is freaking out because it thinks that there aren''t mongrels running, and it tries to start them. Thankfully I

Hi all, I''ve been having problems with the apache 2.2-mod_proxy_balancer- mongrel setup. My setup is: CentOS 4.3 apache 2.2.3 (compiled from source) with mod_proxy_balancer mysql 4.1 ruby 1.8.4 mongrel 0.3.14 (I know I need to update but I think this problem is independent of the mongrel version) mongrel_cluster 0.2.0 rails_machine 0.1.1 I have apache setup as per Coda''s

I currently run a handfull of sites on a MediaTemple VPS - which is blazing fast and very cheap for what I get. BUT installing rails and mysql v4 was a major pain in my ass, along with other things. I''m considering switching to a Textdrive business hosting plan but wanted to get some feedback from list members first. I pay about $200 a month quarterly for my MediaTemple service.

Hey folks, I''m falling behind in my Mongrel duties and seriously need to recruit an enterprising individual to take on the patch queue and help push out a new release with some minor fixes. The goal would be to just get patches that are currently languishing, pull them together, put them in the source, write some tests to try them, and then one slight design change. If this works out

I''m confused. Wasn''t threading fixed in 1.8.6, negating the need for fastthread? Why is fastthread still a requirement of Mongrel? Just curious. :)

Hi All, I''m hosting with MediaTemple who are currently using 0.3.3 of mongrel on their GridServer. My rails app has an image upload facility whereby if you upload a large image (e.g. 5Mb) mongrel crashes. I''ve requested an upgrade to the latest version of mongrel but don''t believe that''s going to happen too soon. I''m not getting too much