search for: atzen

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

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

...ngrel for production on FreeBSD and if necessary I am willing to spend some time trying to resolve these issues, but I will probably need some help if I am to succeed. So please let me know if I can provide any further information or give me a pointer to where to go from here. -- Cheers, - Jacob Atzen

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---------------------------

...le to make Mongrel crash. Finally I have provided a debug patch for the Sync library which simply adds a lot of debug output to STDERR. I believe it might be of use in future performance optimizations as there seems to be happening a lot of work managing the queued up clients. -- Cheers, - Jacob Atzen -------------- next part -------------- Index: lib/mongrel.rb =================================================================== --- lib/mongrel.rb (revision 353) +++ lib/mongrel.rb (working copy) @@ -687,7 +687,6 @@ reap_dead_workers("max processors") else...

...01502/vendor/plugins/backgroundrb/server/lib/backgroundrb/middleman.rb:199:in `new_worker'' As can be seen it seems to stem from a call to new_worker. Though the issue also seems to prop up when requesting an existing worker. Any ideas on where I should start to look? -- Thanks, - Jacob Atzen

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 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

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

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, 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

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

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 =

Hi all, I''m trying to setup a puppet installation on FreeBSD. So far I have only one puppetmaster and one puppetclient, both with 0.24.4 from FreeBSD ports. On the master I''ve defined a couple of classes including this: class apache22 { package { apache22: ensure => installed, source => "http://x.x.x.x/packages/apache-2.2.9_5.tbz", provider =>

Hi, In Agile Web Development with Rails section on Transactions (p 381) there are two main examples. 1) making changes in two records in the same database table 2) making changes in two records each in a different *database* I want to do what is in between: changes in two records each in a different table of the same database. Suppose they are apples and oranges tables. How do I write this?

I''ve been working through the book ''Beginning Ruby on Rails E-Commerce'' which is very heavy on Test Driven Development. As in, you have to write tests for scaffolding methods and validations and crap like that. And then they fail. And you KNOW its the test not the method. So you spend 2x the time writing a test that has to be adapted when requirements change. You

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! I''ve been following the new mongrel tuneup guide (a huge thanks for that btw) and here are my results. I''ve basically only gotten to the point where I''m tuning up 1 mongrel because I suspect I have a performance problem with my rails app. http://mongrel.rubyforge.org/docs/how_many_mongrels.html The first number is the 10s nconns and the second is the max req/s as

What''s a rule of thumb for guesstimating how many Mongrels to use in a cluster for an app? I have an app that gets about 5000 unique visitors per day. I figured I''d give it plenty of Mongrels -- twenty to be specific. After running out of memory and hitting the swap periodically, I scaled it back to five and it still seems to serve up visitors fine. So, is there some super-secret