1nsca-ng(8) The NSCA-ng Manual nsca-ng(8)
2
6 nsca-ng - monitoring command acceptor
7
9 nsca-ng [-FSs] [-b listen] [-C file] [-c file] [-l level] [-P file]
10 nsca-ng -h | -V
12
14 The nsca-ng server makes the Nagios command file accessible from remote
15 systems. This allows for submitting passive check results, downtimes,
16 and many other commands to Nagios (or compatible monitoring solutions).
17 The communication with clients is TLS encrypted and authenticated using
18 pre-shared keys (as per RFC 4279). The nsca-ng server supports per-
19 client passwords and fine-grained authorization control.
20 The server process rereads its configuration file when it receives a
22 hangup signal (SIGHUP) by executing itself with the name and arguments
23 it was started with.
24 When compiled with systemd(1) support, the nsca-ng server auto-detects
26 whether it was socket activated. If so, it behaves as if the -F option
27 was specified, while it ignores the -b option and the listen setting in
28 the nsca-ng.cfg(5) file. The nsca-ng server supports systemd(1)'s no‐
29 tify process startup type as well as the WatchdogSec feature (see the
30 systemd.service(5) manual).
31
33 -b listen
34 Bind to the specified listen address or host name. The default
35 setting is “*”, which tells nsca-ng to listen on all available
36 interfaces. A colon (“:”) followed by a service name or port
37 number may be appended in order to override the default port
38 (5668) used by nsca-ng. If this option is specified, the listen
39 setting in the nsca-ng.cfg(5) file is ignored.
40 -C file
42 Submit monitoring commands into the specified file. This should
43 be the named pipe (FIFO) that Nagios checks for external com‐
44 mands to process. By default, nsca-ng submits commands into
45 /var/nagios/rw/nagios.cmd. This option takes precedence over
46 the command_file setting in the nsca-ng.cfg(5) file.
47 -c file
49 Read the configuration from the specified file instead of using
50 the default configuration file /etc/nsca-ng.cfg. If a directory
51 is specified instead of a file, the configuration will be read
52 from all files with a .cfg or .conf extension in this directory
53 and all subdirectories. Symbolic links are followed.
54 -F Don't detach from the controlling terminal, and write all mes‐
56 sages to the standard error output (unless the -s option is
57 specified).
58 -h Print usage information to the standard output and exit.
60 -l level
62 Use the specified log level, which must be an integer value be‐
63 tween 0 and 5 inclusive. A value of 0 tells nsca-ng to generate
64 only fatal error messages, 1 adds non-fatal error messages, 2
65 adds warnings, 3 additionally spits out every submitted monitor‐
66 ing command (plus startup and shutdown notices), 4 also logs
67 each message sent or received at the protocol level, and 5 gen‐
68 erates additional debug output. The default log level is 3. If
69 this option is specified, the log_level setting in the
70 nsca-ng.cfg(5) file is ignored.
71 -P file
73 During startup, try to create and lock the specified file and
74 write the process ID of the nsca-ng daemon into it. Bail out if
75 another process holds a lock on the file. By default, no such
76 PID file is written. This option takes precedence over the
77 pid_file setting in the nsca-ng.cfg(5) file.
78 -S Write all messages to the standard error output and (with the
80 exception of startup messages) to the system logger. This op‐
81 tion may only be specified together with the -F option.
82 -s Send all messages to the system logger, except for startup mes‐
84 sages. This is the default behaviour (unless the -F option is
85 specified).
86 -V Print version information to the standard output and exit.
88
90 /etc/nsca-ng.cfg
91 The nsca-ng.cfg(5) configuration file.
92
94 nsca-ng.cfg(5), send_nsca(8), send_nsca.cfg(5)
95 http://www.nagios.org/developerinfo/externalcommands/
97
99 Holger Weiss <holger@weiss.in-berlin.de>
100Version 1.6 March 19, 2019 nsca-ng(8)