Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Nagios on certification testbed | ||||||||
Line: 98 to 98 | ||||||||
| ||||||||
Added: | ||||||||
> > | WMS checks
| |||||||
Useful links |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
Nagios on certification testbedIn this page we describe the services monitored by the nagios server installed on cream-17.pd.infn.itInstall NRPE clientTo monitor a service (from the nagios server on cream-17.pd.infn.it) you need to install NRPE client using this procedure:
Nagios pluginsUsually the PLUGINPATH depends on the architecture (substitute variable with the right line in the command description):
Default checksThese checks are activate on all hosts:
Custom checksWe suppose that these custom plugins are installed in <PLUGINPATH>/gLite directoryCREAM checksThe following checks are based on the output of a shell monitoring script installed by default on a CREAM CE. All these checks required root permission so instead of add user nagios to sudoers file we prefer to add a cron job which run the monitoring script and save the output on the file /tmp/cream.mon. This is the cron job which must be installed on the client before activating these plugins:*/1 * * * * root /opt/glite/bin/glite_cream_load_monitor --show > /tmp/cream.mon
Batch System checksYou have to choose beetween pbs/torque and lsf
Worker Node checksThe option depends from the installed batch system
Generic checks
Cream CLI checksThis is useful to test Cream CE through CreamCLI direct submission. To run this plugin you need to modify the nrpe configuration file of the host (i.e. the UI):-dont_blame_nrpe=0 +dont_blame_nrpe=1 -command_timeout=600 +command_timeout=1200
Useful links
|