Week of 160425

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 until 15:20, exceptionally to 15:30.
  • The SCOD rota for the next few weeks is at ScodRota
  • General information about the WLCG Service can be accessed from the Operations Web
  • Whenever a particular topic needs to be discussed at the daily meeting requiring information from site or experiments, it is highly recommended to announce it by email to wlcg-operations@cernSPAMNOTNOSPAMPLEASE.ch to make sure that the relevant parties have the time to collect the required information or invite the right people at the meeting.

Tier-1 downtimes

Experiments may experience problems if two or more of their Tier-1 sites are inaccessible at the same time. Therefore Tier-1 sites should do their best to avoid scheduling a downtime classified as "outage" in a time slot overlapping with an "outage" downtime already declared by another Tier-1 site supporting the same VO(s). The following procedure is recommended:
  1. A Tier-1 should check the downtimes calendar to see if another Tier-1 has already an "outage" downtime in the desired time slot.
  2. If there is a conflict, another time slot should be chosen.
  3. In case stronger constraints cannot allow to choose another time slot, the Tier-1 will point out the existence of the conflict to the SCOD mailing list and at the next WLCG operations call, to discuss it with the representatives of the experiments involved and the other Tier-1.

As an additional precaution, the SCOD will check the downtimes calendar for Tier-1 "outage" downtime conflicts at least once during his/her shift, for the current and the following two weeks; in case a conflict is found, it will be discussed at the next operations call, or offline if at least one relevant experiment or site contact is absent.

Links to Tier-1 downtimes




  • local: Xavier(SCOD+Storage), Maarten (ALICE), Oliver (CMS), Michal (ATLAS), Marian (Networking and transfer metrics), Julia Andreeva, Maria Alandes, Marcelo (LHCb), Andrea Manzi (Middleware office), Laurence (Computing and batch services)
  • remote: Michael (BNL), Kyle (OSG), Christian (NDGF), Di Qing (TRIUMF), Dmitri (KIT), Rolf(IN2P3), Onno (NL-T1), Sang Un (KISTI), Tiju (RAL)

Experiments round table:

  • ATLAS reports (raw view) -
    • Activities:
      • MC15c, derivation production, and Heavy Ion reprocessing ongoing
      • re-validation of T0 spillover mechanism
    • Problems:
      • Wigner connection problem cause no major service disruption
      • T1 DATADISKs getting full - BNL, FZK, NIKHEF - data rebalanced
      • FZK-LCG2 tape backend server broken (ELOG:57170,GGUS:121013) - transfers from tape fail with "Too many queued requests"
      • BNL-SARA transfers are slow (GGUS:120957) - comments during the meeting:
        • Michael Ernst: found packet losses on the BNL-SARA path.
        • Marian: BNL to CERN also shows constant packet losses constantly - ticket opened with OPN. Also commented that perfSonar not working at SARA.
        • Sang-Un: Ongoing ticket with SURFnet affecting KISTI network link. SURFnet is going to replace faulty optical amplifier card which is currently yielding errors.

  • CMS reports (raw view) -
    • Data taking started over the weekend, currently recording data with magnet off, magnet expected to be on after scrubbing this week
    • Production activities at high scales
    • Problems to report
      • (Tuesday, April 19): Network problem at Wigner caused Frontier not being able to connect to Oracle databases (cms_orcon_adg_wig), solved quickly (INC:1007831)

  • ALICE -
    • NTR

  • LHCb reports (raw view) -
    • Acitvity
      • Reco16 validation production on Full stream first data launched
    • Site Issues
      • T0:
      • T1:
        • SARA transfer problems (GGUS:121005) fixed - Onno: please let us know if you need more info.
        • GRIDKA SRM problem (GGUS:120968) and observed very low staging throughput - Dmitri mentioned forthcoming downtime for LHCb (details below)

Sites / Services round table:

  • ASGC:
  • BNL: ntr
  • CNAF:
  • FNAL:
  • GridPP:
  • IN2P3: ntr
  • JINR:
  • KISTI: ntr
  • KIT:
    • Our tape system will be down for scheduled maintenance on 26th and 27th. The core management service will be migrated onto new hardware. A downtime as been created in GOCDB.
  • NDGF: ntr
  • NL-T1: ntr
  • NRC-KI:
  • OSG: ntr
  • PIC: ntr - received apologies from Pepe
  • RAL: ntr
  • TRIUMF:ntr

  • CERN computing services:
    • ce503 needs to be replaced due to network problem by condorce01 ITSSB
    • ETF framework entered production phase for CMS, LHCb and ALICE (ATLAS on hold for the moment)
  • CERN storage services: data coming again smile
  • Network and transfer metrics:
    • perfSonar show ASGC connectivity not reaching 10Gbps, investigations ongoing.
  • CERN databases:
  • GGUS:
  • MW Officer:ntr
  • Security:


  • Operations coordination meeting THIS week on Thursday at 15h30'
Edit | Attach | Watch | Print version | History: r14 < r13 < r12 < r11 < r10 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r14 - 2016-04-26 - MaartenLitmaath
    • 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