similar to: Mongrel woes fixed

Hi list, I''m seeing a couple of issues with Mongrel. I''m running FreeBSD 6.1 and have previously been told that there are known conflicts between this and Mongrel, yet I hope these issues will be resolved with time. I''m overloading Mongrel with httperf on my local workstation. Mongrel is started directly with the mongrel_rails command and there is only one mongrel

I''m going to make a change to how Mongrel is versioned to help out folks packaging it and tracking it as a pre-release. Previously I just did whatever was simplest, but now I''m going to do a slightly different approach. This is open for comment and suggestions. Here''s the new rules: 1) There are only official and pre-releases. This doesn''t change. 2) The

I''m running a site that gets ~30k to 40k page hits per day. In the last 4 days my mongrel processes have been jumping into high CPU usage a couple of times a day to the point where my site becomes unresponsive (database on a diff machine with no load). The only way for me to resolve the problem and reduce load on the machine is to delete my rails cache directory (I have plenty of space

Hi all, We use mongrel behind apache (using mod_proxy_balancer) to run an internal app for our business. Lately we''ve been seeing frequent errors from some of our mongrel processes. [Sun Dec 16 08:48:47 2007] [error] [client <CLIENT1>] (70007)The timeout specified has expired: proxy: error reading status line from remote server 127.0.0.1, referer:

Hi, I''ve got to active project both running on the last Apache 2.2 and on Mongrel 0.3.13.3. One is running perfectly, the other gets (always on the same pages, but not after each request, it seems to be random) a ProxyError every now and then which leads to the mongrel process being called to die and subsequently slowing down the whole web site. I have to restart the mongrel

I''m trying to run a single worker that could perform a periodic task for a given user. >From a controller, I imagine something like: def start_job MiddleMan.ask_work(:worker => :foo_worker, :worker_method => :perform_task, :data => { :user_id = current_user.id }) end def check_job @status = MiddleMan.ask_status(:worker => :foo_worker)[current_user.id] end

Hello Everyone, We''re hard at work getting the hot new win32 service Luis wrote out and ready for production. We''re hoping to have that included in the 1.0 RC1 release we make very soon. This pre-release is just to make sure that we didn''t step on any toes. Install it with: $ gem install fastthread --source=http://mongrel.rubyforge.org/releases $ gem install

Hi guys, I''ve finally managed to get my server up and running with mongrel_cluster and all that jazz. My rails app works fine, but when I try to access my svn repos as I was doing before everything was setup rail is giving me a 404. What can I add to my httpd.conf to prevent this? Here''s a snip from my httpd.conf relating to the domain: ---HTTPD.CONF---------------------------

Hi to everybody, This my first post on the list. I''m a newby of mongrel & rails, I''ve deployed my first project and everything seems to work fine, the only problem I have is the following: After about 1 or 2 days of the mongrel_rails daemon running the mongrel.pid in the log directory disappears, the mongrel process is still there running but doesn''t respond

Hi list, I''m having some issues getting backgroundrb to play nice with more than one mongrel. When I run my app on a single mongrel instance it works fine. I have two different problems show up in my backgrounrb_server.log. The top of the backtrace is shown here: 20070130-12:03:03 (92473) failed to find slave socket - (RuntimeError) 20070130-12:03:03 (92473)

Hi everybody, May be somebody has a clue, why I get these errors below, while trying to migrate. Any help is very appreciated! Greetinx Rafael I was trying to experiment a litte bit with redMine (www.redmine.org). But I can only install it locally. On a system with already a mongrel_cluster running, I get strange errors, already while trying to start the migration rake db:migrate

Is this the behavior that supposedly indicates a problem with a particular action? Mongrel in development mode randomly hangs on random actions. Further requests cause USR1 logs like: Mon Sep 18 13:04:03 PDT 2006: 0 threads sync_waiting for /, 2 still active in mongrel. Mon Sep 18 13:07:52 PDT 2006: 1 threads sync_waiting for /public/stylesheets/table.css, 3 still active in mongrel. Mon Sep 18

I have a really long series of queries (import from other database*) that takes about 2 or 3 minutes. I wanted to spawn a thread and put the job there, but there seems to be some problems with active record and threads: (this is what I found after googling) Thread.abort_on_exception = true => true 100.times do Thread.new do Client.find(:first) end end this throws an exception... So

Can someone point me to a date/time validator or updater. I have an event start datetime and an event end datetime. I want to validate that the end datetime is after the start datetime. Figure there is some code or library out there already, if you know one, please forward it. Thank you! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

Morning Folks, As most of you know there were a few people who had the following three bugs: * CLOSE_WAIT: Lots of sockets in CLOSE_WAIT state. * 99% CPU: Mongrel''s getting "stuck" pegged at 99% CPU. * LEAK: Memory leak. I''ve successfully fixed these bugs or attributed them to one main cause: pstore. First, the memory leak was because of a bug in how the GC in Ruby

Hey folks, I ran into a few people at RubyConf who were having 99% CPU issues. Please contact me if you meet the following criteria: 1. You are running a production site. 2. You are experiencing 99% CPU errors. 3. This is frequent enough that you cannot manage it. Thank you. Please contact me off-list about it. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/

I suspect this has more to do with Ruby than Puppet, but I know little about Ruby and Google has failed me, so I''m asking here. I''m finally getting some of our older systems brought into Puppet. I installed it on several this morning without incident, but there are two (more or less identical RHEL 5.3 systems) that throw horrible errors. These systems did not have Puppet or Ruby

Hi, I have some problems in using filter. My filter functions need to have arguments, but filter functions take only symbol that refer to function name. Consider the following code: class BlogController < ApplicationController before_filter :authorize For instance, authorize need arguments. So how can I pass arguments to filter function? Any helps always appreciate.

Sorry if this has been asked before; it seems like a simple problem. I have a controller called ItemController which displays information about specific items to a user on various pages. The routing looks like "items/:item/:action". Is there any way to automatically look up the :item in the items table (it''s just an ID). I tried: before_filter { @current_item =

- ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] - puppet-2.7.19-1.el5 I''m facing with the following error when starting puppet agent: **`puppet agent --server=puppetmaster.domain.com --no-daemonize --verbose --debug`** debug: Failed to load library ''selinux'' for feature ''selinux'' debug: Puppet::Type::User::ProviderDirectoryservice: