UMD-1 UMD-1.1.0

From EGIWiki
Jump to: navigation, search
Alert.png This article is Deprecated and should no longer be used, but is still available for reasons of reference.


UMD 1.1.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.proxyrenewal.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: 1.3.21


emi.arc-infosys.sl5.x86_64

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


emi.unicore-uvos.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: 1.4.2


emi.storm.sl5.x86_64

  • Additional Details:
  • Installation Notes: Issues/bugs found during the verification process:
    • Wrong paths for backend logrotate (/var/log/storm/storm-backend* intead of /opt/storm/backend/var/log/storm-backend*): https://ggus.eu/tech/ticket_show.php?ticket=72683
    • Wrong paths for backend cron script, similar to previous point.
    • storm.properties is not correctly generated if it contains hand-made changes.
    • yaim-storm does not create namespace.xml correctly for size due to the use of df.
  • Known Issues:
    • Wrong protocols in lcg-gt do not give proper srm error, and fills the frontend logs: https://ggus.org/tech/ticket_show.php?ticket=72464 . To be solved in the next release.
    • The info system has problems (to be solved in the next release):
      • Incorrectly sets the variables GlueServiceName and GlueServiceType. Fix on config_gip_glue2_storm and config_gip_storm located in /opt/glite/yaim/functions/local.
      • Publishes GlueSAUsedOnlineSize and GlueSAStateUsedSpace as -1 during calculation of the spaces.
      • If the info system is not corrected tests fail.
      • While determining the size of a space token spaces are reported by the info system as -1. This is picked up as critical by GSTAT.
    • The Frontend does not return client IP information due to gsoap library that needs IPv6 enabled: https://ggus.eu/tech/ticket_show.php?ticket=72867
    • The Backend uses du in case of Tape wrongly, publishing wrong size information.
    • By default, if you install the emi.storm.gridhttps-mp package, StoRM will work until a reboot when it will stop working: https://ggus.eu/tech/ticket_show.php?ticket=72845
    • Two of the five EA sites have observed the Frontend crash with segmentation faults, this issues is reported and should be solved in the next release of this component: https://ggus.eu/tech/ticket_show.php?ticket=71437
  • Version: 1.7.0


emi.lb.sl5.x86_64

  • Additional Details: It was tested as a standalone server, and the basic job registration has been proven to work correctly with an EMI WMS and a glite3.1 WMS.
    • Therefore:
      • the lb should not work as a proxy ( don't define the GLITE_LB_TYPE) ,
      • and also define the GLITE_LB_SUPER_USERS variable to allow the access from the WMS node.
  • Installation Notes:
  • Known Issues: Issues found:
    • bdii is started when configured with yaim, but not included in gLiteservices to init upon restart. GGUS ticket: https://ggus.eu/tech/ticket_show.php?ticket=71448
      • If needed, use /sbin/service bdii restart to start bdii service.
    • Due to faulty DNS over IPv6 resolution in the c-ares library (v. 1.6.0), L&B does not work in most scenarios involving IPv6-only machines. Upgrade c-ares to 1.7.3 and relaunch yaim to get full IPv6 functionality.
    • Background purge works and return code is handled correctly. It also results in a clean termination of a slave, though, which is currently reported by the master to syslog with priority 'Error' despite being harmless (The actual wording is 'Slave \d exited with return code 1'). This does not pose a problem, just a false alarm for a person reading the logs.
    • In the case when the LB service is installed on a separate machine from WMS service, and configured to use gLite-3.1 WMS service. With this configuration, job cannot be purged from LB service. From UI machine the following warning message can be observed after output retrieval:
Warning - JobPurging not allowed
 (The Operation is not allowed: Unable to complete job purge)
  • Workaround:
    • This problem is solved by giving ADMIN_ACCESS to the WMS service at LB machine by adding the WMS DN in section action "ADMIN_ACCESS" of /etc/glite-lb/glite-lb-authz.conf file.
  • Version: 3.0.12

emi.bdii-core.sl5.x86_64

  • Additional Details: This is an internal Component for Top-BDII and Site-BDII updated for compatibility with Arc Infosys.
  • Installation Notes: Top-BDII and Site-BDII services should be updated and the services restarted if your site uses ARC-Infosys.
  • Known Issues: See Arc InfoSys known issues above.
  • Version: 5.2.4-1