Page 1 of 1
Configuration of check_aws_status - Warning
Posted: Tue Jul 26, 2016 1:53 pm
by sgiworks
Hello Team,
While configuration of check_aws_status plugin, I am getting following warning. Can you please help in the resolution.
Warning
(No output on stdout) stderr: /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- nokogiri (LoadError)
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /usr/local/nagios/libexec/check_aws_status.rb:4
Regards,
Swapnil
Re: Configuration of check_aws_status - Warning
Posted: Tue Jul 26, 2016 11:46 pm
by Box293
Have you tested the plugin from the command line before adding it to Nagios XI? If yes, did it work?
You may need to install some gems.
The script requires these:
Code: Select all
require 'rubygems'
require 'nokogiri'
require 'open-uri'
require 'pp'
This guide explains how:
http://guides.rubygems.org/rubygems-basics/
Re: Configuration of check_aws_status - Warning
Posted: Mon Oct 10, 2016 1:25 pm
by sgiworks
I have a new warning message, after amending the command to /usr/bin/python $USER1$/check_aws_status_feed.py
(No output on stdout) stderr: Traceback (most recent call last):
File "/usr/local/nagios/libexec/check_aws_status_feed.py", line 18, in <module>
import feedparser
ImportError: No module named feedparser
Re: Configuration of check_aws_status - Warning
Posted: Mon Oct 10, 2016 2:23 pm
by sgiworks
one more step further, managed to fix earlier issue by installing "sudo yum install python-pip"
now with a new UNKNOWN ERROR:
AWS UNKNOWN: Feed
http://status.aws.amazon.com/rss/ec2.rss could not be parsed. Check command options.
Note: I am trying with this plugin:
https://exchange.nagios.org/directory/P ... ge/details
Regards,
Swapnil
Re: Configuration of check_aws_status - Warning
Posted: Mon Oct 10, 2016 3:32 pm
by sgiworks
Don't worry, issue has been fixed. our DBA made some changes in the script and got it working.
All Set
Thanks,
Swapnil
Re: Configuration of check_aws_status - Warning
Posted: Mon Oct 10, 2016 3:58 pm
by dwhitfield
It sounds like this issue has been resolved. Is it okay if we lock this thread? Thanks for choosing the Nagios forums!