Checking for cron
jmarquart at planalytics.com
jmarquart at planalytics.com
Fri Sep 20 18:40:24 CEST 2002
or - if already running ssh - you can do:
checkcommand:
define command{
command_name check_remote_procs
command_line $USER1$/check_by_ssh -H $HOSTADDRESS$
/path/to/host/checks/check_procs -c $ARG1$ -w $ARG2$ -u $ARG3$ -C $ARG4$
}
and then a service:
define service{
use your-favorite-template
host_name host.to.check
service_description CROND proc
check_command check_remote_procs!1:50!1:20!root!crond
}
and then you can check your process using the plugins - and securely.
-j
Fredrik W
-------------- next part --------------
?nglund <Fredrik.Wanglund at datavis.se> on 09/20/2002 01:58:00 AM
To: "Carroll, Jim P [Contractor]" <jcarro10 at sprintspectrum.com>, "Nagios-Users
(E-mail)" <nagios-users at lists.sourceforge.net>
cc: (bcc: John J. der Schalla Marquart/Planalytics)
Subject: RE: [Nagios-users] Checking for cron
-------------- next part --------------
Nagios_statd from http://www.twoevils.org/html/files.php will do the trick.
-----Original Message-----
From: Carroll, Jim P [Contractor] [mailto:jcarro10 at sprintspectrum.com]
Sent: Thu 19-Sep-02 16:45
To: 'Nagios-Users (E-mail)'
Cc:
Subject: RE: [Nagios-users] Checking for cron
Write a plugin to basically do "ps -ef | grep cron | grep -v grep" and if
the answer is null, return a critical error "exit 2". Then call it remotely
using NRPE from your Nagios host.
But this begs the question... are you seriously having problems with cron
abending?
If I were you, I'd be checking logfiles and/or running truss and/or checking
with SunSolve. If you're still not having any luck, try and install xinetd.
But seriously, I'd consider cron to be one of those daemons that never
exits, unless someone's been mucking with the libraries (or the binary, for
that matter).
jc
> -----Original Message-----
> From: Derek Belrose [mailto:derek at omegabyte.com]
> Sent: Thursday, September 19, 2002 3:33 AM
> To: 'Nagios-Users (E-mail)'
> Subject: [Nagios-users] Checking for cron
>
>
> Hey guys, I'm running Nagios to monitor a bunch of different systems
> (mostly the Sun/Cobalt Raqs) and I need to keep a close watch on crond
> to make sure it DOES NOT drop.
>
> I'm running it on one server and having it check others using the
> standard check_* plugins and I tend to want to stay away from SNMP due
> to a severe lack of understanding of it.
>
> Any ideas on how I may check this on a reoccurring basis?
>
> Derek
> Omegabyte Networks
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
More information about the Users
mailing list