search for: mongrel_debug

Hello, I''ve install ror/mongrel etc, etc on a linux server (rhes). As i''m not root, all package startinf from ruby have been install into ~/gconf/usr ruby-1.8.6 and all of this gem package: -r-xr--r-- 1 dimnce dba 168448 Aug 9 14:53 rails-1.2.3.gem -r-xr--r-- 1 dimnce dba 84480 Aug 9 14:56 rake-0.7.3.gem -r-xr--r-- 1 dimnce dba 217088

Hi, Anyone succeeded in installing Mongrel on Sun Solaris? It looks like the installation is broken. I have started using Mongrel recently and not sure where to look when something is missing. First the file http11.so was not installed in /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib I''ve resolved that and when tried to start mongrel from the command line I received the

...ally_call_remote function so I ran mongrel with debug enabled Mongrel seg faults after a few minutes The mongrel filelog shows 5 files open when this happens. Same log files that are open all the time. Wed Dec 19 15:10:21 -0700 2007 FILES OPEN BEFORE REQUEST /calibration/ackAdjustDistance --- log/mongrel_debug/objects.log: 2 /home/scott/NetBeansProjects/webmonitor/config/../log/development.log: 1 log/mongrel_debug/rails.log: 1 log/mongrel_debug/files.log: 1 log/mongrel_debug/threads.log: 1 log/mongrel_debug/access.log: 1 There are 2 threads running Wed Dec 19 15:10:21 -0700 2007 REQUEST /calibration/ac...

Hi all, Ruby 1.8.4 Windows XP Pro / Solaris 10 Mongrel 0.3.12 Rails 1.1.2 I''ve got a fairly simple and straightforward layered dispatching web service setup for my Rails app. This simple xmlrpc script works fine with WEBrick, but chokes on Mongrel. Is there anything special I need to do to make web services work with Mongrel and Rails? Some Google searching indicates that there had

Hello, I have problem with Mongrel 0.3.14 on unix I can not use the "-B" (debug) with the "--prefix" flag the mongrel_debug/logs files are being created but never update. Do anyone have a work around for this ? Yves

Hello all, My Rails app is logging some rather strange requests: Processing StoreController#index (for ::1 at 2006-07-03 13:18:48) [GET] Session ID: ed5e2a0e5b4b9290835a969cdd749e6e Parameters: {"action"=>"index", "controller"=>"store"} Completed in 0.08174 (12 reqs/sec) | Rendering: 0.07951 (97%) | DB: 0.00000 (0%) | 200 OK [http://127.0.0.1/]

Hi all, few days ago mongrel start crashing on one of my sites, i upgraded to latest version (1.0.1) but problem still exists. When i try to load page in browser random elements are missing or page is blank (empty html). In mongrel.log i''m getting: Mon Oct 22 01:10:47 +0200 2007: ERROR: stream closed Mon Oct 22 01:10:47 +0200 2007: ERROR: closed stream Mon Oct 22 01:10:47 +0200 2007:

Hi All I am using version 0.3.13.3 and since there is no logging support for win32 application. I was wondering if it was possible to get any kind of logging at all. I have tried to these two options 1. Stream redirection using "mongrel_rails start -c C:/myspace/snapshot -p 4111 -t 70 -e production -P log/mongrel-1.pid > C:\temp\mongrel-1.log" The console print the output stream

Hi, I have Apache (2.2) setup to proxy requests through to Mongrel (0.3.12.4) for a Rails (1.1.2) application (on ruby 1.8.4). The setup is great, but I''m experiencing some nightly failures. I thought I''d post here before digging in too deeply, but it looks like Rails is going into lala land and Mongrel can''t recover... Seems like everything gets all backed up in

I just noticed something interesting (or not) about getting to my RoR app on the 2 browsers. I''ve tested it running Webrick or Mongrel_rails and get the same behavior. The app is at http://www.mydomain.com:myport#/app/list Specifying that complete URL works fine in both browsers. However in IE if you just specify www.mydomain.com:myport#/app/list I get page not found. In FF the URL

I''m trying to set up several different Rails apps on the same domain, each one running Mongrel. After reading all of the documentation, it''s fairly clear how to use subdomains - create several Apache virtual hosts, each of which has a different ProxyPass and ProxyPassReverse command to redirect from different ports (ie, 3000, 3100), and then have each Mongrel instance (or

Hi, Thanks Zed - this is very interesting. One item in particular caught my eye: Does anyone on this list have any comments or validation that Rails 1.2.1 is 2-4 times as slow as Rails 1.1.6? Topfunky provided a link that purports what looks like really horrible performance and memory characteristics for Rails 1.2.1, even v. 1.1.6:

I have been running a proxied mongrel-hosted app behind apache 2.0 (don''t need clustering) for several months, and loving it. In that instance, I am proxying the root of the virtual host to mongrel. I am now in a situation where I need to proxy a directory name to mongrel for a new application, and not having any success. I saw Zed''s mention of the --prefix option in 0.3.13.4,

I was playing a bit with Mongrel to test it out before using it in production, but I have an issue with Latin accented letters being all messed up. I''ve included the right content-type in the HTML and both Lighty +Fastcgi and Webrick have no problem with them. Any tips? Thanks, - michele

Hi there, Has anyone tried acts_as_ferret with Edge Rails and Mongrel? When I install the plugin to a project that has Edge Rails frozen, and the Mongrel gem installed, I can''t start the server. There''s no error, it just doesn''t start. I''ve used acts_as_ferret in the past with WEBrick, and stable Rails releases without a hitch. If I remove the

...a series of handlers on any URIs and they''ll be processed in order. This gives you an advanced and fast pipe-lined processing system and is already used to implement the extensive debugging support Mongrel has. * Debugging, Debugging, Debugging. Try the -B option and then look in the log/mongrel_debug logs. I''ll be beefing this up to insane usefulness for the 0.3.13 release. * Support for sendfile on FreeBSD, Linux, and Solaris if you install the ruby-sendfile (http://rubyforge.org/projects/ruby-sendfile) gem. This is experimental but already gives a 20% boost on static files. * Addit...

...a series of handlers on any URIs and they''ll be processed in order. This gives you an advanced and fast pipe-lined processing system and is already used to implement the extensive debugging support Mongrel has. * Debugging, Debugging, Debugging. Try the -B option and then look in the log/mongrel_debug logs. I''ll be beefing this up to insane usefulness for the 0.3.13 release. * Support for sendfile on FreeBSD, Linux, and Solaris if you install the ruby-sendfile (http://rubyforge.org/projects/ruby-sendfile) gem. This is experimental but already gives a 20% boost on static files. * Addit...

...ng is working correct. When i however copy the application to the Unix Box, start Mongrel and load the page i get an error in the mongrel.log file with following text: ** Changing group to "www". ** Changing user to "www". ** Installing debugging prefixed filters. Look in log/mongrel_debug for the files. ** 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 (without restart). It might not work well...

...Win32 since it uses services). * Reload works better and doesn''t break the restart. * More logging of the start-up process. * There is a wicked nice debugging framework that logs object counts, open files, and request params between each request. Try mongrel_rails start -B and look in log/mongrel_debug. * The Rails specific components are now in Mongrel::Rails modules. * More examples using the Mongrel::Configurator. * Dramatic speed improvements on FreeBSD, especially if you install the ruby18-nopthreads version. * Slight speed improvements on Mac OSX. OSX is like shoving a slug through a chees...

...four character fix. I hate that. THREAD DEBUGGING This release also adds a few things to help people debug their use of threads within their Ruby on Rails applications. When you run mongrel_rails with the -B (debugging) option Mongrel will report all active threads between each request to log/mongrel_debug/thread.log. If you see reports of Mongrel being overloaded, threads getting killed, or having to wait for Mongrel to shutdown then turn on debugging (-B) and look in this log. You most likely are doing something that keeps the thread from exiting. Mongrel also deals with dead threads much better....