Skip to content

Instantly share code, notes, and snippets.

@ktheory
Created January 11, 2012 18:51
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ktheory/1596165 to your computer and use it in GitHub Desktop.
Save ktheory/1596165 to your computer and use it in GitHub Desktop.
chef log
[Wed, 11 Jan 2012 17:02:10 +0000] INFO: Processing service[nagios-nrpe-server] action enable (nagios::client line 63)
[Wed, 11 Jan 2012 17:02:10 +0000] INFO: Processing nagios_nrpecheck[check_load] action add (nagios::client line 69)
[Wed, 11 Jan 2012 17:02:10 +0000] INFO: Adding check_load to /etc/nagios/nrpe.d/
[Wed, 11 Jan 2012 17:02:10 +0000] INFO: Processing template[/etc/nagios/nrpe.d/check_load.cfg] action create (/var/chef/cache/cookbooks/nagios/providers/nrpecheck.rb line 23)
...
[Wed, 11 Jan 2012 17:02:10 +0000] INFO: template[/etc/nagios/nrpe.d/check_load.cfg] sending restart action to service[nagios-nrpe-server] (delayed)
[Wed, 11 Jan 2012 17:02:10 +0000] ERROR: Running exception handlers
[Wed, 11 Jan 2012 17:02:12 +0000] FATAL: Saving node information to /var/chef/cache/failed-run-data.json
[Wed, 11 Jan 2012 17:02:12 +0000] ERROR: Exception handlers complete
[Wed, 11 Jan 2012 17:02:12 +0000] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[Wed, 11 Jan 2012 17:02:12 +0000] FATAL: NoMethodError: undefined method `run_action' for "service[nagios-nrpe-server]":String
@rogernolan
Copy link

Hi, did you manage to solve this error, I'm seeing exactly the same.

@ktheory
Copy link
Author

ktheory commented Jan 25, 2012

Not really. I tried changing the nagios_nrpecheck to use the "old style" notification syntax recommended here: http://www.sharp-tools.net/archives/002187.html
Then this error seemed to happen less, but still happened sometimes. (I don't recall the particular conditions.)

Eventually I just stopped using the nagios_nrpecheck provider altogether; and wrote my own templates that notify nagios-nrpe-server.

@rogernolan
Copy link

yeah, I tried that fix too :-(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment