similar to: 0.3.12.1 Quick Bug Fix Pre-Release

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

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

For some users, request.remote_ip always return nil. According to the RAILS''s help: REMOTE_ADDR is the standard but will fail if the user is behind a proxy. HTTP_CLIENT_IP and/or HTTP_X_FORWARDED_FOR are set by proxies so check for these before falling back to REMOTE_ADDR. HTTP_X_FORWARDED_FOR may be a comma- delimited list in the case of multiple chained proxies; the first is the

Hi, we''re seeing a really weird problem in our production environment. "Connection: Keep-Alive\r\n" is being pre-pended to the RAW_POST_DATA, which makes requests error out. This bug is seen infrequently and *seems* to be browser-related, although I can''t reproduce it using the browser reported in HTTP_USER_AGENT. Set up is a apache 2.2 -> hardware load balancer

Hi, we''re seeing a really weird problem in our production environment. "Connection: Keep-Alive\r\n" is being pre-pended to the RAW_POST_DATA, which makes requests error out. This bug is seen infrequently and *seems* to be browser-related, although I can''t reproduce it using the browser reported in HTTP_USER_AGENT. Set up is a hardware load balancer (NetScaler)

Hello Everyone, Mongrel is due for a 0.3.12 release which will feature some pretty insane goodies for everyone. There''s talk of IOWA support, lots of speed improvements (including sendfile support), a great Configurator which makes configuring Mongrel a snap (especially for framework implementers), and a ton of debugging stuff. WARNING This is a pre-release announcement for the

Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File

Hi, When I go to my homepage all is well, however when the Pingdom bot arrives (every few seconds!), it throws the following error: ActionController::RenderError occurred in home#index: You called render with invalid options : available [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:808:in `render_with_no_layout'' My index action doesn''t call render, it

Hi, what is the preferd way to configure/start mongrel? [ ] with Mongrel::Configurator => HttpServer [ ] @var = HttpServer.new(...) @var.run I ask because the only debug methode i have found was in Mongrel::Configurator ;-) @Zed: are you also subscribed on nitro list?! regards Alex

I''m having a problem where the DRb server seems to be disappearing (crashing?) and I don''t know how to track down the cause or work around the problem. Unfortunately I haven''t found a way to reproduce the problem, but it seems to happen fairly often (maybe once a day). Other then that ferret seems to be working well. I can''t seem to find any trace of the

Hello Everyone, Mongrel is due for a 0.3.12 release which will feature some pretty insane goodies for everyone. There''s talk of IOWA support, lots of speed improvements (including sendfile support), a great Configurator which makes configuring Mongrel a snap (especially for framework implementers), and a ton of debugging stuff. WARNING This is a pre-release announcement for the

Hi All, I am setting up puppetmaster with nginx and passenger and separating the Puppetmaster primary CA server. I have 3 host loadbalancer01 - Nginx doing LB on IP address and also running puppetmaster with passenger under 127.0.0.1 (port 8140). primaryca - Puppetmaster Primary CA pclient - Puppet Client The did the following steps: On Primary CA server: ---------------------------- cd

Hi Folks, I''d love for everyone to grab the 0.3.12 pre-release gems from http://mongrel.rubyforge.org/releases/ and tell me if their stuff breaks. You can get it with a simple: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ This release features the following goodies: * The -n and -t options to mongrel_rails start have changed in meaning to be the maximum number

On the server [root@bangvmpllDA02 logs]# ruby -v ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [root@bangvmpllDA02 logs]# puppet --version 3.0.1 and [root@bangvmpllDA02 logs]# service nginx configtest nginx: the configuration file /apps/nginx/nginx.conf syntax is ok nginx: configuration file /apps/nginx/nginx.conf test is successful [root@bangvmpllDA02 logs]# service nginx status

This patch adds the support of multiple transports in the VSOCK core. With the multi-transports support, we can use vsock with nested VMs (using also different hypervisors) loading both guest->host and host->guest transports at the same time. Major changes: - vsock core module can be loaded regardless of the transports - vsock_core_init() and vsock_core_exit() are renamed to

This patch adds the support of multiple transports in the VSOCK core. With the multi-transports support, we can use vsock with nested VMs (using also different hypervisors) loading both guest->host and host->guest transports at the same time. Major changes: - vsock core module can be loaded interdependently of the transports - each 'struct virtio_transport' has a new feature fields

Hello all, new convert to Mongrel here and am trying to get things going. Right now I can start mongrel up just fine and it seems to work great, but I''m trying to use the nifty console I heard about and can''t seem to get it going. `mongrel_rails console` Cannot run the console script: unititialized constant RailsConfigurator Any ideas? I just installed everything yesterday

IPv4 addresses started looking very ugly the first time I got IPv6 working on bogomips.org. In case somebody else can''t stand how IPv4-mapped-IPv6 addresses look, the workaround is to use two listeners and ensure the IPv6 one is ipv6only. Unicorn itself supports IPv6, too, but nobody uses/needs it. I''ll add :ipv6only support shortly (probably tomorrow). >From

As a preparation to support multiple transports, this patch adds the 'transport' member at the 'struct vsock_sock'. This new field is initialized during the creation in the __vsock_create() function. This patch also renames the global 'transport' pointer to 'transport_single', since for now we're only supporting a single transport registered at run-time.

As a preparation to support multiple transports, this patch adds the 'transport' member at the 'struct vsock_sock'. This new field is initialized during the creation in the __vsock_create() function. This patch also renames the global 'transport' pointer to 'transport_single', since for now we're only supporting a single transport registered at run-time.