Week of 160201

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


Monday - canceled

  • Note: Mon-Wed this week the WLCG Workshop is being held in Lisbon.
  • The next ops meeting will be held on Thursday this week!


  • local:
  • remote:

Experiments round table:

  • ALICE -

Sites / Services round table:

  • CERN batch and grid services:
  • CERN storage services:
  • Databases:
  • GGUS:
  • Grid Monitoring:
  • MW Officer:




  • local: Shao Ting Cheng (ASGC), Oliver Gutsche (CMS), Xavier (SCOD+IT/ST), Emil (IT-DB), Andrea (IT-ST)
  • remote: Michael (BNL), Jens (NDGF), John (RAL), Rolf (IN2P3), Elizabeth (OSG), Andrew (Nikhef). Matteo (CNAF), Dario (ATLAS), Vladimir (LHCb), Scott (OSG), David (FNAL)

Experiments round table:

  • ATLAS reports (raw view) -
    • CREAM-CE problems still not understood. Followed in GGUS-119258. No news since yesterday but production seems to have restarted in earnest everywhere. Reprocessing ongoing.

  • CMS reports (raw view) -
    • The glideInWMS factories (both CERN and FNAL) cannot create any new VM in the 'CMS Tier 0 on AI' project (all we get is a timeout in the factory logs). All the old VM expired already, so we currently have no resources in the Tier0. We urgently need a solution for the problem. GGUS:119312
    • lsf-rdd monitoring pages (like http://lsf-rrd.cern.ch/lrf-lsf/info.php?queue=cmscaf1nh) became restricted to CERN onsite access
      • change seemed to have fallen through the cracks, CMS had agreement before to keep these pages accessible from offsite for monitoring
      • working with experts to remedy restriction
    • physical machine emergency requests
      • CMS is running services on physical machines, cases have been discussed with cloud team and no virtual solution could be found
      • no request form for physical machines, especially for expedited cases in emergency situation
      • currently have to use virtual machine request form, mark in comment as physical machine, then the case is being discussed -> longer latency
    • to all sites:
      • As announced, the CMS xrootd SAM test will become mandatory (error instead of warning in case of failure) for all sites next Monday, Feb 8th

  • ALICE -
    • NTR

  • LHCb reports (raw view) -
    • Data Processing
      • Stripping 24 started
      • MC and User jobs
    • Main issue
      • Problem with using md5 in proxy. (GGUS:119294) + SARA; Fixed at sites side and creating new proxy without md5 for LHCb production jobs
    • Site Issues
      • T0:
        • CERN EOS issue (GGUS:119233) Fixed; we have backlog of files in Failover SEs
      • T1:

Sites / Services round table:

  • ASGC: New year break from 6/02 to 14/02, support in best effort.
  • BNL: ntr
  • CNAF: Downtime errata corrige: we announced a downtime on 18/Feb but we just inserted a WARNING on the GOCDB because all the services will be online during the intervention: https://goc.egi.eu/portal/index.php?Page_Type=Downtime&id=19761 (2) We are going to dismount afs (old software area) from all the wns. This should not impact on the LHC activities.
  • FNAL: ntr
  • GridPP:
  • IN2P3: Ntr
  • JINR:
  • KISTI:
  • KIT:
  • NDGF: ntr
  • NL-T1: Upgraded dcache on Tuesday. Impacted by java issues md5 hash fixed (see ), besides this running normally.
  • NRC-KI:
  • OSG: ntr
  • PIC:
  • RAL: Bad tape may cause up to 5k ATLAS files to be lost (to be confirmed)

  • CERN batch and grid services: network Intervention next Wed from 10:00 to 13:00, 2 FTS nodes will be drained cause they are going to be disconnected from the network. This is going to be transparent to users.
  • CERN storage services: nothing to add besides the issue of the java impacting MD5 certificates.
  • Databases: Alice online patched yesterday afternoon (OS patch). CMS DB intervention scheduled for next week postponed: offline and active dataguard for CMS online DB. Interventions next week: firewall deployment on CMS offline DB scheduled for Monday (should be transparent) - possibly some site missing as a side effect. Warning for next week on Tuesday as there are interventions planned on the storage backend that hold most of production databases including WLCG prod and experiment DBs: Atlas, LHCb, and alice and dataguard and also CASTOR databases.
  • GGUS:
  • Grid Monitoring:
  • MW Officer:
    • update on the broadcast sent to the sites Tue and Wed: the latest version of OpenJDK 1.6/1.7/1.8 on all platforms disables by default MD5 signed certificates/proxies. This is causing issues to LHCb ( the certificate used for FTS transfer and available on myproxy was still MD5 signed..it has been updated so at least FTS transfers are fine) but also to CMS, ( SAM and Phedex transfers are affected). The issue is still under investigation, but in the meantime we suggest not to upgrade Java based grid services to the latest openjdk or upgrade and enable again MD5 as explained in the mails we have circulated.


Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r9 - 2016-02-04 - 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