opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
158 / 193
normally make only sense if you have only one or two depots. You may also give a comma separated list of depot
servers.
An other way to define the checks is to give the name of a opsi groups. So you may check the software roll out state
of all products in a given opsi product group. If you have for example a product group accounting you may use the
following call:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkProductStatus -g accounting
Now you will check all products that are Members of the opsi product group accounting by this single check. Important
is to see, that the resolution of the opsi group is done while the check at the opsi server. So you may change the opsi
group at the opsi Management interface and so you will change the products that will checked without any changes
at the Nagios server.
Note
Sub groups (groups in groups) will not be resolved.
In the same way it is possible to define the clients that should be checked by giving the name of a opsi client group.
An example for a client group productiveclients:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkProductStatus -g accounting -G \
productiveclients
This would check all products of the product group accounting at all clients of the client group productiveclients.
Note
Sub groups (groups in groups) will not be resolved.
Note
You may also give a comma separated list of opsi groups.
Check: opsi-check-depotsync
If you are using multiple opsi depots the monitoring of synchronicity is important. Even if your depots are for good
reasons not completely synchronize they should be synchrony as much as possible to avoid problems by moving a
client from one depot to another.
This check monitors if your depots are synchronize according to product ids, product versions and package versions.
This check returns:
• OK
If all is in sync.
• Warning
If there is any difference
You should run this check always on the config server because all the data come from the backend of the config server.
Here are some examples.
The base variant:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkOpsiDepotSyncStatus
This base variant is equivalent to the following call: