search for: signalexception

...ith the way exceptions are caught and re-raised. In AbstractAdapter.log (connection_adapters/abstract_adapter.rb:144), Exception is rescued and reraised as an ActiveRecord::StatementInvalid exception. While in most cases I''m sure this is fine, Exception includes things like SystemExit and SignalException, which have nothing to do with invalid SQL. If I''m executing a statement when I send a TERM signal to the process (or call exit(0) when I trap it), if I catch StatementInvalid and deal with it somehow my script is going to continue running. I just noticed in r8484 the other thing I was go...

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

...ve and continue on to the next job in the queue if any particular job hits an unexpected exception. So we take the approach of wrapping our job invocations in a ''rescue Exception'' block and re-raising (allowing the process to die) in the case where the exception is a SystemExit or SignalException. So the AR approach of rescuing and re-raising as a StatementInvalid breaks this approach and leaves us in a situation where we have to do resort to less reliable methods of inspecting the rescued exceptions, like parsing the exception message. It also leads to confusing behavior where you sometime...

...ass --signal to the start-stop-daemon, which defaults to TERM. Dashboard runs out of webrick by default, which catches and ignores TERM, but will respond to INT and stop sanely. Currently, running ''service puppet-dashboard stop'' returns [2012-03-27 10:24:17] ERROR SignalException: SIGTERM /usr/lib/ruby/1.8/webrick/server.rb:91:in `select'' and then waits for the retry timeout, at which point start-stop-daemon SIGKILLs the ruby process. If --signal is set to INT in the init script, running ''service puppet-dashboard stop'' returns...

I need to be able to restart my server based on a specific database change. I''ve been trying a call to system("script/process/reaper -a graceful -d dispatch.fcgi") but that raises a transaction error which rolls back the save. I wasn''t aware that after_save would rollback. That''s potentially useful but pretty much not right now. Here''s my code: def

...on the list, the appropriate next debugging step is to send a SIGUSR1 signal to the spinning mongrel to get it to spit out what it thinks it is currently running. All we get from this is the following: /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in `join'': SIGUSR1 (SignalException) from /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in `join'' from /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in `join'' from /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:136:in `run'' from /usr/lib/ruby/gems/1.8/...

I am running a RoR application on Apache 1.3/RedHat 7.3/MySQL 3.1.23 (Old versions I know, but upgrading to latest versions are not practical for a number of reasons). There are 5 RoR FastCGI processes configured using FastCgiServer. What I am finding is that, after a while, some of the FastCGI processes seem to ''hang''. They no longer process requests, and the only way to

...ass --signal to the start-stop-daemon, which defaults to TERM. Dashboard runs out of webrick by default, which catches and ignores TERM, but will respond to INT and stop sanely. Currently, running ''service puppet-dashboard stop'' returns [2012-03-27 10:24:17] ERROR SignalException: SIGTERM /usr/lib/ruby/1.8/webrick/server.rb:91:in `select'' and then waits for the retry timeout, at which point start-stop-daemon SIGKILLs the ruby process. If --signal is set to INT in the init script, running ''service puppet-dashboard stop'' returns...