Week of 190603

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
• 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

• Best practices for scheduled downtimes

Monday

Attendance:

• local: Borja (Chair, Monitoring), Julia (WLCG), Roberto (Storage)
• remote: Darren (RAL), Dave (FLAB), David C (ATLAS), Di (TRIUMF), Gavin (Computing), Konrad (LHCb), Marcelo (CNAF), Sang-Un (KISTI), Xavier (KIT), Xin (BNL)

Experiments round table:

• ATLAS reports ( raw view) -
  • Smooth running at 400k cores including 100k from HLT farm
  • VOMS server overloading issue: INC:1993132

David reported ticket has been unattended for a while, double checking it seems it's in "waiting for user" so ATLAS should drop a line there.

• CMS reports ( raw view) -
  • Likely nobody available from CMS today
  • CPU utilisation still lower than usual, since HLT farm is still off
  • Opened a number of (less urgent) GGUS tickets to ask sites to register Squids
  • No major issues

• ALICE -
  • NTR

• LHCb reports ( raw view) -
  • Smooth running at ~100K jobs, Usual activity
    • User jobs, MC productions, and WG productions this week
  • Issues
    • RAL:
      • Timeouts when accessing job input data (GGUS:141462)
      • Auth failures for accessing files by user jobs (GGUS:141262)
    • CERN:
      • Poor transfer efficiency from CERN WN to outside storage GGUS:141112

Sites / Services round table:

• ASGC:
• BNL: On Saturday 06/01, campus wide DNS issue affected T1 facility services, resulting in failed jobs and transfers, computing farms drained for 4~8 hours. Fixed at ~6PM UTC on the same day.
• CNAF: Electrical Intervention next monday (June 10th). It should be transparent.
• EGI:
• FNAL:
• IN2P3: Site in scheduled downtime tomorrow : CEs and SEs will be off for the morning.
• JINR: NTR
• KISTI:
• KIT: Losing availability for LHCb, because their SAM test jobs fail on SL7 WNs. Following the recommendation of our site contact, we filed a GGUS ticket on the subject: GGUS:141561.
• NDGF: Doing lots of dcache pool updates today, unable to attend the meeting. This will complete the dCache 5.1.1 upgrade.
• NL-T1:
• NRC-KI:
• OSG:
• PIC:
• RAL: NTR
• TRIUMF: NTR

• CERN computing services:
• CERN storage services:
  • EOSLHCB Overloaded since today ~13:53 with high rate of writes. We applied a write rate limit to protect the instance (OTG:0050681). We are still investigating.
• CERN databases:
• GGUS: NTR
• Monitoring:
  • Draft availability reports for May 2019 sent around
  • ATLAS ssb collector stuck, some data gaps in the plots
• MW Officer:
• Networks: NTR
• Security: NTR

AOB:

• NOTE: the operations meeting next Mon will be virtual .
• You may provide relevant incidents, announcements etc. for the operations record.