80 likes | 96 Views
GGUS summary (3 weeks). To calculate the totals for this slide and copy/paste the usual graph please: Take the summary from the table on https://gus.fzk.de/download/wlcg_metrics/html/20110509_escalationreport_wlcg.html 2. Add them in
E N D
GGUS summary (3 weeks) • To calculate the totals for this slide and copy/paste the usual graph please: • Take the summary from the table on • https://gus.fzk.de/download/wlcg_metrics/html/20110509_escalationreport_wlcg.html • 2. Add them in • https://twiki.cern.ch/twiki/pub/LCG/WLCGOperationsMeetings/ggus-tickets.xls • 3. Add up the last 3 weeks i.e. 25-Apr + 2-May + 9-May and put them in this table. • 4. Copy/paste the graph from the .xls file of point 2 above. • 5. In case of trouble email maria.dimou but you’ll have to wait until Monday evening • as I am on official training without computer access. 1
Support-related events since last MB There were 6 real ALARM tickets since the 2011/04/19 MB (3 weeks), 5 submitted by ATLAS, 1 by CMS, all ‘solved’ and ‘verified’. Notified sites were: CERN IN2P3 NDGF FZK Details follow… WLCG MB Report WLCG Service Report
ATLAS ALARM->CERN CASTOR no read or write possible on T0merge GGUS:69954 WLCG MB Report WLCG Service Report
ATLAS ALARM->CERN CASTOR no read or write possible on T0merge GGUS:69992 WLCG MB Report WLCG Service Report
ATLAS ALARM-> IN2P3 gridftp GGUS:70113 1/5/2020 WLCG MB Report WLCG Service Report 5
ATLAS ALARM -> srmNDGF from/to failures GGUS:70157 1/5/2020 WLCG MB Report WLCG Service Report 6
CMS ALARM -> CERN CMSR DB hung GGUS:70114 1/5/2020 WLCG MB Report WLCG Service Report 7
ATLAS ALARM -> Transfer errors from/to FZK GGUS:70119 1/5/2020 WLCG MB Report WLCG Service Report 8