Week of 200928

WLCG Operations Call details

  • For remote participation we use the Vidyo system. Instructions can be found here.

General Information

  • The purpose of the meeting is:
    • to report significant operational issues (i.e. issues which can or did degrade experiment or site operations) which are ongoing or were resolved after the previous meeting;
    • to announce or schedule interventions at Tier-1 sites;
    • to inform about recent or upcoming changes in the experiment activities or systems having a visible impact on sites;
    • to provide important news about the middleware;
    • to communicate any other information considered interesting for WLCG operations.
  • The meeting should run from 15:00 Geneva time until 15:20, exceptionally to 15:30.
  • The SCOD rota for the next few weeks is at ScodRota
  • Whenever a particular topic needs to be discussed at the operations meeting requiring information from sites or experiments, it is highly recommended to announce it by email to wlcg-scod@cernSPAMNOTNOSPAMPLEASE.ch to allow the SCOD to make sure that the relevant parties have the time to collect the required information, or invite the right people at the meeting.

Best practices for scheduled downtimes



  • remote: Kate (chair, DB), Julia (WLCG), Maarten (WLCG, ALICE), Borja (monitoring), Eric (storage), Vincent (security), Christoph (CMS), Nils (computing), Darren (RAL), Ivan (ATLAS), Dave M (FNAL)

Experiments round table:

  • ATLAS reports ( raw view) -
    • VOMS issues
      • What is the testing procedure before upgrade?
    • Pilot upgrade problem - affecting the accounting.

VOMS Configuration Guidelines: VOMSLSCfileConfiguration Maarten mentioned during the meeting, that each site should have both VOMS servers configured. Ivan confirmed ATLAS will add it to its instructions.

Julia announced that the follow up of the VOMS issue will take place during the next WLCG Ops Coordination meeting.

Maarten has provided the following timeline to the VOMS issue: Testing was concentrated on the VOMS admin as clients were not expected to be affected. Next testing campaign will also include clients. Server broke its own library and caused older client versions to stop working. It was possible to fix the error on the server side. The first upgrade had to be rolled back due to this issue, it was re-done today but one end point was in the wrong state as discovered by ATLAS and this upgrade was also rolled back. The issue is now understood and was related to the endpoint not being properly restarted. The next upgrade date is to be announced, possibly Tuesday morning.

Christoph reported that CMS has experienced no major issues but some strange behaviour and will check if that behaviour corresponds to the VOMS incident timeline.

  • ALICE -
    • CERN: since ~00:00 the number of running jobs has been
      steadily decreasing to very low values (GGUS:148808)

Sites / Services round table:

  • ASGC: nc
  • BNL: nc
  • CNAF: Scheduled Downtime on October 1st from 07:30PM to 10:00PM CEST for an intervention to the border router, GOCDB Link
  • EGI: nc
  • IN2P3: NTR
  • PIC: nc
  • RAL: NTR

  • CERN computing services:
    • Scheduled downtime on two CEs to upgrade to CentOS7 OTG0059293. Note downtime also in GOCDB. CE will be unavailable throughout upgrade, but also will reject new jobs from Wednesday at 17:00 CET in order to be drained for the intervention.
  • CERN storage services:
  • CERN databases: NTR
  • GGUS:
    • A new release is planned for Wed this week
      • Release notes
      • A downtime has been scheduled for 07:00-09:00 UTC
      • Test alarms will be submitted as usual
  • Monitoring: NTR
  • MW Officer: nc
  • Networks: nc
  • Security: NTR


Edit | Attach | Watch | Print version | History: r21 < r20 < r19 < r18 < r17 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r21 - 2020-09-30 - NikolayVoytishin
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback