similar to: exception logging

I''m setting up a Rails app for a client that uses Windows. I''m getting this error: c:/ruby/lib/ruby/gems/1.8/gems/mongrel-0.3.18/lib/mongrel/rails.rb: 32: uninitial ized constant Mongrel::HttpHandler (NameError) from c:/ruby/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:21:in `re quire'' from c:/ruby/lib/ruby/gems/1.8/gems/mongrel-0.3.18/bin/

Hello, So, I grabbed the mongrel_upload_progress code from subversion because I really need something similar for a project I am working on. Anyway, I installed the gem and can''t figure out a few things. 1) I''m not sure what Upload < GemPlugin::Plugin "/handlers" is for 2) How to call the Progress < GemPlugin::Plugin "/handlers" handler. While I

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 tried using the killall -USR1 mongrel_rails to check on a problem, and all I get is mongrel_rails: no process killed Nothing shows in the log. Any ideas? I''m using the latest pre-release, and a ''ps'' shows my cluster is running. Cheers, Brett

I tried to install Rails + Mongrel on CentOS4.3 64Bit (my provider only has the 64 Bit version available). I found out, that I have to install gcc and emacs-common and have to copy the *.h files of the ruby source into a certain directory (see below). But finally I get an error messag when I start mongrel and I have no idea how to solve that problem: wget

This on Ubuntu testing with the default ruby1.8 package, RubyForge current gems, mongrel...this look familiar to anyone?? andre@andre:~/rails_apps/depot$ mongrel_rails /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel/rails.rb:44: uninitialized constant Mongrel::HttpHandler (NameError) from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:21:in `require'' from

Hi, I just gave Mongrel a try on my Rails app. After running ''mongrel_rails start'' everything seems fine. Yet, when I start a request I get the following error message on the console: ERROR: You have a nil object when you didn''t expect it! The error occured while evaluating nil.readpartial That''s it. The application works fine with Webrick and

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''m not sure what''s happening so I''ll try and explain what I know. I am getting the error "Thu Aug 17 20:01:57 MDT 2006: BAD CLIENT (xx.xx.xx.xx): Invalid HTTP format, parsing fails." I''m running mongrel 0.3.13.4 from gem source, and running on a Macbook Pro. I am running rails in development mode and if I switch to running webrick, all requests

Sometime my mongrel server threads..would simply stop responding to the requests...and in the logs i get following error: Tue Sep 05 03:56:40 IST 2006: ERROR: Transport endpoint is not connected - getpeername(2) Tue Sep 05 03:59:21 IST 2006: ERROR: Transport endpoint is not connected - getpeername(2) Tue Sep 05 03:59:21 IST 2006: ERROR: Transport endpoint is not connected - getpeername(2) Tue Sep

I have seen several threads here and elsewhere about ferret and/or aaf causing seemingly random segfaults in mongrel. However, I didn''t see in any of these threads if a resolution was ever offered. I am currently experiencing this problem and I am keen to get a solution. I appreciate any update that anyone can give me. Best Regards, Danny -- Posted via http://www.ruby-forum.com/.

Hi, I am using Mongrel with my own XmlRpcHandler and I get sporadic "500" errors from Mongrel. The handler wraps around the xmlrpc/server module and I am pretty sure that the error is mine and neither in mongrel or xmlrpc/server. I catch all exceptions in my xmlrpc/server handler and do not send out 500 http answers from there. Thus, I expect the problem is in my handler.

I''m having no luck trying to daemonize mongrel running a camping server. When mongrel daemonizes, I get: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723:in `accept'': closed stream (IOError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' ... (This was after I disabled the unhandled exception catchall in the

Hello I''ve a client which send this request to a mongrel HTTPHandler : res=Net::HTTP.post_form(URI.parse(''http://localhost:3000/test''),{"a"=>1,"b"=>2}) But in the handler I can''t read the parameters one by one, I can read the entire String only : class Serveur class MyHandler < Mongrel::HttpHandler def process(req, resp)

Hi all, I''ve been having problems with the apache 2.2-mod_proxy_balancer- mongrel setup. My setup is: CentOS 4.3 apache 2.2.3 (compiled from source) with mod_proxy_balancer mysql 4.1 ruby 1.8.4 mongrel 0.3.14 (I know I need to update but I think this problem is independent of the mongrel version) mongrel_cluster 0.2.0 rails_machine 0.1.1 I have apache setup as per Coda''s

Hi all, I encounter timeout errors during file uploads in my Rails application. I think the problem may be in the Mongrel configuration. Here is my setup: * Load balancer (Cisco CSM, my provider''s Catalyst 6509) * Apache 2.2.3 with mod_proxy_balancer * Mongrel 0.3.13.3 * Rails 1.1.6 * Ruby 1.8.4 * MySQL 5.0.22 * file_column I host an application in which users may upload medium files

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

Hey all I am working with a technology standard (specific to the commercial print industry) by which each element within the workflow has bi- directional HTTP messaging. As each side needs a http server, I thought I could either: a) use a gem plugin to modify the behavior of mongrel b) subclass Mongrel::HttpHandler In short, its xml messaging between two points; each with a HTTP client

Hi, I''ve a few problems with my rails app at the minute, causing mongrels in a cluster to die, while I debug I''ve setup monit to keep the site running. Problem is, whenever monit starts one of my mongrels via mongrel_rails cluster::start --only 8000 --clean -C /url/to/yml/file I get the following in my log/mongrel.log: ** Mongrel available at 127.0.0.1:8000 ** Writing PID file

Hi mongrel-users, This is my first post, so I''m not sure if it''s been asked before, but I can''t find an answer anywhere. If I have one rails application running, one processor I''m running it on, and mongrel is multi-threaded, why should I have more than one mongrel running? Everyone seems to agree on 3-5 mongrels per rails app, but why? I must be