Week of 160314

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

ALICE ATLAS CMS LHCB
  BNL FNAL  

Monday

Attendance:

  • local: Maria Alandes (chair and minutes), Julia Andreeva (WLCG), Mark Slater (LHCb), Xavier Espinal and Jesus Lopez (Storage), Ben Jones (Computing), Liana Lupsa (DB), Vincent Brillault (Security), Andrea Manzi (MW Officer), Maria Dimou (GGUS)
  • remote: Stefan Roiser (LHCb), Jose Hernandez (CMS), Dave Mason (FNAL), Rolf Rumler (IN2P3), Dimitri (KIT), Ulf Tigerstedt (NDGF), Onno Zweers (NL-T1), Elizabeth Prout (OSG), Jose Flix (pic), John Kelly (RAL), Di Qing (TRIUMF)

Experiments round table:

  • CMS reports (raw view) -
    • FTS transfer issue at several US sites. Using legacy proxies signed with MD5 by old glite-transfer client.
Maria asks whether the issue is related with FTS2 clients or MD5 legacy proxies. Andrea Manzi confirms this is related to MD5 proxies. Jose also reports about the SAM incident affecting CMS early morning. No problems seen after the reboot.

  • ALICE -
    • High activity on average
      • New record reached Thu morning: 99372 running jobs!
    • EOS out of memory this morning (OTG:0029311)
      • Led to many job failures around the grid for a few hours

Xavier explains that EOS namespace was restarted to fix the problem. This is all related to the high number of ALICE files. New HW is in the process of being installed, nodes will double memory and this should help improve the situation with ALICE.

  • LHCb reports (raw view) -
    • RAL: Two disk servers went down over the weekend but are now back up.

Maria explains that after a mail exchange with Stefan she learnt that the next day IN2P3, CERN and KIT will be all in downtime. She suggests to discuss offline how to avoid these situations in the future. Although CERN and IN2P3 announced their downtime several weeks before, KIT defined their downtime after the 3PM meeting last week, so it's difficult for WLCG to detect this type of things.

Sites / Services round table:

  • ASGC: NA
  • BNL: NA
  • CNAF: NA
  • FNAL: NTR. 2016 Pledges will be presented in Ops Coord meeting.
  • GridPP: NA
  • IN2P3:
    • 2016 Pledges will be presented in Ops Coord meeting.
    • On Wednesday, March 9th, for about 5 minutes around 11 o’clock we had an internal network problem impacting connections between our two machine rooms. About 500 jobs were lost because of that, many of them from LHC experiments. One dCache server had difficulties to recover from that which might have caused problems. The tickets we saw up to now didn’t seem to be related to this incident.
    • A reminder: tomorrow, March 15th, there will be a whole day downtime for many of our services. Important: one of the interventions is a change in the batch system version which requires to empty all batch queues when restarting in the afternoon. The batch system will start draining already late this evening. All downtimes have been declared.
  • JINR: NA
  • KISTI: NA
  • KIT:
    • 2016 Pledges will be presented in Ops Coord meeting.
    • Availability recalculation needed for ATLAS.
    • Downtime for the LHCb SE today and tomorrow in order to install storage extensions.
  • NDGF: NTR. 2016 Pledges will be presented in Ops Coord meeting.
  • NL-T1: NTR. Will check who can present pledges.
  • NRC-KI: NA
  • OSG: NTR
  • PIC: NTR. 2016 Pledges will be presented in Ops Coord meeting.
  • RAL: NTR. 2016 Pledges will be presented in Ops Coord meeting.
  • TRIUMF: NTR. 2016 Pledges will be presented in Ops Coord meeting.

  • CERN computing services:
    • SAM CMS instance became unresponsive today early morning (2016-03-14) and was rebooted at around 8:30am. Investigation is ongoing on what is causing the recent instabilities.
  • CERN storage services:
  • CERN databases:
    • ATLAS ATLR related TNS entities missing from central tnsnames.ora - incident - Some TNS entities maybe missing from central tnsnames.ora on AFS and DFS, experts are investigating the issue
    • Oracle GoldenGate replication services update - The Oracle GoldenGate Services hosts will be updates with the latest security patches. During this operation there might be a delay in the replication time.
  • GGUS: A new release scheduled next week. More news on Monday next week.
  • MW Officer:
    • The EMI software repository has been replaced by the EGI Preview repo (https://wiki.egi.eu/wiki/Preview_Repository). It will be updated monthly with software released by the PTs ( In particular it's the main source of distribution for software like Argus, VOMS and StoRM).
  • Security:
    • Advisory on NSS vulnerability broadcasted by EGI SVG (https://wiki.egi.eu/wiki/SVG:Advisory-SVG-CVE-2016-1950). All running resources MUST be either patched or software removed by 2016-03-22 00:00 UTC. Maria asks whether it is known which services rely on NSS. Andrea replies that it's not known, but at least FTS is.

AOB: (MariaD) Please remember the http://indico.cern.ch/e/MW-Readiness_16 MW Readiness WG meeting this Wed 16/3 at 4pm CET. Also, Ops Coord meeting this Thu 17/3 at 3:30pm CET.

Edit | Attach | Watch | Print version | History: r20 < r19 < r18 < r17 < r16 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r20 - 2016-03-15 - MariaALANDESPRADILLO
 
    • 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-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback