VDT logo
Search:

(Powered by Google)

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

On 2009-01-22, the VDT team announced the release of VDT 1.10.1s.

Changes to VDT 1.10.1s

  1. VOMS was updated to fix a bug whereby the server would stop issuing proxies after 8 hours of inactivity. This change only affects server installations. (VDT ticket 4472)
  2. The Squid init script (created by the Configure-Squid package) was updated to reset the cache on startup. This should eliminate problems where Squid would fail to start, or would run in a degraded mode after an unexpected termination. (VDT ticket 4670)
  3. The vdt-version script has minor improvements. Most notably, when an update for software is available, the version of the update is listed.

Changes that do not require updates.

  1. When configuring the Gratia GridFTP transfer probe, it is necessary to have the $VDT_LOCATION/monitoring/osg-user-vo-map.txt file present. If this file is missing, configure_gratia will now print a warning to the post-install/README file. (VDT ticket 4603)
  2. We have added a new check to the VDT prerequisite checking script that validates OLD_VDT_LOCATION (if it is set) prior to an installation. The check ensures that OLD_VDT_LOCATION is set to an existing directory, and the canonical path is not the same as the canonical path of VDT_LOCATION. This will work for all new installations.

Updating to VDT 1.10.1s

If you installed VDT 1.10.1 after VDT 1.10.1s was released on 2009-01-22, you do not need to do any of these update operations because you will have 1.10.1s.

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

Pre-update directions

Before you do any of the update directions that follow, please run the following commands to stop services and take a backup of your installation. This applies 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.

Updating VOMS

This update ought to affect only the VOMS server. If you wish to update the other components, you may do so, but we expect no functional difference.

Do this step to update the VOMS server (look for the $VDT_LOCATION/glite/sbin/voms file): 

pacman -update VOMS-Server

Optional VOMS Update Steps

Do this step to update the VOMS client (look for the $VDT_LOCATION/glite/bin/voms-proxy-init file): 

pacman -update VOMS-Client

If your installation includes only the VOMS Essential package (look for the $VDT_LOCATION/glite/lib/libvomsapi_nog.so file), but not VOMS client or server, then do this step to update it: 

pacman -update VOMS-Essentials

Updating Configure-Squid

Do this step only if your installation includes the Configure-Squid package (look for the $VDT_LOCATION/vdt/setup/configure_squid file). To get the improvements from this update, the configuration script must be run manually after the update, as shown below. 

pacman -update Configure-Squid
vdt/setup/configure_squid

Updating VDT-Version

pacman -update VDT-Version

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.

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