Difference between revisions of "UMD-1 UMD-1.0.0"
(50 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
= ''' | {{Template:Deprecated}} | ||
= '''UMD 1.0: Additional information for provided products'''<br> = | |||
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 [http://repository.egi.eu/ this release] of UMD. | |||
== emi.ui.sl5.x86_64 == | == emi.ui.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:''' | ||
*'''Known Issues:''' | *'''Known Issues:''' | ||
**before using lcg-* commands users must export CSEC_NOTHREAD: | **before using lcg-* commands users must export CSEC_NOTHREAD: | ||
*** #export CSEC_NOTHREAD=1 | |||
**dCache clients (srm* commands) need to use Oracle/Sun JDK. Oracle/Sun JDK is the default java installed on the node. | **dCache clients (srm* commands) need to use Oracle/Sun JDK. Oracle/Sun JDK is the default java installed on the node. | ||
**LCG_GFAL_INFOSYS | **lcg_utils/GFAL bug: LCG_GFAL_INFOSYS with list of 2 or more topBDIIs returns an error message: No such file or directory | ||
***GGUS Ticket: https://ggus.eu/tech/ticket_show.php?ticket=72196 | ***GGUS Ticket: https://ggus.eu/tech/ticket_show.php?ticket=72196 | ||
***Workaround is to use only 1 topBDII host: | ***Workaround is to use only 1 topBDII host: | ||
***# $export LCG_GFAL_INFOSYS=<TOP_BDII_HOST>:<PORT> | |||
** Due to the buggy libtar library which is dynamically linked to glite-wms-job-submit command some of the input files in InputSandbox are not transfered correctly to WMS depending on the length of LB hostname in JobID. | |||
***https://ggus.eu/tech/ticket_show.php?ticket=76867 | |||
***Quick workaround is to add some characters to filenames of input files if needed. But it's a bit tricky because WMS can randomly include '_' character(s) to JobID and they are translated to '_5f' sequence. | |||
<br> | |||
<br> | |||
== emi.apel.sl5.x86_64 == | == emi.apel.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:''' | ||
**Mysql server must be installed and Mysql root passwd must be set before yaim configuration: | **Mysql server must be installed and Mysql root passwd must be set before yaim configuration: | ||
Line 46: | Line 37: | ||
*'''Known Issues:''' | *'''Known Issues:''' | ||
**Problems publishing data to central apel server: | **Problems publishing data to central apel server: | ||
**GGUS ticket: https://ggus.eu/ws/ticket_info.php?ticket=71814 | ***GGUS ticket: https://ggus.eu/ws/ticket_info.php?ticket=71814 | ||
**Workaround is to change the timeout to a higher number: in /opt/glite/etc/glite-apel-publisher/publisher-config-yaim.xml. By default, it is set to 30 minutes (1800000 milliseconds), extending it, for example, to 7200000. | ***Workaround is to change the timeout to a higher number: in /opt/glite/etc/glite-apel-publisher/publisher-config-yaim.xml. By default, it is set to 30 minutes (1800000 milliseconds), extending it, for example, to 7200000. | ||
<br> | <br> | ||
Line 54: | Line 44: | ||
== emi.argus.sl5.x86_64 == | == emi.argus.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:''' | ||
**In case of reinstallation, save your policy in a file to be loaded later with “pap-admin apf”. In case policy cache stands for a while, once policies are loaded don’t forgot to reload policies and clear pdp cache responses with: | **In case of reinstallation, save your policy in a file to be loaded later with “pap-admin apf”. In case policy cache stands for a while, once policies are loaded don’t forgot to reload policies and clear pdp cache responses with: | ||
Line 70: | Line 60: | ||
**Argus encoding of roles/groups in gridmapdir links differs from that of CEs: https://ggus.org/tech/ticket_show.php?ticket=71548 | **Argus encoding of roles/groups in gridmapdir links differs from that of CEs: https://ggus.org/tech/ticket_show.php?ticket=71548 | ||
**Argus does not update time of gridmapdir links: https://ggus.org/tech/ticket_show.php?ticket=71550 | **Argus does not update time of gridmapdir links: https://ggus.org/tech/ticket_show.php?ticket=71550 | ||
**Argus NRPE restart commands hard-code erroneous init.d scripts: https://ggus.org/tech/ticket_show.php?ticket=72328 | **Argus NRPE restart commands hard-code erroneous init.d scripts: https://ggus.org/tech/ticket_show.php?ticket=72328 | ||
<br> | |||
== emi.bdii-site.sl5.x86_64 == | == emi.bdii-site.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:''': | ||
* | **Bug in UMD-1 glite-yaim-bdii-4.3.3, site-BDII and top-BDII correctly are not correctly configured. The bdii service is not available after a reboot due to a bug in /opt/glite/yaim/functions/config_bdii_5.2: the bdii service is just configured with: | ||
/sbin/chkconfig --add bdii | |||
As the chkconfig-documentation states, this statement does *NOT* lead to the service being started at boot time. An addidtional "chkconfig bdii on" is needed to do this. The quick fix is to do after yaim configuration: | |||
/sbin/chkconfig bdii on | |||
<br> | ***https://ggus.eu/tech/ticket_show.php?ticket=71455 and https://ggus.eu/tech/ticket_show.php?ticket=74166 | ||
***The fix has been done in EMI update 6, and as such will be integrated into next release of UMD1.3 | |||
**It has been observed in a production site bdii a very high CPU consumption leading to unresponsiveness to ldap queries: | |||
***The issue is under investigation. | |||
***Possible mitigation of the issue is to use openldap2.4: | |||
yum install openldap2.4.x86_64 openldap2.4-servers.x86_64 | |||
SLAPD=/usr/sbin/slapd2.4 # add this variable in your site-info.def | |||
chkconfig bdii on | |||
<br> | |||
== emi.bdii-top.sl5.x86_64 == | == emi.bdii-top.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:''' | ||
**Bug in UMD-1 glite-yaim-bdii-4.3.3, site-BDII and top-BDII correctly are not correctly configured. The bdii service is not available after a reboot due to a bug in /opt/glite/yaim/functions/config_bdii_5.2: the bdii service is just configured with: | |||
/sbin/chkconfig --add bdii | |||
As the chkconfig-documentation states, this statement does *NOT* lead to the service being started at boot time. An addidtional "chkconfig bdii on" is needed to do this. The quick fix is to do after yaim configuration: | |||
/sbin/chkconfig bdii on | |||
***https://ggus.eu/tech/ticket_show.php?ticket=71455 and https://ggus.eu/tech/ticket_show.php?ticket=74166 | |||
***The fix has been done in EMI update 6, and as such will be integrated into next release of UMD1.3 | |||
**GLUE2EndpointImplementationVersion: yaim | **GLUE2EndpointImplementationVersion: yaim | ||
***It is incorrect when querying the Glue2 resource info | ***It is incorrect when querying the Glue2 resource info | ||
<br> | <br> | ||
== emi.cream.sl5.x86_64 == | == emi.cream.sl5.x86_64 == | ||
Line 111: | Line 127: | ||
**In case of shared VO software area, create a blank config_cream_vo_tag_dir function in /opt/glite/yaim/functions/local/ dir | **In case of shared VO software area, create a blank config_cream_vo_tag_dir function in /opt/glite/yaim/functions/local/ dir | ||
<br> | |||
== emi.cluster.sl5.x86_64 == | == emi.cluster.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:'''No issues found during EGI's Software Provisioning | ||
<br> | <br> | ||
== emi. | == emi.lsf-utils.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:''' | ||
** | **Dynamic info lsf uninitialized value on an EMI Cream-CE. GGUS: https://ggus.eu/ws/ticket_info.php?ticket=71613. | ||
**In /var/log/bdii/bdii-update.log displays this "warning" (Use of uninitialized value in concatenation (.) or string at /usr/bin/glite-info-dynamic-lsf line 1027 (#1)). To suppress this warning assign a defined value to your variables. | **In /var/log/bdii/bdii-update.log displays this "warning" (Use of uninitialized value in concatenation (.) or string at /usr/bin/glite-info-dynamic-lsf line 1027 (#1)). To suppress this warning assign a defined value to your variables. | ||
<br> | <br> | ||
== emi. | == emi.torque-utils.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:'''No issues found during EGI's Software Provisioning<br> | ||
<br> | <br> | ||
== | == emi.torque-client.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 | |||
<br> | |||
<br> | <br> | ||
Line 153: | Line 167: | ||
== emi.torque-server.sl5.x86_64 == | == emi.torque-server.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:'''No issues found during EGI's Software Provisioning<br> | ||
<br> | <br> | ||
Line 162: | Line 175: | ||
== emi.dgas.sl5.x86_64 == | == emi.dgas.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:'''No issues found during EGI's Software Provisioning<br> | ||
<br> | <br> | ||
== emi.dpm.sl5.x86_64 == | == emi.dpm.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:''' | ||
**Correct metapackage is: | **Correct metapackage is: | ||
Line 186: | Line 198: | ||
**Workaround is to use a different edgusers.conf (set variable EDGUSERS in site-info.def) | **Workaround is to use a different edgusers.conf (set variable EDGUSERS in site-info.def) | ||
*'''Known Issues:''' | *'''Known Issues:''' | ||
**After yaim runs manually set “chkconfig bdii on” and “chkconfig ldap on” | **After yaim runs manually set “chkconfig bdii on” and “chkconfig ldap on” | ||
<br> | |||
<br> | <br> | ||
Line 193: | Line 206: | ||
== emi.glexec_wn.sl5.x86_64 == | == emi.glexec_wn.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:''' | ||
**Run ldconfig after each update, as the packages don't seem to do this by themselves. | **Run ldconfig after each update, as the packages don't seem to do this by themselves. | ||
Line 202: | Line 215: | ||
*'''Known Issues:''' | *'''Known Issues:''' | ||
**This version of C-PEP needs to be tested more on root-squashed environments. | **This version of C-PEP needs to be tested more on root-squashed environments. | ||
**The verify-proxy plugins fails to verify Terena eScience Personal certificate chains deeper then 5 certificates. 5 is ok, 6 is not. | **The verify-proxy plugins fails to verify Terena eScience Personal certificate chains deeper then 5 certificates. 5 is ok, 6 is not. | ||
<br> | <br> | ||
Line 211: | Line 221: | ||
== emi.lb.sl5.x86_64 == | == emi.lb.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:''' | ||
**Job registration has been proven to work correctly with an EMI WMS and a glite3. | **Job registration has been proven to work correctly with an EMI WMS and a glite3.1 WMS. | ||
**bdii is | **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 | ||
***use ''/sbin/service bdii restart'' to start bdii service | ***If needed, use ''/sbin/service bdii restart'' to start bdii service. | ||
*'''Known Issues:''' | *'''Known Issues:''' | ||
**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. | **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.<br> | ||
<br> | <br> | ||
Line 224: | Line 233: | ||
== emi.voms_mysql.sl5.x86_64 == | == emi.voms_mysql.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:''' | ||
**The VO AUPs (for example https://<VOMS_HOST>:8443/voms/<VO>/aup/load.action) aren't shown because voms-admin is still pointing to a path that doesn't exist any more: /var/glite/etc/voms-admin/<VO>/vo-aup.txt.. | **The VO AUPs (for example https://<VOMS_HOST>:8443/voms/<VO>/aup/load.action) aren't shown because voms-admin is still pointing to a path that doesn't exist any more: /var/glite/etc/voms-admin/<VO>/vo-aup.txt.. | ||
Line 232: | Line 241: | ||
mysql> select * from aup_version; | mysql> select * from aup_version; | ||
mysql> update aup_version set url="file:/etc/voms-admin/<VO>/vo-aup.txt" where url="file:/var/glite/etc/voms-admin/<VO>/vo-aup.txt"; | mysql> update aup_version set url="file:/etc/voms-admin/<VO>/vo-aup.txt" where url="file:/var/glite/etc/voms-admin/<VO>/vo-aup.txt"; | ||
<br> | <br> | ||
Line 239: | Line 246: | ||
== emi.wn.sl5.x86_64 == | == emi.wn.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:''' | ||
**Python-ldap package missing: | **Python-ldap package missing: | ||
***GGUS ticket: https://ggus.org/tech/ticket_show.php?ticket=71167 | ***GGUS ticket: https://ggus.org/tech/ticket_show.php?ticket=71167 | ||
Line 255: | Line 262: | ||
#update-alternatives --install /usr/bin/java java /usr/java/default/bin/java 2000 \ | #update-alternatives --install /usr/bin/java java /usr/java/default/bin/java 2000 \ | ||
--slave /usr/bin/keytool keytool /usr/java/default/bin/keytool \ | |||
--slave /usr/bin/rmiregistry rmiregistry /usr/java/default/bin/rmiregistry \ | |||
--slave /usr/lib/jvm/jre jre /usr/java/default/jre | |||
**WN does not pass org.sam.WN-SoftVer test: | **WN does not pass org.sam.WN-SoftVer test: | ||
***GGUS ticket:https://ggus.eu/ws/ticket_info.php?ticket=71723 | ***GGUS ticket:https://ggus.eu/ws/ticket_info.php?ticket=71723 | ||
***No workaround at the moment: waiting for SAM Update-12. | ***No workaround at the moment: waiting for SAM Update-12.<br> | ||
<br> | <br> | ||
Line 268: | Line 274: | ||
== emi.unicore-gateway.sl5.x86_64 == | == emi.unicore-gateway.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:'''No issues found during EGI's Software Provisioning<br> | ||
<br> | |||
<br> | <br> | ||
Line 279: | Line 282: | ||
== emi.unicore-client.sl5.x86_64 == | == emi.unicore-client.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:'''No issues found during EGI's Software Provisioning<br> | ||
<br> | |||
<br> | <br> | ||
Line 290: | Line 290: | ||
== emi.unicore-hila.sl5.x86_64 == | == emi.unicore-hila.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:''' | ||
** | **HiLA shell doesn't write log files, messages are displayed directly in the command line.<br> | ||
<br> | |||
<br> | <br> | ||
Line 302: | Line 299: | ||
== emi.unicore-xuudb.sl5.x86_64 == | == emi.unicore-xuudb.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:'''No issues found during EGI's Software Provisioning<br> | ||
<br> | |||
<br> | <br> | ||
Line 312: | Line 307: | ||
== emi.unicore-uvos.sl5.x86_64 == | == emi.unicore-uvos.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:'''No issues found during EGI's Software Provisioning | ||
<br> | <br> | ||
== emi.unicore-ws | == emi.unicore-ws.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:'''No issues found during EGI's Software Provisioning | ||
<br> | <br> | ||
Line 331: | Line 323: | ||
== emi.unicore-tsi.sl5.x86_64 == | == emi.unicore-tsi.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:'''No issues found during EGI's Software Provisioning<br> | ||
<br> | <br> | ||
Line 340: | Line 331: | ||
== emi.proxyrenewal.sl5.x86_64 == | == emi.proxyrenewal.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:''' | ||
**It is worth noting that MyProxy in its standard setup generates usage statistics and sends that information to MyProxy developers (outside the scope of EMI). | **It is worth noting that MyProxy in its standard setup generates usage statistics and sends that information to MyProxy developers (outside the scope of EMI).<br> | ||
<br> | <br> | ||
Line 351: | Line 341: | ||
*'''Additional Details:''' This package is included into ARGUS product. Read ARGUS release notes for further information. | *'''Additional Details:''' This package is included into ARGUS product. Read ARGUS release notes for further information. | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:'''No issues found during EGI's Software Provisioning<br> | ||
<br> | <br> | ||
Line 359: | Line 348: | ||
== emi.unicore-registry.sl5.x86_64 == | == emi.unicore-registry.sl5.x86_64 == | ||
*'''Additional Details:''' | *'''Additional Details:'''No issues found during EGI's Software Provisioning | ||
*'''Installation Notes:''' | *'''Installation Notes:'''No issues found during EGI's Software Provisioning | ||
*'''Known Issues:''' | *'''Known Issues:'''No issues found during EGI's Software Provisioning<br> | ||
<br> | <br> | ||
== emi.arc- | == emi.arc-client.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:''' | |||
**arctest can not find targets, reports bogus error: http://bugzilla.nordugrid.org/cgi-bin/bugzilla/show_bug.cgi?id=2423<br> | |||
<br> | |||
== emi.lfc_mysql.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 | |||
<br> | |||
Latest revision as of 12:45, 21 January 2015
![]() |
UMD 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.ui.sl5.x86_64
- Additional Details:No issues found during EGI's Software Provisioning
- Installation Notes:
- Known Issues:
- before using lcg-* commands users must export CSEC_NOTHREAD:
- #export CSEC_NOTHREAD=1
- dCache clients (srm* commands) need to use Oracle/Sun JDK. Oracle/Sun JDK is the default java installed on the node.
- lcg_utils/GFAL bug: LCG_GFAL_INFOSYS with list of 2 or more topBDIIs returns an error message: No such file or directory
- GGUS Ticket: https://ggus.eu/tech/ticket_show.php?ticket=72196
- Workaround is to use only 1 topBDII host:
- $export LCG_GFAL_INFOSYS=<TOP_BDII_HOST>:<PORT>
- Due to the buggy libtar library which is dynamically linked to glite-wms-job-submit command some of the input files in InputSandbox are not transfered correctly to WMS depending on the length of LB hostname in JobID.
- https://ggus.eu/tech/ticket_show.php?ticket=76867
- Quick workaround is to add some characters to filenames of input files if needed. But it's a bit tricky because WMS can randomly include '_' character(s) to JobID and they are translated to '_5f' sequence.
- before using lcg-* commands users must export CSEC_NOTHREAD:
emi.apel.sl5.x86_64
- Additional Details:No issues found during EGI's Software Provisioning
- Installation Notes:
- Mysql server must be installed and Mysql root passwd must be set before yaim configuration:
#yum install mysql-server #service mysqld start #chkconfig --level 345 mysqld on #Mysqladmin –u root password ‘<a-good-password>’
- Known Issues:
- Problems publishing data to central apel server:
- GGUS ticket: https://ggus.eu/ws/ticket_info.php?ticket=71814
- Workaround is to change the timeout to a higher number: in /opt/glite/etc/glite-apel-publisher/publisher-config-yaim.xml. By default, it is set to 30 minutes (1800000 milliseconds), extending it, for example, to 7200000.
- Problems publishing data to central apel server:
emi.argus.sl5.x86_64
- Additional Details:No issues found during EGI's Software Provisioning
- Installation Notes:
- In case of reinstallation, save your policy in a file to be loaded later with “pap-admin apf”. In case policy cache stands for a while, once policies are loaded don’t forgot to reload policies and clear pdp cache responses with:
/etc/init.d/argus-pdp reloadpolicy /etc/init.d/argus-pepd clearcache
- YAIM function for a minimal working configuration (based on traditional CE authorization config) does not exist yet.
- Workaround: a script was proposed http://wwwae.ciemat.es/~delgadop/from-groupmap-to-policy.sh
- Added to a deployment twiki: https://twiki.cern.ch/twiki/bin/view/LCG/GlexecDeployment
- Known Issues:
- The PAP authorization configuration parser does not support kerberized style DN like, "/DC=country/DC=DC/O=organization/CN=host/host_name": https://ggus.eu/dmsu/dmsu_ticket.php?ticket=69841.
- The common EMI XACML profile is not yet finalize, and not yet implemented by Argus.
- Argus does not encode hyphens in gridmapdir links as CEs: https://ggus.org/tech/ticket_show.php?ticket=71547
- Argus encoding of roles/groups in gridmapdir links differs from that of CEs: https://ggus.org/tech/ticket_show.php?ticket=71548
- Argus does not update time of gridmapdir links: https://ggus.org/tech/ticket_show.php?ticket=71550
- Argus NRPE restart commands hard-code erroneous init.d scripts: https://ggus.org/tech/ticket_show.php?ticket=72328
emi.bdii-site.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::
- Bug in UMD-1 glite-yaim-bdii-4.3.3, site-BDII and top-BDII correctly are not correctly configured. The bdii service is not available after a reboot due to a bug in /opt/glite/yaim/functions/config_bdii_5.2: the bdii service is just configured with:
/sbin/chkconfig --add bdii
As the chkconfig-documentation states, this statement does *NOT* lead to the service being started at boot time. An addidtional "chkconfig bdii on" is needed to do this. The quick fix is to do after yaim configuration:
/sbin/chkconfig bdii on
- https://ggus.eu/tech/ticket_show.php?ticket=71455 and https://ggus.eu/tech/ticket_show.php?ticket=74166
- The fix has been done in EMI update 6, and as such will be integrated into next release of UMD1.3
- It has been observed in a production site bdii a very high CPU consumption leading to unresponsiveness to ldap queries:
- The issue is under investigation.
- Possible mitigation of the issue is to use openldap2.4:
yum install openldap2.4.x86_64 openldap2.4-servers.x86_64 SLAPD=/usr/sbin/slapd2.4 # add this variable in your site-info.def chkconfig bdii on
emi.bdii-top.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:
- Bug in UMD-1 glite-yaim-bdii-4.3.3, site-BDII and top-BDII correctly are not correctly configured. The bdii service is not available after a reboot due to a bug in /opt/glite/yaim/functions/config_bdii_5.2: the bdii service is just configured with:
/sbin/chkconfig --add bdii
As the chkconfig-documentation states, this statement does *NOT* lead to the service being started at boot time. An addidtional "chkconfig bdii on" is needed to do this. The quick fix is to do after yaim configuration:
/sbin/chkconfig bdii on
- https://ggus.eu/tech/ticket_show.php?ticket=71455 and https://ggus.eu/tech/ticket_show.php?ticket=74166
- The fix has been done in EMI update 6, and as such will be integrated into next release of UMD1.3
- GLUE2EndpointImplementationVersion: yaim
- It is incorrect when querying the Glue2 resource info
emi.cream.sl5.x86_64
- Additional Details:
- New yaim variable USE_ARGUS If the value for this variable is yes, ARGUS is used as authorization system for the CREAM CE. If instead the value for this variable is no, the old authorization systems (i.e. gJAF, LCAS, LCMAPS) are used.
- Installation Notes:
- Centos5 specific issue: mm-mysql package depends explicitly on JDK (from Oracle). This makes the installation fail with a dependency problem if JDK is not installed. A workaround is to manually download and install the jdk package from Oracle.
- MYSQL_PASSWORD variable is a mandatory for yaim cream configuration.
- Known Issues:
- http://grid.pd.infn.it/cream/field.php?n=Main.KnownIssues
- Non critical (for the moment), but worth mentioning here:
pbs_mom: LOG_ERROR::Operation now in progress (115) in scan_for_exiting, cannot connect to port 1023 in client_to_svr - connection refused
- In certain cases jobs are aborted immediately after submission (problem identified and being worked on):
- In case of shared VO software area, create a blank config_cream_vo_tag_dir function in /opt/glite/yaim/functions/local/ dir
emi.cluster.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
emi.lsf-utils.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:
- Dynamic info lsf uninitialized value on an EMI Cream-CE. GGUS: https://ggus.eu/ws/ticket_info.php?ticket=71613.
- In /var/log/bdii/bdii-update.log displays this "warning" (Use of uninitialized value in concatenation (.) or string at /usr/bin/glite-info-dynamic-lsf line 1027 (#1)). To suppress this warning assign a defined value to your variables.
emi.torque-utils.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
emi.torque-client.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
emi.torque-server.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
emi.dgas.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
emi.dpm.sl5.x86_64
- Additional Details:No issues found during EGI's Software Provisioning
- Installation Notes:
- Correct metapackage is:
yum install emi-dpm_mysql
- VO default dirs are not created: An issue was found into /etc/cron.monthly/create-default-dirs-DPM.sh script. GGUS ticket: https://ggus.eu/tech/ticket_show.php?ticket=71357. LCG_LOCATION variable is not defined and the script fails to find DPM binaries. To solve this issue DPM administrators MUST define LCG_LOCATION inside create-default-dirs-DPM.sh. As example:
LCG_LOCATION=/usr
- In a fresh install mysql server must be installed before yaim configuration.
- In a fresh install /etc/cron.monthly/create-default-dirs-DPM.sh MUST be executed after yaim configuration.
- SL 5.6 uses user and group ids which cause conflicts with those in /opt/glite/yaim/examples/edgusers.conf (e. g. group avahi-autoipd:x:156: conflicts with group infosys ):
- Workaround is to use a different edgusers.conf (set variable EDGUSERS in site-info.def)
- Known Issues:
- After yaim runs manually set “chkconfig bdii on” and “chkconfig ldap on”
emi.glexec_wn.sl5.x86_64
- Additional Details:No issues found during EGI's Software Provisioning
- Installation Notes:
- Run ldconfig after each update, as the packages don't seem to do this by themselves.
- All services are recommended to be restarted. gLExec is an exception, as it is not a service.
- Glexec yaim plugin contains syntax errors: GGUS ticket: https://ggus.org/tech/ticket_show.php?ticket=71569
- When trying to run the yaim configuration for glexec wn, yaim complains with the following error: /opt/glite/yaim/bin/../defaults/glite-glexec_wn.post: line 66: unexpected EOF while looking for matching `"' /opt/glite/yaim/bin/../defaults/glite-glexec_wn.post: line 77: syntax error: unexpected end of file.
- This issue can be easily fixed using a patch: https://ggus.org/pages/windownload.php?attid=ATT7716
- Known Issues:
- This version of C-PEP needs to be tested more on root-squashed environments.
- The verify-proxy plugins fails to verify Terena eScience Personal certificate chains deeper then 5 certificates. 5 is ok, 6 is not.
emi.lb.sl5.x86_64
- Additional Details:No issues found during EGI's Software Provisioning
- Installation Notes:
- Job registration has been proven to work correctly with an EMI WMS and a glite3.1 WMS.
- 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.
- Known Issues:
- 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.
- 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.
emi.voms_mysql.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:
- The VO AUPs (for example https://<VOMS_HOST>:8443/voms/<VO>/aup/load.action) aren't shown because voms-admin is still pointing to a path that doesn't exist any more: /var/glite/etc/voms-admin/<VO>/vo-aup.txt..
- the workaround proposed for the AUP problem is to update the table.
- The VO AUPs (for example https://<VOMS_HOST>:8443/voms/<VO>/aup/load.action) aren't shown because voms-admin is still pointing to a path that doesn't exist any more: /var/glite/etc/voms-admin/<VO>/vo-aup.txt..
mysql> select * from aup_version; mysql> update aup_version set url="file:/etc/voms-admin/<VO>/vo-aup.txt" where url="file:/var/glite/etc/voms-admin/<VO>/vo-aup.txt";
emi.wn.sl5.x86_64
- Additional Details:No issues found during EGI's Software Provisioning
- Installation Notes:
- Python-ldap package missing:
- GGUS ticket: https://ggus.org/tech/ticket_show.php?ticket=71167
- Python-ldap package is missing, therefore WN probes are not executable.
- Workaround: Installing python-ldap and openldap-clients is enough for WN probes:
- Python-ldap package missing:
yum install python-ldap opendlap-clients
- Known Issues:
- dcache client tools fail with java errors.
- GGUS ticket: https://ggus.org/tech/ticket_show.php?ticket=71198
- Using SUN's JDK instead of gcj solves the issue.
- Configure the default java version to use, e.g:
- dcache client tools fail with java errors.
#update-alternatives --install /usr/bin/java java /usr/java/default/bin/java 2000 \ --slave /usr/bin/keytool keytool /usr/java/default/bin/keytool \ --slave /usr/bin/rmiregistry rmiregistry /usr/java/default/bin/rmiregistry \ --slave /usr/lib/jvm/jre jre /usr/java/default/jre
- WN does not pass org.sam.WN-SoftVer test:
- GGUS ticket:https://ggus.eu/ws/ticket_info.php?ticket=71723
- No workaround at the moment: waiting for SAM Update-12.
- WN does not pass org.sam.WN-SoftVer test:
emi.unicore-gateway.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
emi.unicore-client.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
emi.unicore-hila.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:
- HiLA shell doesn't write log files, messages are displayed directly in the command line.
- HiLA shell doesn't write log files, messages are displayed directly in the command line.
emi.unicore-xuudb.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
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
emi.unicore-ws.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
emi.unicore-tsi.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
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:
- It is worth noting that MyProxy in its standard setup generates usage statistics and sends that information to MyProxy developers (outside the scope of EMI).
- It is worth noting that MyProxy in its standard setup generates usage statistics and sends that information to MyProxy developers (outside the scope of EMI).
emi.argus-ees.sl5.x86_64
- Additional Details: This package is included into ARGUS product. Read ARGUS release notes for further information.
- Installation Notes:No issues found during EGI's Software Provisioning
- Known Issues:No issues found during EGI's Software Provisioning
emi.unicore-registry.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
emi.arc-client.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:
- arctest can not find targets, reports bogus error: http://bugzilla.nordugrid.org/cgi-bin/bugzilla/show_bug.cgi?id=2423
- arctest can not find targets, reports bogus error: http://bugzilla.nordugrid.org/cgi-bin/bugzilla/show_bug.cgi?id=2423
emi.lfc_mysql.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