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.1k Update

On 2008-10-06, the VDT team announced the release of VDT 1.10.1k.

Changes to VDT 1.10.1k

Please note: This release includes security fixes for Condor, Tomcat 5.5, and MySQL 5.0. Please see details below.

Condor and Condor-Cron have been upgraded from 7.0.4 to 7.0.5. Some of the included fixes are security fixes, and we recommend upgrading Condor. Full information about the updates are available here.
LFC (the LCG File Catalog) was added to the VDT. More information about LFC (VDT ticket 3754)
The VDT Apache build now includes mod_expires and mod_headers, but these modules are not loaded by default. To enable the modules, look in the $VDT_LOCATION/vdt-app-data/apache/vdt-webapps.conf Apache configuration file. (VDT ticket 3909)
OSG RSV Core was updated to 2.3.6, so that (following this release) updates to Apache will not require extra commands to preserve configuration of the RSV output directory. (VDT tickets 3907, 3970)
Tomcat 5.5 was updated to version 5.5.27, which includes some minor security updates. Tomcat 5.5.27 release notes (VDT ticket 3969)
MySQL 5 was updated to version 5.0.67 to bring the VDT up to date with all the latest bug and security fixes. MySQL 5.0.67 release notes (VDT ticket 3903)
Gratia services and reporting were updated to version 0.34.9b to fix a SQL problem exposed by the MySQL 5 update. The update also came with improvements to record handling for large, buggy records and improved logging and diagnostics. (VDT ticket 4098)
UberFTP has been updated to 2.0. This corrects problems with the Mac OS X version. (VDT ticket 3671)
Multiple changes to the handling of xinetd configuration files by vdt-control, part of VDT-Service-Management.
- When possible, user changes to the file at $VDT_LOCATION/vdt/services/xinetd-* will be preserved. (VDT ticket 3768)
- Settings that are entirely missing from the configuration file will be added. (VDT ticket 3768)
- The setting “per_source” has been added with a value of 300. This is to override much lower default limits present on some operating system distributions. The lower limit can cause problems for busy machines running the Globus Gatekeeper, especially on a restart. (VDT ticket 3687)
VDT-Logrotate has been updated. vdt-rotate-gram-logs previously would fail if more than about 6,000 gram_job_mgr* files were to be archived. This has been fixed. (VDT ticket 3960)
We added LCG-Utils to the VDT-Client (and therefore the related OSG Client). This mostly affects fresh installations, unless you want the LCG-Utils to be added to your client installation.

We have updated vdt-version. It now presents information in a slightly different format. For example:

You have installed a subset of VDT version 1.10.1k:

Software                                                 Status              
--------                                                 ------              
Apache HTTPD 2.2.9                                       OK                  
Berkeley Storage Manager (BeStMan) 2.2.0.11.a            -                   
gLite CEMon Server 1.9.1-0                               -                   
CA Certificates v41 (includes IGTF 1.25 CAs)             -                   
Condor/Condor-G 7.0.5                                    OK 
...
Status legend:
OK: Software is up to date with the latest release in VDT version
1.10.1
- : Not enough information to determine if updates are available.
See man page for more information.

In particular, vdt-version can — in some instances — tell you precisely what version of the software you’ve installed, and if there is an upgrade. Prior to this release, vdt-version would tell you the version that was in the lettered VDT update from which you had installed at least component, even if you hadn't updated all components. Unfortunately, to avoid extra updates, we will phase in version information over time, so many components (the ones marked with a hyphen in the status field) may continue not to be accurate version numbers. (VDT ticket 4090)

We updated VOMS, but it is not a functional change and you can ignore it. It is not a new version of VOMS. See below for details.
The configure_mysql had a minor bug fix. It is only relevant for people doing fresh installations, so you do not need to update it.
This release is the first one for which the VDT team now does fully automated testing of all RSV probes on all platforms, to ensure that all of the probes, as well as the systems they test, are working. This testing is internal, so there are no updates for end-users.

Updating to VDT 1.10.1k

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

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 will 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

Getting LFC

You can install any of the following LFC packages:

LFC: The LFC server and client software. This package does not provide MySQL, and assumes that you can configure it to use your own version of MySQL.
LFC-MySQL: The LFC server and client, as well as MySQL 5. MySQL-5 will be configured to work with the LFC server.
LFC-Server: Just the LFC server. No client, no MySQL.
LFC-Client: Just the LFC client (including Python interface). No server, no MySQL.

Updating Condor

Do this step if and only if your installation includes the Condor package (look for the $VDT_LOCATION/condor directory).

pacman -update Condor

Updating Condor-Cron

Do this step if and only if your installation includes the Condor Cron package (look for the $VDT_LOCATION/condor-cron directory).

pacman -update Condor-Cron

Updating Apache

Do this step if and only if your installation includes the Apache package (look for the $VDT_LOCATION/apache directory).

Note: Do this part of the update process before updating OSG RSV Core or Tomcat 5.5. Doing the updates in the right order will help ensure a working VDT following the updates.

cp -p $VDT_LOCATION/apache/htdocs/index.html $VDT_LOCATION/BACKUP_index.html
pacman -update Apache
mv $VDT_LOCATION/BACKUP_index.html $VDT_LOCATION/apache/htdocs/index.html

Updating OSG RSV Core

Do this step if and only if your installation includes the OSG RSV Core package (look for the $VDT_LOCATION/osg-rsv/config directory).

pacman -update OSG-RSV
vdt/setup/configure_osg_rsv --setup-for-apache
# Re-configure OSG-RSV (see link below)

NOTE: After updating, you must reconfigure OSG-RSV. See the configuration instructions here.

Updating Tomcat 5.5

Do this step if and only if your installation includes the Tomcat 5.5 package (look for the $VDT_LOCATION/tomcat/v55 directory).

pacman -update Tomcat-5.5

If (and only if) you have installed the Gratia web services package (look for the $VDT_LOCATION/gratia/gratia_services directory), you must also recreate some extra Tomcat configuration.

vdt/setup/configure_gratia --reporting

Updating MySQL 5

Do this step if and only if your installation includes the MySQL 5 package (look for the $VDT_LOCATION/mysql5 directory).

pacman -update MySQL-5

Updating UberFTP

Do this step if and only if your installation includes the UberFTP package (look for the $VDT_LOCATION/globus/bin/uberftp executable).

pacman -update UberFTP

Updating VDT-Service-Management

pacman -update VDT-Service-Management

NOTE: If the command above produces no output, then it simply means that you already have the update — most likely from doing one or more of the other updates list on this page. Nevertheless, you should read the rest of the steps in this section, because they may still apply to you.

If you have VDT services enabled of the type “inetd”, you will need to re-enable them to update their xinetd configuration files. The most likely services are “globus-gatekeeper” and “gsiftp”. You can determine which services you have installed are of this type inetd with the following command:

vdt-control --list | grep inetd

For each matching service, you will need to run the following command:

vdt-control --on SERVICE-NAME

For example, if you are running both the globus-gatekeeper and gsiftp services, you would use the following:

vdt-control --on globus-gatekeeper
vdt-control --on gsiftp

Updating VDT-Logrotate

pacman -update VDT-Logrotate

NOTE: If the command above produces no output, then it simply means that you already have the update — most likely from doing one or more of the other updates list on this page. There are no further actions to take for this update.

Updating vdt-version

All other updates will bring along the update to VDT version automatically, so there is no need to do anything. If you are not doing any other updates, you can get the update to vdt-version by doing the following:

pacman -update VDT-Version

Updating VOMS

You do not need to update VOMS unless you using the LFC, and then you should get the update automatically if you install LFC. This is because the only part of VOMS that changed was the addition of some new flavors of libraries needed for LFC. If you really want to update anyway, you can update any of the following:

pacman -update VOMS         # If you run a VOMS Server and use VOMS client commands
pacman -update VOMS-Server  # If you run a VOMS Server
pacman -update VOMS-Client  # If you use VOMS client commands, like voms-proxy-init

Getting LCG-Utils (for the VDT-Client)

pacman -get LCG-Utils