Note: This version of the VDT (1.10.1) is supported, but is not our latest stable release. The current stable release is 2.0.0.

VDT 1.10.1n Update

On 2008-11-24, the VDT team announced the release of VDT 1.10.1n.

Changes to VDT 1.10.1n

Updated Gratia-Reporting and Gratia-Services to a new major version. These packages include the web application that collects Gratia data, but not the probes that collect the data. Most OSG CEs do not contain these packages and thus do not need this part of the update.
The update changes how these Gratia webapps runs inside Tomcat. As a result, the VDT team strongly recommends that you do not run Gratia alongside any other webapps in the same Tomcat 5.5 installation. For example, do not run it on your CE, which runs CEMon in Tomcat 5.5, or in the same installation as GUMS. (VDT ticket 4033)
Updated Gratia Probes to a new major version. (VDT ticket 4062)
Updated OSG-RSV and OSG-RSV-Probes to include new bug fixes. This update fixes scripts that referenced /bin/env instead of /usr/bin/env and an issue that caused incorrectly named Gratia files. (VDT ticket 4123)
Updated VOMS to pick up some bug fixes. Now, voms-proxy-init will fail correctly if the request is for a non-existent role or group, and proxy requests for non-existent users will not cause the VOMS server to hang. (VDT ticket 4246)
Updated the glexec configuration script to work correctly with the new VOMS version. (VDT ticket 4418)
Updated the Procd to fix some bugs. The Procd is software that is installed with glexec, so only glexec users must upgrade.
Updated vdt-version to have a timeout when fetching the version information from the VDT web page so that if the wget command hangs, vdt-version will still return. This package is updated as part of updating all other packages, so there’s no need for a separate update step just for it. (VDT ticket 4258)

Updating to VDT 1.10.1n

If you installed VDT 1.10.1 after VDT 1.10.1n was released on 2008-11-24, you do not need to do any of these update operations because you will have 1.10.1n.

The best way to do the update is to update the individual packages that have changed. To be clear, we do not recommend using pacman -update without specifying specific package names. Also note that you only need to update packages if you installed them. You can see what packages have been installed with:

pacman -lc

Common update directions

Before you do the update directions that follow, please run the following commands. They apply for all of the updates.

cd $VDT_LOCATION
. setup.sh
vdt-control --off
cp -pr $VDT_LOCATION BACKUP-LOCATION

The copy command makes a complete backup of your VDT installation, in case something goes wrong. Do not skip this step!

Updating CA-Certificates

Note: if you have not yet updated your CA-Certificates package (released on September 11th in VDT 1.10.1i), some of the following updates may automatically include this update for you. After this update, you will need to do a one-time configuration to re-install the certificates on your system. Many of the components installed by the VDT will not work until the certificates are re-installed. See the full instructions.

1. Updating Gratia-Reporting

This step is only for installations that include the Gratia-Reporting package; look for the $VDT_LOCATION/gratia/gratia_reporting directory.

Note: You must update Configure-Tomcat before updating Gratia-Reporting.

pacman -update Configure-Tomcat
pacman -update Gratia-Reporting

2. Updating Gratia Probes

You just need to update the Gratia Probes that you have installed. If you are running an OSG site, you probably have one for your batch system and the “Metric” probe. (If you are using the managed fork job manager, update the Gratia-Condor-Probe). Select the commands below that apply to the probes you have installed:

# Select the batch system probe you have
pacman -update Gratia-Condor-Probe
pacman -update Gratia-LSF-Probe
pacman -update Gratia-PBS-Probe
pacman -update Gratia-SGE-Probe

# OSG sites probably need the Metric probe updated (for RSV)
pacman -update Gratia-Metric-Probe

# The glexec probe is only if you use glexec
pacman -update Gratia-Glexec-Probe

3. Updating OSG-RSV

This step is only for installations that include the OSG-RSV package; look for the $VDT_LOCATION/osg-rsv directory.

pacman -update OSG-RSV
# Re-configure OSG-RSV (see link below)

Note: After updating, you will need to reconfigure OSG-RSV. For configuration, see the instructions here.

4. Updating VOMS

This step is only for installations that include parts of the VOMS package; see below for details.

If your install includes glite/bin/voms-proxy-info, update VOMS-Client:
```
pacman -update VOMS-Client
```
If your install includes glite/sbin/voms, update VOMS-Server:
```
pacman -update VOMS-Server
```

5. Updating Glexec

This step is only for installations that include the Glexec package; look for the $VDT_LOCATION/glexec-osg directory.

If you have glexec and if you update VOMS, you MUST do this update and rerun configure_glexec, or else your glexec binaries will not run.

pacman -update Configure-Glexec
$VDT_LOCATION/vdt/setup/configure_glexec

6. Updating Procd

This step is only for installations that include the Procd package; look for the $VDT_LOCATION/procd directory.

pacman -update Procd

Post-update directions

If you are finished applying all lettered updates, do not forget to restart services, typically using vdt-control. For example, to turn on all services:

vdt-control --on