Note: This version of the VDT (1.7.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.
VOMS Admin is the web interface to VOMS. VDT 1.7.1 has version 1.2.19-2-pre2-0. We have been experiencing persistent failures when installing VOMS Admin on Fedora Core 4, x86-64. Although this is not a widely used platform, we do not understand the problems well, and we do not know if they will manifest elsewhere.
If you install VOMS Admin and the installation fails while installing VOMS:
Package [/opt:vdt.caches:http://vdt.cs.wisc.edu/vdt_171_cache:VOMS] not [installed]:
Package [/opt:vdt.caches:http://vdt.cs.wisc.edu/vdt_171_cache:VOMS] has not been installed. Can't setup.
Package [/opt:vdt.caches:http://vdt.cs.wisc.edu/vdt_171_cache:VDT] not [installed]:
Package [/opt:vdt.caches:http://vdt.cs.wisc.edu/vdt_171_cache:VDT] has not been installed. Can't setup.
Then look in vdt-install.log. If you see an error like this while installing
VOMS-Server, it may be the same problem we’re experiencing, and we would
really like to know about it. Please let us know!
ERROR [main] Could not update org.glite.security.voms.database.flavours.MySQLSequence$1@7745c859: update affected 0 rows. - flavours.MySQLSequence ERROR [main] Internal database inconsistency detected: Could not update org.glite.security.voms.database.flavours.MySQLSequence$1@7745c859: update affected 0 rows. - database.Database Database deployment failed. Inspect above messages for an explanation.
Also, VOMS Admin 1.2.19-2-pre2-0 contains a known bug for which we install a workaround. However, the workaround disables the automatic request clean-up feature. We hope to release a new version of the VDT with a new, fixed version of VOMS Admin before any automatic clean-ups would occur, so we don’t expect this to cause problems.
This version of the VDT added Web Services GRAM support for SGE. Unfortunately, it does not yet work. Jeff Porter is helping us track down the remaining problems and get it to work. We hope to have it working by VDT 1.8.0.
Note that Pre-web services GRAM support (aka GRAM 2) for SGE has been in the VDT for a while and continues to work correctly.
CEMon is failing on RedHat Enterprise Linux 5 in our nightly tests. Unfortunately, we have not had time to debug it. We do not know if it is a failure in the service or in the client tools we use to debug it. If it is the former, it may be a serious problem. If it is the latter, it is not nearly so serious.
Globus 4 is run in its own container, not within Tomcat. Because we already have several known services that run within Tomcat, Globus 4 is running on a non-standard port: 9443 instead of 8443. If you wish to change this, just edit the globus-ws init script. Also note that we have a workaround for this problem.
Globus does not support MDS 2 on 64 bit platforms. Our 32 bit server build works on x86-64 machines, but the client only works when authentication is disabled (-x flag). Clients from 32 bit machines can authenticate to a 64 bit server without problems.
We have been unable to get working 32-bit installations on IA-64 machines (using VDT_PRETEND_32). On RedHat Enterprise Linux 3 (AS), running the 32-bit globus-rls-server binary consistently locked up the test machine, necessitating a hard reboot; if the RLS init script was installed in /etc/rc.d/init.d, rebooting caused the machine to lock up. On an IA-64 Scientific Linux 4 machine, all 32-bit binaries would refuse to run, preventing the installation from completing. Despite trying hard to fix these problems, they remain.
Our build of MySQL 5 doesn’t work on Debian 3.1. This prevents the Gratia service from working.