Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "UMD-1 UMD-1.3.0"

From EGIWiki
Jump to navigation Jump to search
Line 57: Line 57:
<br>
<br>


== emi.bdii-site.sl5.x86_64-1.0.1 ==
== emi.bdii-site.sl5.x86_64  ==


*'''Additional Details:''' No issues found during EGI's Software Provisioning.  
*'''Additional Details:''' No issues found during EGI's Software Provisioning.  

Revision as of 12:50, 25 October 2011

UMD 1.3.0 : Additional information for provided products

While undergoing the EGI Software Provisioning process, some installation issues and known problems were detected and documented. This document provides the same information, in one single place, where site admins may learn about the provided software prior to installation or, with later updates to UMD -1, upgrading their systems.

Each section that follows will be linked by the relevant sections provided in the EGI Software Repository for this release of UMD.

emi.arc-ce.sl5.x86_64-1.1.0

  • Additional Details: No issues found during EGI's Software Provisioning.
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version: 1.1.0-1


emi.arc-client.sl5.x86_64-1.1.0

  • Additional Details: No issues found during EGI's Software Provisioning.
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version: 1.1.0-1


emi.arc-infosys.sl5.x86_64-1.1.0

  • Additional Details: No issues found during EGI's Software Provisioning.
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: Documentation improvements are still needed.
  • Version: 1.1.0-1


emi.argus.sl5.x86_64-1.4.0

  • Additional Details:
    • The Argus services have unbundled some of the required libraries. The VOMS API (vomsjapi.jar), the EMI Trustmanager (trustmanager.jar and trustmanager-axis.jar), and BouncyCastle (bcprov.jar) libraries are now installed separately, and used by the Argus services. Future update of these libraries will not require a repackaging of the Argus services.
    • The Argus services have now a memory limit set (PAP 256MB, PDP 256MB, PEP Server 128MB).
    • The Argus services have a new production configuration for the log files:
      • Daily log files rotating (midnight) or when the file size >= 100MB.
      • Rotated log files are gzipped.
      • Log files are keep for 90 days.
  • Installation Notes:
    • Applying the update will stop the Argus services (PAP, PDP and PEP Server).
    • You must re-configure the Argus services with YAIM. This automatically restart all the services.
  • Known Issues:
#grep JOPT /etc/sysconfig/argus-pepd
PEPD_JOPTS=\"-Xmx512M\"
#/etc/init.d/argus-pepd restart
  • Version: 1.4.0


emi.bdii-site.sl5.x86_64

  • Additional Details: No issues found during EGI's Software Provisioning.
  • Installation Notes: The BDII should be reconfigured so that the updated configuration is run.
  • Known Issues:
    • If bdii (or slapd) crashes regularly, it's advisable to manually install openldap 2.4 provided in the UMD repository:
yum install openldap2.4-servers
  • Add the following variables to your site-info.def yaim configuration file and re-run yaim:
SLAPD=/usr/sbin/slapd2.4
  • Version: 1.0.1


emi.bdii-top.sl5.x86_64-1.0.1

  • Additional Details: The BDII should be reconfigured so that the updated configuration is run.
  • Installation Notes: /etc/cron.hourly/generate-fcr-exclude-file. This file does not exist in the topbdii after install and yaim configuration.
  • Known Issues:
echo "SITE_NAME=<YOUR SITE NAME>" > /etc/bdii/gip/glite-info-site-defaults.conf
  • Version: 1.0.1


emi.dcache.sl5.x86_64-1.9.14

  • Additional Details:
    • Fixed several bugs in the pool, poolmanager, spacemanager and tansfermanager.
    • The most significant change is the downgrade to Jetty 7.2-2. Jetty 7.4.2 introduced in dCache 1.9.12-6 was the source of a regression in socket error handling.
    • The documentation was updated to better match the FHS compliant version of dCache. GGUS ticket: https://ggus.eu/tech/ticket_show.php?ticket=72686.
  • Installation Notes: Just do a yum update and restart dCache.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version: 1.9.12-10


emi.glexec_wn.sl5.x86_64-1.0.1

  • Additional Details:
    • This update of the gLExec workernode fixes a minor bug in the yaim configuration that would cause some variables to have the wrong (or no) default value.
    • This fix will mitigate the problems in OpenSSL (or Globus OpenSSL) by retrying the Path Length checks for RFC5280 and RFC3820 though a new routine that double checks if the chain is really invalid according to the initially stated failure condition. http://software-witchcraft.blogspot.com/2011/07/cream-did-it-using-bugs-in-path-length.html
    • The CREAM CE uses gLExec and LCMAPS to resolve a Unix account in one of its deployment options. The certificate chain will be checked by the lcmaps-plugins-verify-proxy component, launched by the gLExec/LCMAPS combination. The component triggers an X509_V_ERR_PROXY_PATH_LENGTH_EXCEEDED error code, even while the chain is fully valid. There are three important triggers required:
      • The user is required to use a certificate issued from a CA certificate with a path length constraint set to 0 (=zero). This is the case for the Terena eScience Personal, Terena SSL and the FNAL CA.
      • The job must flow through the CREAM CE frontend service, not directly to gLExec on the shell.
      • The proxy certificate chain must have at least two delegations, or more to trigger the error.
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version: 1.0.1


emi.unicore-client.sl5.x86_64-6.4.1

  • Additional Details:
    • Missing filetransfer parameters (e.g. client host for UFTP) are automatically set.
    • The "append" option (-a) is now also available for "get-file".
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version: 6.4.1


emi.unicore-tsi.sl5.x86_64-6.4.1

  • Additional Details:
    • Submit.pm: handle TSI_STDERR and TSI_STDOUT sent from XNJS for redirecting output and error.
    • Fix: Torque: GetStatusListing.pm now handles non-word characters in queue name.
    • Updated the manual.
  • Installation Notes:
    • Upgrading: the rpm does yet fully support upgrading. We recommend making a backup of the /etc/unicore/tsi/* files, and installing from scratch, i.e. erasing unicore-tsi first and then re-installing.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version: 6.4.1


emi.unicorex.sl5.x86_64-6.4.1

  • Additional Details:
    • This is a minor update to the 6.4.0 release, fixing a few bugs. A minor new feature in this release is ACL support on Linux (provided the file system supports it).
  • Installation Notes: After updating the libraries, the UNICORE/X server must be restarted.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version: 6.4.1


ige.globus-gridftp.sl5.x86_64-5.0.4

  • Additional Details: No issues found during EGI's Software Provisioning.
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version: 5.0.4


ige.globus-rls.sl5.x86_64-5.0.4

  • Additional Details: No issues found during EGI's Software Provisioning.
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version: 5.0.4