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 "Agenda-05-11-2012"

From EGIWiki
Jump to navigation Jump to search
Line 21: Line 21:
===2. Operational Issues ===
===2. Operational Issues ===
==== 2.1 Updates from DMSU ====
==== 2.1 Updates from DMSU ====
=== problem in retrieving the job output after EMI2 update 4 (WMS)===
for details see [https://ggus.eu/tech/ticket_show.php?ticket=87802 GGUS 87802]
it seems that if an user never used the myproxy and he isn't currently using it, she can retrieve the output without any problem.
For the other kind of users, the problem occurrs (see the details in that ticket).
* the user proxy is usually stored in the Sandboxdir, but if the user is using the myproxy service, that file is a symlink to the real file stored in the proxy renewal directory (/var/glite/spool/glite-renewd). When the jobs ends, that proxy is purged so that the user hasn't any more the permissions to retrieve the output
* For the moment a simple workaround is to submit a new job, and before its ending, retrieve the output of any previous job.
Moreover it was also noticed that if in the jdl there isn't the variable related to myproxy, in the jdl stored in the Sandboxdir it is wrongly contained that variable set to the myproxy hostname that is set by default on the UI.
Instead if in the jdl it is present an empy variable like the following:
  MyProxyServer = "";
the jdl stored on the WMS will properly contain it, the proxy is stored in the SandBoxDir (no symlink to proxy renewal dir) and the user is able to retrieve the output when the job ends.


===3. AOB ===
===3. AOB ===

Revision as of 10:39, 5 November 2012

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

Detailed agenda: Grid Operations Meeting 22 October 2012

EVO direct link Pwd: gridops
EVO 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 Updates from DMSU

problem in retrieving the job output after EMI2 update 4 (WMS)

for details see GGUS 87802

it seems that if an user never used the myproxy and he isn't currently using it, she can retrieve the output without any problem. For the other kind of users, the problem occurrs (see the details in that ticket).

  • the user proxy is usually stored in the Sandboxdir, but if the user is using the myproxy service, that file is a symlink to the real file stored in the proxy renewal directory (/var/glite/spool/glite-renewd). When the jobs ends, that proxy is purged so that the user hasn't any more the permissions to retrieve the output
  • For the moment a simple workaround is to submit a new job, and before its ending, retrieve the output of any previous job.

Moreover it was also noticed that if in the jdl there isn't the variable related to myproxy, in the jdl stored in the Sandboxdir it is wrongly contained that variable set to the myproxy hostname that is set by default on the UI. Instead if in the jdl it is present an empy variable like the following:

  MyProxyServer = "";

the jdl stored on the WMS will properly contain it, the proxy is stored in the SandBoxDir (no symlink to proxy renewal dir) and the user is able to retrieve the output when the job ends.

3. AOB