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
 
(18 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Template:Deprecated}}
= '''UMD 1.3.0 : Additional information for provided products'''  =
= '''UMD 1.3.0 : Additional information for provided products'''  =


Line 5: Line 7:
Each section that follows will be linked by the relevant sections provided in the EGI Software Repository for [http://repository.egi.eu/ this release] of UMD.  
Each section that follows will be linked by the relevant sections provided in the EGI Software Repository for [http://repository.egi.eu/ this release] of UMD.  


== emi.arc-ce.sl5.x86_64-1.1.0 ==
== emi.arc-ce.sl5.x86_64  ==


*'''Additional Details:''' No issues found during EGI's Software Provisioning.  
*'''Additional Details:''' No issues found during EGI's Software Provisioning.  
**Detailed release notes: http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-8-14-10-2011
*'''Installation Notes:''' 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.  
*'''Known Issues:'''  
**org.arc.LFC-ops Nagios probe fails, there's a ticket for Nagios with patch to be applied to NGI Nagios when ARC is being checked: https://ggus.eu/tech/ticket_show.php?ticket=72260
*'''Version:''' 1.1.0-1
*'''Version:''' 1.1.0-1


<br>  
<br>  


== emi.arc-client.sl5.x86_64-1.1.0 ==
== emi.arc-client.sl5.x86_64  ==


*'''Additional Details:''' No issues found during EGI's Software Provisioning.  
*'''Additional Details:''' No issues found during EGI's Software Provisioning.  
**Detailed release notes: http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-8-14-10-2011
*'''Installation Notes:''' 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.  
*'''Known Issues:''' No issues found during EGI's Software Provisioning.  
Line 23: Line 28:
<br>  
<br>  


== emi.arc-infosys.sl5.x86_64-1.1.0 ==
== emi.arc-infosys.sl5.x86_64  ==


*'''Additional Details:''' No issues found during EGI's Software Provisioning.  
*'''Additional Details:''' No issues found during EGI's Software Provisioning.  
**Detailed release notes: http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-8-14-10-2011
*'''Installation Notes:''' 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.  
*'''Known Issues:''' Documentation improvements are still needed.  
Line 32: Line 38:
<br>  
<br>  


== emi.argus.sl5.x86_64-1.4.0 ==
== emi.argus.sl5.x86_64  ==


*'''Additional Details:'''  
*'''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.  
**Detailed release notes: http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-7-22-09-2011
**The Argus services have now a memory limit set (PAP 256MB, PDP 256MB, PEP Server 128MB).
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
**The Argus services have a new production configuration for the log files:  
*'''Known Issues:'''
***Daily log files rotating (midnight) or when the file size &gt;= 100MB.
**JavaOutofMemoy problem: https://ggus.eu/tech/ticket_show.php?ticket=75290
***Rotated log files are gzipped.
**Solution: Increase the memory limit to &gt;= 512MB in /etc/sysconfig/argus-pepd and restart the service
***Log files are keep for 90 days.
 
#grep JOPT /etc/sysconfig/argus-pepd
PEPD_JOPTS="-Xmx512M"
#/etc/init.d/argus-pepd restart


*'''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:''' No issues found during EGI's Software Provisioning.
*'''Version:''' 1.4.0
*'''Version:''' 1.4.0


<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:'''  
*'''Installation Notes:''' The BDII should be reconfigured so that the updated configuration is run.  
**Detailed release notes: http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-6-01-09-2011
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Known Issues:'''  
*'''Known Issues:'''  
**If bdii (or slapd) crashes regularly, it's advisable to manually install openldap 2.4 provided in the UMD repository:
**If bdii (or slapd) crashes regularly, it's advisable to manually install openldap 2.4 provided in the UMD repository:
Line 65: Line 71:
*'''Version:''' 1.0.1
*'''Version:''' 1.0.1


<br>
<br>  


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


*'''Additional Details:''' The BDII should be reconfigured so that the updated configuration is run.  
*'''Additional Details:'''  
**Detailed release notes: http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-6-01-09-2011
*'''Installation Notes:''' /etc/cron.hourly/generate-fcr-exclude-file. This file does not exist in the topbdii after install and yaim configuration.  
*'''Installation Notes:''' /etc/cron.hourly/generate-fcr-exclude-file. This file does not exist in the topbdii after install and yaim configuration.  
**A workaround is needed. Savannah ticket: https://savannah.cern.ch/bugs/?84232  
**A workaround is needed. Savannah ticket: https://savannah.cern.ch/bugs/?84232  
*'''Known Issues:'''
*'''Known Issues:'''  
**Missing /etc/bdii/gip/glite-info-site-defaults.conf: https://ggus.eu/tech/ticket_show.php?ticket=72561
**workaround to protect OSG: EMI-1 top-level BDII instances are creating a high load on the MyOSG portal at the beginning of each hour, which threatens the stability of the portal. The trouble comes from this hourly cron job: /etc/cron.hourly/glite-info-update-endpoints The BDII developers have been asked to produce a fix ASAP. In the meantime, if your top-level BDII has that cron job, please insert a random sleep into the script like this (lines wrapped for readability):
#!/bin/sh
perl -e 'sleep rand 3300'
/usr/bin/glite-info-update-endpoints -c /etc/glite/glite-info-update-endpoints.conf > \
/var/log/glite/glite-info-update-endpoints.log 2>&1
**Missing /etc/bdii/gip/glite-info-site-defaults.conf: https://ggus.eu/tech/ticket_show.php?ticket=72561  
**Workaround: Check if the file exists and it's contents. If it's missing do:
**Workaround: Check if the file exists and it's contents. If it's missing do:
  echo "SITE_NAME=<YOUR SITE NAME>" > /etc/bdii/gip/glite-info-site-defaults.conf
 
  echo "SITE_NAME=&lt;YOUR SITE NAME&gt;" &gt; /etc/bdii/gip/glite-info-site-defaults.conf
 
*'''Version:''' 1.0.1
*'''Version:''' 1.0.1


<br>
== emi.dcache.sl5.x86_64  ==


== emi.dcache.sl5.x86_64-1.9.14  ==
*'''Additional Details:''' No issues found during EGI's Software Provisioning.  
 
**Detailed release notes: http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-8-14-10-2011
*'''Additional Details:'''  
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
**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.  
*'''Known Issues:''' No issues found during EGI's Software Provisioning.  
*'''Version:''' 1.9.12-10
*'''Version:''' 1.9.12-10
Line 92: Line 102:
<br>  
<br>  


== emi.glexec_wn.sl5.x86_64-1.0.1 ==
== emi.glexec_wn.sl5.x86_64  ==


*'''Additional Details:'''  
*'''Additional Details:''' No issues found during EGI's Software Provisioning.  
**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.  
**Detailed release notes: http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-7-22-09-2011
**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.  
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Known Issues:''' No issues found during EGI's Software Provisioning.  
*'''Known Issues:''' No issues found during EGI's Software Provisioning.  
Line 107: Line 112:
<br>  
<br>  


== emi.unicore-client.sl5.x86_64-6.4.1 ==
== emi.unicore-client.sl5.x86_64  ==


*'''Additional Details:'''  
*'''Additional Details:''' No issues found during EGI's Software Provisioning.
**Missing filetransfer parameters (e.g. client host for UFTP) are automatically set.
**Detailed release notes: http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-7-22-09-2011
**The "append" option (-a) is now also available for "get-file".
*'''Installation Notes:''' 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.  
*'''Known Issues:''' No issues found during EGI's Software Provisioning.  
Line 118: Line 122:
<br>  
<br>  


== emi.unicore-tsi.sl5.x86_64-6.4.1 ==
== emi.unicore-tsi.sl5.x86_64  ==


*'''Additional Details:'''  
*'''Additional Details:''' No issues found during EGI's Software Provisioning.
**Submit.pm: handle TSI_STDERR and TSI_STDOUT sent from XNJS for redirecting output and error.  
**Detailed release notes: http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-7-22-09-2011
**Fix: Torque: GetStatusListing.pm now handles non-word characters in queue name.
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
**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.  
*'''Known Issues:''' No issues found during EGI's Software Provisioning.  
*'''Version:''' 6.4.1
*'''Version:''' 6.4.1
Line 131: Line 132:
<br>  
<br>  


== emi.unicorex.sl5.x86_64-6.4.1 ==
== emi.unicorex.sl5.x86_64  ==


*'''Additional Details:'''  
*'''Additional Details:''' No issues found during EGI's Software Provisioning.
**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).  
**Detailed release notes: http://www.eu-emi.eu/emi-1-kebnekaise-updates/-/asset_publisher/Ir6q/content/update-7-22-09-2011
*'''Installation Notes:''' After updating the libraries, the UNICORE/X server must be restarted.  
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Known Issues:''' No issues found during EGI's Software Provisioning.  
*'''Known Issues:''' No issues found during EGI's Software Provisioning.  
*'''Version:''' 6.4.1
*'''Version:''' 6.4.1
Line 141: Line 142:
<br>  
<br>  


== ige.globus-gridftp.sl5.x86_64-5.0.4 ==
== ige.globus-gridftp.sl5.x86_64  ==


*'''Additional Details:''' No issues found during EGI's Software Provisioning.
*'''Additional Details:''' No issues found during EGI's Software Provisioning.  
*'''Installation Notes:''' 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.
*'''Known Issues:''' No issues found during EGI's Software Provisioning.  
*'''Version:''' 5.0.4
*'''Version:''' 5.0.4


<br>  
<br>  


== ige.globus-rls.sl5.x86_64-5.0.4 ==
== ige.globus-rls.sl5.x86_64  ==


*'''Additional Details:''' No issues found during EGI's Software Provisioning.
*'''Additional Details:''' No issues found during EGI's Software Provisioning.  
*'''Installation Notes:''' 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.
*'''Known Issues:''' No issues found during EGI's Software Provisioning.  
*'''Version:''' 5.0.4
*'''Version:''' 5.0.4


<br>  
<br>
 
 
[[Category:UMD]]

Latest revision as of 11:42, 21 January 2015

Alert.png This article is Deprecated and should no longer be used, but is still available for reasons of reference.



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


emi.arc-client.sl5.x86_64


emi.arc-infosys.sl5.x86_64


emi.argus.sl5.x86_64

#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

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

  • Additional Details:
  • Installation Notes: /etc/cron.hourly/generate-fcr-exclude-file. This file does not exist in the topbdii after install and yaim configuration.
  • Known Issues:
    • workaround to protect OSG: EMI-1 top-level BDII instances are creating a high load on the MyOSG portal at the beginning of each hour, which threatens the stability of the portal. The trouble comes from this hourly cron job: /etc/cron.hourly/glite-info-update-endpoints The BDII developers have been asked to produce a fix ASAP. In the meantime, if your top-level BDII has that cron job, please insert a random sleep into the script like this (lines wrapped for readability):
#!/bin/sh
perl -e 'sleep rand 3300'
/usr/bin/glite-info-update-endpoints -c /etc/glite/glite-info-update-endpoints.conf > \
/var/log/glite/glite-info-update-endpoints.log 2>&1
echo "SITE_NAME=<YOUR SITE NAME>" > /etc/bdii/gip/glite-info-site-defaults.conf
  • Version: 1.0.1

emi.dcache.sl5.x86_64


emi.glexec_wn.sl5.x86_64


emi.unicore-client.sl5.x86_64


emi.unicore-tsi.sl5.x86_64


emi.unicorex.sl5.x86_64


ige.globus-gridftp.sl5.x86_64

  • 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

  • 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