Firstly, apologies as since our site reinstall Durham is missing space
tokens - its on the list of things to fix.
Secondly, I created a simple nagios check to ensure our site was
publishing space tokens correctly. See below for anyone interested in
adding something similar to their local nagios.
You need two files, the "check_space-tokens.sh" script and
"space-token-list" - a text file with a list of expected tokens (in
alphabetical order). It does an ldap query (you'll have to change the
host name to your SE) and then does a diff with the expected.
# cat /usr/lib/nagios/plugins/space-token-list
ATLASDATADISK
ATLASMCDISK
ATLASPRODDISK
# cat /usr/lib/nagios/plugins/check_space-tokens.sh
#!/bin/bash
# Usage: check_space_tokens
# Description:
# This plugin uses ldapsearch to query the service-level BDII on SE01
# to see whether the space tokens being published match a pre-defined
list.
OK=0
WARNING=1
CRITICAL=2
PATH="/usr/bin:/usr/sbin:/bin:/sbin"
TOKENS="/usr/lib/nagios/plugins/space-token-list"
HOST=$1
LDAPRESULT=`ldapsearch -x -h se01.dur.scotgrid.ac.uk -p 2170 -b "o=grid"
| grep GlueVOInfoTag | sort | cut -d\ -f 2 | diff -q - $TOKENS`
if [ "$LDAPRESULT" != "" ] ; then
echo "Space tokens differ from list. Ensure $TOKENS is up to
date, and that publishing is working ok."
exit $CRITICAL
fi
exit $OK
Cheers,
Phil
Greig A. Cowan wrote:
> Hi all, Stephen,
>
> Following on from todays meeting, I have worked out why the
> ATLASDATADISK token disappeared from ECDF's DPM. I added a CMS_DEFAULT
> token a couple of days ago and forgot to specify a group which could
> write to it, i.e., I didn't have the --gid option:
>
> dpm-reservespace --gspace 2T --poolname cms --token_desc=CMS_DEFAULT
> --gid=141
>
> The reservation was successful but it resulted in the information
> publishing breaking as the current GIP falls over if there is a token
> which does not have a group assigned to it.
>
> Can all sites check that their reservations have groups assigned to
> them? Use the following command:
>
> dpm-listspaces
>
> and look for "Authorized FQANs" line. It should have a VOMs role
> attached to it.
>
> Stephen: I think this should be submitted as a bug in the current
> provider. It's not really that urgent though as the new GIP (which
> doesn't have this problem) should come with the forthcoming release of
> DPM 1.7.
>
> Cheers,
> Greig
>
|