similar to: Mongrel in development mode not reloading classes

I have RoR running and have configured RAGI (per the new tutorial provided at ETel http://www.snapvine.com/code/ragi) but I get this: --- user# script/server => Booting WEBrick... [2006-01-30 14:20:25] INFO RAGI::CallServer: default-handler= port=4573 [2006-01-30 14:20:25] INFO WEBrick 1.3.1 [2006-01-30 14:20:25] INFO ruby 1.8.2 (2004-12-25) [i586-linux] [2006-01-30 14:20:25] WARN TCPServer

Hi, I''m trying to make my Rails app auto-install my required gems, by invoking the gem installation in boot.rb. I''ll use the ActionMailer gem as an example: ... system "sudo gem install actionmailer --version=1.2.5 -y" ... Problem is that this fails on the first invocation of Mongrel - it can''t find the gem. However, if I kill and restart mongrel (with the

Hi all, I''ve a model class Toto in the model directory. I don''t understand why i have to restarts WebBrick to view changes i make in this class FYI : in the development. rb i desabled class cache with config.cache_classes = false Regards Luciano -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi All First of all - I would like to say Mongrel is fantastic! We are developing a hybrid solution incorporating a central server and local servers (which allows offline working) - with Webrick we were suffering from 500 (and other errors) that the switch to Mongrel has fixed. Since we are providing the local server as a download application we wanted to find a way to package up the code and

Sorry if this is the wrong place to ask, but when I run mongrel evented using swiftiply and then send it the USR2 signal to restart it, it dies. Without eventing, USR2 restarts mongrel as expected. Anyone else seen this? Here''s a dump: $ EVENT=1 mongrel_rails start -d -P /tmp/m.pid -p 4321 Using Evented Mongrel ** Ruby version is up-to-date; cgi_multipart_eof_fix was not loaded $ kill

Hi, I am using a railsapp to call an external app and print some barcode-labels. My problem is, after a while there seems to be a timeout. Then I need to stop the Mongrel-Server and restart it. Below you can see the error message, when i stop the server. Has somebody seen this before? Greetings, Oli C:\etikett>mongrel_rails start -d -e production ** WARNING: Win32 does not support daemon

Hi, I have some problem with mongrel server. While I am trying access http://localhost:3000, getting the following error message mongrel_rails start ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). **

Hello, I don''t know if this is really relevant anymore because a new version is about to be released it seems, however I''ve been trying to run mongrel 0.3.12.4 on a development server in development mode (simply with mongrel_rails start). I try to access the server and the first page (static file) loads, but then the server dies and I get this in the logs. I''m

I''m trying to deploy a rails app for development on slicehost and I can''t seem to get mongrel to work correctly. When I run mongrel_rails start I get: ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop

It appears that rails ''should'' reload controllers as they are modified. "As soon as a method is created or changed, it immediately is noticed and integrated into the current Rails system." http://www.linuxjournal.com/node/8433/print Do other peoples'' rails do that? Is this just me? If I understand correctly with each call it should load the file with the

Hello! Run problems after upgrading to mongrel 1.0.3 from 1.0.1: # uname -sr FreeBSD 7.0-BETA1 # mongrel_rails start ** Starting Mongrel listening at :3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload

Hi all, I have a problem with mongrel-1.1.2 running with Apache Apache/2.0.61 and MySQL 5.0.45 on FreeBSD 6.1. I''m developing my application with InstantRails that uses Mongrel and everything is working great. I have about 30 shops in a table. I also store the logo images (png files) in the table for each shop. Under Windows/InstantRails everything is working correct. When i however

Hi all, I''m getting a strange, intermittent Thread deadlock in production: deadlock 0x2a988d7008: sleep:F(3) - /opt/ruby/default/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723 CPU usage spikes to a full core and Apache 502''s on requests that got handed to that particular listener each time. I tried attaching with gdb, and gdb twisted itself into a knot. Anyone have

I would like to write AGI script in Ruby Would anybody please show me right direction.. Thanks

I seem to have a (recent) problem with mongrel on NetBSD. I''m running a development release of NetBSD (called NetBSD-current 4.99.34). When I start mongrel, it listens on the IPv6 wildcard address, but not on the IPv4 wildcard: => Booting Mongrel (use ''script/server webrick'' to force WEBrick) => Rails application starting on http://0.0.0.0:3000 => Call with

I am running Rails 2.1.0 on an XP box. In development I have config.cache_classes = false. But...when I mod my controller code it does not pick up the change. This happens in Webrick and Mongrel (1.1.5) Ideas? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this

Hello, I have released Ruby Asterisk Gateway Interface (ruby-agi) v0.0.2b. Any feedback, bug report, suggession, feature request is most welcome. ruby-agi homepage: http://www.rubyforge.org/projects/ruby-agi/ Download ruby-agi v0.0.2b here: http://rubyforge.org/frs/download.php/5965/ruby-agi_v0.0.2b.tgz Thanks, Mohammad Khan

This patch: - adds --prefix option to service::install in mongrel-service plugin - fixes bug with config values merging in the service - enables gemplugins in the service. Questions: - why the load_plugins command was commented out? It seems working for me. - why bin/mongrel_rails_service and bin/mongrel_rails_svc still in the main package? - a lot of code is duplicated in both versions

Hi everyone. Zed, thanks for Mongrel. I''ve been running mongrel on my WiFi cafe site (http://wifi.earthcode.com), and it''s been great. It handled a front-page digg a few weeks ago without blinking. However, I''m setting up a staging environment right now, and I''m getting what looks like three mongrel processes *all listening on the same port* for each mongrel

I am having different results between when I start mongrel with script/ server and with mongrel_rails start. When I run script/server to boot mongrel everything runs fine, no errors. When I run mongrel_rails start I get the following errors - verified the problem on a fresh app and on two different environments (mac and yes, windows server 2008). The actual line of fault changes but the problem