summaryrefslogtreecommitdiffstats
path: root/FAQ
diff options
context:
space:
mode:
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ128
1 files changed, 67 insertions, 61 deletions
diff --git a/FAQ b/FAQ
index 370ac99..5ba948f 100644
--- a/FAQ
+++ b/FAQ
@@ -1,87 +1,93 @@
1Frequently Asked Questions 1Frequently Asked Questions
2************************** 2**************************
3 3
41. Q: Where can I find documentation for <insert name> plugin? 4Q: Where can I find documentation for <insert name> plugin?
5 5
6 A: All plugins that comply with minimal development guideline for 6A: All plugins that comply with minimal development guideline for
7 this project include internal documentation. The documentation 7 this project include internal documentation. The documentation
8 can be read executing plugin with the '-h' option ('--help' if 8 can be read executing plugin with the -h or --help option. If
9 long options are enabled). If the '-h' option does not work, that 9 the '-h' option does not work, that is a bug.
10 is a bug.
11 10
122. Q: What version of <insert name> plugin am I running?
13 11
14 A: All plugins that comply with minimal development guideline for 12Q: What version of <insert name> plugin am I running?
15 this project include detailed version information. When executed
16 with the '-V' option, a version string will be printed:
17 13
18 check_radius (nagios-plugins 1.3.0-alpha1) 1.11 14A: All plugins that comply with minimal development guideline for
15 this project include detailed version information. When executed
16 with the '-V' option, a version string will be printed:
19 17
20 Note that this string include both the assigned package release 18 check_radius (nagios-plugins 1.3.0-alpha1) 1.11
21 name and the CVS-generated revision for the individual plugin.
22 Authors should strictly adhere to this format. All bug reports
23 and help requests should reference this information.
24 19
253. Q: What information do I need to include when asking for help or 20 Note that this string include both the assigned package release
26 submitting a bug report? 21 name and the CVS-generated revision for the individual plugin.
22 Authors should strictly adhere to this format. All bug reports
23 and help requests should reference this information.
27 24
28 A: At a minimum, the output from 'uname -a' and the version string
29 from '<plugin_name> -V' and, of course, a description of the
30 problem and any solution/patch.
31 25
324. Q: I'm using Redhat Linux (or some other RPM-based distribution). 26Q: What information do I need to include when asking for help or
33 Which packages should I install? 27 submitting a bug report?
34 28
35 A: The package nagios-plugins-<version>.<arch>.rpm contains only 29A: At a minimum, the output from 'uname -a' and the version string
36 those plugins that should work on any POSIX compliant system. In 30 from '<plugin_name> -V' and, of course, a description of the
37 other words, you should be able to install this package on your 31 problem and any solution/patch.
38 system, no matter what else is or in not installed.
39 32
40 However, most of us have more complex systems than barebones
41 POSIX. We tried creating a variety of separate packages so
42 each dependency could be installed cleanly, but many people
43 found that this resulted in too many packages. So in the end,
44 all the non-POSIX plugins were folded into one RPM
45 (nagios-plugins-<version>.<arch>.rpm). Most people will need to
46 use RPM's '--nodeps' option to install this package.
47 33
485. Q: My system uses the .deb package format. What packages should I 34Q: I'm using Redhat Linux (or some other RPM-based distribution).
49 install? 35 Which packages should I install?
50 36
51 A: We strive for cooperation between all packagers and developers. 37A: The package nagios-plugins-<version>.<arch>.rpm contains only
52 The answers for .deb are the same as for RPM, after changing the 38 those plugins that should work on any POSIX compliant system. In
53 package name suffixes accordingly. 39 other words, you should be able to install this package on your
40 system, no matter what else is or in not installed.
54 41
556. Q: I prefer to build my own RPMs. Do I need to install all of the 42 However, most of us have more complex systems than barebones
56 various dependencies? 43 POSIX. We tried creating a variety of separate packages so
44 each dependency could be installed cleanly, but many people
45 found that this resulted in too many packages. So in the end,
46 all the non-POSIX plugins were folded into one RPM
47 (nagios-plugins-<version>.<arch>.rpm). Most people will need to
48 use RPM's '--nodeps' option to install this package.
57 49
58 A: Beginning with the 1.2.9-1 release, you may run
59 50
60 rpm --define 'custom 1' -ta nagios-plugins-<release>.tar.gz 51Q: My system uses the .deb package format. What packages should I
52 install?
61 53
62 In prior releases, you must unpack the tarball and build the 54A: We strive for cooperation between all packagers and developers.
63 RPM using nagios-custom.spec with 'rpm -ba'. 55 The answers for .deb are the same as for RPM, after changing the
56 package name suffixes accordingly.
64 57
657. Q: I get an error like
66 58
67 Warning: Return code of 127 for check of service 'PING' on host 'anyhost' was out of bounds. 59Q: I prefer to build my own RPMs. Do I need to install all of the
60 various dependencies?
68 61
69 when I run Nagios. (Often check_ping runs just fine on the 62A: Beginning with the 1.2.9-1 release, you may run
70 command line).
71 63
72 A: Commonly, system administrators will make security as tight as 64 rpm --define 'custom 1' -ta nagios-plugins-<release>.tar.gz
73 possible on the monitoring system. Sometimes this includes OS
74 options or hardening scripts that prevent unprivileged users from
75 running the ping command. Nagios runs with no more privileges
76 than 'nobody' -- check to be sure that the nagios user can
77 actually run check ping. (This can also happen with other binaries
78 executed by nagios, but ping seems to be far and away the biggest
79 offender.)
80 65
818. Q: I have a plugin to offer. What do I do to get it accepted? 66 In prior releases, you must unpack the tarball and build the
67 RPM using nagios-custom.spec with 'rpm -ba'.
82 68
83 A: Send it to nagiosplug-devel@lists.sourceforge.net. Usually, we
84 just drop it into contrib until we have a chance to check if the
85 standard options are used, etc.
86 69
87 You can also get feedback on improving the plugin via the mailing list. 70Q: I get an error like
71
72 Warning: Return code of 127 for check of service 'PING' on host 'anyhost' was out of bounds.
73
74 when I run Nagios. (Often check_ping runs just fine on the
75 command line).
76
77A: Commonly, system administrators will make security as tight as
78 possible on the monitoring system. Sometimes this includes OS
79 options or hardening scripts that prevent unprivileged users from
80 running the ping command. Nagios runs with no more privileges
81 than 'nobody' -- check to be sure that the nagios user can
82 actually run check ping. (This can also happen with other binaries
83 executed by nagios, but ping seems to be far and away the biggest
84 offender.)
85
86
87Q: I have a plugin to offer. What can I do?
88
89A: You can make it available on NagiosExchange (http://nagiosexchange.org)
90 where other people can find it for use.
91
92 You can also get feedback on improving the plugin via the
93 nagiosplug-devel@lists.sourceforge.net mailing list.