4
0

FAQ 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293
  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 (nagios-plugins 1.3.0-alpha1) 1.11
  13. Note that this string include both the assigned package release
  14. name and the CVS-generated revision for the individual plugin.
  15. Authors should strictly adhere to this format. All bug reports
  16. and help requests should reference this information.
  17. Q: What information do I need to include when asking for help or
  18. submitting a bug report?
  19. A: At a minimum, the output from 'uname -a' and the version string
  20. from '<plugin_name> -V' and, of course, a description of the
  21. problem and any solution/patch.
  22. Q: I'm using Redhat Linux (or some other RPM-based distribution).
  23. Which packages should I install?
  24. A: The package nagios-plugins-<version>.<arch>.rpm contains only
  25. those plugins that should work on any POSIX compliant system. In
  26. other words, you should be able to install this package on your
  27. system, no matter what else is or in not installed.
  28. However, most of us have more complex systems than barebones
  29. POSIX. We tried creating a variety of separate packages so
  30. each dependency could be installed cleanly, but many people
  31. found that this resulted in too many packages. So in the end,
  32. all the non-POSIX plugins were folded into one RPM
  33. (nagios-plugins-<version>.<arch>.rpm). Most people will need to
  34. use RPM's '--nodeps' option to install this package.
  35. Q: My system uses the .deb package format. What packages should I
  36. install?
  37. A: We strive for cooperation between all packagers and developers.
  38. The answers for .deb are the same as for RPM, after changing the
  39. package name suffixes accordingly.
  40. Q: I prefer to build my own RPMs. Do I need to install all of the
  41. various dependencies?
  42. A: Beginning with the 1.2.9-1 release, you may run
  43. rpm --define 'custom 1' -ta nagios-plugins-<release>.tar.gz
  44. In prior releases, you must unpack the tarball and build the
  45. RPM using nagios-custom.spec with 'rpm -ba'.
  46. Q: I get an error like
  47. Warning: Return code of 127 for check of service 'PING' on host 'anyhost' was out of bounds.
  48. when I run Nagios. (Often check_ping runs just fine on the
  49. command line).
  50. A: Commonly, system administrators will make security as tight as
  51. possible on the monitoring system. Sometimes this includes OS
  52. options or hardening scripts that prevent unprivileged users from
  53. running the ping command. Nagios runs with no more privileges
  54. than 'nobody' -- check to be sure that the nagios user can
  55. actually run check ping. (This can also happen with other binaries
  56. executed by nagios, but ping seems to be far and away the biggest
  57. offender.)
  58. Q: I have a plugin to offer. What can I do?
  59. A: You can make it available on NagiosExchange (http://nagiosexchange.org)
  60. where other people can find it for use.
  61. You can also get feedback on improving the plugin via the
  62. nagiosplug-devel@lists.sourceforge.net mailing list.