Week of 190624

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
  • General information about the WLCG Service can be accessed from the Operations Portal
  • 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



  • local: Miro (Chair, DB), Vladimir (LHCb), Claire (ATLAS), Petr (ATLAS), Gavin (Compute), Vincent (Security), Maarten (ALICE), Borja (Monitoring), Belinda (Storage), Giuseppe (Storage)
  • remote: Onno (NL-T1), Sang-Un (KISTI), Di (TRIUMF), Darren (RAL), Brian (RAL), Christian (NDGF), Marcelo (INFN), David (IN2P3)

Experiments round table:

  • ALICE -
    • NTR

  • LHCb reports ( raw view) -
    • Activity:
      • MC, user jobs and re-stripping of 2018 data.
    • Issues:

Sites / Services round table:

  • ASGC: Scheduled downtime for DPM upgrade from 1.10 to 1.12 DOME. The downtime is scheduled from 01:00 1/7/2019 to 19:00 2/7/2019 in UTC. In principle, day 2( 2/7 ) is for spare, just in case things go south. The downtime is already set in GOCDB.
  • BNL: changed dCache configuration to add more tape read pools, 4~5 GB/s tape staging throughput observed in recent ATLAS data carousel test.
  • CNAF:
    • Storm frontend incident last Wednesday 19th affected all VOs. Storm was blocked during the night, automatic system did not restarted the services.
    • GGUS:141879 CreamCE red - Under investigation
  • EGI: NC
  • IN2P3: NTR
  • JINR: Loss of power in the computer center 18-19.06, caused grid services to get down. All is restored on 19.06 in the evening.
  • KIT: NTR
  • NDGF: Preprod system upgraded to dCache 5.2.0, had issues, downgraded to 5.1.4. That release has issues with frontends behind haproxy. Production kept on 5.1.2.
  • NL-T1:
    • After last week's dCache downtime we had network problems in two racks. Reboot of two network switches fixed it. It may have been caused by NIC firmware updates in combination with a certain switch software level (GGUS:141783)
  • NRC-KI: NC
  • OSG: NC
  • PIC: NC
  • RAL: NTR

  • CERN computing services:
  • CERN storage services:
    • Early warning about a non-transparent intervention in CASTOR ( OTG0051004): the service will be unavailable on July 18th, 2019, likely for the entire day.
  • CERN databases: CASTOR backend database update planned for July 18th.
  • Monitoring:
    • Final availability reports for May 2019 sent around
  • MW Officer: NTR
  • Networks: NTR
  • Security: NTR


Edit | Attach | Watch | Print version | History: r21 < r20 < r19 < r18 < r17 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r21 - 2019-06-24 - 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