(r6) WLCGDailyMeetingsWeek160829 < LCG

LCG Web>WLCGCommonComputingReadinessChallenges>WLCGOperationsMeetings>WLCGDailyMeetingsWeek160829 (revision 6) (raw view)~~EditAttachPDF~~
---+!! Week of 160829

%TOC%

---++ WLCG Operations Call details

   * At CERN the meeting room is [[https://maps.cern.ch/mapsearch/?centerX=2492565&centerY=1121070&centerScale=2500][513]] R-068.

   * For remote participation we use the Vidyo system. Instructions can be found [[https://indico.cern.ch/conferenceDisplay.py?confId=287280][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 [[https://wlcg-ops.web.cern.ch/][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@cernSPAMNOT.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.
   1. If there is a conflict, another time slot should be chosen.
   1. 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

%INCLUDE{ "WLCGDowntimesTemplate" }%

---++ Monday

Attendance:
   * local:
   * remote:

Experiments round table:

   * ATLAS [[https://twiki.cern.ch/twiki/bin/view/AtlasComputing/ADCOperationsWeeklySummaries2016][reports]] ([[https://twiki.cern.ch/twiki/bin/view/AtlasComputing/ADCOperationsWeeklySummaries2016?raw=on][raw view]]) -
      * Activities:
         * normal running - grid is full
      * Problems:
         * RRC-KI-T1 finished the downtime - some files seemed to be unavailable (GGUS:123587) - files declared lost 
 

   * CMS [[https://twiki.cern.ch/twiki/bin/view/CMS/FacOps_WLCGdailyreports][reports]] ([[https://twiki.cern.ch/twiki/bin/view/CMS/FacOps_WLCGdailyreports?raw=on][raw view]]) -

Accesses and dumps.. then back since weekend to stable beams with 2220x2220 BCMS. Expected beam dump by LHC at 15:00 today.

   * CASTORCMS intervention* (Aug-24): version upgrade for CASTOR{ALICE,CMS}. 
      * https://cern.service-now.com/service-portal/view-outage.do?n=OTG0032396
      * Scheduled 10:00-12:00, ended at 12:30. CMS may have suffered from the restart of xroot daemons, no problems reported though.

   * Reduced link capacity to Wigner* (Aug-26): One of the two 100Gbit links connecting Geneva to the WIGNER datacenter went down on Aug-26 at ~11am due to a fibre cut.
      * https://cern.service-now.com/service-portal/view-outage.do?from=CSP-Service-Status-Board&n=OTG0032611
      * Operator localized the fault, reported to be resolved on Aug 26, at 17:40.
      * Still on Saturday at noon, experiments’ network is at 83% on Kibana critical services monitoring: related?

   * SAM tests outage* (Aug-25):
      * solved after a Condor restart, so the "real" SAM tests (=prod) are OK since Aug-25 at 5pm CERN time (not in preprod though)

   * CMS critical services, lxbatch* (Aug-23): service unavailable for >1h
      * ELOG + service-now ticket submitted. OK after some hrs.

   * Queuing data traffic from T1_US_FNAL to PIC and JINR* (Aug-23) -> GGUS:123559 (solved already)
      * persisted over several shifts. Debugged to be related to O(15) files on a problematic disk at the source site. Now OK.

   * Condor submit errors at T1_RU_JINR* (Aug-27/28) -> GGUS:123608
      * seen as SAM3 CE errors, ELOG opened, then GGUS (solved with no explanation - to be checked)

   * !PhEDEx agents down at T1_RU_JINR* (Aug-28) -> GGUS:123614
      * root cause: loss of network connection to Moscow. 
      * not sure if we got the corresponding unscheduled downtime correctly, as it did not appear at the time of ticketing in either the CMS Site Downtime Calendar or in the SSB. To be checked.

   * ALICE -
      * NTR

   * LHCb [[https://twiki.cern.ch/twiki/bin/view/LHCb/ProductionOperationsWLCGdailyReports][reports]] ([[https://twiki.cern.ch/twiki/bin/view/LHCb/ProductionOperationsWLCGdailyReports?raw=on][raw view]]) -
      * Activity
         * Monte Carlo simulation, data reconstruction and user jobs on the Grid
      
      * Site Issues
         * T0: 
            * NTR
         * T1:
            * Pilots aborted at RRC-KI (GGUS:123599)

Sites / Services round table:

   * ASGC:
   * BNL:
   * CNAF:
   * EGI:
   * FNAL:
   * !GridPP:
   * !IN2P3:
   * JINR:
   * KISTI:
   * KIT:
   * NDGF:
   * NL-T1:
   * NRC-KI:
   * OSG:
   * PIC:
   * !RAL: !RAL Closed today and tomorrow (29/30 August)
   * TRIUMF:

   * CERN computing services:
      * [[https://cern.service-now.com/service-portal/view-outage.do?from=CSP-Service-Status-Board&n=OTG0032525][LCG router reboot]] on Thursday 1 September between 10.00 and 11.00 .. two ~7 minute outages. A GOCDB downtime (will be) declared. Will affect:
         * VOMS service
         * LXbatch - some nodes will lose connectivity. 
         * CEs ce403, ce404, ce406, ce407 and cesatltzero1.
         * Some VMs will also lose connectivity during this period (you will have been mailed details from network team).
   * CERN storage services:
   * CERN databases:
   * GGUS:
   * Monitoring:
   * MW Officer:
   * Networks:
   * Security:

AOB:
Topic revision: r6 - 2016-08-29 - GavinMcCance
LCG Wikis
LCG Service
Coordination
LCG Grid
Deployment
LCG
Apps Area
Public webs
Welcome Guest
- Cern Search
- TWiki Search
- Google Search
LCG All webs
Copyright &© 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