The check is working correctly - /mnt/store is a valid path in both
circumstances. Remember, in Unix mounted filesystems all sit on top of the
/ filesystem, so when you umount the filesystem on /mnt/store, that
mountpoint still exists (on /).
The way I've done it in the past is by using -r/-R to
hello list!
hello.. I am running a nagios disk check that reports OK even when the
partition is not mounted or the machine is shut down .. how can I test the
check and adjust it so that it reports accurately?
## Machine info
CentOS release 5.6 (Final)
i686
##Nagios Version
Nagios Core 3.3.
Hi All,
Andreas Ericsson wrote:
> Hi all. I attended the Nagios World Conference North America last week
> and though I'd dish out some kudos where such are due, and also dense
> up the information to any newcomers that might get lucky when looking
> for solutions to any particular problems.
>
> O
service syslog restart did restart the syslog service, however no changes
have been made. Logs about NRPE are still going to /var/log/messages, even
though I added "local4.* /var/log/nrpe.log" to that file, and the nrpe.cfg
I changed it to local4 as well...
On Wed, Oct 5, 2011 at 11:24 AM, Schi
It somewhat depends upon your operating system (and Linux distribution, if you
use Linux). On a RedHat based system you may want to try "service syslog
restart". Typically syslog reloads its configuration, if you sent him the
SIGHUP signal. So you may want to use ps -ef | grep syslog to determi
I made the change and restarted xinted. How do I restart syslog?
On Wed, Oct 5, 2011 at 10:43 AM, Schimpke, Dr. Thomas - bhn <
schimpke.tho...@bhn-services.com> wrote:
> Hi,
>
> it's not nrpe's config file - it's xinetd's config file for the nrpe
> service. nrpe is started by xinetd as soon as a
Hi all. I attended the Nagios World Conference North America last week
and though I'd dish out some kudos where such are due, and also dense
up the information to any newcomers that might get lucky when looking
for solutions to any particular problems.
Overall, the standard of the conference was v
Hi,
it's not nrpe's config file - it's xinetd's config file for the nrpe service.
nrpe is started by xinetd as soon as a request from the nagios server arrives.
So you simply need to restart xinetd (or reload its configuration).
If you still use SYSLOG (and not FILE), then you should configure
I've made the configuration change - now I'm guessing I need to restart NRPE
daemon to read in the changed config file. How do I restart NRPE? I want it
to run as a daemon, and I believe that it is...there's an nrpe file in
/etc/xinte.d/...I already restarted xinted after I made the log file chang
Hi
you can change log_facility=daemon to something like
log_facility=local4
and add this to your syslog.conf, for example
local4.*/var/log/nrpe.log
Best regards
Martin
On Wednesday 05 October 2011 15:13:42 R. Leigh Hennig wrote:
> On my remote
These aren't messages from nrpe but from xinetd. You should set the log_type
parameter in nrpe's config fiule for the xinetd. Either use SYSLOG with
facility local0 and configure syslog to log local0 to a file .../nrpe.log or use
FILE as a parameter for the log_type and and the full path to the d
Hi R.,
Am Mittwoch 05 Oktober 2011, 15:13:42 schrieb R. Leigh Hennig:
> On my remote hosts, /var/log/messages is filling up with messages like
> this:
>
> Sep 26 06:33:53 xinetd[13362]: EXIT: nrpe status=0 pid=8099
> duration=0(sec)
> Sep 26 06:34:01 xinetd[13362]: START: nrpe pid=8105
> from=
On my remote hosts, /var/log/messages is filling up with messages like this:
Sep 26 06:33:53 xinetd[13362]: EXIT: nrpe status=0 pid=8099
duration=0(sec)
Sep 26 06:34:01 xinetd[13362]: START: nrpe pid=8105 from=
Sep 26 06:34:01 xinetd[13362]: EXIT: nrpe status=0 pid=8105
duration=0(sec)
Sep 26 0
13 matches
Mail list logo
