Week of 200629

WLCG Operations Call details

• At CERN the meeting room is 513-R-068.

• 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

• Best practices for scheduled downtimes

Monday

Attendance:

• local:
• remote: Andrew (Nikhef), Andrew (TRIUMF), Borja (Chair, Monitoring), Brian (RAL), Dave (FNAL), Gavin (Computing), Ivan (ATLAS), Jens (NDGF), Maarten (ALICE), Pepe (PIC), Vladimir (LHCb), Xavier (KIT), Xin (BNL)

Experiments round table:

• ATLAS reports ( raw view) -
  • Storage / Oracle / DBoD intervention:
    • We recovered well over the DB outage.
    • It would be nice to avoid interventions on the weekend.
  • CTA migration: goes online today

• CMS reports ( raw view) -
  • CW is on vacation this week
  • Various users had issues with creating VOMS proxies during the weekend
    • Time window in good correlation with Oracle maintenance
    • Gavin: OTG:0057349 (announced last week in this meeting)
    • We wonder about DB dependencies for VOMS, DBoD or Oracle or both?
    • Gavin: Dependency on both MySQL for its primary database and on Oracle-based CERN HR Foundation database
  • Otherwise no major trouble

• ALICE -
  • NTR

• LHCb reports ( raw view) -
  • Activity:
    • Usual MC, user and WG production.
  • Issues:
    • PIC: DATA transfer problem GGUS:147655

Sites / Services round table:

• ASGC: NC
• BNL: NTR
• CNAF: NTR
• EGI: NC
• FNAL: NTR
• IN2P3: NTR
• JINR: NTR
• KISTI: NTR
• KIT: NTR
• NDGF: NTR
• NL-T1: A failed certificate update on the Nikhef CEs stopped job submission to Nikhef for part of the weekend, now resolved.
• NRC-KI: NC
• OSG: BC
• PIC: We have a network degradation, since the main fiber was cut and it's being repaired. Traffic goes through secondary line, low bandwidth, which has created saturation. Sorry for the inconveniences, we hope this will be solved during the afternoon.
• RAL: Power Cut 22/06/2020 took down Tier 1 ( and Tier 2). Blown PDUs have been replaced and site back up 24/06/2020. (Full compute Capacity took some time to recover.) RALOPN connection was intervened on ("Low Light on Fibre")
• TRIUMF: NTR

• CERN computing services: NTR
• CERN storage services: NC
• CERN databases: NC
• GGUS: NTR
• Monitoring:
  • Final reports for the May 2020 availability sent around
• MW Officer:
  • CERN Grid CA OCSP service incident June 24-25 (OTG:0057432)
    • After a scheduled intervention, the OCSP service became inaccessible from outside CERN
    • CERN Grid CA certificates were thus refused by CREAM CE instances at tens of sites
      • It appears other CE flavors rely on CRLs only and just ignore OCSP services
    • This affected the 4 experiments and, through the SAM tests, those sites
      • Some A/R recomputations may be needed
• Networks: NTR
• Security: NTR

AOB: