cate ,v" to
quickly locate every configuration file you've ever changed. If you
weren't using a CM system before, you'll have to locate your config
files manually. Be sure to use CM in the future.
- Morty
-
h nagios 3.0.x files.
The stuff I transfer on a Debian nagios is:
dirs="/etc/nagios3"
files="/var/lib/nagios3/retention.dat /var/www/index.html"
You may also want to grab /var/log/nagios3 if you want the old
history.
- Morty
SER6=`hostname`
And the command like so:
check_command check_nrpe!check_foo_$USER6$
- Morty
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landsca
ed options unless I turn on dont_blame_nrpe=1,
which I don't want to do.
- Morty
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and
different host in the cluster
could still be up. But I also don't want it tied to every host in the
cluster because then I could get duplicate notifications.
What am I missing?
Thanks!
- Morty
--
RSA(R) Confere
e code at all to a TRACE request, which is
good from my perspective.
- Morty
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
thr
check_http_trace
command_line$USER1$/negate -sw OK -o CRITICAL -c OK --
$USER1$/check_http -j TRACE -f sticky -H $HOSTADDRESS$ -p $ARG1$ $ARG2$
}
But IMHO, that's something of a hack. And it doesn't deal with the 401 issue.
- Morty
--
t 200. In the first case, both 200 and
401 are acceptable; in the latter case, I want 405 rather than 200.
Is there a way to require or allow a different response code?
I'm using check_http 1.4.15, as packaged with Debian 5.x. I googled,
but didn't find clue. :(
T
on and run netstat in the mode that shows all sockets and
what processes are bound to them. Under linux, that's netstat -pan.
Under Windows, I think it's something like netstat -ban.
- Morty
--
What You Don
o setup (and don't seem to have great performance impact),
> or you could parse nagios.dat and get the acknowledgments from
> there, then push them to the secondary server.
Interesting. Do you have example code? I'm currently using a file
backend, but I could switch to a DB ba
ilter
events so only acknowledgements and the like are sent between systems.
Do you have example code? Thanks!
- Morty
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading error
The default nagios start/stop script sends errors to stdout rather
than stderr. This isn't proper *nix behavior. It's also not good for
scripting around nagios. I.e. I have a script that wants to do
/etc/init.d/nagios stop >/dev/null && $other_stuff &&
/etc/init.d/nagios start >/dev/null && $mor
g, unless you want to write
> something that checks for new acks and dumps them into the command
> pipe. So, if you want to maintain acks and downtime, you'll need to
> have your backup disabled for the syncs.
y.html, but
scenario one doesn't discuss syncing acknowledgements, and scenario 2
is active/passive.
Thanks!
- Morty
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and thre
14 matches
Mail list logo
