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 "Agenda-28-01-2013"
| Line 25: | Line 25: | ||
==== 2.1 Status of unsupported middleware update ==== | ==== 2.1 Status of unsupported middleware update ==== | ||
==== 2.2 Updates from DMSU ==== | ==== 2.2 Updates from DMSU ==== | ||
=== LFC-Oracle problem === | |||
Details [https://ggus.eu/tech/ticket_show.php?ticket=90701 GGUS #90701] | |||
The error is occurring with EMI2 emi-lfc_oracle-1.8.5-1.el5 and Oracle 11: | |||
#lfc-ls lfc-1-kit:/grid | |||
send2nsd: NS002 - send error : client_establish_context: The server had a problem while authenticating our connection | |||
lfc-1-kit:/grid: Could not secure the connection | |||
Experts suspect it is due to the use of Oracle 11 client when the LFC code has been | |||
compiled against the Oracle 10 API. The LFC developers expect | |||
to provide rpms built against Oracle 11 shortly. | |||
=== list-match problem with EMI2 WMS === | |||
Details [https://ggus.eu/tech/ticket_show.php?ticket=90240 GGUS #90240] | |||
Some CEs have enabled only a group or a role in their queues, not the entire VO: | |||
GlueCEAccessControlBaseRule: VOMS:/gridit/ansys | |||
GlueCEAccessControlBaseRule: VOMS:/gridit/ansys/Role=SoftwareManager | |||
so, when your primary attribute is: | |||
attribute : /gridit/ansys/Role=NULL/Capability=NULL | |||
if you use an EMI-2 WMS, you cannot match those resources (instead you can if use EMI-1 WMS) | |||
It seems that the problem is in the value of ''WmsRequirements'' contained the file ''/etc/glite-wms/glite_wms.conf'': the filter set in that variable is different from the one used in the EMI-1 WMS. The developers are investigating on it | |||
=== proxy renewal problems on EMI1 WMS === | |||
Details [https://ggus.eu/tech/ticket_show.php?ticket=89801 GGUS #89801] | |||
Under some circumstances, ICE cannot renew the user credentials due to glite-wms-ice-proxy-renew hanging processes. It is believed that the guilty is this [https://savannah.cern.ch/bugs/index.php?95584 Savannah bug]. | |||
The bug is already solved in EMI2. | |||
=== Problems with aliased DNS names of myproxy === | |||
Details [https://ggus.eu/tech/ticket_show.php?ticket=89105 GGUS #89105] | |||
DNS aliases of myproxy server (i.e. used to implement round-robin | |||
load balance and/or high availability) may cause problems to proxy | |||
renewal when '''all''' DNS aliases, including the canonical name, | |||
are not included in the host certificate of the myproxy server | |||
''SubjectAltNames'' extensions. | |||
The failure may not appear always (it depends on multiple conditions | |||
like versions of globus etc.), however, sites are encouraged | |||
to use certificates which cover all the DNS aliases thoroughly. | |||
=== 3. AOB === | === 3. AOB === | ||
Revision as of 16:01, 25 January 2013
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Detailed agenda: Grid Operations Meeting 07 January 2013
| Audio conference link | No password |
| Audio conference details | Indico page |
1. Middleware releases and staged rollout
1.1. Update on the status of EMI updates
1.2. Staged Rollout
2. Operational Issues
2.1 Status of unsupported middleware update
2.2 Updates from DMSU
LFC-Oracle problem
Details GGUS #90701
The error is occurring with EMI2 emi-lfc_oracle-1.8.5-1.el5 and Oracle 11:
#lfc-ls lfc-1-kit:/grid send2nsd: NS002 - send error : client_establish_context: The server had a problem while authenticating our connection lfc-1-kit:/grid: Could not secure the connection
Experts suspect it is due to the use of Oracle 11 client when the LFC code has been compiled against the Oracle 10 API. The LFC developers expect to provide rpms built against Oracle 11 shortly.
list-match problem with EMI2 WMS
Details GGUS #90240
Some CEs have enabled only a group or a role in their queues, not the entire VO:
GlueCEAccessControlBaseRule: VOMS:/gridit/ansys GlueCEAccessControlBaseRule: VOMS:/gridit/ansys/Role=SoftwareManager
so, when your primary attribute is:
attribute : /gridit/ansys/Role=NULL/Capability=NULL
if you use an EMI-2 WMS, you cannot match those resources (instead you can if use EMI-1 WMS)
It seems that the problem is in the value of WmsRequirements contained the file /etc/glite-wms/glite_wms.conf: the filter set in that variable is different from the one used in the EMI-1 WMS. The developers are investigating on it
proxy renewal problems on EMI1 WMS
Details GGUS #89801
Under some circumstances, ICE cannot renew the user credentials due to glite-wms-ice-proxy-renew hanging processes. It is believed that the guilty is this Savannah bug. The bug is already solved in EMI2.
Problems with aliased DNS names of myproxy
Details GGUS #89105
DNS aliases of myproxy server (i.e. used to implement round-robin load balance and/or high availability) may cause problems to proxy renewal when all DNS aliases, including the canonical name, are not included in the host certificate of the myproxy server SubjectAltNames extensions.
The failure may not appear always (it depends on multiple conditions like versions of globus etc.), however, sites are encouraged to use certificates which cover all the DNS aliases thoroughly.