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.1.0"

From EGIWiki
Jump to navigation Jump to search
Line 15: Line 15:
== emi.mpi.sl5.x86_64  ==
== emi.mpi.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:''' It has been seen that CREAM/torque + MAUI is not able to execute parallel jobs when it requested more than one processor. It seems there is a bug that it had been corrected but it has appeared again. More information about the bug can be found on GGUS Ticket: https://ggus.eu/ws/ticket_info.php?ticket=57828
*'''Known Issues:''' It has been seen that CREAM/torque + MAUI is not able to execute parallel jobs when it requested more than one processor. It seems there is a bug that it had been corrected but it has appeared again. More information about the bug can be found on GGUS Ticket: https://ggus.eu/ws/ticket_info.php?ticket=57828
This is a torque/maui problem that affects to MPI jobs but is not exclusive of that kind of jobs.  
This is a torque/maui problem that affects to MPI jobs but is not exclusive of that kind of jobs.  
**Fine grained process mapping is not supported with Slurm or Condor schedulers.
 
**Fine grained process mapping is not supported with Slurm or Condor schedulers.  
**Shared filesystem detection only works in Linux.
**Shared filesystem detection only works in Linux.


 
<br> <br>  
<br>  


== emi.unicore-uvos.sl5.x86_64  ==
== emi.unicore-uvos.sl5.x86_64  ==
Line 35: Line 36:
== emi.storm.sl5.x86_64  ==
== emi.storm.sl5.x86_64  ==


*'''Additional Details:'''  
*'''Additional Details:''' No issues found during EGI's Software Provisioning.
*'''Installation Notes:''' Minor bugs found during the verification process:  
*'''Installation Notes:''' Minor 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 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 protocols in lcg-gt do not give proper srm error, and fills the frontend logs: https://ggus.org/tech/ticket_show.php?ticket=72464  
**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  
*'''Known Issues:'''
*'''Known Issues:''' No issues found during EGI's Software Provisioning.


<br>  
<br>  
Line 52: Line 53:
*'''Known Issues:''' Minor Issues found:  
*'''Known Issues:''' Minor 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  
**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.
***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.
**Due to faulty DNS over IPv6 resolution in the c-ares library (v. 1.6.0), L&amp;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.
**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.


Line 60: Line 61:
== emi.wms.sl5.x86_64  ==
== emi.wms.sl5.x86_64  ==


*'''Additional Details:'''This release still contains the issue with respect to proxies signed by EMI VOMS (is solved in EMI 1 update 4 not included in this UMD release). Current workaround is to install the voms server certificates for the new installed or upgraded voms servers. This implies that the repository has to include the package including this certificates ( as it was for lcg-vomscerts) and the NGIs have to supply it as well with their custom servers.
*'''Additional Details:'''This release still contains the issue with respect to proxies signed by EMI VOMS (is solved in EMI 1 update 4 not included in this UMD release). Current workaround is to install the voms server certificates for the new installed or upgraded voms servers. This implies that the repository has to include the package including this certificates ( as it was for lcg-vomscerts) and the NGIs have to supply it as well with their custom servers.  
*'''Installation Notes:'''
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.
*'''Known Issues:'''
*'''Known Issues:'''  
** User Documentation Some links are not working. API doc not available. GGUS ticket: https://ggus.eu/tech/ticket_show.php?ticket=71065
**User Documentation Some links are not working. API doc not available. GGUS ticket: https://ggus.eu/tech/ticket_show.php?ticket=71065  
** Proxy renewal fails in ICE: https://savannah.cern.ch/bugs/?84155
**Proxy renewal fails in ICE: https://savannah.cern.ch/bugs/?84155

Revision as of 15:07, 26 July 2011

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.


emi.mpi.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 has been seen that CREAM/torque + MAUI is not able to execute parallel jobs when it requested more than one processor. It seems there is a bug that it had been corrected but it has appeared again. More information about the bug can be found on GGUS Ticket: https://ggus.eu/ws/ticket_info.php?ticket=57828

This is a torque/maui problem that affects to MPI jobs but is not exclusive of that kind of jobs.

    • Fine grained process mapping is not supported with Slurm or Condor schedulers.
    • Shared filesystem detection only works in Linux.



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.storm.sl5.x86_64

  • Additional Details: No issues found during EGI's Software Provisioning.
  • Installation Notes: Minor bugs found during the verification process:
  • Known Issues: No issues found during EGI's Software Provisioning.


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.2 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: Minor 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.


emi.wms.sl5.x86_64

  • Additional Details:This release still contains the issue with respect to proxies signed by EMI VOMS (is solved in EMI 1 update 4 not included in this UMD release). Current workaround is to install the voms server certificates for the new installed or upgraded voms servers. This implies that the repository has to include the package including this certificates ( as it was for lcg-vomscerts) and the NGIs have to supply it as well with their custom servers.
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues:
Retrieved from "https://wiki.egi.eu/w/index.php?title=UMD-1_UMD-1.1.0&oldid=22143"