We have seen many testing problems with a number of different software components on Suse 9 IA-64 and Debian 3.1 (Sarge).
Our PyGlobus build is not linking properly with SSL on SUSE 9 x86_64 This prevents the build from completing, and therefore PyGlobus doesn't work on these platforms. However, the VDT installation will complete (apparently) successfully.
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 (IA64 or x86-64). We used to provide the 32-bit version on x86-64, but due to the fact that we now link against the OS-provided OpenSSL which is 64-bit, we don't support MDS 2 on 64-bit platforms at all.
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.
See the separate Mac OS X page for known problems on the platform.