RAL Tier1 Operations Report for 16th November 2016
| Review of Issues during the week 9th to 16th November 2016.
|
- There was a problem with one of the Atlas Frontier launchpads on Monday 14th. All three such systems were updated to the newer release (3.5.22)
| Resolved Disk Server Issues
|
- GDSS713 (CMS Disk - D1T0) crashed on Sunday morning. It was returned to service the following day - initially read-only. Our checks did not find any fault on the server.
| Current operational status and issues
|
- There is a problem seen by LHCb of a low but persistent rate of failure when copying the results of batch jobs to Castor. There is also a further problem that sometimes occurs when these (failed) writes are attempted to storage at other sites.
- The intermittent, low-level, load-related packet loss that has been seen over external connections is still being tracked. The replacement of the UKLight router appears to have reduced this - but we are allowing more time to pass before drawing any conclusions.
| Ongoing Disk Server Issues
|
| Notable Changes made since the last meeting.
|
- There was a short (one to two hour) interruption to tape mounts while the system that runs the tape library control software was swapped on Tuesday morning (15th Nov).
- LHCb writing to the 'D' tapes. The migration of their data from 'C' to 'D' tapes is underway - with around 100 (some 10%) of the tapes done.
None
| Advanced warning for other interventions
|
| The following items are being discussed and are still to be formally scheduled and announced.
|
Listing by category:
- Castor:
- Merge AtlasScratchDisk and LhcbUser into larger disk pools
- Update to Castor version 2.1.15. Planning to roll out January 2017. (Proposed dates: 10th Jan: Nameserver; 17th Jan: First stager (LHCb); 24th Jan: Stager (Atlas); 26th Jan: Stager (GEN); 31st Jan: Final stager (CMS)).
- Update SRMs to new version, including updating to SL6. This will be done after the Castor 2.1.15 update.
- Fabric
- Firmware updates on older disk servers.
| Entries in GOC DB starting since the last report.
|
| Service
|
Scheduled?
|
Outage/At Risk
|
Start
|
End
|
Duration
|
Reason
|
| gridftp.echo.stfc.ac.uk, s3.echo.stfc.ac.uk, s3.echo.stfc.ac.uk, xrootd.echo.stfc.ac.uk
|
SCHEDULED
|
OUTAGE
|
16/11/2016 10:30
|
16/11/2016 14:30
|
4 hours
|
Upgrading backend network behind Echo Storage service
|
| Open GGUS Tickets (Snapshot during morning of meeting)
|
| GGUS ID |
Level |
Urgency |
State |
Creation |
Last Update |
VO |
Subject
|
| 124876
|
Green
|
Less Urgent
|
On Hold
|
2016-11-07
|
2016-11-15
|
OPS
|
[Rod Dashboard] Issue detected : hr.srce.GridFTP-Transfer-ops@gridftp.echo.stfc.ac.uk
|
| 124785
|
Red
|
Urgent
|
Reopened
|
2016-11-02
|
2016-11-09
|
CMS
|
Configuration updated AAA - CMS Site Name missing
|
| 124606
|
Yellow
|
Very Urgent
|
In Progress
|
2016-10-24
|
2016-11-01
|
CMS
|
Consistency Check for T1_UK_RAL
|
| 122827
|
Green
|
Less Urgent
|
Waiting for Reply
|
2016-07-12
|
2016-10-11
|
SNO+
|
Disk area at RAL
|
| 120350
|
Yellow
|
Less Urgent
|
In Progress
|
2016-03-22
|
2016-08-09
|
LSST
|
Enable LSST at RAL
|
| 117683
|
Red
|
Less Urgent
|
On Hold
|
2015-11-18
|
2016-10-05
|
|
CASTOR at RAL not publishing GLUE 2 (Updated. There are ongoing discussions with GLUE & WLCG)
|
Key: Atlas HC = Atlas HammerCloud (Queue ANALY_RAL_SL6, Template 808); CMS HC = CMS HammerCloud
| Day |
OPS |
Alice |
Atlas |
CMS |
LHCb |
Atlas HC |
CMS HC |
Comment
|
| 09/11/16 |
100 |
100 |
100 |
100 |
100 |
92 |
N/A |
|
| 10/11/16 |
100 |
100 |
100 |
100 |
100 |
100 |
100 |
|
| 11/11/16 |
100 |
100 |
100 |
100 |
100 |
100 |
N/A |
|
| 12/11/16 |
100 |
100 |
100 |
99 |
100 |
100 |
N/A |
Single SRM test failure: User timeout over
|
| 13/11/16 |
100 |
100 |
100 |
100 |
100 |
100 |
97 |
|
| 14/11/16 |
100 |
100 |
100 |
100 |
100 |
100 |
93 |
|
| 15/11/16 |
100 |
100 |
N/A |
100 |
100 |
100 |
100 |
(Atlas tests not reporting).
|
- There was a discussion about the Tier1's response to the CVE-2016-5195 security issue. In particular that the batch system stopped accepting new work until the patch was received and applied. Storage continued to be available.
- At present Durham is the only Dirac site from which we have received production data. Test data has been received from the Leicester site.
