search

schubergphilis / Check_Nexenta

Nagios plugin to monitor Nexenta systems.
Apache License 2.0
5 stars 12 forks source link

API error occured #2

Closed dangul closed 10 years ago

dangul commented 11 years ago

Hi, our monitor system getting error after a upgrade to NexentaStor 3.1.5. We getting following error sometimes:

CRITICAL: API error occured: {u'message': u'Cannot introspect object com.nexenta.nms(/Root/Folder): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.'}

Could it be a bug ?

Thanks Daniel

brennmiddag commented 11 years ago

Hi Daniel,

That error occurs sometimes when the NMS does not respond. This happened in older versions of NexentaStor as well. One of the things I did is disable the reporters (setup reporter disable). Since you have proper monitoring these reporters add little value, and when a report is running the NMS sometimes hangs for multiple minutes.

I will also try to catch this particulair message in the error handling code, and report a "nms unavailable" warning instead (maybe with a counter, since you do want a critical if this goes on for more then 5 minutes or so).

Regards,

Brenn

dangul commented 11 years ago

Ok, thanks... Could you implement that "nms unvailable" within a custom value (say 5 min) it would be really great! Thanks for answer!

//Daniel

dangul commented 11 years ago

Hi, is it possible to implement a timeout value to the plugin ?

//Daniel

brennmiddag commented 10 years ago

Added a nms_retry value which can be set trough the config file. Defaults to 2 (as set since Nov 18 2013 after your initial request. forgot to post feedback back then).