RAL Tier1 Operations Report for 3rd July 2019
Review of Issues during the week 26th June 2019 to the 3rd July 2019.
|
- Frontier Service went down over weekend. Tier-1’s interpretation is that ATLAS were probably doing “something silly” with their US HPCs. The Production Manager to find out when the disk replacement for the Oracle database took place and if it went smoothly.
- CMS job failures: In the last two weeks several periods of CMS SRM failures. Investigation on going: Hammer Cloud jobs have been 25% failure rate recently. New monitoring doesn’t allow us to split HC work from normal production. HC failures could be due to problems accessing data at other sites (e.g. not our fault), or could be a problem at RAL.
45% job failure rate at RAL for production work. Significantly higher than other Tier-1s, not just log collect, many normal production jobs. Error code is related to file reads. Echo caching?!
Current operational status and issues
|
Notable Changes made since the last meeting.
|
Entries in GOC DB starting since the last report.
|
Service
|
ID
|
Scheduled?
|
Outage/At Risk
|
Start
|
End
|
Duration
|
Reason
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
Service
|
ID
|
Scheduled?
|
Outage/At Risk
|
Start
|
End
|
Duration
|
Reason
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
Advanced warning for other interventions
|
The following items are being discussed and are still to be formally scheduled and announced.
|
Listing by category:
- DNS servers will be rolled out within the Tier1 network.
GGUS Tickets Closed Last week
|
Key: Atlas HC = Atlas HammerCloud (Queue RAL-LCG2_UCORE, Template 841); CMS HC = CMS HammerCloud
|