FAQ 1.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455
  1. Frequently Asked Questions
  2. **************************
  3. Q: Where can I find documentation for <insert name> plugin?
  4. A: All plugins that comply with minimal development guideline for
  5. this project include internal documentation. The documentation
  6. can be read executing plugin with the -h or --help option. If
  7. the '-h' option does not work, that is a bug.
  8. Q: What version of <insert name> plugin am I running?
  9. A: All plugins that comply with minimal development guideline for
  10. this project include detailed version information. When executed
  11. with the '-V' option, a version string will be printed:
  12. check_radius v1.4.16 (monitoring-plugins 1.4.16)
  13. All bug reports and help requests should reference this
  14. information.
  15. Q: What information do I need to include when asking for help or
  16. submitting a bug report?
  17. A: At a minimum, the output from 'uname -a' and the version string
  18. from '<plugin_name> -V' and, of course, a description of the
  19. problem and any solution/patch.
  20. Q: I get an error like
  21. Warning: Return code of 127 for check of service 'PING' on host 'anyhost' was out of bounds.
  22. when I run Nagios. (Often check_ping runs just fine on the
  23. command line).
  24. A: Commonly, system administrators will make security as tight as
  25. possible on the monitoring system. Sometimes this includes OS
  26. options or hardening scripts that prevent unprivileged users from
  27. running the ping command. Nagios runs with no more privileges
  28. than 'nobody' -- check to be sure that the nagios user can
  29. actually run check ping. (This can also happen with other binaries
  30. executed by nagios, but ping seems to be far and away the biggest
  31. offender.)
  32. Q: I have a plugin to offer. What can I do?
  33. A: You can make it available on MonitoringExchange (http://monitoringexchange.org)
  34. where other people can find it for use.
  35. You can also get feedback on improving the plugin via the
  36. devel@monitoring-plugins.org mailing list.