similar to: FAILSAFE preventing errors from displaying?

I''m trying to use the exception notifier plugin and I''m getting this error message: NoMethodError (undefined method `respond_to'' for #<Adm::PeriodController:0xb74c9804>): /vendor/plugins/exception_notification/lib/exception_notifiable.rb:64:in `render_500'' /vendor/plugins/exception_notification/lib/exception_notifiable.rb:76:in

I un-commented the following in my environments.rb file config.plugins = [ :all, :exception_notification, :ssl_requirement] but I get the following errors: in `ensure_all_registered_plugins_are_loaded!'': Could not locate the following plugins: exception_notification and ssl_requirement (LoadError) from /Users/mitch/.gem/ruby/1.8/gems/rails-2.3.2/lib/rails/plugin/loader.rb:44:in

I''ve recently run into a problem with one of my applications that refuses to send emails using ActionMailer. Looking at the log, it become obvious what''s happening, the system is looking for templates with underscores at the end. Notice the exception_notification_ . For example: ActionView::ActionViewError (No rhtml, rxml, rjs or delegate template found for

Hi everyone, So, I''ve got exception_notification working now, but not in development mode on localhost. In my ApplicationController, I''ve added: local_addresses.clear Shouldn''t that be enough? Thank you! Sean

Hi. I am using rails 2.3.5 I just installed exception_notification 2.3.3.0 using ''sudo gem install exception_notification'' I have add config.gem "exception_notification" in environment.rb and ''include ExceptionNotification::Notifiable'' in application_controller.rb Now I am trying it out in development environment. It seems to catch my exception

Hey guys, This is the final list of the new maintainers of each plugin. We need two more things to do: First please the owners of the repos add the rest of the maintainers. Second I will add a note on each rails/plugin mentioning this repos updates. So from now on, if someone else is interested in helping/contributing please send a message to the appropriate repo owner. verification

folks. I have dev.domain.org and qa.domain.org. I have two copies of same rails application on the two diff subdomains. When an error happens only dev.* exception_notification sends email. For qa.* I get the RuntimeError. Not the 500.html file. Donnow what''s happening. I am on Site5, FastCGI, Apache 1.33 Thx ajay -- Posted via http://www.ruby-forum.com/.

Hi all, I installed the exception_notification plugin via ''script/plugin install'', and when configure it and try to run it, I get: NameError uninitialized constant ExceptionNotifiable This error occured while loading the following files: application.rb exception_notifiable.rb In my application.rb, I added this: include ExceptionNotifiable And in my development

Today I worked on adding email exception notification to some ancillary background processes for a Rails app. Since I was already using Jamis'' exception notification plugin to notify me of errors in controllers for the web app, I figured that the path of least resistance was to try to figure out how to hook it into the daemon code. At first it looked easy. I just needed to

Exception Notifier seems to have ceased working for some reason. I thought perhaps a change in edge rails was to blame, but I rolled back to 4900 and the problem was still there. The problem is that it generates an error in the _session.rhtml partial. It looks as if a method in the PP class is bombing. It says wrong number of argument (1 for 0), but there is no method on that line with

I installed the exception notifier via: /script/plugin install -x exception_notification It resides in the vendor/exception_notification directory (as advertised). I''ve configured environment.rb with the following: ExceptionNotifier.exception_recipients = %w(blakemiller-uBzjpPW2m0pBDgjK7y7TUQ@public.gmane.org) ExceptionNotifier.sender_address = %("Application Error"

Hi, I have two questions re the Exception Notifier plugin (i.e. which you install via "ruby script/plugin install exception_notification") Q1 - In it''s current setup (where it uses /public/500.html) is it possible to remove the "Status: 500 Internal Server Error Content-Type: text/html" text which seems to mysteriously get place at the top of the page? Q2 -

During our last week of Ferret / aaf usage (also our first week of Ferret / aaf usage), I have received 8 messages stating that our app encountered a Ferret::QueryParser::QueryParseException. For instance: A Ferret::QueryParser::QueryParseException occurred in foo#search: Error occurred in src/q_parser.y:279 - yyerror couldn''t parse query "com -- 404". Error message

problem: rails 2.3.2 is not generating config.action_controller.session_store = :active_record_store in environment.rb this is the code in environment.rb --------------------------------------------------------------------------- # Be sure to restart your server when you modify this file # Specifies gem version of Rails to use when vendor/rails is not present RAILS_GEM_VERSION =

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages when link training fails.

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages when link training fails.

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages when link training fails.

From: Ben Skeggs <bskeggs at redhat.com> [ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages when link training fails.

I have some clients that run centos6 and I need to have users be able to access the "failsafe terminal" from the login screen. The old options (from 4/5) for choosing your session aren't present. I've googled a bit on this but don't seem to be using a good search string as most of the hits have nothing to do with this and the rest aren't helpful. So, just wondering

For the mailing list archive and for anyone else interested. A few years ago we needed to automatically run a second AGI if the first AGI failed i.e. a "failsafe" setup. Mainly because I'm not a very good programmer. 8-| The code below is very similar to what we use in production. This code is also at http://pastebin.com/LBaLhdfJ for a while. "sm" stands for Switch