opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkOpsiDepotSyncStatus -d all
159 / 193
So if you don’t give the depots which are have to be checked, all known depots will be checked. If you have a lot of
depots the interpretation of the result is complicated, so it is a good idea to define a lot of single checks where the
depots are given as comma separated list:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkOpsiDepotSyncStatus -d \
configserver.domain.local,depotserver.domain.local
With this check you compare all products, that are installed on both depots. Any product which is installed only on
one of the depot is ignored and will not effect the result.
If you want to include products which are not installed on all checked depots, you have to use the strictmode switch:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkOpsiDepotSyncStatus -d \
configserver.domain.local,depotserver.domain.local --strictmode
Now also differences about missing products will be seen.
If you like to exclude a product from the check (perhaps because this product should be in different versions on
different depots) you may do this by using the -x option. Here you may also use a comma separated list:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkOpsiDepotSyncStatus -d \
configserver.domain.local,depotserver.domain.local --strictmode -x firefox,thunderbird
This check will not warn if the products firefox or thunderbird or not in sync.
Instead of excluding products you may give an explicit list of products that has to been checked:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkOpsiDepotSyncStatus -d \
configserver.domain.local,depotserver.domain.local --strictmode -e firefox,thunderbird
In this case only firefox and thunderbird will be checked. We recommend to use this check variant with strictmode
to see if one of the products is missing.
./check_opsi.py -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkOpsiDepotSync
Check: nagios client plugin check via opsiclientd
This check gives you an easy possibility to integrate checks that collects the data direct on the client with a minimum
of configuration work.
So this check tells the opsiclientd which is running at the opsi client to run a command, fetch the output and send it
back.
This extension is not intended to be a complete replacement of a full featured Windows Nagios agent. It is only a
light weight alternative.
The plugins which the opsiclientd may call must be compatible to the Nagios plug-in development guidelines.
(More details at: http://nagiosplug.sourceforge.net/developer-guidelines.html ).
In order to run such a plugin on the client, it has to be installed at the client. This problem you will solve by deploying
it as an opsi package. The path where the plugin is installed at client doesn’t matter because you have to give the
complete path at check definition. We recommend to install all plugins in one directory to ease the maintenance of
the plugins at the client.
For security reasons you should make sure that non privileged users have no write access to the plugins, because they
will be executed from the opsiclientd with system privileges.
There are lot of ready to use plugins at the internet. One important address to look is:
http://exchange.nagios.org/
In the following we assume that your plugins are installed at C:\opsi.org\nagiosplugins\ and we will find ther the
plugin check_win_disk.exe out of the package nagioscol from
http://sourceforge.net/projects/nagiosplugincol/