Note: This version of the VDT (1.8.1) is no longer supported. Feel free to look through the documentation and install it, but we cannot guarantee support for it. The current stable release is 2.0.0.

VDT 1.8.1h Update

On 2007-01-28, the VDT team announced the release of VDT 1.8.1h.

Changes to VDT 1.8.1h

GUMS has been upgraded from 1.2.14 to 1.2.15. This update fixes several bugs that may be critical at some sites. See the ticket for more information. (VDT ticket 3240)
Syslog-ng has been upgraded from 2.0.4 to 2.0.7 to prevent two denial of service vulnerabilities as well as a number of bug fixes. Syslog-ng change log (VDT ticket 3257)
MySQL 5 was upgraded from 5.0.41 to 5.0.51a. This is the most recent version, and it includes security and bug fixes since 5.0.41. (VDT ticket 3260)
Java 5 was upgraded from 1.5.0_13 to 1.5.0_14. This is the most recent version, and it contains security and bug fixes since 1.5.0_13. (VDT ticket 3261)
We have fixed a bug in the Managed Fork job manager, which will fix problems that some systems have with the Condor Grid Monitor. (VDT ticket 3245)

Updating to VDT 1.8.1h

If you installed VDT 1.8.1 after VDT 1.8.1h was released on 2007-01-28, you do not need to do any of these update operations because you will have 1.8.1h.

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 -l -d 1

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!

1. Updating GUMS

Note: if you have the GUMS package installed, updating it will fetch an update for both GUMS-Client and GUMS-Service. If you have either GUMS-Client or GUMS-Service installed, you will need to update them individually. If you are updating GUMS or GUMS-Client, you need to backup one configuration file prior to the update:

Updating GUMS:

cp gums/config/gums-client.properties gums-client.properties.vdtsave
pacman -update GUMS
mv gums-client.properties.vdtsave gums/config/gums-client.properties

# Re-enable the gums-host-cron script if desired
vdt/sbin/vdt-register-service -name gums-host-cron --enable

Updating GUMS-Client:

cp gums/config/gums-client.properties gums-client.properties.vdtsave
pacman -update GUMS-Client
mv gums-client.properties.vdtsave gums/config/gums-client.properties

# Re-enable the gums-host-cron script if desired
vdt/sbin/vdt-register-service -name gums-host-cron --enable

Updating GUMS-Service:

pacman -update GUMS-Service

2. Updating Syslog-ng

cp syslog-ng/etc/syslog-ng.conf syslog-ng.conf.backup
pacman -update Syslog-ng
mv syslog-ng.conf.backup syslog-ng/etc/syslog-ng.conf

3. Updating MySQL-5

pacman -update MySQL-5

# After updating, your MySQL-5 install may be disabled in the VDT.  To re-enable it, run the following command:
vdt/setup/configure_mysql --server y --version 5

4. Updating JDK-1.5

pacman -update JDK-1.5

5. Updating Globus-ManagedFork-Setup

 pacman -update Globus-ManagedFork-Setup