Документ взят из кэша поисковой машины. Адрес оригинального документа : http://theory.sinp.msu.ru/pipermail/ru-ngi/attachments/20160330/e8f1c32a/attachment.html
Дата изменения: Wed Mar 30 19:46:23 2016
Дата индексирования: Mon Apr 11 01:45:15 2016
Кодировка:

<html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> б б Dear colleagues, please, read the mail below and react if it is necessary. б б б б Regards,б б Andrey. <div class="moz-forward-container"> -------- Forwarded Message -------- <table class="moz-email-headers-table" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject: </th> <td>ATLAS dumps</td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th> <td>Wed, 30 Mar 2016 16:36:34 +0100</td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th> <td>Alessandra Forti <a class="moz-txt-link-rfc2396E" href="mailto:Alessandra.Forti@cern.ch"><Alessandra.Forti@cern.ch></a></td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Reply-To: </th> <td>LCG <a class="moz-txt-link-rfc2396E" href="mailto:lcg@ihep.ru"><lcg@ihep.ru></a></td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th> <td><a class="moz-txt-link-abbreviated" href="mailto:atlas-adc-tier1@cern.ch">atlas-adc-tier1@cern.ch</a>, <a class="moz-txt-link-abbreviated" href="mailto:atlas-adc-tier2@cern.ch">atlas-adc-tier2@cern.ch</a></td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th> <td>atlas-adc-cloud-all (contact for all the ATLAS cloud supports) <a class="moz-txt-link-rfc2396E" href="mailto:atlas-adc-cloud-all@cern.ch"><atlas-adc-cloud-all@cern.ch></a></td> </tr> </tbody> </table> <meta http-equiv="content-type" content="text/html; charset=utf-8"> Dear ATLAS Site Administrators, in the past months all of you have received a ticket asking you to setup a monthly cron to generate dumps so that atlas can perform consistency checks. Most of you replied positively and provided dumps for one or two months, but didn't setup any cron and therefore the system can perform the checks only at the few sites that did setup the cron. We are reluctant to reopen the tickets to fix this, they probably were closed trusting the cron wasn't a problem to setup (I know at some sites this was not the case, but many could do it). Can I ask you to please check that you have setup the cron jobs? You can check your active end points in atlas using this command (*) cl=<your-cloud> headnode=<your-headnode> curl -s <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://atlas-agis-api.cern.ch/request/ddmendpoint/query/list/?json&state=ACTIVE&site_state=ACTIVE&cloud=$cl">"http://atlas-agis-api.cern.ch/request/ddmendpoint/query/list/?json&state=ACTIVE&site_state=ACTIVE&cloud=$cl"</a>| egrep '"se":|endpoint'|sed 's/New.*WebUI//g'| cut -f4 -d'"'|sed '/^$/d'|tac | paste -d' ' - - |sed 's/ //g'|egrep -iv 'dev|test|v6'|grep srm: |grep $site for example for my site aforti@vm7>cl=UK aforti@vm7>headnode=bohr3226.tier2 aforti@vm7>curl -s <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://atlas-agis-api.cern.ch/request/ddmendpoint/query/list/?json&state=ACTIVE&site_state=ACTIVE&cloud=$cl">"http://atlas-agis-api.cern.ch/request/ddmendpoint/query/list/?json&state=ACTIVE&site_state=ACTIVE&cloud=$cl"</a>| egrep '"se":|endpoint'|sed 's/New.*WebUI//g'| cut -f4 -d'"'|sed '/^$/d'|tac | paste -d' ' - - |sed 's/ //g'|grep srm:|grep $headnode srm://bohr3226.tier2.hep.manchester.ac.uk:8446/srm/managerv2?SFN=/dpm/tier2.hep.manchester.ac.uk/home/atlas/atlasscratchdisk/ srm://bohr3226.tier2.hep.manchester.ac.uk:8446/srm/managerv2?SFN=/dpm/tier2.hep.manchester.ac.uk/home/atlas/atlaslocalgroupdisk/ srm://bohr3226.tier2.hep.manchester.ac.uk:8446/srm/managerv2?SFN=/dpm/tier2.hep.manchester.ac.uk/home/atlas/atlasdatadisk/ please check that under each end point you have the directory dumps and that you have a working cron job to produce the dumps (best at the end of the month on a day likely to appear on each month between the 25th and the 28th is all fine. thanks for your cooperation cheers alessandra (*) unfortunately this doesn't work very well for all the sites in the US cloud because there are some more unpredictable entries though it is still possible to recompose the end point. PS Cloud squads could you help checking your sites too. If you don't grep for the head node all the cloud end points should appear. Thanks a lot <pre class="moz-signature" cols="72">-- Respect is a rational process. \\// Fatti non foste a viver come bruti (Dante) </pre> </div> </body> </html>