GGUS summary (5 weeks) VOUserTeamAlarmTotal ALICE2002 ATLAS CMS6208 LHCb Totals
8/9/2015WLCG MB Report WLCG Service Report 2 Support-related events since last MB There were 3 real ALARM tickets since the 2010/12/07 MB (5 weeks), all submitted by ATLAS. GGUS:65533 contained a link to the generic URL of the ‘IT service status board’ which points to something else the next day. The persistent one should be used instead for ticket data integrity, i.e. support-servicestatus/IncidentArchive/ CCpowerCut.htmGGUS:65533 During the 2010/12/20 CERN CC Power Cut no notification or Remedy PRMS ticket creation was possible for more than 24 hrs. GGUS:65292 was a test ALARM by GGUS developer against KIT. Details follow…GGUS:65292
ATLAS ALARM->CERN LFC BAD VOMSCERT 8/9/2015WLCG MB Report WLCG Service Report 3 What time UTCWhat happened 2010/12/09 13:57GGUS ALARM ticket opened, automatic notification to AND automatic assignment to ROC_CERN. 2010/12/09 14:46Ticket dispatcher re-assigns the ticket into the CERN Remedy PRMS LFC category in the CERN local ticketing system (GGUS-PRMS transit is automatic). 2010/12/09 14:57Supporter on rota updates vomscert and sets ticket to ‘solved’ with copy to the service manager. 2010/12/09 15:16Submitter sets status ‘verified`
ATLAS ALARM->IN2P3 LFC SERVER DOWN 8/9/2015WLCG MB Report WLCG Service Report 4 What time UTCWhat happened 2010/12/12 02:28GGUS ALARM ticket opened, automatic notification to AND automatic assignment to NGI_France. 2010/12/14 09:01Site puts ticket to status ‘solved’ with description ‘DB connection problem now fixed’. 2010/12/19 12:45Submitter sets status ‘verified`
ATLAS ALARM->CERN CC POWER CUT 8/9/2015WLCG MB Report WLCG Service Report 5 What time UTCWhat happened 2010/12/18 12:26 SATURDAY GGUS ALARM ticket opened, automatic notification to AND automatic assignment to 2010/12/18 15:31Submitter provides additional information on ATLAS critical services needing quick recovery. 2010/12/19 04:39 SUNDAY Another member of the Authorised ALARMers submits info on unknown DATADISK locality. 2010/12/20 07:29Creation of the Remedy PRMS ticket. 2010/12/20 07:51Status set to ‘solved’ by the helpdesk pointing to ‘service status board’service status board 2010/12/20 08:05Submitter sets status to ‘verified’.